On 9/5/2015 1:56 PM, Mark Fenbers wrote: > The log data is from solr.log. There are a couple of puzzling items. > > 1. On line 2015-09-05 19:19:56.678, it shows a "lib" subdir > (/localapps/dev/EventLog/lib) which doesn't exist and isn't > specified anywhere that I can find (lots of "find | grep" > commands). I did, at one point, specify this in a version of > solrconfig.xml that I was experimenting with, but have since removed > that long ago. The fact that this still appears is strange, as if > it is using an old cache or something. > 2. On line 2015-09-05 19:19:57.455, it shows a .../conf/conf/... and I > can't figure out where the double "conf" is coming from. > /localapps/dev/EventLog/solr/conf/conf/solrconfig.xml doesn't exist, > and solrconfig.xml resides in > /localapps/dev/EventLog/solr/conf/ (just one conf) where it belongs!
Your solr home is /localapps/dev/EventLog ... Solr automatically loads any jar found in the lib directory in the solr home, so it is attempting to use /localapps/dev/EventLog/lib for the classloader. For the other things you noticed, I believe I know why that is happening too. This SHOULD be the structure of a core instanceDir, if "collection1" is the name of that directory. This is highly simplified and missing things you would likely find in the directory structure: collection1/ |-core.properties |-conf/ |--solrconfig.xml |--schema.xml |--stopwords.txt |-data/ |--index/ |---[Lucene index files go here] The directory with the core.properties file is the instanceDir. The instanceDir is supposed to contain a conf directory and a data directory. It appears that you have this of structure in your solr home (leaving a lot of things out on this one): solr/ |-conf/ |--core.properties |--solrconfig.xml |--schema.xml This is why it is looking in a path that has "conf" twice -- it is going to the instanceDir (where it found core.properties) and assuming that it will find a conf directory there. The conf directory is not supposed to be the instanceDir. Thanks, Shawn
