SabNZBD has been running flawlessly for 6 months until recently.  I will not be able to hit the url and when I do a ps aux | grep python I do not see it running.  I manually kick it off again only to have it crap out a few hours later.  My other python apps continue to run fin (couchpotato and sickbeard)  Only thing I see in the syslog is:

 

Sep 10 12:06:05 nas kernel: python[7062]: segfault at 4 ip 08099572 sp b518cf70 error 4 in python[8048000+11f000] (Errors)

 

some other python stuff in the logs:

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/library/hachoir_core/error.py (Errors)

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/library/transmissionrpc/error.py (Errors)

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/library/transmissionrpc/error.pyc (Errors)

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/cherrypy/_cperror.pyc (Errors)

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/cherrypy/_cperror.py (Errors)

 

any ideas?  Thanks in advance.

When it crashes run free -m to see how your memory looks, such as if its full. How much ram do you have? Install and data directories for all three?

 

The segfault means a memory error, if you have plenty of free memory when Sab crashes I'd run memtest overnight to check your ram. I think this is the most likely culprit. Have you added any addons recently?

Thanks for the reply!  I have 4GB of ram and only those 3 apps running so I assume plenty of RAM.  Have not changed my setup since day 1 really. (no new addons).

 

That being said, I ran a free -m right now while Sab is running, and it looks like I barely have any memory free?

 

 

root@nas:~# free -m

                          total      used      free    shared    buffers    cached

Mem:                  3796      3589        206          0        152      3088

-/+ buffers/cache:              349      3447

 

Might try posting this on the sabnzbd.org forums....

 

Myk

 

 

SabNZBD has been running flawlessly for 6 months until recently.  I will not be able to hit the url and when I do a ps aux | grep python I do not see it running.  I manually kick it off again only to have it crap out a few hours later.  My other python apps continue to run fin (couchpotato and sickbeard)  Only thing I see in the syslog is:

 

Sep 10 12:06:05 nas kernel: python[7062]: segfault at 4 ip 08099572 sp b518cf70 error 4 in python[8048000+11f000] (Errors)

 

some other python stuff in the logs:

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/library/hachoir_core/error.py (Errors)

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/library/transmissionrpc/error.py (Errors)

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/library/transmissionrpc/error.pyc (Errors)

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/cherrypy/_cperror.pyc (Errors)

Sep 10 03:52:28 nas logger: ./.custom/couchpotato/cherrypy/_cperror.py (Errors)

 

any ideas?  Thanks in advance.

It's probably the version of python you're using. If you installed SickBeard/CP/SabNZBD via plugins, it should be fine. However, if you did a mixture of plugins/manual installation (aka go script, fixed directories), the dependencies in the manual installation may conflict with the python version that the plugins installs.

Hey thanks for the reply, all manual via go script and havent changed a thing since the beginning.  No new python or dependencies...seems odd it would just now start crapping out.

Your memory usage is fine. The used memory includes memory used for cache, which is released  when needed by other programs.

 

That being said, I would shutdown unraid and boot back up choosing memtest instead of unraid, let memtest run overnight, check back in the morning to see how your memory did and how many errors you get. If you are relatively error free then time to troubleshoot elsewhere.

 

Do you run cache_dirs by any chance? If so, and your memtest comes back clean, try disabling cache_dirs and see if the issue goes away.

Thanks for the linux memory lesson Influencer! 

 

So I ran the Memtest, came back squeaky clean.

 

I do not run cache_dirs.

 

Any other ideas?  Possible bad cache drive?  I may just take this opportunity to install 5.0.  I have not really had a reason to since everything has been working how I wanted for so long.  Maybe this is the push I need...

I actually can't find any sort of feedback from Sab or the OS.

 

Do you know exactly where I should be looking?