0.7.20:sab won't come back after computer returns from sleep

[wcanyon]

Scenario: Got Sickbeard and Sab running on a HTPC. Both are running fine.

But when I put the computer to sleep at night, Sab never comes back. Sickbeard is fine with it, always available after a resume. I used to have a different version of Sab running on my HTPC and it came back after sleep just fine. When I open the PC and see the tray icons, Sab is there. But when I hit "Show Interface" it won't come up. So I Shutdown Sab and then restart it and it's fine. But I have to do this every time and it's annoying. Looks like a bug.

edit: there's a note up there about using Beta Board for 0.7, but 0.7 is the current release.

[sander]

Which OS?

what if you go to http://localhost:8080/sabnzbd/ after a sleep?

[wcanyon]

Windows 7 Pro

> what if you go to http://localhost:8080/sabnzbd/

Nothing. It times out.

[sander]

And is SABnzbd still running after the sleep? Check the processes (ctrl-alt-del, and then choose correct option)

[wcanyon]

Yes, it's still running. I used "Show all processes" in task manager and see one Sab process. When I hit Show Interface from the tray icon nothing comes up (timeout).

[sander]

Interesting. Do you have a firewall installed on your Windows machine?

Further test: check if SABnzbd is still listening like this:

Code: Select all

C:\Users\Sander>tasklist | find /i "Sab"
SABnzbd-helper.exe            2344 Services                   0      7.608 K
SABnzbd-service.exe           2304 Services                   0     26.216 K

C:\Users\Sander>netstat -aon | find /i "2344"

C:\Users\Sander>netstat -aon | find /i "2304"
  TCP    [::]:8080              [::]:0                 LISTENING       2304

The above shows SABnzbd-service.exe is indeed listening on port 8080. What is the output on your Windows before and after the sleep?

[wcanyon]

When I come back from sleep I don't have the helper or the service.

Code: Select all

C:\Windows\system32>tasklist | find /i "Sab"
SABnzbd.exe                   4992 Console                    1      4,444 K

C:\Windows\system32>netstat -aon | find /i "4992"
  TCP    192.168.1.83:8080      0.0.0.0:0              LISTENING       4992

The account that I'm logging on as is _not_ and admin, is that relevant?

[sander]

The LISTENING record: is that before or after the sleep?

Can you try "0.0.0.0" instead of 192.168.1.83 as listening port?

And: firewal, or not?

[wcanyon]

Firewall: standard windows firewall

LIstening record: after sleep

Just restarted Sab, put 0.0.0.0 in the host config and put comp to sleep. Brought it back. Results:

web interface shows on localhost, 127., 0.0., and computer name (media-pc). So, all good.

I'm not sure that it's actually fixed though. The sleeps that I've been putting it in have been very short, like under 10 mins. That should make zero difference but that's the only variable I can find here.

[sander]

Good that it works.

Hypothesis: your IP address changes during the sleep ...

[wcanyon]

That seems likely. However, SickBeard isn't bothered by that and the prior version of Sab I was using wasn't bothered by it (I've always used DHCP IIRC).

Still looks like a bug to me.

[shypike]

the prior version of Sab I was using wasn't bothered by it .

Which version still worked and which one stopped working?

[wcanyon]

0.7.20: fails intermittently

0.5.?: ran with no problems for a year+

It's been fine across 5 or 6 sleeps now so it seems too intermittent to recreate or bother with.