-----Original message----- > From:Mark Miller <markrmil...@gmail.com> > Sent: Wed 24-Oct-2012 01:33 > To: solr-user@lucene.apache.org > Subject: Re: Failure to open existing log file (non fatal) > > Why the process died, I cannot say. Seems like the world of guesses is > just too large :) If there is nothing in the logs, it's likely a the > OS level? But if there are no dump files or evidence of it in system > logs, I don't even know where to start.
Me neither, perhaps it was cosmic radiation, i'll keep digging. > > All I can help with is that the exception is an expected possibility > after a Solr crash (on the next startup). Yes, the node recovered itself in the minutes after the exception and continued to run fine. At least other users can now google for the error and ignore it for now. Thanks! > > - Mark > > On Tue, Oct 23, 2012 at 6:48 PM, Markus Jelsma > <markus.jel...@openindex.io> wrote: > > Hi, > > > > I checked the logs and it confirms the error is not fatal, it was logged > > just a few seconds before it was restarted. The node runs fine after it was > > restarted but logged this non fatal error replayed the log twice. This > > leaves the question why it died, there is no log of it dying anywhere. We > > don't recover rsyslogd so it was running all the time and there is no > > report of an OOM-killer there. > > > > Any more thoughts to share? > > > > Thanks > > Markus > > > > > > -----Original message----- > >> From:Chris Hostetter <hossman_luc...@fucit.org> > >> Sent: Wed 24-Oct-2012 00:38 > >> To: solr-user@lucene.apache.org > >> Subject: Re: Failure to open existing log file (non fatal) > >> > >> > >> : Perhaps we can improve the appearance of this - but it's expected to > >> happen in crash cases. > >> > >> in case it wasn't clear: there's no indication that this "Failure to open > >> existing log file" *caused* any sort of crash -- it comes from the > >> initialization code of the UpdateHandler when a SolrCore is being created > >> as part of Solr startup. > >> > >> So this is an error that was definitely logged after tomcat was restarted. > >> > >> : > It seem the error is more fatal than the error tells me, the indexing > >> : error and the exception happened within a few seconds of eachother. Any > >> : ideas? Existing issue? File bug? > >> > >> > >> -Hoss > >> > > > > -- > - Mark >
