xlelx

Just updated and it appears to be running again. Appreciate the quick turnaround!

Back to about 1 month ago with binhex/arch-jackett:0.22.2390-1-01 and still not working. Going back to :latest now and waiting for a fix at this point or maybe setting up an additional indexer for the server.

I am seeing the same thing here. I rolled back all the way to binhex/arch-jackett:0.23.62-1-01 so far to try and get this working again but no success so far.

Just updated to 4.9.4. Had to do an 'unraid-api start' to get it going after updating, but once it completely started up I seem to have no more issues. Thanks all for the fix! The only issue I am seeing now are intermittent 503 errors reported by the plugin in the UI. They do come and go, but it has been mostly stable and my flash backup does complete.

Another thing to point out in my instance, I have no logo present and when I click on the menu at the top right it does nothing.

Getting this same exact error when I do unraid-api start or unraid-api restart from cli. Just updated to 4.9.1 a few moments ago. For reference: <anonymous_script>:1 SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at ApiStateConfig.parseConfig (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:971:32) at async loadApiConfig (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:1071:24) at async PluginService.listPlugins (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:2253:34) at async PluginService.importPlugins (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:2219:32) at async PluginCliModule.register (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:12650:25) Node.js v22.16.0 EDIT: Diags attached fortress-diagnostics-20250709-0052.zip

Flawless upgrade from 6.12.14 to 7.0.0 here. I uninstalled the Folder View plugin before upgrading as suggested in the Update Assistant tool, reinstalled once I got up and running with no issues. Stopped all containers and VMs, stopped the array, then did the upgrade as per my usual process for upgrades. Plugins downloaded and then rebooted without issues. Side bonus; The SAS spin down plugin is actually spinning down my drives now where it never would in the past, so I appreciate this as it drops my server's power usage by about 1/3 with my drives spun down. For those curious this is on a Dell PERC H710 mini controller in a Poweredge R720xd with an 8 drive array including the parity drive.

Uninstalled/Reinstalled as directed by support and others here and it worked like a charm. Issue resolved!

As the documentation pointed out that this was also for the My Servers plugin I signed out of it on my Unraid server and now cannot sign back in. Have tried email address as preferred in the new method and my username as was done before. I have also submitted this case through the support form via the plugin.

Glad you got something useful from my post! Another update... The container restarted successfully after last weeks appdata backup. I thought I had this beat, but there was an update last night which broke this again. Same errors. On a whim I reinstalled python2 from the container console (docker exec -it nzbget bash, then apk update, and finally apk add python2) and also deleted the custom-services.d folder. I then restarted the container and it worked like a charm. Dunno if this fix will work for everyone. Someone may want to just try deleting the README file in the custom-services.d folder rather than the whole folder to see if that makes things happy as well. I am not until it breaks the next time, if it breaks a next time

An update: Curiously 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. I can stop the container, pull in my old nzbget.conf, then restart it (so I retain my path settings, etc easily) and it continues to work fine. I can then also re-install VideoSort from here (https://github.com/nzbget/VideoSort/releases), version 8.0 at the time of this writing, and it too works fine. I might add that I did install Video sort into the /custom-cont-init.d folder as the previous README advised. As part of the VideoSort install I have also installed Python 2 through the docker's console. It will work fine once NZBGet is reloaded from making changes through the container's web interface as well. 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: s6-rc-compile: fatal: during resolution of bundle user: undefined service name custom-svc-README.txt s6-rc: fatal: unable to take locks: No such file or directory s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111 s6-rc-compile: fatal: during resolution of bundle user: undefined service name custom-svc-README.txt s6-rc: fatal: unable to take locks: No such file or directory s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111 s6-rc-compile: fatal: during resolution of bundle user: undefined service name custom-svc-README.txt s6-rc: fatal: unable to take locks: No such file or directory s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111 s6-rc-compile: fatal: during resolution of bundle user: undefined service name custom-svc-README.txt [custom-init] removing existing custom services... [custom-init] no custom services found, skipping... [custom-init] no custom services found, skipping... [custom-init] no custom services found, skipping... [custom-init] no custom services found, skipping... 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. Seems it does not like VideoSort or Python 2 all of a sudden and I am not aware of a good replacement.

Hi all! I am getting the following error after my weekly application data backup and cannot access the web UI for NZBGet and figure out why. And yes, I have tried restarting the container and pulling it down again a few times. Only thing I have not done is reboot the whole server. s6-supervise custom-svc-README.txt (child): fatal: unable to exec run: Exec format error s6-supervise custom-svc-README.txt: warning: unable to spawn ./run - waiting 10 seconds I do also see this in the log before these lines: [custom-init] python2.sh: exited 0 ******************************************************** ******************************************************** * * * !!!! * * Custom scripts or services found in legacy locations * * !!!! * * Please move your custom scripts and services * * to /custom-cont-init.d and /custom-services.d * * respectively to ensure they continue working. * * * * Visit https://linuxserver.io/custom for more info. * * * ******************************************************** ******************************************************** Any help would be appreciated!