rutorrent icon indicating copy to clipboard operation
rutorrent copied to clipboard

Unraid container issue s6-rc fatal

Open motif82 opened this issue 7 months ago • 3 comments

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?

motif82 avatar Jul 08 '24 20:07 motif82