realdiel

Doh! Ok. I may do the switch then if I can't figure out what's going on here.

Starting a new post since I haven't seen a response to my initial post from December 1st. Still dead in the water with torrenting. Looking at moving to another torrent client or going with a torrenting VPN service to offload this from my environment altogether. After years of use, I can't pull up the web UI for Deluge ("This site can’t be reached" initiating this from within the UNRAID GUI under the Docker page for this docker; IP and port are the same as before when it worked) and it appears to not be seeding (have HNR with my trackers). I've attempted to restore it as before, but still can't get this docker to work. Here's the log below. Any suggestions? Hoping this is a quick fix as moving to another torrent client or offloading this to a VPN torrent service is looking like a PITA to me. I'd rather stay the course if possible. 🤞 ***************************************************************************** [info] Writing changes to Deluge config file '/config/web.conf'... 2024-01-01 11:33:40,056 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2024-01-02 04:00:03,291 WARN received SIGTERM indicating exit request 2024-01-02 04:00:03,292 DEBG killing watchdog-script (pid 73) with signal SIGTERM 2024-01-02 04:00:03,293 INFO waiting for watchdog-script to die 2024-01-02 04:00:03,295 DEBG 'watchdog-script' stderr output: Terminated 2024-01-02 04:00:03,296 DEBG 'watchdog-script' stdout output: [info] Waiting for child processes to exit... [info] All child processes exited, exiting while loop... [info] All child processes exited, exiting 'watchdog.sh' script... 2024-01-02 04:00:03,297 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23181582822672 for <Subprocess at 23181582976912 with name watchdog-script in state STOPPING> (stdout)> 2024-01-02 04:00:03,297 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23181580600976 for <Subprocess at 23181582976912 with name watchdog-script in state STOPPING> (stderr)> 2024-01-02 04:00:03,298 INFO stopped: watchdog-script (exit status 0) 2024-01-02 04:00:03,298 DEBG received SIGCHLD indicating a child quit Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-01-02 04:00:10.758877 [info] Host is running unRAID 2024-01-02 04:00:10.778928 [info] System information Linux 5bce46582aa0 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 GNU/Linux 2024-01-02 04:00:10.806147 [info] PUID defined as '0' 2024-01-02 04:00:10.852687 [info] PGID defined as '0' 2024-01-02 04:00:10.952580 [info] UMASK defined as '000' 2024-01-02 04:00:10.977080 [info] Permissions already set for '/config' 2024-01-02 04:00:11.004748 [info] Deleting files in /tmp (non recursive)... 2024-01-02 04:00:11.038421 [info] VPN_ENABLED defined as 'no' 2024-01-02 04:00:11.060972 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE 2024-01-02 04:00:11.084717 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2024-01-02 04:00:11.107469 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2024-01-02 04:00:11.131829 [info] DELUGE_ENABLE_WEBUI_PASSWORD not defined,(via -e DELUGE_ENABLE_WEBUI_PASSWORD), defaulting to 'yes' 2024-01-02 04:00:11.155585 [info] Starting Supervisor... 2024-01-02 04:00:11,545 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2024-01-02 04:00:11,545 INFO Set uid to user 0 succeeded 2024-01-02 04:00:11,549 INFO supervisord started with pid 7 2024-01-02 04:00:12,550 INFO spawned: 'start-script' with pid 71 2024-01-02 04:00:12,551 INFO spawned: 'watchdog-script' with pid 72 2024-01-02 04:00:12,552 INFO reaped unknown pid 8 (exit status 0) 2024-01-02 04:00:12,557 DEBG 'start-script' stdout output: [info] VPN not enabled, skipping configuration of VPN 2024-01-02 04:00:12,557 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-01-02 04:00:12,557 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-01-02 04:00:12,557 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22421319608976 for <Subprocess at 22421319731280 with name start-script in state RUNNING> (stdout)> 2024-01-02 04:00:12,557 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22421330322384 for <Subprocess at 22421319731280 with name start-script in state RUNNING> (stderr)> 2024-01-02 04:00:12,557 INFO exited: start-script (exit status 0; expected) 2024-01-02 04:00:12,558 DEBG received SIGCHLD indicating a child quit 2024-01-02 04:00:12,593 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2024-01-02 04:00:12,596 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2024-01-02 04:00:12,598 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2024-01-02 04:00:12,970 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has an undefined value [info] Deluge key 'listen_interface' will have a new value '' [info] Writing changes to Deluge config file '/config/core.conf'... 2024-01-02 04:00:13,209 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has an undefined value [info] Deluge key 'outgoing_interface' will have a new value '' [info] Writing changes to Deluge config file '/config/core.conf'... 2024-01-02 04:00:13,444 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of 'ed245fa046284bd999b98097404968b9' [info] Deluge key 'default_daemon' will have a new value 'ed245fa046284bd999b98097404968b9' [info] Writing changes to Deluge config file '/config/web.conf'... 2024-01-02 04:00:13,489 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2024-01-02 04:00:14,141 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846

