SABnzbd Forums

Hi Guys,

Version: 0.5.6 final
OS: Windows 7 X64 Ultimate
Install-type: Windows Installer
Skin (if applicable): Default
Firewall Software: Microsoft Essentials
Are you using IPV6? no
Is the issue reproducible? yes
Connection: 120Mbit
News Provider: Hitnews

I have .nzb associated with SABnzbd to automatically add a downloaded NZB file to te queue. This has been working great for months, but recently (I think it started with 0.5.6) it is starting more instances (not always, but sometimes I see 4 or 5. Another awkward thing is that it creates it's own port. Normally I use 8080, but the new instances number up with 5 (so the next I see is 8085 and so on). I'm not sure what happens with the queue (has every instance it's own queue?) and also it's hard to find out what is where and why. Last but not least performance is getting very bad with more than one instance running (with 4 there is nearly no response at all).

Is it a bug? And what can I do to prevent the unintended instances?

Thanks in advance for your help.

JoopvB

Is your sabnzbd.ini file located at the default location?
Do you start your first instance using the -f parameter?
The NZB association can only work if you have the sabnzbd.ini file
at the default location.

SABnzbd.ini is in Appdata/Local/sabnzbd. Correct, I think.

I start SABnzbd via Startup, but not with -f. Could that explain the problem?

JoopvB wrote: I start SABnzbd via Startup, but not with -f. Could that explain the problem?

Not sure.
The startup and the association must use the same location.
If you use the NZB association as setup by the SABnzbd installer, it will not use the -f parameter.
Subsequently, your startup should not use it either.
You should find the log file and see where SABnzbd thinks it's INI file is.
It's in Appdata/local/sabnzbd/logs .

I have been through the log file but it doesn't say anything about the ini file. What phrase should I look for?

I think you'd better use the poor man's NZB association instead.
See: http://wiki.sabnzbd.org/howto-associate

The current method is a bit problematic and we're looking at a different implementation.