search

k44sh / rutorrent

rTorrent/ruTorrent Docker compatible with Radarr/Sonarr
MIT License
28 stars 5 forks source link

Unraid container issue s6-rc fatal #8

Open motif82 opened 2 months ago

motif82 commented 2 months ago

HI, having an issue with my container not firing up after stopping. I'm running it on Unraid and when it's running it's going smooth with no issue but if I stop the container for backups or need to reboot, I'm having a hard time getting it going again. It will try to start and then shut right down. This is what the log shows.

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/configurations.sh s6-rc: fatal: timed out s6-sudoc: fatal: unable to get exit status from server: Operation timed out /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

Sometime if I restart it a few times, it will eventually start running but I usually have to remove the container and reinstall or, do a clean reboot to get it going.

Not sure if this is an Unraid issue or something I messed up when making the container. This is my first try at one so my guess is the latter. All my other containers that I'm running from the community application center in Unraid are running just fine. Does anthing jump out at you from the log?

k44sh commented 1 month ago

Hi @motif82,

This error seems to be related to a problem with s6-overlay, which is used for managing processes in a container.

With the version where you encountered the problem, I wasn't able to reproduce the issue.

Maybe there's a specific situation with Unraid ¯ \ (ツ) / ¯

I've just pushed a new version for ruTorrent v4.3.6.

It's a new Docker image. Maybe it will solve your problem?

motif82 commented 1 month ago

Thanks for the reply, I'll give the new version a try this weekend. I have been doing some searching and it looks like this was an ongoing problem with the s6-overlay timing out too soon in a lot of different programs. They removed the time out command in its latest version. Not sure if that's written into the program or in unraid.

https://github.com/just-containers/s6-overlay/commit/e2738d136bbdedbe3553b947f3c18183fc70e56c

motif82 commented 1 month ago

I did try the new version but it was giving me the same errors with s6-overlay. I put in a variable command of S6_CMD_WAIT_FOR_SERVICES_MAXTIME = 0 as suggested on the S6 page and it started right up. I'll do some more testing to confirm that this fixed the issue.