Greetings! For some reason, Binhex - DelugeVPN won't run on my UNRAID server anymore. Its run fine for years prior so not sure what occurred to prevent it from running now. I've recently successfully replaced some capacity drives, but that's it. I've attempted to restart the app, reinstall it and now reboot my server. I can't get the web UI to load and my torrents don't appear to be seeding. My other dockers run fine. Is there a document that explains how to interpret a log file as there appears to be some line items there that could be of concern. The docker shows as started, but the log shows "Deluge Web UI not running". Tinkering with Deluge further, I was able to install just the vanilla Deluge docker and pull up the web UI no problem. Edit: Any suggestions on how to get DelugeVPN back up? I still have quite a few HnRs now despite it showing as running on the Docker page for UNRAID (can't pull up the web UI). I pulled up the console and checked for the host and it showed as offline and "Connection was refused by other side: 111: Connection refused. ". Not sure how to proceed here other than try another torrent client. 2Edit: You can close this one. I did an app restore for deluge and am up and running again. 3Edit: Can't pull up the web UI for Deluge and it appears to not be seeding. I've attempted to restore it as before, but still can't get this docker to work. Here's the log below. Any suggestions? [info] Deluge process listening on port 58846 2023-12-18 22:44:53,993 WARN received SIGTERM indicating exit request 2023-12-18 22:44:53,994 DEBG killing watchdog-script (pid 72) with signal SIGTERM 2023-12-18 22:44:53,994 INFO waiting for watchdog-script to die 2023-12-18 22:44:53,994 DEBG 'watchdog-script' stderr output: <Deferred at 0x1531d72b5b10 current result: <twisted.python.failure.Failure builtins.AttributeError: 'ConnectionRefusedError' object has no attribute 'message'>> 2023-12-18 22:44:53,994 DEBG 'watchdog-script' stdout output: [info] Waiting for child processes to exit... 2023-12-18 22:44:53,995 DEBG 'watchdog-script' stdout output: [info] All child processes exited, exiting while loop... 2023-12-18 22:44:53,995 DEBG 'watchdog-script' stdout output: [info] All child processes exited, exiting 'watchdog.sh' script... 2023-12-18 22:44:53,995 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22453359396560 for <Subprocess at 22453362367120 with name watchdog-script in state STOPPING> (stdout)> 2023-12-18 22:44:53,995 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22453377238224 for <Subprocess at 22453362367120 with name watchdog-script in state STOPPING> (stderr)> 2023-12-18 22:44:53,995 INFO stopped: watchdog-script (exit status 0) 2023-12-18 22:44:53,995 DEBG received SIGCHLD indicating a child quit Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2023-12-18 22:48:03.566571 [info] Host is running unRAID 2023-12-18 22:48:03.586372 [info] System information Linux 00cbefe71d84 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 GNU/Linux 2023-12-18 22:48:03.608965 [info] PUID defined as '0' 2023-12-18 22:48:03.633366 [info] PGID defined as '0' 2023-12-18 22:48:03.691838 [info] UMASK defined as '000' 2023-12-18 22:48:03.714275 [info] Permissions already set for '/config' 2023-12-18 22:48:03.738033 [info] Deleting files in /tmp (non recursive)... 2023-12-18 22:48:03.765418 [info] VPN_ENABLED defined as 'no' 2023-12-18 22:48:03.786464 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE 2023-12-18 22:48:03.810486 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2023-12-18 22:48:03.835168 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2023-12-18 22:48:03.857653 [info] DELUGE_ENABLE_WEBUI_PASSWORD not defined,(via -e DELUGE_ENABLE_WEBUI_PASSWORD), defaulting to 'yes' 2023-12-18 22:48:03.882736 [info] Starting Supervisor... 2023-12-18 22:48:04,022 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2023-12-18 22:48:04,023 INFO Set uid to user 0 succeeded 2023-12-18 22:48:04,024 INFO supervisord started with pid 7 2023-12-18 22:48:05,026 INFO spawned: 'start-script' with pid 71 2023-12-18 22:48:05,028 INFO spawned: 'watchdog-script' with pid 72 2023-12-18 22:48:05,028 INFO reaped unknown pid 8 (exit status 0) 2023-12-18 22:48:05,031 DEBG 'start-script' stdout output: [info] VPN not enabled, skipping configuration of VPN 2023-12-18 22:48:05,031 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2023-12-18 22:48:05,031 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2023-12-18 22:48:05,031 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22652256504848 for <Subprocess at 22652256503888 with name start-script in state RUNNING> (stdout)> 2023-12-18 22:48:05,032 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22652269960464 for <Subprocess at 22652256503888 with name start-script in state RUNNING> (stderr)> 2023-12-18 22:48:05,032 INFO exited: start-script (exit status 0; expected) 2023-12-18 22:48:05,032 DEBG received SIGCHLD indicating a child quit 2023-12-18 22:48:05,046 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2023-12-18 22:48:05,049 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2023-12-18 22:48:05,050 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2023-12-18 22:48:05,246 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has an undefined value [info] Deluge key 'listen_interface' will have a new value '' [info] Writing changes to Deluge config file '/config/core.conf'... 2023-12-18 22:48:05,437 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has an undefined value [info] Deluge key 'outgoing_interface' will have a new value '' [info] Writing changes to Deluge config file '/config/core.conf'... 2023-12-18 22:48:05,635 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of 'ed245fa046284bd999b98097404968b9' [info] Deluge key 'default_daemon' will have a new value 'ed245fa046284bd999b98097404968b9' [info] Writing changes to Deluge config file '/config/web.conf'... 2023-12-18 22:48:05,670 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2023-12-18 22:48:06,104 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846

After searching for this exact subject, I'm adding that I'd like to also see an official roadmap of sorts from Lime Tech. I really enjoy using UNRAID and am curious what's next on the horizon.

I have since moved my Roon Core from an UNRAID docker to ROCK on a NUC and am still getting these odd intermittent hang-ups with Roon sw on either of my Windows 10 machines. Could be an end point sw related issue regardless of the OS (Linux, Windows or MAC), but there's also a possible memory leak issue on the server side too that a recent update was supposed to fix with mixed results (970 build)? Just wanted to call this out as these recent intermittent hang-ups/program terminations are likely not associated with this docker. https://community.roonlabs.com/t/roon-keeps-freezing-and-crashing-on-windows-mostly-when-resuming-from-minimized-roon-investigating/199688/144

**SOLVED** A friend suggested I remove the "/login" URL portion I normally use to log into my UNRAID server instead of "xxx.xxx.x.x/login" and it worked without a password. Got into the web GUI, set a root password, tried the login URL again with the new password and all is well now. 😁

I misplaced my root password and tried these steps, but still can't login from the web GUI: I get this error when attempting to login with a password for root whether I delete those three files, or edit the shadow file: "Warning: file(/etc/nginx/htpasswd): failed to open stream: No such file or directory in /usr/local/emhttp/login.php on line 85 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/login.php on line 85" Attemtpting to log into UNRAID via root without a password prompts me to enter a password. I attempted to access UNRAID locally via a monitor, KB and mouse plugged into, but I don't get video because I believe I'm running a beta BIOS for my Asrock board that had some issue with quicksync and the onboard VGA being used at the same time. Any suggestions for getting back into my UNRAID server?

Since I couldn't find support from Roon on my issue above, (they wouldn't touch it without me moving off of this docker which I will if I have to), I reinstalled this Docker "steefdebruijn/docker-roonserver", and still get the random lockups using Roon with the error below from the Docker log: "at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)" I don't know what to do at this point other than abandon the docker which I would rather not since it has been working great for well over a year.

