Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've configured a sample Apache Solr 4.1 installation using this tutorial. The sample http://localhost:8090/solr (changed the port in server.xml) worked and redirected me to http://localhost:8090/solr/admin with some output. Now, I've upgraded to Solr 4.3 by stopping tomcat6, removing /var/lib/tomcat6/webapps/solr.war and solr, replacing the solr.war with the new one. After starting tomcat6, /var/lib/tomcat6/webapps/solr gets recreated. However, http://localhost:8090/solr now throws a 404.

HTTP Status 404 - /
type Status report
message /
description The requested resource () is not available.
Apache Tomcat/6.0.35

It is strange, that it shows no paths, but only when I try to reach something in /solr. When I type in something random, the paths show up correctly in the 404, so something seems to be done by tomcat, but it is not correct.

share|improve this question
up vote 2 down vote accepted

i ran into a similar problem, it has somthing to do with this: "Slf4j/logging jars are no longer included in the Solr webapp."

you have to do the same as here:

in your case probably: copy all files from example/lib/ext/ to /var/lib/tomcat6/lib/ (lib most likely doesn't exist, so create it)

share|improve this answer
My god, why isn't this documented anywhere. Will test it, thanks! – SebiF May 23 '13 at 14:16

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.