|
Thursday 16 December 2010 6:18:13 pm
We had a trouble call from a new client whose eZ Find install suddenly stopped working. Error was:
"<body><h2>HTTP ERROR: 500</h2><pre>Severe errors in solr configuration.
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"
... and so on.
From the command line, Solr seemed to start fine. Polling Solr directly didn't work.
Seemed like a rather common error with a useful error message, but no one had changed any configuration files from the default. Re-indexing with the --clean flag did not help.
Somehow the index had gotten corrupted -- for what reason, we don't know. Maybe it was a half-pushed data change that resulted in a fatal error on edit. Either way, the fix was to manually clear extension/ezfind/java/solr/data/index and then re-index. (Thankfully this was a small, one-site index.) eZ Find works again! So if you're on a small site with a similar error, the "just clear the index manually" (after backing it up) method might be the right time-sensitive solution.
http://www.mugo.ca
Mugo Web, eZ Partner in Vancouver, Canada
|
