cores adminPath="/admij/cores"

Was that a cut and paste?  If so, the /admij/cores is presumably incorrect, and 
ought to be /admin/cores

-----Original Message-----
From: Jaeger, Jay - DOT [mailto:jay.jae...@dot.wi.gov] 
Sent: Wednesday, September 28, 2011 4:10 PM
To: solr-user@lucene.apache.org
Subject: RE: Trouble configuring multicore / accessing admin page

One time when we had that problem, it was because one or more cores had a 
broken XML configuration file. 
Another time, it was because solr/home was not set right in the servlet 
container.
Another time it was because we had an older EAR pointing to a newer release 
Solr home directory.  Given what you did, I suppose that is possible in your 
case, too.

In all cases, the Solr log provided hints as to what was going wrong.

JRJ

-----Original Message-----
From: Joshua Miller [mailto:jos...@itsecureadmin.com] 
Sent: Wednesday, September 28, 2011 2:41 PM
To: solr-user@lucene.apache.org
Subject: Trouble configuring multicore / accessing admin page

Hello,

I am trying to get SOLR working with multiple cores and have a problem 
accessing the admin page once I configure multiple cores.

Problem:
When accessing the admin page via http://solrhost:8080/solr/admin, I get a 404, 
"missing core name in path".

Question:  when using the multicore option, is the standard admin page still 
available?

Environment:
- solr 1.4.1
- Windows server 2008 R2
- Java SE 1.6u27
- Tomcat 6.0.33
- Solr Experience:  none

I have set -Dsolr.solr.home=c:\solr and within that I have a solr.xml with the 
following contents:

<solr persistent="true" sharedLib="lib">
  <cores adminPath="/admij/cores">
    <core name="core0" instanceDir="cores/core0" />
    <core name="core1" instanceDir="cores/core1" />
  </cores>
</solr>

I have copied the example/solr directory to c:\solr and have populated that 
directory with the cores/{core{0,1}} as well as the proper configs and data 
directories within.

When I restart tomcat, it shows a couple of exceptions related to 
queryElevationComponent and null pointers that I think are due to the DB not 
yet being available but I see that the cores appear to initialize properly 
other than that

So the problem I'm looking to solve/clarify here is the admin page - should 
that remain available and usable when using the multicore configuration or am I 
doing something wrong?  Do I need to use the CoreAdminHandler type requests to 
manage multicore instead?

Thanks,
--
Josh Miller
Open Source Solutions Architect
(425) 737-2590
http://itsecureadmin.com/

Reply via email to