Hi All. I'd appreciate some assistance on this one as it's driving me nuts and making me want to revert to a pre v7 release.
I'm running the latest of sabnzbd on Windows Server 2008 R2 and find that every time I choose to download and launch an nzb, a new instance of sabnzbd on a new port is launched rather than simply adding the nzb to the queue of an instance that is already running and perhaps downloading something else. This often results in multiple instances each downloading the same nzb. My connection to my newsserver is also blocked due to too many connections (as both instances are attempting to make 30 connections.
Any advice on how to have only one instance running would be very much appreciated.
Cheers
Slippa
sabnzbd creating multiple instances
Forum rules
Help us help you:
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.
Re: sabnzbd creating multiple instances
I've gone ahead and configured sabnzbd as a service and installed nzbdStatus which fixes the problem. I'm not a fan of the tray icon and multiple instances.
Re: sabnzbd creating multiple instances
SABnzbd associates itself with NZB files, so that each time an NZB is double-clicked SABnzbd is started.
At startup it needs to find out whether an instance is already running and how to reach it.
For this, the registry is read. Some ways of installing make this hard, especially when
multiple user accounts are used.
Running as as service can make most of those problems go away, as you have seen.
At startup it needs to find out whether an instance is already running and how to reach it.
For this, the registry is read. Some ways of installing make this hard, especially when
multiple user accounts are used.
Running as as service can make most of those problems go away, as you have seen.