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

eZ debug

Timing:	Jan 18 2025 10:20:32
Script start
Timing:	Jan 18 2025 10:20:32
Module start 'layout'
Timing:	Jan 18 2025 10:20:32
Module start 'content'
Timing:	Jan 18 2025 10:20:32
Module end 'content'
Timing:	Jan 18 2025 10:20:32
Script end

Main resources:

Total runtime	0.4311 sec
Peak memory usage	4,096.0000 KB
Database Queries	56

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	588.2031	152.6563
Module start 'layout'	0.0057	0.0036	740.8594	39.5313
Module start 'content'	0.0093	0.4205	780.3906	542.5391
Module end 'content'	0.4297	0.0013	1,322.9297	12.0859
Script end	0.4311		1,335.0156

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.7764	16	0.0002
Check MTime	0.0014	0.3155	16	0.0001
Mysql Total
Database connection	0.0011	0.2517	1	0.0011
Mysqli_queries	0.3853	89.3811	56	0.0069
Looping result	0.0005	0.1206	54	0.0000
Template Total	0.4002	92.8	2	0.2001
Template load	0.0023	0.5333	2	0.0011
Template processing	0.3979	92.2897	2	0.1989
Template load and register function	0.0001	0.0202	1	0.0001
states
state_id_array	0.0008	0.1940	1	0.0008
state_identifier_array	0.0007	0.1668	2	0.0004
Override
Cache load	0.0019	0.4450	19	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0004	0.0937	2	0.0002
Fetch class attribute name	0.0011	0.2529	4	0.0003
XML
Image XML parsing	0.0010	0.2345	2	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0018	4	0.0000
General
dbfile	0.0017	0.4044	25	0.0001
String conversion	0.0000	0.0024	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 10 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs