Page 1 of 1

Several copies of sabnzbd running

Posted: May 5th, 2011, 7:43 am
by Faust42
Hello.

I've upgraded to 0.6 this morning, and suddenly I have several instances of sabnzbd running. I've checked them and it seems that they all use different ports (I think), so I have

Code: Select all

https://localhost:9090 (the one I setup)
https://localhost:9095
https://localhost:9100
And every time I try to send a new nzb through firefox, it starts sab on a new port.

Any idea how to fix that?

Thanks in advance.
___________

Version: 0.6.0
OS: Win 7 x64 SP1
Install-type: Windows Installer.
Firewall Software: Comodo Firewall.
Is the issue reproducible? yes
Firefox 4.0.1

Re: Several copies of sabnzbd running

Posted: May 5th, 2011, 8:12 am
by shypike
When you send an NZB to SABnzbd, a new instance is started.
This new instance tries to find an exiting one.
For some reason this fails on your system.
So don't use the "send to" method, instead use the watched folder
or a FF plugin like nzbdStatus.

Re: Several copies of sabnzbd running

Posted: May 5th, 2011, 8:45 am
by Faust42
0.6 was the problem. Reverting back to 0.5.6 fixed everything.  ;D

Re: Several copies of sabnzbd running

Posted: May 5th, 2011, 9:43 am
by shypike
If you're willing to forgo the new features of 0.6.0,
just to solve this one issue, be my guest.

Re: Several copies of sabnzbd running

Posted: May 5th, 2011, 12:51 pm
by shypike
Well, I can confirm your problem.
There's a bug in the communication between the running and the starting instance.
Will be fixed asap.

Re: Several copies of sabnzbd running

Posted: May 16th, 2011, 6:44 am
by Faust42
Hello.

After updating to 0.6.1, I've noticed that when I use non-HTTPS interface (http://localhost) everything works flawlessly. Enabling HTTPS in 'General' settings brings back the problem.

Should I try switching the SSL type?

Thanks in advance.

Re: Several copies of sabnzbd running

Posted: May 16th, 2011, 7:29 am
by shypike
Faust42 wrote: After updating to 0.6.1, I've noticed that when I use non-HTTPS interface (http://localhost) everything works flawlessly. Enabling HTTPS in 'General' settings brings back the problem.
An interesting observation!
I will look into this and let you know the result.