Forums / Extensions / eZ Find / Possible solution for "Severe errors in solr configuration"

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Possible solution for "Severe errors in solr configuration"

Previous topic

eZ Find

Next topic

Author	Message
Peter Keung	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
Robin Muilwijk	Friday 17 December 2010 6:28:03 am Thanks for sharing this experience and solution Peter! Regards Robin Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation. LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk

Author

Message

Peter Keung

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

Robin Muilwijk

Friday 17 December 2010 6:28:03 am

Thanks for sharing this experience and solution Peter!

Regards Robin

Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation.

LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk