SABnzbd Forums

I've been using sabnzbd with sickbeard for a long time now but have ran into an issue and am not sure what the cause. Sabnzbd is suddenly hanging with the sabToSickBeard.exe post processing. Sabnzbd itself is working fine for everything apart from sickbeard. Sickbeard is sending it nzb's it just when it gets to the post processing that it hangs. I've tried different versions of each (currently on sabnzbd 0.7.16 and sickbeard 502) and nothing i've tried has worked. If i go into the nzb search section (search settings) on sickbeard and try the test button, it's saying "Unable to connect to host" or gives an api error 99% of the time, even though the sabnzbd settings are ok and have entered them 10 plus times to make sure. Something seems to be causing an issue between the two programs but dont know what. Anyone else experience an issue like this? Why it suddenly started happening i do not now. I think it might possibly have been the installation of another program that used one of the same ports, but i've tried different ports and it made no difference.

If anyone has any suggestions it would be great!

When they do communicate i see the json result like this in the sab log

2013-12-30 10:06:17,887::DEBUG::[interface:420] API-call from 192.168.1.11 [Sick Beard/alpha2-build-502 (Windows 7)] {'mode': 'auth'}
2013-12-30 10:06:17,900::DEBUG::[interface:420] API-call from 192.168.1.11 [Sick Beard/alpha2-build-502 (Windows 7)] {'output': 'json', 'apikey': 'a3dab15c17e23c43dd943cb0zfaf5cf1', 'mode': 'queue', 'ma_username': 'root', 'ma_password': 'password'}

when they do not communicate i just see this

2013-12-30 10:06:32,112::DEBUG::[interface:420] API-call from 192.168.1.10 [Sick Beard/alpha2-build-502 (Windows 7)] {'mode': 'auth'}

its not that the api or username/password are incorrect as they very odd time the programs do connect. And i've tried new api keys etc and that made no difference. Just seems to be very strange. Turning off firewall and anti virus makes no difference.

Sab and sickbeard run on the same pc and i use the pc's ip in their settings. Again the settings have worked for a year or two so its not an incorrect ip issue.

The problem looks to be on the SickBeard side.
As you can see: even in the second case there is communication going from SickBeard to SABnzbd.
The first call is always "auth". For some reason SickBeard doesn't make the "queue" call.
Is there any logging from the SickBeard side?