RE: Unable to get multicore working

2011-08-17 Thread Jaeger, Jay - DOT
st of luck! -Original Message- From: David Sauve [mailto:dnsa...@gmail.com] Sent: Tuesday, August 16, 2011 5:00 PM To: solr-user@lucene.apache.org Subject: Re: Unable to get multicore working Ok. Fixed that too, now. The schema didn't define "long". Looks like everything is a-

RE: Unable to get multicore working

2011-08-17 Thread Gaurav Shingala
can you please try persistent="true" in solr tag as per my knowledge it will solve your 404 - Not found error. Regards, Gaurav > Date: Tue, 16 Aug 2011 12:44:45 -0700 > From: dnsa...@gmail.com > To: solr-user@lucene.apache.org > Subject: Unable to get multicore working > > I've been trying (u

Re: Unable to get multicore working

2011-08-16 Thread David Sauve
> -Original Message- > From: David Sauve [mailto:dnsa...@gmail.com] > Sent: Tuesday, August 16, 2011 4:24 PM > To: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache.org) > Subject: Re: Unable to get multicore working > > I updated my `solr.xml` as follo

RE: Unable to get multicore working

2011-08-16 Thread Jaeger, Jay - DOT
y, August 16, 2011 4:24 PM To: solr-user@lucene.apache.org Subject: Re: Unable to get multicore working I updated my `solr.xml` as follow: and I'm still seeing the same 404 when I true to view /solr/admin/ or /solr/live/admin/ That said, the logs are showing a different error

Re: Unable to get multicore working

2011-08-16 Thread David Sauve
August, 2011 at 2:06 PM, Jaeger, Jay - DOT wrote: > > > > > Whoops: That was Solr 4.0 (which pre-dates 3.1). > > > > > > I doubt very much that the release matters, though: I expect the behavior > > would be the same. > > > > > > -Origin

Re: Unable to get multicore working

2011-08-16 Thread Donald Organ
gt; > Whoops: That was Solr 4.0 (which pre-dates 3.1). > > > > I doubt very much that the release matters, though: I expect the behavior > would be the same. > > > > -Original Message- > > From: Jaeger, Jay - DOT [mailto:jay.jae...@dot.wi.gov] > >

Re: Unable to get multicore working

2011-08-16 Thread David Sauve
h that the release matters, though: I expect the behavior > would be the same. > > -Original Message- > From: Jaeger, Jay - DOT [mailto:jay.jae...@dot.wi.gov] > Sent: Tuesday, August 16, 2011 4:04 PM > To: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache

RE: Unable to get multicore working

2011-08-16 Thread Jaeger, Jay - DOT
@lucene.apache.org Subject: RE: Unable to get multicore working I tried on my own test environment -- pulling out the default core parameter out, under Solr 3.1 I got exactly your symptom: an error 404. HTTP ERROR 404 Problem accessing /solr/admin/index.jsp. Reason

RE: Unable to get multicore working

2011-08-16 Thread Jaeger, Jay - DOT
:124) (etc.) Adding the defaultCoreName fixed it. I expect this is indeed your problem. -Original Message- From: David Sauve [mailto:dnsa...@gmail.com] Sent: Tuesday, August 16, 2011 3:50 PM To: solr-user@lucene.apache.org Subject: Re: Unable to get multicore working Nope. Only thing in

Re: Unable to get multicore working

2011-08-16 Thread David Sauve
Nope. Only thing in the log: 1 [main] INFO org.mortbay.log - Logging to org.slf4j.impl.SimpleLogger(org.mortbay.log) via org.mortbay.log.Slf4jLog 173 [main] INFO org.mortbay.log - Redirecting stderr/stdout to /var/log/jetty/2011_08_16.stderrout.log On Tuesday, 16 August, 2011 at 1:45 PM, Ale

RE: Unable to get multicore working

2011-08-16 Thread Jaeger, Jay - DOT
That won't work -- it would have to identify one of the three cores in your cores list (say, "live"). -Original Message- From: David Sauve [mailto:dnsa...@gmail.com] Sent: Tuesday, August 16, 2011 3:29 PM To: solr-user@lucene.apache.org Subject: Re: Unable to get multi

Re: Unable to get multicore working

2011-08-16 Thread Alexei Martchenko
Is your solr.xml in usr/share/jetty/solr/solr.xml? lets try this xml instead Can you see the logs? You should see something like this 16/08/2011 17:30:55 org.apache.solr.core.SolrResourceLoader *INFO: Solr home set to 'solr/'* 16/08/2011 17:30:55 org.apache.solr.servlet.SolrDispatchF

Re: Unable to get multicore working

2011-08-16 Thread David Sauve
Just the one `solr.xml`. The one I added (well, symlinked form my config folder -- I like to keep my configurations files organized so they can be managed by git) `start.jar` is in `usr/share/jetty/start.jar`. On Tuesday, 16 August, 2011 at 1:33 PM, Alexei Martchenko wrote: > AFAIK you're st

Re: Unable to get multicore working

2011-08-16 Thread Alexei Martchenko
AFAIK you're still seeing singlecore version where is your start.jar? search for solr.xml, see how many u've got plz. 2011/8/16 David Sauve > I've installed using aptitude so I don't have an example folder (that I > can find). > > /solr/ does work (but lists no cores) > /solr/live/admin/

Re: Unable to get multicore working

2011-08-16 Thread David Sauve
I tried setting `defaultCoreName="admin"` and that didn't seem to change anything. I also tried adding an `env-entry` for "solr/home" pointing to "/home/webteam/config" but that didn't seem to help either. The logs don't have any errors in them, besides 404 errors. On Tuesday, 16 August, 20

Re: Unable to get multicore working

2011-08-16 Thread David Sauve
I've installed using aptitude so I don't have an example folder (that I can find). /solr/ does work (but lists no cores) /solr/live/admin/ does not -- 404 On Tuesday, 16 August, 2011 at 1:13 PM, Alexei Martchenko wrote: > Lets try something simplier. > My start.jar is on \apache-solr-3.3.0\e

Re: Unable to get multicore working

2011-08-16 Thread Alexei Martchenko
Lets try something simplier. My start.jar is on \apache-solr-3.3.0\example\ Here's my local config placed in \apache-solr-3.3.0\example\solr\ Create \apache-solr-3.3.0\example\solr\softwares01\conf\ and \apache-solr-3.3.0\example\solr\softwares01\data\ http://localhost:8983/solr/ should

RE: Unable to get multicore working

2011-08-16 Thread Jaeger, Jay - DOT
Perhaps your admin doesn’t work because you don't have defaultCoreName="whatever-core-you-want-by-default" in your tag? E.g.: Perhaps this was enough to prevent it starting any cores -- I'd expect a default to be required. Also, from experience, if you add cores, and you have securi