sabnzbd 0.4.5 suddenly stops responding

[SuperSnackman]

Hiya,

I am using sabnzbd on a linux machine. I only use it for a few days so I can't say this is a new problem or not. It downloads fine, but after some time it suddenly stops responding on the webif, and it doesn't process my NZB-folder anymore.

I looked in the log files, but I can't see anything particular in it. The last two crashes happened while 'playing' with the web interface, but the last crash happened while it was just downloading. As far as I can see the downloads are still running, it just 'shuts down' the web interface, and stops reading my NZB folder. 3 crashes in less than 24 hours time is way too much I think.

Anyone else here with similiar problems? Are there known issues with some python versions? I use 2.5.1.
Browsing the forum I found some similar problems. Something with SSL, but I don't use SSL. And something about problems with BIG NZB-files. I am currently downloading something with a nine megabytes NZB-file, could this be the problem?

Thanks for your response...

Update: I stopped downloading from the big NZB file and everything seems to respond a lot faster now. I'll post a new update is there is no crash in the next 12 hours

New update: after parring my latest download, the web interfaces stopped responding. And it doesn't start unpacking my download

[sander]

Some questions / remarks:

Does SAB crash (and thus quit), or does it just stop responding? Check with "ps -ef | grep sabnzbd".
Is the webinterface still responding?
Do you run SAB from the commandline? If so, there must be output. Can you post it here?
A 7 MB NZB?! What are you downloading? A 25 GB file? Where do you get your NZBs from? Do smaller NZBs come in OK?
Your Python 2.5.1 seems OK.

[SuperSnackman]

Some questions / remarks:

Does SAB crash (and thus quit), or does it just stop responding? Check with "ps -ef | grep sabnzbd".
Is the webinterface still responding?
Do you run SAB from the commandline? If so, there must be output. Can you post it here?
A 7 MB NZB?! What are you downloading? A 25 GB file? Where do you get your NZBs from? Do smaller NZBs come in OK?
Your Python 2.5.1 seems OK.

I decided not to restart SAB since the last 'crash'. It looks like it steel keeps running and downloading. The only thing is that the web interface is not accessible anymore. I still can connect to the webserver, I just don't get any data. I run SAB as a daemon. The log-files show that it is still downloading. I was downloading 48gb of rar-files. I get my NZB-files from a dutch website: nzbindex.nl .
As far as I can see it is now busy parring and repairing my latest download. The log-files are still filling up, but the error-log is empty.

I am running SAB on a NAS called 'Kurobox'.  It is a very small computer with a minimum amount of memory and a very slow processor (128mb ram, 266mhz powerpc). So I think that has something to do with it too.

Update: after several hours it finished parring + unrarring. The end result is ok, and I even got the email saying 'job done!'. Unfortunately the webif is still not respondig. It is still busy doing a new job. Also it doesn't pick up a new NZB-file in the scan folder.

Could this be a problem with the priority given to the builtin webserver? Does the webserver has its own log file?

[shypike]

You need to scale down to minimum memory usage.
No memory cache.
Avoid extremely large NZB files.
Don't create a large queue (above 25 jobs).

It does help if you can create a swap partition.

We are planning on lowering memory usage.
But we still have a long way to go.

[SuperSnackman]

What do you mean with 'no memory cache'.  I do have swap memory:

Output from TOP

Mem:    127400K total,  125544K used,    1856K free,      152K buffers
Swap:  530136K total,  137772K used,  392364K free,    3488K cached

[shypike]

Memory cache is this:
http://sabnzbd.wikidot.com/configure-general
Item: Article Cache Limit

[SuperSnackman]

That was already disabled. I also limited my download speed to 500kb/sec - just for the sake of it. I restarted my machine. After going for 30 minutes the web interface stops responding again!