[prev in list] [next in list] [prev in thread] [next in thread]
List: solr-user
Subject: Re: SOLR init error
From: Jan_Høydahl <jan.asf () cominvent ! com>
Date: 2023-02-18 23:49:47
Message-ID: AC2540D1-369C-47F7-8608-781F22B9F3AA () cominvent ! com
[Download RAW message or body]
This is an ancient version. Not seen the error before.
I'd first attempt to reboot every Solr node. If it persists, your best bet would be \
deleting the entire collection and recreating/re-indexing.
Jan Høydahl
> 18. feb. 2023 kl. 17:30 skrev Unknown Surname <marcsub@cwgsy.net.invalid>:
>
> Dear list,
>
> We have a system running DSpace CRIS 5.10 which uses SOLR
>
> Server version name: Apache Tomcat/8.5.54 (Debian)
> Server version number: 8.5.54.0
> OS Name: Linux
> OS Version: 4.9.0-18-amd64
> JVM Version: 1.8.0_322-8u322-b06-1~deb9u1-b06
> Solo-spec 4.10.2
> solr-impl 4.10.2 1634293 - mike - 2014-10-26 05:56:21
> lucene-spec 4.10.2
> lucene-impl 4.10.2 1634293 - mike - 2014-10-26 05:51:56
>
> Browsing to the home page gives an Internal System Error.
>
> Looking at the log for /var/log/tomcat8/localhost.2023-02-14.log
>
> Getting the following message
>
> msg=SolrCore 'search' is not available due to init failure: Error opening \
> new searcher,trace=org.apache.solr.common.SolrException: SolrCore 'search' \
> is not available due to init failure: Error opening new searcher
> Digging deeper it seems to be caused by
>
> Caused by: org.apache.lucene.index.CorruptIndexException: codec mismatch: actual \
> codec=CompoundFileWriterData vs expected codec=Lucene41PostingsWriterPos (resource: \
> MMapIndexInput(path="/home/dspace/solr/search/data/index/_o42_Lucene41_0.pos"))
>
> Any suggestions about how I might go about fixing this? A point in the right \
> direction would be greatly appreciated. If more information is needed please let me \
> know
> Kind regards
> Marc
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic