Since upgrading from 0.4.x to 0.5.0 sabnzbdplus is nearly unusable because it's frequently crashing when I'm not connected with the browser.
I've written a helper script which restarts sabnzbdplus when it has crashed and writes a log entry:
...
Restarted at Son Feb 28 09:55:50 CET 2010
Restarted at Son Feb 28 09:56:03 CET 2010
Restarted at Son Feb 28 09:56:15 CET 2010
Restarted at Son Feb 28 09:56:28 CET 2010
Restarted at Son Feb 28 09:56:40 CET 2010
Restarted at Son Feb 28 09:56:52 CET 2010
Restarted at Son Feb 28 09:57:05 CET 2010
Restarted at Son Feb 28 09:57:17 CET 2010
Restarted at Son Feb 28 09:57:30 CET 2010
Restarted at Son Feb 28 09:57:42 CET 2010
Restarted at Son Feb 28 09:57:54 CET 2010
Restarted at Son Feb 28 09:58:07 CET 2010
Restarted at Son Feb 28 09:58:19 CET 2010
Restarted at Son Feb 28 09:58:32 CET 2010
...
As you can see sabnzbdplus is cashing very frequently. The strange detail is when I'm connected with a browser the program runs without crashes.
Also very strange is that I get disk error warnings although free disk space is enough (676G) and the rights are correctly set. Although the warnings appear in the log the files are sometimes created and sometimes not.
0.5.0 is frequently crashing on ubuntu karmic
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- 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.
0.5.0 is frequently crashing on ubuntu karmic
Last edited by elvis on February 28th, 2010, 4:46 am, edited 1 time in total.
Re: 0.5.0 is frequently crashing on ubuntu karmic
Did you have you looked at the logging files at all?
What happens if you run it directly from a terminal windows?
That way you should see the logging directly and also very
likely the reason why it crashes.
What happens if you run it directly from a terminal windows?
That way you should see the logging directly and also very
likely the reason why it crashes.