After updating SABnzbd shuts itself down after a few minutes from starting. I backed up my AppData folder before the update so I rolled back to Beta6 and it's still happening - not sure what's going on here. Logs are available at pastebin.
Version: 0.5.0 RC3
OS: Windows 7 Ultimate x64
Install-type: Installer
Skin (if applicable): Plush
Firewall Software: Comodo
Are you using IPV6? no
Is the issue reproducible? yes - for me
-EDIT-
It's not just the UI not working, the actual process disappears from the running processes list.
After Update to RC3 SABnzbd Shuts Down After a Few Minutes
Forum rules
Help us help you:
Help us help you:
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
After Update to RC3 SABnzbd Shuts Down After a Few Minutes
Last edited by tehgooch on January 23rd, 2010, 5:33 pm, edited 1 time in total.
Re: After Update to RC3 SABnzbd Shuts Down After a Few Minutes
I tried rebooting and the issue did not go away. I gave up and tried to sort out a file sharing problem. Left the homegroup (ugh, I hate windows 7 - it's too "user friendly"), logged out and in, and now SABnzbd is working fine.
P.S.
"user friendly" = dumbed down
P.S.
"user friendly" = dumbed down
Re: After Update to RC3 SABnzbd Shuts Down After a Few Minutes
Rebooted my computer and the behaviour is back. I'm scratching my head at what could be causing this.
Re: After Update to RC3 SABnzbd Shuts Down After a Few Minutes
It was all Comodo firewall acting up. Turned out to be the source of my file sharing issues as well. I literally added a rule to allow traffic in from my entire subnet at the very top of the incoming rules list (just a local private lan) and it was still refusing filesharing connections without printing it in the log or giving a notification. What a piece of junk!