Support Forum

Have you tried enabling sabnzbd again in Sonarr?
If you click the Test button on the Config page for SABnzbd in Sonarr?

In de interface, klik op het moersleutel icoontje bovenin.
In het venster dat dan opent, zet onderin in de dropdown het op Debug.
Als het dan weer fout gaat, klik dan in hetzelfde venster op Toon Log.

Is there more in the log? It seems maybe the first or last lines of the error got cut off, in which it says what exception is being thrown.
If you can't post it due to the forum software, you can also email it to me at [email protected]

Kun je iets meer vertellen: welk besturingssysteem gebruik je?
Kun je logging op Debug zetten in Status and Interface settings scherm? Als zoiets weer gebeurd, kun je me dan via Show Logging (zelfde scherm) de logs sturen op [email protected]
Gebruik je sonarr/radarr/CouchPotato?

The ASUS is setting illegal cookies using the colon in the cookie name, making the SABnzbd webserver unable to continue processing. It's kind of strange that they share cookies, if both using different IPs. Usually it helps to for example access SABnzbd through the device-name instead of the IP-addr...

There is nothing specific you can change from SABnzbd. Seems the external drive is just not available, but seems unclear why.
Maybe indeed a timeout, what does the last line of the error say in the log? "directory not found"?

When do you get the error? Only during startup or during downloading to?

So maybe you have some weird redirection setup in your hosts file? I am not sure what is going wrong, clearly it is starting since it doesn't stop running right? So besides that.. The rest is problem with your OS, since it's a specialized OS we hope you have the specialization to find out what's up ...

If you include in that command the -l 2 it should show you "Listening on x.x.x.x:8088"
What does it say there?

And you are sure SABnzbd is running?
Did you do
netstat -l
To see where SABnzbd is listening?
If you run SABnzbd from the command-line the logging will show you where it is listening, start it like this:
python2 SABnzbd.py -l 2

Didn't answer my question on what system you are running it? Is it a NAS or a remote device? If it is a local system you should set it to 127.0.0.1. Unless you did something to your hosts file, this should work. If it's a remote device you should set it to 0.0.0.0 You might need a restart of your sy...

We need more information.
What system are you on? How did you install sabnzbd?
Are you sure it is running?
Have you read the FAQ about how to reset the host and port?

If that doesn't work, enable +Debug in the Status Window, after it happens again download the log via Show Logging and then inspect what it is doing at this timepoint.

Nee nee, je moet niet dat met die * doen.
Anders gaat het script straks veel te veel doen. Het werkt beste op losse job folders.

Do you have a Watched folder set up? If so, what is this folder? Does it contain a lot of files? Sabnzbd will try and inspect all archives also when scanning watched folder, which might cause this cpu spike. Try choosing a folder that's really unique for just NZBs. Another thing I could imagine is R...