How do I fix this installation problem with multicore Solr on Ubuntu 10.04?

**EDIT**

I've written up a quick howto on getting multicore going:

[To see links please register here]

Following instructions from the two sites below, I've installed [Tomcat][1] 6 and [Solr][2] 1.4.

*

[To see links please register here]

*

[To see links please register here]

I have successfully got it up and running on a server running 9.04 with multicore support, but on the 10.04 I can't seem to get it to work.

I am able to reach localhost:xxxx/solr/ on the 10.04 box and see a single link to the Solr Admin, but following the link takes me to a 404 page with the following output:

/solr/admin/
HTTP Status 404 - missing core name in path
The requested resource (missing core name in path) is not available

I am also unable to access /solr/site1/ as I would except - it similarly returns a 404.

<!-- from /var/solr/solr.xml, site dirs exist -->
<cores adminPath="/admin/cores">
<core name="site1" instanceDir="site1" />
<core name="site2" instanceDir="site2" />
</cores>

<!-- from /etc/tomcat6/Catalina/localhost/solr.xml -->
<Context docBase="/var/solr/solr.war" debug="0" privileged="true" allowLinking="true" crossContext="true">
<Environment name="solr/home" type="java.lang.String" value="/var/solr" override="true" />
</Context>

[1]:

[To see links please register here]

[2]:

[To see links please register here]

I don't know why the link in `http://localhost:xxxx/solr/` is wrong, but the admin URL for site1 is `http://localhost:xxx/solr/site1/admin/` (notice the slash at the end, it's required, otherwise you'll get a 404).

A query in the site1 core would look like this: `http://localhost:xxxx/solr/site1/select/?q=solr&version=2.2&start=0&rows=10&indent=on`

`http://localhost:xxx/solr/site1/` **is** a 404, that is the correct response.

For those coming here via Google:

I had this same problem, which I eventually tracked down to permissions on the solr.home directory (the cores didn't exists as it couldn't create directories for them). Check the latest catalina log file in /var/log/tomcat6/ for any issues.