Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: <CAA70BoWLBSXF-+t9d4Ou_+q773==fd1pM=ug1Gh=_FoSLSRcjg@mail.gmail.com>
References: <CAA70BoWLBSXF-+t9d4Ou_+q773==fd1pM=ug1Gh=_FoSLSRcjg@mail.gmail.com>
From: Chetas Joshi <chetas.joshi@gmail.com>
Date: Fri, 19 May 2017 16:05:15 -0700
Message-ID: <CAA70BoXmaist5_rf4eoV7cfAETLMR0gG76D5y1_B_3+AmBt0-w@mail.gmail.com>
Subject: Re: Solr coreContainer shut down
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary="94eb2c06aabceb6029054fe88d2a"
archived-at: Fri, 19 May 2017 23:05:27 -0000

--94eb2c06aabceb6029054fe88d2a
Content-Type: text/plain; charset="UTF-8"

I found the reason why this is happening!
I am using chef and running install_sol_service.sh with option -n -f. So,
every time chef-client runs it is stopping the already running solr
instance. Now, I have removed option -f (no upgrade) but running into an
error.

I have a question on the following peice of code.

if [ ! "$SOLR_UPGRADE" = "YES" ]; then

  if [ -f "/etc/init.d/$SOLR_SERVICE" ]; then

    print_usage "/etc/init.d/$SOLR_SERVICE already exists! Perhaps Solr is
already setup as a service on this host? To upgrade Solr use the -f option."

    exit 1

  fi


  if [ -e "$SOLR_EXTRACT_DIR/$SOLR_SERVICE" ]; then

    print_usage "$SOLR_EXTRACT_DIR/$SOLR_SERVICE already exists! Please
move this directory / link or choose a different service name using the -s
option."

    exit 1

  fi

fi


If I don't wanna upgrade and there is an already installed service, why
should it be exit 1 and not exit 0? Shouldn't it be like....

if [ ! "$SOLR_UPGRADE" = "YES" ]; then

  if [ -f "/etc/init.d/$SOLR_SERVICE" ]; then

    print_usage "/etc/init.d/$SOLR_SERVICE already exists! Perhaps Solr is
already setup as a service on this host? To upgrade Solr use the -f option."

    *exit 0*

  fi


Thanks!

On Fri, May 19, 2017 at 1:59 PM, Chetas Joshi <chetas.joshi@gmail.com>
wrote:

> Hello,
>
> I am trying to set up a solrCloud (6.5.0/6.5.1). I have installed Solr as
> a service.
> Every time I start solr servers, they come up but one by one the
> coreContainers start shutting down on their own within 1-2 minutes of their
> being up.
>
> Here are the solr logs
>
> 2017-05-19 20:45:30.926 INFO  (main) [   ] o.e.j.s.Server Started @1600ms
>
> 2017-05-19 20:47:21.252 INFO  (ShutdownMonitor) [   ]
> o.a.s.c.CoreContainer Shutting down CoreContainer instance=1364767791
>
> 2017-05-19 20:47:21.262 INFO  (ShutdownMonitor) [   ] o.a.s.c.Overseer
> Overseer (id=169527934494244988-<HOST>:8983_solr-n_0000000006) closing
>
> 2017-05-19 20:47:21.263 INFO  (OverseerStateUpdate-169527934494244988-
> <HOST>:8983_solr-n_0000000006) [   ] o.a.s.c.Overseer Overseer Loop
> exiting : <HOST>:8983_solr
>
> 2017-05-19 20:47:21.268 INFO  (ShutdownMonitor) [   ]
> o.a.s.m.SolrMetricManager Closing metric reporters for: solr.node
>
>
> The coreContainer just shuts down (no info in the solr logs). Is the jetty
> servlet container having some issue? Is it possible to look at the Jetty
> servlet container logs?
>
> Thanks!
>

--94eb2c06aabceb6029054fe88d2a--