Happened again today. Solr stopped running. Apache hasn't stopped in 10
days, so this is not due to a server reboot.

Solr is not being run with the oom-killer.  And when I grep for ERROR in
the logs, there is nothing from today.

On Mon, May 18, 2020 at 3:15 PM James Greene <ja...@jamesaustingreene.com>
wrote:

> I usually do a combination of grepping for ERROR in solr logs and checking
> journalctl to see if an external program may have killed the process.
>
>
> Cheers,
>
> /************************************
> *       James Austin Greene
> *  www.jamesaustingreene.com
> *              336-lol-nerd
> ************************************/
>
>
> On Mon, May 18, 2020 at 1:39 PM Erick Erickson <erickerick...@gmail.com>
> wrote:
>
> > ps aux | grep solr
> >
> > on a *.nix system will show you all the runtime parameters.
> >
> > > On May 18, 2020, at 12:46 PM, Ryan W <rya...@gmail.com> wrote:
> > >
> > > Is there a config file containing the start params?  I run solr like...
> > >
> > > bin/solr start
> > >
> > > I have not seen anything in the logs that seems informative. When I
> grep
> > in
> > > the logs directory for 'memory', I see nothing besides a couple entries
> > > like...
> > >
> > > 2020-05-14 13:05:56.155 INFO  (main) [   ]
> > o.a.s.h.a.MetricsHistoryHandler
> > > No .system collection, keeping metrics history in memory.
> > >
> > > I don't know what that entry means, though the date does roughly
> coincide
> > > with the last time solr stopped running.
> > >
> > > Thank you.
> > >
> > >
> > > On Mon, May 18, 2020 at 12:00 PM Erick Erickson <
> erickerick...@gmail.com
> > >
> > > wrote:
> > >
> > >> Probably, but check that you are running with the oom-killer, it'll be
> > in
> > >> your start params.
> > >>
> > >> But absent that, something external will be the culprit, Solr doesn't
> > stop
> > >> by itself. Do look at the Solr log once things stop, it should show if
> > >> someone or something stopped it.
> > >>
> > >> On Mon, May 18, 2020, 10:43 Ryan W <rya...@gmail.com> wrote:
> > >>
> > >>> I don't see any log file with "oom" in the file name.  Does that mean
> > >> there
> > >>> hasn't been an out-of-memory issue?  Thanks.
> > >>>
> > >>> On Thu, May 14, 2020 at 10:05 AM James Greene <
> > >> ja...@jamesaustingreene.com
> > >>>>
> > >>> wrote:
> > >>>
> > >>>> Check the log for for an OOM crash.  Fatal exceptions will be in the
> > >> main
> > >>>> solr log and out of memory errors will be in their own -oom log.
> > >>>>
> > >>>> I've encountered quite a few solr crashes and usually it's when
> > >> there's a
> > >>>> threshold of concurrent users and/or indexing happening.
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Thu, May 14, 2020, 9:23 AM Ryan W <rya...@gmail.com> wrote:
> > >>>>
> > >>>>> Hi all,
> > >>>>>
> > >>>>> I manage a site where solr has stopped running a couple times in
> the
> > >>> past
> > >>>>> week. The server hasn't been rebooted, so that's not the reason.
> > >> What
> > >>>> else
> > >>>>> causes solr to stop running?  How can I investigate why this is
> > >>>> happening?
> > >>>>>
> > >>>>> Thank you,
> > >>>>> Ryan
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> >
>

Reply via email to