SOLR error update dspace 5.2 -> 6.3 -> 7.0 ,

457 views
Skip to first unread message

Jorge Alberto Bonilla Castaneda

unread,
Jun 13, 2022, 4:38:55 PM6/13/22
to DSpace Technical Support
SOLR error

Hello , I am trying to update the dspace of the library where I work , for this the first step was to take the assetstore folder and the database and import it to a server with 6.3 , making slight corrections based on other useful publications of this group

However, when upgrading this dspace 6.3 to 7.2, I have not been able to get past the backend installation process, mainly step 10 point iii , of the official documentation
https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace

when we check http://localhost:8983/solr/ , it doesn't recognize dspace cores:
Captura de pantalla 2022-06-13 142026.png

As extra data, the SOLR installation commands have been:
#from root user
cd /opt
sudo wget https://downloads.apache.org/lucene/solr/8.11.1/solr-8.11.1.tgz
sudo tar -zxf solr-8.11.1.tgz
sudo chown -R biblio:biblio solr-8.11.1
cd
sudo nano .profile
#from biblio user
/opt/solr-8.11.1/bin/solr start 


Thank you in advance for your help



AVISO DE CONFIDENCIALIDAD: Este mensaje y cualquier archivo adjunto al mismo, se dirige exclusivamente a su(s) destinatario(s), y no puede ser compartido o reenviado a un tercero sin autorización del remitente. Solo puede ser utilizado por las personas o entidades a las cuales está dirigido.
Si usted no es el destinatario al que ha sido remitida esta información, queda prohibida, cualquier modificación, retención, difusión o copia total o parcial, y no puede emprender con ella ningún tipo de acción. Le rogamos que lo comunique inmediatamente por esta misma vía y proceda a su eliminación.
Si es miembro de la Comunidad Educativa de la UDB y viola lo anterior será sujeto a sanción disciplinaria conforme al Art.134, literales “r”, “s”, y “t” del Reglamento General Administrativo-Académico.

CONFIDENTIALITY NOTICE: The content of this email and any attachments are intended solely for the addressee(s). The information cannot be shared without the authorization of the sender. It can only be used by the intended recipients.
If you are not the intended recipient, you are hereby notified that any modification, dissemination, full or partial copy of this email is forbidden. You must not take any kind of action in reliance on it. Please, notify the sender by replying to this email and delete the message without copying or disclosing it.
If you are a member of the UDB community and were to violate the foregoing, you will be subject to disciplinary actions in accordance to Article 134, literal “r”, “s”, and “t” of the General Administrative-Academic Regulations.

Tim Donohue

unread,
Jun 13, 2022, 5:24:19 PM6/13/22
to DSpace Technical Support
Hi,

Before we can provide any help, you would need to check the Solr logs to get more details on the underlying error.  It's possible it's something as simple as a permissions error, or something like that.

Notice how that "SolrCore Initialization Failures" red box says at the bottom to "Please check your logs for more information".  That's helpful advice because it can give you the clues needed to solve the problem.

Good luck & let us know on this list what you find in the Solr logs.

Tim

Jorge Alberto Bonilla Castaneda

unread,
Jun 13, 2022, 5:37:25 PM6/13/22
to DSpace Technical Support
ok I understand, thank you very much for your help, the log gives me the following messages:
FireShot Capture 081 - Solr Admin - 172.16.99.132.png

Tim Donohue

unread,
Jun 13, 2022, 6:08:23 PM6/13/22
to DSpace Technical Support
Hi,

Unfortunately that logging screenshot isn't much help either.  There's a lot of errors there which seems like it could imply some major issue right at the beginning of startup. You may want to check to see if earlier logs exist (as earlier errors may snowball into those later errors).  You also may want to look for the "solr.log" file on your system to see if more detailed logs can be found there (perhaps with a Java stacktrace or similar).

Based on what you've shared so far, there seem to be a very large number of "generic" errors.  What we are looking for is a more specific error which may point out the root problem.

That's all the help I can give based on the info provided so far.  Maybe others will see a clue here that could help indicate the root problem.

Tim

Jorge Alberto Bonilla Castaneda

unread,
Jun 13, 2022, 6:18:43 PM6/13/22
to DSpace Technical Support
I understand, in the same way I thank you very much for your help, could you tell me where that solr log would be? 

 It is true what it says, I have searched for the resolution of these generic errors on the internet and in this group but I always found different solutions, probably because of what I mentioned that they are generic errors 

 I will be waiting for any other response from the group

 thanks to all

Mark H. Wood

unread,
Jun 14, 2022, 10:21:22 AM6/14/22
to dspac...@googlegroups.com
On Mon, Jun 13, 2022 at 03:18:43PM -0700, Jorge Alberto Bonilla Castaneda wrote:
> I understand, in the same way I thank you very much for your help, could
> you tell me where that solr log would be?

The precise answer depends on how you have installed and configured
Solr, and how it is started. Since you ask the question, you probably
haven't changed the default, which ought to be in 'server/logs'
beneath the directory in which you unpacked Solr. You can find the
default logging configuration in 'server/resources/log4j2.xml'

