On 5/24/2013 11:14 AM, srinalluri wrote: > I am unable to setup solr4. I am getting this error: HTTP Status 503 - > Server is shutting down. I don't see anything in tomcat logs. > > conf/Catalina/localhost\solr4new.xml: > > <?xml version="1.0" encoding="utf-8"?> > <Context docBase="/apps/solr1/solr4new/solr.war" debug="0" > crossContext="true"> > <Environment name="solr/home" type="java.lang.String" > value="/apps/solr1/solr4new" override="true"/> > </Context> > > /apps/solr1/solr4new/: > |-- bin > |-- collection1 > | |-- conf > | | |-- lang > | | |-- velocity > | | `-- xslt > | `-- data > `-- logs
Which exact 4.x version are you trying? Version 4.2.1 and earlier will generally log to tomcat's log, which is probably actually a result of tomcat intercepting java.util.logging calls. These versions include slf4j jars in the .war file that bind to java.util.logging. Version 4.3.0 aims for complete logging flexibility. To get that, it includes no logging jars in the .war file. You have to provide them. They are included in the 4.3 example in the lib/ext folder for jetty. The included jars bind slf4j to log4j, and the example also provides a log4j.properties file to configure log4j. If you don't include any of the required slf4j jars, Solr will fail to start, though the error should be logged by your servlet container. If you copied the jars from lib/ext into tomcat's lib directory, then Solr will start. By default, you won't get any logging, unless you provide a log4j configuration file (usually log4j.properties), and either put it in the classpath or explicitly tell log4j how to find it. There is more info here, but this page still needs a fair amount of work: http://wiki.apache.org/solr/SolrLogging Thanks, Shawn
