Yes - try adding it to solr.xml - thats where the CoreContainer looks for it.
-- - Mark http://www.lucidimagination.com djain101 wrote: > Any help is much appreciated. > > Thanks, > Dharmveer > > > djain101 wrote: > >> Hi, >> >> We have set <abortOnConfigurationError>false</abortOnConfigurationError> >> in solrconfig.xml for all the cores but still whenever any configuration >> error occurs search does not work in any of the cores. Is there any other >> configuration we have to set so as to not affect search in the cores which >> are configured correctly? >> >> For one of the core, we got following error today but then none of the >> core is working after that. The below message suggests to add >> abortOnConfigurationError in solr.xml but we have it added in >> solrconfig.xml for all the cores. Do we need to add in solr.xml? If yes, >> where? >> >> Please suggest what is the right way to configure so that if one core >> fails due to configuration errors, all other cores remain unaffected? >> >> ***************************************************************** >> Check your log files for more detailed information on what may be wrong. >> >> If you want solr to continue after configuration errors, change: >> >> <abortOnConfigurationError>false</abortOnConfigurationError> >> >> in solr.xml >> >> java.lang.RuntimeException: java.io.IOException: Cannot create directory: >> /usr/local/app/data/search/core09/index >> *********************************************************************** >> >> > >
