SaltyKram

supervisord.log Hi Binhex, I'm having an issue with warnings of timeout connections using ProtonVPN with Sabnzbvpn. It looks like the below: WARNING 4 minutes ago Failed to connect: [Errno 9] Bad file descriptor news.eweka.nl:563 (81.171.92.219) WARNING 4 minutes ago Failed to connect: [Errno 9] Bad file descriptor news.eweka.nl:563 (81.171.92.219) WARNING 4 minutes ago Failed to connect: timed out news.eweka.nl:563 (81.171.92.219) Although the above is Eweka, it appears to happen with connections to all of my other backup providers as well - it seems to depend on if it is actively being used/connected to. Sabnzb and my downloads appear to continue downloading even after this error shows up. Prior to using ProtonVPN, I have used Mullvad in this same container flawlessly. I am currently using ProtonVPN in your qBittorrent container also without issue. I have switched ports on the providers from 443 to 563, switched from Wireguard back to openvpn, added 8.8.8.8 to the name server - all result in the same error. The only thing that fixes these warnings is switching back to Mullvad, so it seems to be specific to ProtonVPN. My redacted debug log is attached. Any ideas on how I can make ProtonVPN work? Thanks!

Oops, I had it set up - I mistakenly assumed it would be pulled into the diagnostics zip. It is attached here in case you find something amiss. As I was writing out my original post, I started thinking more about how it would freeze when it seemed like the server was actively doing something, and possibly drawing more power as a result. Combined with the fact I never saw any error messages on the system logs, it seemed like it had to be power related. The server is hooked up to a Cyberpower UPS 1500PFCLCD. I tried unplugging it from the UPS and directly into the wall, and the system has been rock solid for the past 1 1/2 hours with all containers batch reinstalled and running. I'll keep an eye on it for the next few days, but it looks like an RMA is in my future! syslog-10.10.20.22.log.zip

nasa-diagnostics-20220207-1457.zip Hi, I have been having a lot of trouble keeping Unraid from freezing up and becoming unresponsive when I have any docker services running. Before the shutdown, the server was running for over 60 days without issue. After the shut down, I moved the server a few feet over as we were rearranging furniture. I don't believe anything was damaged during the move. Once I noticed the instability, I deleted my docker.img and began the process of reinstalling my programs. It would always freeze during a batch reinstall of my containers, so I began installing one by one. It seems like if the server is under less load, it would not freeze. Once everything was reinstalled and the containers running, after a while of being on the system would freeze up again. I again deleted my docker.img file and left the docker services off for a few hours, where it seemed to be running just fine. I have tried adding only a handful of containers, it seems like the freezing is not due to a specific container. I'm running 32GB of DDR3 ECC memory, but I couldn't find any warnings or errors related to memory issues. Anyone have any ideas? Diagnostics attached. Thank you!

Hiya, nasa-diagnostics-20210130-1354.zipsyslog-10.10.20.22.log I've got a weird thing with my Unraid Server developing where it seems to have a hard lock up for 2 nights in a row. Here's some info before I start: Unraid 6.8.3 The syslog-10.10.20.22.log that I attached is the log I had setup and running after the first crash, writing to the cache drive. This log captured only the second crash. The zip file is for any other information you need, like hard drive smart tests, etc. The last log written was Jan 30 00:22:59, before I did a reset on Jan 30 12:55:16. Plugins: CA Auto Turbo Write Mode - Not configured CA Auto Update Applications CA Backup / Restore Appdata CA Cleanup Appdata Community Applications Dynamix Active Streams Dynamix Cache Directories Dynamix Date Time Dynamic SSD Trim Dynamix System Information Dynamix System Statistics Dynamix System Temperature Fix Common Problems Nerd Tools Preclear Disks Speedtest Command Line Tool - Disabled Tips and Tweaks Unassigned Devices Unassigned Devices Plus unBALANCE User Scripts I'm not quite sure what is happening - I would be streaming a video via Plex fine the night before, and it seems like overnight the system locks up and stays that way until I reset the server. I cannot access the unraid webgui at all when this happens. After my second lockup, my first thought is maybe modify the scheduled updates which might be too close to each other and possibly conflicting, so after the reset earlier today I changed the schedule to the below: DOCKER AUTO UPDATE 6 AM DAILY PLUGIN AUTO UPDATE 9 AM DAILY MOVER SETTINGS 4 AM DAILY PARITY CHECK 1:30 AM FIRST DAY OF THE MONTH (It's currently running a parity check now) I have also removed any stopped/unused dockers, which in my case would be Emby and unmanic. I had PiHole configured at the router level but I have removed it and put another DNS provider for now, to prevent the issue of my other home devices not connecting to the network. Hope someone can see something on the logs provided that I can't. If I'm missing any information, please let me know and I will provide it. Thank you!