: http://localhost:8080/solr/admin/cores : ?action=CREATE : &name=core1 : &instanceDir=core1 : &config=core0/conf/solrconfig.xml : &schema=core0/conf/schema.xml : (core1 is the name for the new core to be created, and I want to use the : config and schema from core0 to create the new core). : : but the error is always due to the servlet container thinking : $TOMCAT_HOME/bin is the current working directory: : Caused by: java.lang.RuntimeException: *Can't find resource : 'core0/conf/solrconfig.xml'* in classpath or '/opt/solr/core1/conf/', * : cwd=/opt/tomcat/bin
A major pain point is the Solr code base is that various pieces of code assume paths are relative to varoius other paths -- frequently the CWD -- and it's not always clear what the right "fix" is (ie: when should it be the SolrHome dire? when should it be the instanceDir for the current core? when should it be the conf dir for hte current core? etc...) Even if we were startig from scratch right now, it's not clear how paths like the "schema" and "Config" params should be interpreted in a CREATE command (should they be relative the SolrHome? or relative the "instanceDir" param?) Even in cases where it should be obvious, and it would be nice to "fix" these paths, it could easily break things for existing users with code/configs that have come to expect the particular excentricities (in "read only" cases, we can check multiple paths, but that doesn't work for files/dirs that Solr is being asked to create) The easiest workarround: configure tomcat to use your SolrHome dir (ie: "/opt/solr" in your example) as it's Working Directory. -Hoss -- http://lucenerevolution.org/ ... October 7-8, Boston http://bit.ly/stump-hoss ... Stump The Chump!
