I thought I had this beat, but there was an update last night which broke this again. The container restarted successfully after last weeks appdata backup. Glad you got something useful from my post! not sure but it must be related to python2 install during the image install. reinstall image, copy back nf and python.sh' worked for me too. And thanks, your tip 'remove image, move nzbget appdata. Interestingly the exact same thing happened to me. Seems it does not like VideoSort or Python 2 all of a sudden and I am not aware of a good replacement. Still trying to find a permanent fix for this as I naturally don't want to have to do this dance each time I restart the container which will be at least once a week when my appdata backup runs and stops all Docker containers. S6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111 S6-rc: fatal: unable to take locks: No such file or directory S6-rc-compile: fatal: during resolution of bundle user: undefined service name custom-svc-README.txt If I restart the container altogether, I immediately get the same errors on startup and an inaccessible web UI and new errors as listed below: It will work fine once NZBGet is reloaded from making changes through the container's web interface as well. As part of the VideoSort install I have also installed Python 2 through the docker's console. ![]() I might add that I did install Video sort into the /custom-cont-init.d folder as the previous README advised. I can then also re-install VideoSort from here ( ), version 8.0 at the time of this writing, and it too works fine. I can stop the container, pull in my old nf, then restart it (so I retain my path settings, etc easily) and it continues to work fine. *Ĭuriously I am able to remove the container from the Docker tab, remove/rename the nzbget folder in my appdata folder, pull down the container and it runs fine. * respectively to ensure they continue working. * to /custom-cont-init.d and /custom-services.d * ![]() * Please move your custom scripts and services * * Custom scripts or services found in legacy locations * ![]() I do also see this in the log before these lines: S6-supervise custom-svc-README.txt: warning: unable to spawn. S6-supervise custom-svc-README.txt (child): fatal: unable to exec run: Exec format error Only thing I have not done is reboot the whole server. And yes, I have tried restarting the container and pulling it down again a few times. I am getting the following error after my weekly application data backup and cannot access the web UI for NZBGet and figure out why.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |