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
Comment #1
pwolanin commentedcan't reproduce
Comment #2
nick_vhHaving the same issue here.
For now I'll use the single core..
Comment #3
nick_vhReopening :)
Comment #4
pwolanin commentedUnless 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.
Comment #5
nick_vhI'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! ;-)
Comment #6
pwolanin commentedDid 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
Comment #7
pwolanin commentedsee also:
#799970: update README.txt and other docs w.r.t. required conf files.
#1097976: Use ShowFileRequestHandler, gettableFiles is deprecated
Comment #8
micheas commentedIf 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
Comment #9
pwolanin commentedfixed?
Comment #11
rp7 commentedExperiencing the exact same problem. Anyone ever found a solution for this problem?
Using Win7 64bit - Tomcat 7 - Solr 1.4.1.
Comment #12
pwolanin commentedsee #6
Comment #13
rp7 commentedI did - unfortunately didn't cut it.
Comment #14
rp7 commentedGot 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.
Comment #15
chicodasilva commentedIn module README needs to be referenced that elevate.xml, should not be empty.
You get this error in a multicore configuration:
Comment #16
mastermindg commentedIt 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.