SABnzbd fails to run after update in Docker (LSIO version 4.0.1-ls108)

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
Watson
Newbie
Newbie
Posts: 3
Joined: June 26th, 2023, 7:53 am

SABnzbd fails to run after update in Docker (LSIO version 4.0.1-ls108)

Post by Watson »

Hi,

I've been running SABnzbd in Docker, on a Synology DS218+, for several years and have had no issues. This morning I updated (I think from 3.7.2) to 4.0.2 and it's now not working at all. If I try and log in via the web interface, I just "The connection was reset" as an error. But it can't just be just the web interface, as Radarr is reporting "All download clients are unavailable due to failures". So it seems to not be working at all.

I've had a look at the changelogs, but I can't see anything obvious. Was there anything I should have done, before upgrading to v4.x?

I performed the update as I always have, getting the latest, from linuxserver, via Docker's interface. I also tried using SSH to do a pull request, but it said that it was up to date.

I tried stopping SABnzbd, deleting the .ini and restarting, but that made no difference.

Is there something really obvious that I've missed? I set Docker up a while ago and only touch it for updates, so I'm by no means an expert! :)

Many thanks.
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: SABnzbd fails to run after update in Docker

Post by sander »

Is the SAB docker running at all?

On Linux, you can check with "docker ps". I don't know how on Synology ... hopefully via the GUI?
Top
User avatar
safihre
Administrator
Administrator
Posts: 5678
Joined: April 30th, 2015, 7:35 am
Contact:
Contact safihre

Re: SABnzbd fails to run after update in Docker

Post by safihre »

It's a change in the Docker image provider by linuxserver.
See https://github.com/linuxserver/docker-s ... 1587434645
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Top
Watson
Newbie
Newbie
Posts: 3
Joined: June 26th, 2023, 7:53 am

Re: SABnzbd fails to run after update in Docker

Post by Watson »

That's fixed it! Thanks so much, I never would have even thought to search for that.

And that's reminded me to donate again. Got to keep you all supplied with Swiss Cheese! :)

Thanks again.
Top
User avatar
safihre
Administrator
Administrator
Posts: 5678
Joined: April 30th, 2015, 7:35 am
Contact:
Contact safihre

Re: SABnzbd fails to run after update in Docker

Post by safihre »

Glad it worked, I know nothing about Docker so couldn't help otherwise 😄
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: SABnzbd fails to run after update in Docker (LSIO version 4.0.1-ls108)

Post by sander »

So it happens with Linuxserver.io version 4.0.1-ls108, and has to do with (old?) PATH settings?

I've changed the subject to contain LSIO version 4.0.1-ls108 ... hopefully useful for Google and other users
Top
Watson
Newbie
Newbie
Posts: 3
Joined: June 26th, 2023, 7:53 am

Re: SABnzbd fails to run after update in Docker (LSIO version 4.0.1-ls108)

Post by Watson »

Good point. Yes, that seems to be correct. And here's the solution, just in case:

1. Stop container
2. Select the container by clicking it anywhere, then click edit (at top)
3. Under General Settings tab click Advanced Settings
4. Click the PATH variable, then DELETE, then Save.
5. Reset the container, then start.
Top
Post Reply

Return to “General Help”