@xthursdayx (hoping you can shed some light on this as the logged error below is greek to me 😁) I'm running into an issue where my Roon sw on my Windows 10 Pro endpoints will randomly lock up when attempting to browse music (generally happens when Roon has been open on my laptop or desktop PC and the window is minimized for a few minutes - a song comes on I like so I will bring the Roon window to the foreground to tag, add it to a playlist, or just browse it and that's where the lockup occurs). The Roon endpoint sw will freeze while music continues to stream, but the window will either refresh on its own with whatever is playing (has whatever song info was on at the time when I minimized the window), or the app closes and I'm required to reopen it). This is fairly recent behavior as it started happening a few months ago. Up to that point, I've had Roon running without issue for a while now (1.5+ years now as a docker on UNRAID). Reinstalling the Roon sw on my laptop and desktop didn't resolve the issue. Anyone experience this? I did notice this in my log file for the Roon docker below (seems to coincide when the lockup occurs), but don't know what it means. "at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)"

I will second updating both Core and the Roon endpoint sw install from the nag screen with no problem.

I've been running Roon in an UNRAID docker for a little over a month now and it works great even after an update is pushed to the server via a Roon end point device. I actually saw a decrease in the amount of time taken to open Roon and queue up a song after moving back to a docker after running it in an Ubuntu VM initially so updates wouldn't break the server (still had issues with the Roon server losing my SMB music shares at random under Ubuntu). Just when I was about to move to NFS for the music shares, xthursdayx announced the updated Roon docker so I gave it go and man does it run great!

@dkerlee I have the Roon docker (steefdebruijn/docker-roonserver with xthursdayx's adjustments) on my cache drive as well and my music on the array. I experience no slow downs when searching for bands for instance (pretty snappy on my end). Sorry you're having performance issues with yours. Is streaming impacted with the slowdown or just searching?

@xthursdayx It's been a crazy month for me personally and work-wise! Ready for this year to be over with. I was going to start with these steps, but then read the Roon docker has been updated so it works updated from an end point device now. Nice! I moved from my Ubuntu VM to the docker and updated successfully (just read I needed to delete the Roon app data folder which I did not). Now I'm restoring a backup. Runs better on the docker than it did in the Ubuntu VM via SMB. Should I remove the docker, delete the app data folder and start again? I chose to remove the image when I removed the docker.

I got it sorted with AOMEI Partition Assistant. Thanks for the responses!

That's my last resort (downloading everything again manually which won't be easy). I'm trying to go a less labor intensive route if possible as it's around 4TBs and 1,000+ files.