Web interface becomes unresponsive on Windows Home Server (running as service)

[monkeybubbles]

Version: 052 final
OS: Windows Home Server
Install-type: windows exe running as a service
Skin (if applicable): both default and plush
Firewall Software: built in whs firewall
Are you using IPV6? no

Problem: After running sabnzbd for any amount of time (some times an hour, some times 24 hours) the web interface stops responding.  The process appears to still be running, but is using 0% cpu.  Stopping and restarting the service will fix it most of the time.  ALthough occasionally I have to stop and restart several times to bring things back around.

Background:
I've been running sabnzbd successfully on my win7 pc for a while now and recently decided to start using it on my Windows Home Server box instead so I could cut down on the number of computers that are sucking up electricity all day every day.

I followed the guide at http://wiki.wegotserved.com/index.php?t ... ome_Server but ignored the reverse proxy section (I don't want my sabnzbd site accessible from outside my network) and used some custom folders, but other than that I think I stuck to the guide.  I DID use the anyservice installer listed on that page, not sure if this affects the issue or not.

I have a feeling that running sabnzbd as a service is part of the problem, but I believe others are doing this successfully.  Does anyone have any suggestions?

[shypike]

It looks like there are some issues.
Release 0.6.0 will contain proper support to run as a service,
but it's not quite stable yet.
What I see is that it (0.6.0) runs for days on end, but a restart (from Config) doesn't always work properly.
(0.5.x cannot restart when it runs as a service),

One work-around is to schedule a daily shutdown in SABnzbd's scheduler
and to use a scheduled batch file (in the Windows scheduler) to restart the service.
Keep 15 minutes between the shutdown and the service restart.
It's not ideal, bit should work.

We are working on this.

[monkeybubbles]

Is there any kind of workaround for this?

I wonder if I should just go with a regular old "shortcut in the startup folder" and just make sure that I log into my WHS box every time it happens to restart.

I can't wait to see 0.6.0! 

[shypike]

Is there any kind of workaround for this?

I thought I described a work-around.