SABnzbd Port changing on its own?

[sperber]

I'm seeing a strange situation. My Sickbeard to SABnzbd setup works fine. Then, every so often, it stops. After some investigation it turns out that the SABnzbd Port that I've setup in Sickbeard no longer is correct. Somehow, the SABnzbd Port is changing, breaking Sickbeard.

Does SABnzbd change ports dynamically somehow?

TIA

[sander]

Does SABnzbd change ports dynamically somehow?

If, at startup, SABnzbd cannot bind to the port it should use (for example: 8080), it will find a free port, for example 8085.

Main reason that SAB cannot use a port:
- port is in use by another application
- port is in use by ... SABnzbd itself (although this does not happen often anymore ... so maybe SABnzbd has built-in checking against this)

Sander

[shypike]

SABnzbd used to test to see if the same version is already working.
It no longer does that, as soon as it sees any instance running it will try to activate
that instance's UI and then exit.
There may be circumstances that this may still go wrong.
Try starting SickBeard before SABnzbd.

[sperber]

Thanks for the replies. I'll try starting Sickbeard first and see how it goes.