Page 1 of 1

0.7.18 daily restart require Ubuntu server 14.04

Posted: October 16th, 2014, 3:21 pm
by THECHOO
Been happily running sabnzbd for some time on previous ubuntu LTS 12 and upgraded to 14.04 last week.

Ever since i'm getting huge stability issues that I can seem to narrow down. On bringing up sabnzbd and sickbeard everything seems to work fine. After a period of time though sickbeard is reporting that it can no longer send anything to sabnzbd and reports the error:

Code: Select all

SEARCHQUEUE-RSS-SEARCH :: Unknown failure sending NZB to sab. Return text is: 
Note there is no return text it seems - its empty and not reporting the actual error message!

If I restart from command prompt (not restart from within sabnzbd only seems to shut down and it wont restart) then things work for a bit then stop again.

I've tried a reinstall & purge and clear down of the settings and db files.

Anything I'm missing?

Cheers.

Re: 0.7.18 daily restart require Ubuntu server 14.04

Posted: October 16th, 2014, 3:42 pm
by shypike
Can you find out what the default Python version is?

Re: 0.7.18 daily restart require Ubuntu server 14.04

Posted: October 16th, 2014, 4:29 pm
by THECHOO
SABNZBD reporting 2.7.6

Re: 0.7.18 daily restart require Ubuntu server 14.04

Posted: October 17th, 2014, 3:14 am
by shypike
Sander, what's your experience with Ubuntu 14.04?

Re: 0.7.18 daily restart require Ubuntu server 14.04

Posted: October 17th, 2014, 3:25 am
by sander
shypike wrote:Sander, what's your experience with Ubuntu 14.04?
Rockstable for me.

Questions to the OP:

Can you still access SAB's webinterface all the time, so via http://localhost:8080/ ?
When you get problems, what's the output of "netstat -apon | grep 8080"?

Sander

Re: 0.7.18 daily restart require Ubuntu server 14.04

Posted: October 19th, 2014, 12:40 pm
by THECHOO
sander wrote:
shypike wrote:Sander, what's your experience with Ubuntu 14.04?
Rockstable for me.

Questions to the OP:

Can you still access SAB's webinterface all the time, so via http://localhost:8080/ ?
When you get problems, what's the output of "netstat -apon | grep 8080"?

Sander
Hi

Yes I can still access localhost on port 8080

Output of the netstat looks to be fine:

Code: Select all

tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      1751/python      off (0.00/0/0)
tcp        0      0 192.168.0.13:8080       192.168.0.11:62980      ESTABLISHED 1751/python      off (0.00/0/0)
tcp        0      0 192.168.0.13:8080       192.168.0.11:62982      ESTABLISHED 1751/python      off (0.00/0/0)
The one curious thing I've seen; when I used putty to go back in just now after not being on for a couple of days is:

Code: Select all

 System information disabled due to load higher than 2.0
Looking at the info for the vm this doesnt stack up .Memory and CPU usage spiked for a second when I logged in but aside from this the system is doing nothing. Might well be a red herring.

This is proving elusive and odd!