![](https://seccdn.libravatar.org/avatar/b4047644c59f2d63b88e9464c02743fd.jpg?s=120&d=mm&r=g)
On 04/14/2016 08:23 AM, Christopher Myers wrote:
We had that happen with a server once, and what we ended up doing was leaving it logged in as root and running with the console 10 screen up (ctrl+alt+F10.) That way we could see what the last messages were when it hung.
Turned out that the server would randomly spike up in memory usage on a particular process, and would run out of memory, but it wouldn't log anything to the logs about that. So after adding more memory, all was fine and dandy :)
Chris
You would see that happening. It wouldn't be a sudden freeze. Your drive would be thrashing madly, your swap would be filling, and if it couldn't handle an allocate call, something would crash. It would slowly freeze, but some thing would still work. Capslock, numlock would still indicate proper state as you pressed those keys, etc. Memory usage spikes are not random. There was some other underlying problems. Adding memory is just kicking that can down the road a ways. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org