Re: Trouble configuring multicore / accessing admin page
On Sep 28, 2011, at 2:16 PM, Joshua Miller wrote: > On Sep 28, 2011, at 2:11 PM, Jaeger, Jay - DOT wrote: > >> cores adminPath="/admij/cores" >> >> Was that a cut and paste? If so, the /admij/cores is presumably incorrect, >> and ought to be /admin/cores >> > > No, that was a typo -- the config file is correct with admin/cores. Thanks > for pointing out the mistake here. > I was finally able to figure out the issue here. It was the solr.QueryElevationComponent exception in the logs. Once I commented out the related section in each core conf/solrconfig.xml file and restarted tomcat, I could then see the admin page link for each core and click through to manage them. Thanks! Josh Miller Open Source Solutions Architect (425) 737-2590 http://itsecureadmin.com/
Re: Trouble configuring multicore / accessing admin page
On Sep 28, 2011, at 2:11 PM, Jaeger, Jay - DOT wrote: > cores adminPath="/admij/cores" > > Was that a cut and paste? If so, the /admij/cores is presumably incorrect, > and ought to be /admin/cores > No, that was a typo -- the config file is correct with admin/cores. Thanks for pointing out the mistake here. Josh Miller Open Source Solutions Architect (425) 737-2590 http://itsecureadmin.com/
RE: Trouble configuring multicore / accessing admin page
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:
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/
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:
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/
Re: Trouble configuring multicore / accessing admin page
On 9/28/2011 2:24 PM, Robert Petersen wrote: Just go to localhost:8983 (or whatever other port you are using) and use this path to see all the cores available on the box: In your example this should give you a core list: http://solrhost:8080/solr/ Now this is interesting. If I have defaultCoreName in my solr.xml (on 3.4.0), the /solr URL only shows one admin link, which takes me to the /solr/admin/ page for my default core. On that page, I do have links to all the other core admin pages, as usual. If I don't have defaultCoreName, /solr shows admin links for all defined cores. A quick search didn't turn up any Jira issues for this. Is this intended behavior? Thanks, Shawn
Re: Trouble configuring multicore / accessing admin page
On Sep 28, 2011, at 1:24 PM, Robert Petersen wrote: > Just go to localhost:8983 (or whatever other port you are using) and use > this path to see all the cores available on the box: > > In your example this should give you a core list: > > http://solrhost:8080/solr/ > I see "Welcome to Solr!" and "Solr Admin" below that as a link. When I click through the link, I get the 404 error, "missing core name in path". Thanks, Josh Miller Open Source Solutions Architect (425) 737-2590 http://itsecureadmin.com/
RE: Trouble configuring multicore / accessing admin page
Just go to localhost:8983 (or whatever other port you are using) and use this path to see all the cores available on the box: In your example this should give you a core list: http://solrhost:8080/solr/ -Original Message- From: Joshua Miller [mailto:jos...@itsecureadmin.com] Sent: Wednesday, September 28, 2011 1:18 PM To: solr-user@lucene.apache.org Subject: Re: Trouble configuring multicore / accessing admin page On Sep 28, 2011, at 1:03 PM, Shawn Heisey wrote: > On 9/28/2011 1:40 PM, Joshua Miller wrote: >> 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? > > When you enable multiple cores, the URL syntax becomes a little different. On 1.4.1 and 3.2.0, I ran into a problem where the trailing / is required on this URL, but that problem seems to be fixed in 3.4.0: > > http://host:port/solr/corename/admin/ > > If you put a defaultCoreName="somecore" into the tag in solr.xml, the original /solr/admin URL should work as well. I just tried it on Solr 3.4.0 and it does work. According to the wiki, it should work in 1.4 as well. I don't have a 1.4.1 server any more, so I can't verify that. > > http://wiki.apache.org/solr/CoreAdmin#cores Hi Shawn, Thanks for the quick response. I can't get any of those combinations to work. I've added the defaultCoreName="core0" into the solr.xml and restarted and tried the following combinations: http://host:port/solr/admin http://host:port/solr/admin/ http://host:port/solr/core0/admin/ ... (and many others) I'm stuck on 1.4.1 at least temporarily as I'm taking over an application from another resource and need to get it up and running before modifying anything so any help here would be greatly appreciated. Thanks, Josh Miller Open Source Solutions Architect (425) 737-2590 http://itsecureadmin.com/
Re: Trouble configuring multicore / accessing admin page
On Sep 28, 2011, at 1:17 PM, Rahul Warawdekar wrote: > Can you try updating your solr.xml as follows: > Specify > "" instead of > "" > > Basically remove the extra text "cores" in the core element from the > instanceDir attribute. I gave that a try and it didn't change anything. Thanks, Josh
Re: Trouble configuring multicore / accessing admin page
On Sep 28, 2011, at 1:03 PM, Shawn Heisey wrote: > On 9/28/2011 1:40 PM, Joshua Miller wrote: >> 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? > > When you enable multiple cores, the URL syntax becomes a little different. > On 1.4.1 and 3.2.0, I ran into a problem where the trailing / is required on > this URL, but that problem seems to be fixed in 3.4.0: > > http://host:port/solr/corename/admin/ > > If you put a defaultCoreName="somecore" into the tag in solr.xml, the > original /solr/admin URL should work as well. I just tried it on Solr 3.4.0 > and it does work. According to the wiki, it should work in 1.4 as well. I > don't have a 1.4.1 server any more, so I can't verify that. > > http://wiki.apache.org/solr/CoreAdmin#cores Hi Shawn, Thanks for the quick response. I can't get any of those combinations to work. I've added the defaultCoreName="core0" into the solr.xml and restarted and tried the following combinations: http://host:port/solr/admin http://host:port/solr/admin/ http://host:port/solr/core0/admin/ … (and many others) I'm stuck on 1.4.1 at least temporarily as I'm taking over an application from another resource and need to get it up and running before modifying anything so any help here would be greatly appreciated. Thanks, Josh Miller Open Source Solutions Architect (425) 737-2590 http://itsecureadmin.com/
Re: Trouble configuring multicore / accessing admin page
Hi Joshua,
Can you try updating your solr.xml as follows:
Specify
"" instead of
""
Basically remove the extra text "cores" in the core element from the
instanceDir attribute.
Just try and let us know if it works.
On Wed, Sep 28, 2011 at 3:40 PM, Joshua Miller wrote:
> 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:
>
>
>
>
>
>
>
>
> 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/
>
>
--
Thanks and Regards
Rahul A. Warawdekar
Re: Trouble configuring multicore / accessing admin page
On 9/28/2011 1:40 PM, Joshua Miller wrote: 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? When you enable multiple cores, the URL syntax becomes a little different. On 1.4.1 and 3.2.0, I ran into a problem where the trailing / is required on this URL, but that problem seems to be fixed in 3.4.0: http://host:port/solr/corename/admin/ If you put a defaultCoreName="somecore" into the tag in solr.xml, the original /solr/admin URL should work as well. I just tried it on Solr 3.4.0 and it does work. According to the wiki, it should work in 1.4 as well. I don't have a 1.4.1 server any more, so I can't verify that. http://wiki.apache.org/solr/CoreAdmin#cores Thanks, Shawn
