Downloads get stuck about half way

[sander]

Good to hear, and good to know. I think swap is essential if you have little RAM. Can you post the output of "cat /proc/swaps"?

Oh: what happens when you run SAB on your 128MB RAM system *without* swap enabled? (A 'swapoff' should help, I guess ;-) )

Maybe I should write some code so that SABnzbd presents available RAM and Swap (and not just SAB's usage of memory)

[hanker]

Good to hear, and good to know. I think swap is essential if you have little RAM. Can you post the output of "cat /proc/swaps"?

Oh: what happens when you run SAB on your 128MB RAM system *without* swap enabled? (A 'swapoff' should help, I guess ;-) )

Maybe I should write some code so that SABnzbd presents available RAM and Swap (and not just SAB's usage of memory)

Here is the output of cat /proc/swaps:

Code: Select all

$ cat /proc/swaps
Filename       Type          Size          Used          Priority
/dev/sda2      partition     1023612       42496         -1

So you see it's using more swap than it was when I posted earlier today.

BTW, this is a 24/7 production machine, so I'm hesitant to turn the swap off

But I would imagine that when some process requested more memory than the system could supply, it would make that process crash. Anyway, sab and sickbeard run totally rock solid on this little $25 appliance, which BTW has no local storage other than the boot flash drive. All hard disks are accessed by NFS. No problem at all.

[sander]

My VPS runs SABnzbd very well, and has the following information:

Code: Select all

sander@toverdoos:~$ cat /proc/swaps
Filename                                Type            Size    Used    Priority
/dev/xvda2                              partition       524284  85252   -1

sander@toverdoos:~$ cat /proc/meminfo | head -2
MemTotal:         243264 kB
MemFree:           26376 kB
sander@toverdoos:~$

Of course this is static information, so displaying it all the time is not so useful. Maybe just an alert at startup if Ram + Swap is very low.