CODEWITHSUNDEEP
solrjettyhttp-status-code-404
kshama
kshama

Reputation: 1627

HTTP ERROR: 404 missing core name in path with solr

I am new to Solr. After installing it in ubuntu 8.10, when I was following the example to index as per this link, I got this error in Jetty:

HTTP ERROR: 404 missing core name in path

What should I do to solve this?

Upvotes: 38

Views: 58314

Answers (10)

H6_
H6_

Reputation: 32808

I had gotten the same error:

HTTP ERROR: 404 missing core name in path

In my case, I forgot to set the solr/home value in the WEB-INF/web.xml file.

<env-entry>
   <env-entry-name>solr/home</env-entry-name>
   <env-entry-value>/put/your/solr/home/here</env-entry-value>
   <env-entry-type>java.lang.String</env-entry-type>
</env-entry>

After I added the above code and restarted the server, the error was gone.

Upvotes: 19

szydan
szydan

Reputation: 2596

Hi I've got exactly this error when my solrconfig.xml was malformed (missing closing tag element ). It was for solr 3.5.0 Once I fixed the solrconfig the error went away.

Upvotes: 0

Alexandru Pupsa
Alexandru Pupsa

Reputation: 1868

My problem was in Tomcat Installed Dir\conf\Catalina\localhost\solr.xml

<Context docBase="C\:\\Program Files\\Apache Software Foundation\\Tomcat 6.0\\webapps\\solr" debug="0" crossContext="true" >
   <Environment name="solr/home" type="java.lang.String" value="D:\\workspace\\common\\src\\test\\resources\\solr\\cores" override="true" />
</Context>

The cores folder path was wrong for me, as I moved the workspace from one machine to another.

Upvotes: 0

Dawe7
Dawe7

Reputation: 11

I'm not use SolrCores, but:

After installing new solr version, I got error "HTTP ERROR: 404 missing core name in path" And http://xxx:8080/solr-tour/admin/cores was empty. (If you don't use solrCore, 1 entry is here normally)

I must stop tomcat, delete his localfiles, and start again

/etc/init.d/tomcat5 stop
rm -rf /usr/share/tomcat5/work/Catalina/localhost/*
rm -rf /usr/share/tomcat5/webapps/*
rm -rf /usr/share/tomcat5/logs/*
/etc/init.d/tomcat5 start

Upvotes: 1

Pierco
Pierco

Reputation: 79

In my case, it was happening due to a previous installation of Solr. So I had to delete my old core directory: 

rm -rf /var/lib/solr/mycorename

then recreate the directory with correct permissions: 

sudo mkdir -p /var/lib/solr/mycorename/data
sudo chown -R jetty:jetty /var/lib/solr/mycorename/data

Upvotes: 3

Bhaskar
Bhaskar

Reputation: 1

In my case it was happening due to versioning.

Earlier I was using solr 1.4.1. It was running fine. Then I installed solr 3.6.1 and was getting this error.

A folder named solr is there in the tomcat/webapps directory where you generally put the solr.war file.

  • Delete this solr folder
  • Start tomcat

=> Problem is gone.

Upvotes: 0

mydoghasworms
mydoghasworms

Reputation: 18591

For me the problem was deeper, as I had not set up Solr correctly to begin with.

I followed the instructions here: http://wiki.apache.org/solr/SolrInstall

Basically, apart from just unzipping the solr.war war file to the webapps directory, you need to create a solr home directory (for which you can copy example/solr in the distribution you downloaded).

Then, as per happy-coding's suggestion, you can configure the web.xml file to point to this directory. Restart (if necessary), and voila!

Upvotes: 0

tarequeh
tarequeh

Reputation: 1819

Just to keep a note here, if you deleted all files from your solr/data/index directory but left the directory alone and started getting this error, then stop solr, delete the solr/data/index directory and restart. Solr will create the index directory again. For some reason solr will give you this error if it finds the index directory but not the initial stuff it expects in there.

Upvotes: 4

Jeroen
Jeroen

Reputation: 3429

If you just browse to http://localhost:8983/solr/ you will see all cores listed (at least that did it for me).

Upvotes: 4

Mauricio Scheffer
Mauricio Scheffer

Reputation: 99730

You probably have a multi-core setup and haven't included the core in the URL. e.g. instead of requesting http://localhost:8983/solr/select/?q=*%3A* you have to request http://localhost:8983/solr/MyCoreName/select/?q=*%3A*

Upvotes: 11

Related Questions