Scroopy Noopers

I am starting to see constant daemon crashes at this time. As per the screencap below, the daemon crashes and though I can either restart the container or the daemon through the web UI, it crashes again within a few minutes. Has anyone else run into this? As far as I can tell, nothing has changed recently.

Well it's definitely been more than 3 days at this time, but that seems to have fixed my issue. Thanks a bunch.

Ok, I'll give that a shot. I'll report back if it crashes again, or within the next 3 days if it doesn't. Thanks!

I actually had that turned on in the event of another kernel panic. Here it is; you can see the start of the event at line 69923. syslog

Hello everyone, I've been getting kernel panics every few days now for probably the past month and I'm really not sure what could be causing it. I've moved my installation from my R510 to my R620, swapped out thumb drives, and so far it hasn't been resolved. For reference my machine has the following specs: 2 x E5-2650L V2 8 x 8 GB DDR3 ECC Quadro P1000 LSI 9200-8e I've attached my diags if anyone is willing to look through my system here and offer some kind of insight. If there's anything else you need to make diagnosing this issue simpler, please let me know. dellr620-diagnostics-20211118-2221.zip

So, after casually cruising through Radarr and Sonarr, and seeing that, like with my web browser I have no access to deluge, I did what any other good troubleshooter does who has no idea what to do next. I started clicking buttons while saying to myself "Screw it. What's the worst thing that could happen?". Fortunately, that led me to the "Use SSL" switch in Radarr and I clicked it, hit test and waited to see what would happen. It connected! Well, I thought, this must mean that I should be trying to access deluge through my web browser with an https prefix, so I tried it. Lo and behold, it worked! So, all of the prior complaints I put forth was for nought. I just had to do a little thinking with my noggin. Thank you for reading my excessively long TIFU. I hope you got a low chuckle out of it. TL;DR: must have hit the SSL switch in deluge when I wasn't paying attention. Took me two weeks to figure it out and felt supremely dumb when I did.

That's what I'm seeing too. I have no idea where to go from here.

It's set to bridge.

It sure is

Hey guys, I'm still not sure what I'm missing. I have no LAN access to the web GUI client, though it seems to me that everything is working correctly.

My mistake. Here it is. supervisord.log

Hey guys, I'm seriously loving this software, but after rebooting my machine this morning, I began to have issues. Right now I'm unable to access the web GUI and both Sonarr and Radarr aren't connecting either. Here is a portion of my log: 2020-11-13 15:33:25,644 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2020-11-13 15:33:25,986 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2020-11-13 15:33:30,436 DEBG 'watchdog-script' stdout output: Setting "random_port" to: False Configuration value successfully updated. 2020-11-13 15:33:35,235 DEBG 'watchdog-script' stdout output: Setting "listen_ports" to: (32560, 32560) Configuration value successfully updated. 2020-11-13 15:33:40,132 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2020-11-13 15:33:40,132 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started I'm hoping someone has encountered this before and I've just simply overlooked something.