Agreed. Good enough.
On Tue, Feb 23, 2016 at 12:23 PM, Michael Mior <[email protected]> wrote: > Assuming you have these automated, you could add in a restart of the VM. > Obviously not ideal, but it seems that solves the problem for now. > On Feb 23, 2016 14:24, "Julian Hyde" <[email protected]> wrote: > >> Ok, let's monitor this situation. It's not fatal, because we can still >> run the test suite. But it is inconvenient because my nightly tests >> will generate some false negatives. >> >> On Tue, Feb 23, 2016 at 11:14 AM, Michael Mior <[email protected]> wrote: >> > Unfortunately I think I may have been bitten with this as well. I can't >> be >> > sure, but I believe I left the Cassandra instance in the VM running but I >> > went to use it a couple days later and it had died. Also no signs of any >> > issue in the logs. Fortunately restarting the daemon seems to have gotten >> > things going again without any issue. (I didn't have to restart the VM.) >> > >> > -- >> > Michael Mior >> > [email protected] >> > >> > 2016-02-23 14:11 GMT-05:00 Julian Hyde <[email protected]>: >> > >> >> There doesn't seem to be anything in /var/log/cassandra or >> >> /var/lib/cassandra. I'll check next time there's a failure. >> >> >> >> On Tue, Feb 23, 2016 at 10:54 AM, Vladimir Sitnikov >> >> <[email protected]> wrote: >> >> > Does it leave some logs behind? >> >> > >> >> > For instance: regular java "stdout" logs or some hs_err_pid file. >> >> > >> >> > Blind guess would be "old JRE + random JIT/GC bug == sigsegv". >> >> > >> >> > Vladimir >> >> >>
