octomobiki

This is an interesting concept. the period of inability to access the server DID come after a library refresh in the morning. Ok I feel much better about the situation now and have a better idea about when/where to start poking around. thank you so much!.

too many start retries too quicklyThere is nothing in the log that shows this error trace that I can see. and for all purposes I can see that plexmediaserver is up and running. About 90 minutes after posting this however, my plex server IS accessible. In the interim i have made no changes to the system and actually had to go to work so I wasn't mucking around.

As of this morning I found my Plex in a weird.. not accessible state (according to WebUI). I've tried rebuilding the container and accessing the plex instance directly with the localip:32400 but I simply get an unable to connect. As far as I know overnight there was no changes to my unraid instance and it was working fine just hours before I got to it this morning. I've performed a reboot of unraid underneath it but still nothing. Logs show me this, and the up contents of the container are below as well. any ideas? ``` sh-5.2# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 05:41 ? 00:00:00 /usr/bin/dumb-init -- /bin/bash /usr/local/bin/init.sh root 31 1 0 05:41 ? 00:00:00 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n nobody 95 31 0 05:41 ? 00:00:00 /usr/bin/dumb-init /bin/bash /home/nobody/start.sh nobody 96 95 0 05:41 ? 00:00:00 /bin/bash /home/nobody/start.sh nobody 98 96 35 05:41 ? 00:01:52 /usr/lib/plexmediaserver/Plex Media Server root 113 0 0 05:46 pts/0 00:00:00 sh root 123 113 0 05:46 pts/0 00:00:00 ps -ef sh-5.2# ``` 2025-05-29 05:41:32,933 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2025-05-29 05:41:32,933 INFO Set uid to user 0 succeeded 2025-05-29 05:41:32,935 INFO supervisord started with pid 31 2025-05-29 05:41:33,937 INFO spawned: 'plexmediaserver' with pid 89 2025-05-29 05:41:33,938 INFO reaped unknown pid 32 (exit status 0) 2025-05-29 05:41:34,002 DEBG 'plexmediaserver' stderr output: Plex Media Server is already running. Will not start... 2025-05-29 05:41:34,012 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23394625943408 for <Subprocess at 23394625943072 with name plexmediaserver in state STARTING> (stdout)> 2025-05-29 05:41:34,013 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23394624213136 for <Subprocess at 23394625943072 with name plexmediaserver in state STARTING> (stderr)> 2025-05-29 05:41:34,013 WARN exited: plexmediaserver (exit status 1; not expected) 2025-05-29 05:41:34,013 DEBG received SIGCHLD indicating a child quit 2025-05-29 05:41:35,014 INFO spawned: 'plexmediaserver' with pid 95 2025-05-29 05:41:36,015 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

I lost my update trying to properly quote: the short answer is yes it worked, the not so short answer is, by pinning telegraf my other grafana dashboards do not work. I might have to simply not go this route so my other dashboard continues to work.

So I'm actually getting this error too and I don't see that the original poster responded. I'm going through the initial setup of UUD and on the section with editing the telegraf.conf file and adding the post script to the docker container. "APK" does not work, but 'apt-get' does. if I open a console on the docker container while it is running, I can install the packages. when I add the line to the post arguments, I consistently get that error, even when doign something as simple as: "/bin/sh -c 'apt-get update'", it shows up under 'logs' after a failed start of the docker container.

After working for a day, Deluge suddenly doesn't fully startup. I can't tie it down to any particular setting I've changed. The log files only show the below. I have given it at least 10 minutes or so but never becomes accessible. I checked and there aren't any sort of port conflicts and I don't have anything like running multiple segments on my network. Anything I can possibly check into to get insight on the error? 2024-11-03 20:32:12,603 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-11-03 20:32:12,604 DEBG 'deluge-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2024-11-03 20:32:13,354 DEBG 'deluge-script' stdout output: [info] Deluge process listening on port 58846 2024-11-03 20:32:14,457 DEBG 'deluge-script' stderr output: <Deferred at 0x150c996e3830 current result: None> 2024-11-03 20:32:14,491 DEBG 'deluge-script' stdout output: [info] No torrents with state 'Error' found 2024-11-03 20:32:14,496 DEBG 'deluge-script' stdout output: [info] Starting Deluge Web UI...