I'm sorry that I can't consult my own instance of Solr for a precise
answer. I've made quite a bit of custom configuration here to make
Solr deploy itself in conformance to the Linux Filesystem Hierarchy
Standard and OpenRC, so the log files are where I configured them to
go, not the stock location.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu
signature.asc

Jorge Alberto Bonilla Castaneda

unread,
Jun 14, 2022, 10:38:24 AM6/14/22
to DSpace Technical Support
Hi everyone

 I checked what the solr log said, and I found a few errors, I'll send you the file, solr hasn't been implemented for long on the server so the log doesn't have as many rows 

 Any recommendation is more than welcome.

solr.log

Tim Donohue

unread,
Jun 15, 2022, 4:37:50 PM6/15/22
to DSpace Technical Support
Hi,

The important error in that log is this one:

Caused by: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/opt/solr-8.11.1/server/solr/configsets/oai/data/index/segments_1"))): 3 (needs to be between 7 and 10). This version of Lucene only supports indexes created with release 6.0 and later.

It seems to be saying that you are trying to upgrade an *old* Solr index which is incompatible with the new version of Solr.  Are you attempting to import old Solr data into DSpace 7?  If so, it's not possible to just copy the old Solr data into the new location.  Instead, you must follow our Upgrade guide/instructions: https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace

See step #10 in those instructions which describes what you need to do to bring old Solr data (from 6.x or below) into DSpace 7.  For most old Solr data you'd want to reindex, but for Authority data or Statistics data, you will need to export the old data (see step #2 in upgrade instructions) and then reimport (see step #10) into the new Solr.

Tim

Jorge Alberto Bonilla Castaneda

unread,
Jun 27, 2022, 1:17:25 PM6/27/22
to DSpace Technical Support
hello

After reviewing the documentation and the problems that were reported to me, I was able to solve the problem by deleting the solr folder that contained the old 6.3 cores before running the command 

ant update

so that the new files are downloaded, when doing that it shows me the cores correctly and also the command

[dspace]/bin/dspace oai import

executed successfully, but the command

[dspace]/bin/dspace index-discovery -b

if it gave me an error

# /dspace/bin/dspace index-discovery -b
The script has started
(Re)building index from scratch.
Done with indexing
The script has completed
Exception in thread "Thread-6" java.lang.IllegalStateException: EntityManagerFactory is closed
        at org.hibernate.internal.SessionFactoryImpl.validateNotClosed(SessionFactoryImpl.java:548)
        at org.hibernate.internal.SessionFactoryImpl.getMetamodel(SessionFactoryImpl.java:695)
        at org.hibernate.engine.internal.Collections.processReachableCollection(Collections.java:162)
        at org.hibernate.event.internal.FlushVisitor.processCollection(FlushVisitor.java:50)
        at org.hibernate.event.internal.AbstractVisitor.processValue(AbstractVisitor.java:104)
        at org.hibernate.event.internal.AbstractVisitor.processValue(AbstractVisitor.java:65)
        at org.hibernate.event.internal.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java:59)
        at org.hibernate.event.internal.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:182)
        at org.hibernate.event.internal.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:232)
        at org.hibernate.event.internal.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:92)
        at org.hibernate.event.internal.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:50)
        at org.hibernate.event.service.internal.EventListenerGroupImpl.fireEventOnEachListener(EventListenerGroupImpl.java:108)
        at org.hibernate.internal.SessionImpl.autoFlushIfRequired(SessionImpl.java:1309)
        at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1389)
        at org.hibernate.query.internal.AbstractProducedQuery.doList(AbstractProducedQuery.java:1558)
        at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1526)
        at org.hibernate.query.Query.getResultList(Query.java:165)
        at org.hibernate.query.criteria.internal.compile.CriteriaQueryTypeQueryAdapter.getResultList(CriteriaQueryTypeQueryAdapter.java:76)
        at org.dspace.core.AbstractHibernateDAO.executeCriteriaQuery(AbstractHibernateDAO.java:428)
        at org.dspace.core.AbstractHibernateDAO.list(AbstractHibernateDAO.java:162)
        at org.dspace.authorize.dao.impl.ResourcePolicyDAOImpl.findByDSoAndAction(ResourcePolicyDAOImpl.java:103)
        at org.dspace.authorize.ResourcePolicyServiceImpl.find(ResourcePolicyServiceImpl.java:103)
        at org.dspace.authorize.AuthorizeServiceImpl.getPoliciesActionFilter(AuthorizeServiceImpl.java:501)
        at org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:110)
        at org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
        at org.dspace.discovery.indexobject.DSpaceObjectIndexFactoryImpl.buildDocument(DSpaceObjectIndexFactoryImpl.java:30)
        at org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:134)
        at org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:75)
        at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:165)
        at org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:155)
        at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:322)
        at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:309)
        at org.dspace.discovery.SolrServiceImpl.createIndex(SolrServiceImpl.java:277)
        at org.dspace.storage.rdbms.DatabaseUtils$ReindexerThread.run(DatabaseUtils.java:1332)

Reply all
Reply to author
Forward
0 new messages