You need to find the solr.log file and examine it. What this usually means is that something's wrong with, say, your Solr configs. You should see a more informative message in the Solr log, usually it's a stack trace.
You say that your start "seems to complete successfully". That implies that you were prompted for things like how many Solr instances you wanted to start, a base configset, the name of your collection and the like. Did all that occur? Best, Erick On Mon, Nov 28, 2016 at 8:07 PM, James Muerle <jmue...@ixl.com> wrote: > Hello, > > I am very new to Solr, and I'm excited to get it up and running on amazon > ec2 for some prototypical testing. So, I've installed solr (and java) on > one ec2 instance, and I've installed zookeeper on another. After starting > the zookeeper server on the default port of 2181, I run this on the solr > instance: "opt/solr/bin/solr start -c -z "<ec2addresshiddenbyme>. > us-west-2.compute.amazonaws.com/solr"", which seems to complete > successfully: > > Archiving 1 old GC log files to /opt/solr/server/logs/archived > Archiving 1 console log files to /opt/solr/server/logs/archived > Rotating solr logs, keeping a max of 9 generations > Waiting up to 180 seconds to see Solr running on port 8983 [|] > Started Solr server on port 8983 (pid=13038). Happy searching! > > But then when I run "/opt/solr/bin/solr status", I get this output: > > Found 1 Solr nodes: > > Solr process 13038 running on port 8983 > > ERROR: Failed to get system information from http://localhost:8983/solr due > to: org.apache.http.client.ClientProtocolException: Expected JSON response > from server but received: <html> > <head> > <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> > <title>Error 500 Server Error</title> > </head> > <body><h2>HTTP ERROR 500</h2> > <p>Problem accessing /solr/admin/info/system. Reason: > <pre> Server Error</pre></p><h3>Caused > by:</h3><pre>org.apache.solr.common.SolrException: Error processing the > request. CoreContainer is either not initialized or shutting down. > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:263) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:254) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:518) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) > at java.lang.Thread.run(Thread.java:745) > </pre> > > </body> > </html> > > Typically, this indicates a problem with the Solr server; check the Solr > server logs for more information. > > > I don't quite understand what things could be causing this problem, so I'm > really at a loss at the moment. If you need any additional information, I'd > be glad to provide it. > > Thanks for reading! > James
