cgminer just stopped for me sometime last night... This was the start of a long set of logs at this time:
I can post all the rest if needed, but figured I would start with the above.
Yep you really have run out of ram. The only time I've seen cgminer itself waste lots of ram is when people have the submit-stale feature enabled and it caches lots of old work and keeps trying to submit them for extensive outages, creating more and more network threads since there is no upper limit to how long it will hold onto this work and try repeatedly to send them. I guess I should make them all time out and give up in a future version. I don't ever suggest using the submit-stale feature and I also recommend enabling the --net-delay feature. Why does the submit stale feature exist then? Because people asked for it. Nowadays it's redundant in my opinion. Code:
Mar 16 04:10:40 skynet kernel: [13242.684124] cgminer invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
Mar 16 04:10:40 skynet kernel: [13242.684129] cgminer cpuset=/ mems_allowed=0
Mar 16 04:10:40 skynet kernel: [13242.684133] Pid: 4022, comm: cgminer Tainted: P C 2.6.32-5-686 #1
Mar 16 04:10:40 skynet kernel: [13242.684135] Call Trace:
Mar 16 04:10:40 skynet kernel: [13242.684143] [] ? oom_kill_process+0x60/0x201
Mar 16 04:10:40 skynet kernel: [13242.684148] [] ? __out_of_memory+0xf4/0x107
I can post all the rest if needed, but figured I would start with the above.
But it seemed cgminer was the only thing affected. Other things I checked on the server were still running (web server/sshd).