SABNZB quits??

[pkarza]

I've been using unraid for some time now - with Sickbeard, SABNZB, plex media server, and couchpotato.

 

Lately SABNZB quits, from time to time....  has anyone else had this problem??  It was working without a hitch for over a year... now this has started.

 

I hope this is the right area to ask.

 

Thanks for your help in advance.

[Helmonder]

What does `quits` mean ?

 

Does it stop downloading ?

Does it stop responding ?

Is the process terminated ?

 

What does your syslog show ?

 

[pkarza]

Quits -

 

Stops... becomes unresponsive.  I have to restart on the main page on settings to get it working again.

 

This is bizarre - Sickbeard works flawlessly

[hooger]

I am getting this same error randomly too.  I just keep restarting from the settings menu.

[Benni-chan]

need more info...

which unraid version are you using? which plugin? (unplugged v5 plugin or unmenu or something else)

 

is there anything in your logs? (syslog and sabnzbd logfile)

 

sorry, but without more infos, it would be a (very) lucky guess...

[Helmonder]

Is it unresponsive or is the process stopped ?

[pkarza]

version 5 beta 14 -

 

Nothing in the logs - the log is long and I can post if you want but I have gone through it.

 

I wonder if I upgrade if that will fix things?

 

... yes... it just stops - and the gui goes too - asking me to reload and nothing is there until I restart

[Helmonder]

Anything in the logs referring to OOM ?

[pkarza]

No oom in the log - the box it is in has 1 gb men - isn't that enough?

[Benni-chan]

what is your configuration for sabnzbd and the other plugins? installdir/datadir. (tmp dir for plex)

 

a syslog could help. i also think, that your system runs out of memory. 1 GB is a bit small for running lots of plugins.

[neilt0]

You can't run SABnzbd and cache_dirs with 1GB if you are caching a reasonable number of folders.

[hooger]

So it happened again, so I checked the log and got this:

 

Dec 11 14:57:33 Tower kernel: [ 6463] 999 6463 18903 10997 1 0 0 Plex Media Scan
Dec 11 14:57:33 Tower kernel: [ 7353] 999 7353 35121 5667 1 0 0 python
Dec 11 14:57:33 Tower kernel: [ 7452] 999 7452 42848 7733 1 0 0 python
Dec 11 14:57:33 Tower kernel: [ 7498] 999 7498 34433 5204 1 0 0 python
Dec 11 14:57:33 Tower kernel: [ 7531] 999 7531 34708 5249 1 0 0 python
Dec 11 14:57:33 Tower kernel: [ 7570] 999 7570 35427 6247 0 0 0 python
Dec 11 14:57:33 Tower kernel: Out of memory: Kill process 3619 (python) score 232 or sacrifice child
Dec 11 14:57:33 Tower kernel: Killed process 3619 (python) total-vm:750744kB, anon-rss:468580kB, file-rss:3744kB

 

It says its out of memory, but I have 2GB and never had this problem before until recently.

 

Edit: Sabs install is in the local folder, and the data folder is in the cache drive.  All downloads go to a user share which is cache only, then get sorted by SickBeard, and CouchPotato.  I'm assuming Plex is the problem, but I've used it for awhile now with no problems.  However I guess I did update it recently. (plex temp and library are on cache too)

[Benni-chan]

which plugin do you have installed? do you use cache dirs?

how are the plugins configured?

[Helmonder]

So it happened again, so I checked the log and got this:

 

Dec 11 14:57:33 Tower kernel: [ 6463] 999 6463 18903 10997 1 0 0 Plex Media Scan
Dec 11 14:57:33 Tower kernel: [ 7353] 999 7353 35121 5667 1 0 0 python
Dec 11 14:57:33 Tower kernel: [ 7452] 999 7452 42848 7733 1 0 0 python
Dec 11 14:57:33 Tower kernel: [ 7498] 999 7498 34433 5204 1 0 0 python
Dec 11 14:57:33 Tower kernel: [ 7531] 999 7531 34708 5249 1 0 0 python
Dec 11 14:57:33 Tower kernel: [ 7570] 999 7570 35427 6247 0 0 0 python
Dec 11 14:57:33 Tower kernel: Out of memory: Kill process 3619 (python) score 232 or sacrifice child
Dec 11 14:57:33 Tower kernel: Killed process 3619 (python) total-vm:750744kB, anon-rss:468580kB, file-rss:3744kB

 

It says its out of memory, but I have 2GB and never had this problem before until recently.

 

Edit: Sabs install is in the local folder, and the data folder is in the cache drive.  All downloads go to a user share which is cache only, then get sorted by SickBeard, and CouchPotato.  I'm assuming Plex is the problem, but I've used it for awhile now with no problems.  However I guess I did update it recently. (plex temp and library are on cache too)

 

That is OOM (Out of Memory) Your system is running out of memory and it is terminating the processes it thinks are best getting killed. Check out the following thread for background and solution, but in basis you should also increase memory, its not very expensive these days..

 

 

http://lime-technology.com/forum/index.php?topic=22971.0

 

 

[iansolway]

I'm having this exact same problem, I have managed to link it slightly to Nzbmatrix and couchpotato. Since NZBMatrix finished I'm using free nzbsearches, i think this is causing sabnzbd to become very labour intensive with unpacking and repairing certain movies, if i run sickbeard and sabnzbd i dont get any problems, if i run couchpotato i get no problems, but if couchpotato sends unreliable NZBs to sabnzbd then i get the same error your finding. I may be wrong but this is the only conclusion i can come up with. somebody with more knowledge maybe able to correct me 

[Helmonder]

the combination with nzbmatrix is hard to see... you do not download from an indexer but from your nntp provider..

[iansolway]

Yeah i see what your saying but could it be that nzbmatrix was indexing more reliable files, than some of the free options and this in turn causing more repairs to files. the only other reason i can come up with for this error would be i changed the cache drive to an old drive i had, maybe this is failing, could this cause a low memory error??

[Helmonder]

Possible whenever your memory situation was allready quite critical.. Not much to do if you have allready done the standard stuff:

 

- pause downloading while unpacking;

- download top down