Ah neat, I didn't know the dmesg command…that works great. Dean
From: Franc Carter <franc.car...@sirca.org.au<mailto:franc.car...@sirca.org.au>> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Date: Wednesday, September 18, 2013 6:45 AM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: cassandra just gone..no heap dump, no log info A random guess - possibly an OOM (Out of Memory) where Linux will kill a process to recover memory when it is desperately low on memory. Have a look in either your syslog output of the output of dmesg cheers On Wed, Sep 18, 2013 at 10:21 PM, Hiller, Dean <dean.hil...@nrel.gov<mailto:dean.hil...@nrel.gov>> wrote: Anyone know how to debug cassandra processes just exiting? There is no info in the cassandra logs and there is no heap dump file(which in the past has shown up in /opt/cassandra/bin directory for me). This occurs when running a map/reduce job that put severe load on the system. The logs look completely fine. I find it odd 1. No logs of why it exited at all 2. No heap dump which would imply there would be no logs as it crashed Is there any other way a process can die and linux would log it somehow? (like running out of memory) Thanks, Dean -- Franc Carter| Systems architect|Sirca Ltd <mailto:marc.zianideferra...@sirca.org.au> franc.car...@sirca.org.au<mailto:franc.car...@sirca.org.au> | www.sirca.org.au<http://www.sirca.org.au/> Tel: +61 2 8355 2514 Level 4, 55 Harrington St, The Rocks NSW 2000 PO Box H58, Australia Square, Sydney NSW 1215
