Your solr logs on that node will probably give you a better idea of what the root cause is.
best, Erick > On Feb 24, 2020, at 8:18 AM, Sotiris Fragkiskos <sfra...@gmail.com> wrote: > > Hi all! > I had a cluster with 2 solr nodes, and a single zk host and it all worked > fine. > Then we got 3 more VMs, so i configured them *in parallel* to the *exact* > same configuration, so that they can be added to the existing cluster. > 2 of them connected fine, and the third just refuses to. > I can see it in the solr cloud, but cpu and heap have empty "%" sings next > to them. > When doing service solr status, the error I get is > > ERROR: Failed to get system information from http://***.***.**.**:8983/solr > due to: org.apache.solr.common.SolrException: Parse error : <html> > <head> > <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> > <title>Error 404 Not Found</title> > </head> > <body><h2>HTTP ERROR 404</h2> > <p>Problem accessing /solr/admin/info/system. Reason: > <pre> Not Found</pre></p><h3>Caused > by:</h3><pre>javax.servlet.ServletException: > javax.servlet.UnavailableException: Error processing the request. > CoreContainer is either not initialized or shutting down. > > Any idea what this is? > > Thanks in advance! > > Sotiri
