Assuming you are running on Linux, you might want to check /var/log/messages too (the location might vary), I think the kernel logs forced process termination there. I recall that the kernel will usually picks the process consuming the most memory, there may be other factors involved too.
François On Aug 2, 2011, at 9:04 AM, wakemaster 39 wrote: > Monitor your memory usage. I use to encounter a problem like this before > where nothing was in the logs and the process was just gone. > > Turned out my system was out odd memory and swap got used up because of > another process which then forced the kernel to start killing off processes. > Google OOM linux and you will find plenty of other programs and people with > a similar problem. > > Cameron > On Aug 2, 2011 6:02 AM, "alexander sulz" <a.s...@digiconcept.net> wrote: >> Hello folks, >> >> I'm using the latest stable Solr release -> 3.3 and I encounter strange >> phenomena with it. >> After about 19 hours it just crashes, but I can't find anything in the >> logs, no exceptions, no warnings, >> no suspicious info entries.. >> >> I have an index-job running from 6am to 8pm every 10 minutes. After each >> job there is a commit. >> An optimize-job is done twice a day at 12:15pm and 9:15pm. >> >> Does anyone have an idea what could possibly be wrong or where to look >> for further debug info? >> >> regards and thank you >> alex
