Server: ubuntu 10.04, tomcat6, solr 1.4.1, multi-core setup. After replacing original solrconfig.xml and schema.xml files with apachesolr module provided solrconfig.xml and schema.xml files to core0 folder and restarting tomcat, SOLR doesn't see this updated 'core0' core... If I will put original solrconfig.xml and schema.xml files back and restart tomcat, everything goes back to normal and I can access core0 again. What's can be wrong here? I think the problem is in solrconfig.xml and schema.xml files provided by this module.

Comments

pwolanin’s picture

Status: Active » Closed (cannot reproduce)

can't reproduce

nick_vh’s picture

Having the same issue here.
For now I'll use the single core..

nick_vh’s picture

Status: Closed (cannot reproduce) » Active

Reopening :)

pwolanin’s picture

Priority: Critical » Normal

Unless this is actually a problem with the config files (e.g. syntax error) I'm not sure what we can do here. It's up to you to debug your server.

nick_vh’s picture

I'll try to to put bit more detail in to this issue :
With the default solr schema.xml / solrconfig.xml (without modifications or with modifications to the data dir) the multicore functionality works perfectly fine.

However, whenever I add the schema.xml / solrconfig.xml from any (so far D6 only) version of the ApacheSolr project the 2 links to the cores disappear. I acknowledge that I have to figure out what exactly is the problem so here is my stack

Ubuntu 10.10 virtual machine
Sun Java JDK / Runtime
Tomcat 6 (apt-get version)
I used this guide to get me up and running :
http://yoodey.com/install-solr-141-ubuntu-1010-maven-maverick-multicore-...

I do have a broad understanding of how Solr works and the configuration files but the odd part is that when using only 1 core everything works (using the example of the singlecore Solr) unlike to the multicore.

Also I pledge to figure out the root of this problem and see where it could possible go wrong. I'm not expecting anyone to tell me how or what but I couldn't leave this issue closed since I am having the same strange notice whenever I do this.

Thanks for the quick response though! ;-)

pwolanin’s picture

Did you install all the required config files listed in the README?

Every one of these need to exist, even if empty or Solr will throw an exception on load:

solrconfig.xml
schema.xml
elevate.xml
mapping-ISOLatin1Accent.txt
protwords.txt
stopwords.txt
synonyms.txt

micheas’s picture

If you are using debian (and by extension ubuntu) if you put solr.war in /var/lib/tomcat6/webapps/ only the first set of xml conf files will be used.

I spent a lot of time not realizing that I had to move the war out of the magic directory so I could user /legacysolr and /searchapisolr

pwolanin’s picture

Status: Active » Fixed

fixed?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

rp7’s picture

Status: Closed (fixed) » Active

Experiencing the exact same problem. Anyone ever found a solution for this problem?

Using Win7 64bit - Tomcat 7 - Solr 1.4.1.

pwolanin’s picture

see #6

rp7’s picture

I did - unfortunately didn't cut it.

rp7’s picture

Status: Active » Closed (fixed)

Got it to work. #6 was right - but I can't get it to work if these files are empty. Copying them over from apache-solr-1.4.1\example\solr\conf did the job.

chicodasilva’s picture

Priority: Normal » Minor

In module README needs to be referenced that elevate.xml, should not be empty.
You get this error in a multicore configuration:

INFO: Loading QueryElevation from: /var/solr/core0/conf/elevate.xml
[Fatal Error] :2:1: Premature end of file.
Feb 16, 2012 12:37:37 PM org.apache.solr.common.SolrException log
mastermindg’s picture

It seems like the README and INSTALL files need to be updated to reflect the additional steps of copying the example files to the conf directory. I had the same issue just now from git. Also, search_api_solr latest dev doesn't need the patch, service.inc is already updated.