Andrea:
Yes, it has me stumped. If I restore the Solr indexes and the postgres
database back to the DSpace 4.2 versions and bring up DSpace 4.2, everything
works fine.
I do shutdown tomcat when I do the ant step. Here are my steps, and let me
know if I have forgotten anything:
1) Shutdown tomcat
2) Run mvn -U clear package (I also tried with the Mirage2 option)
3) After successful build, I go to the target/dspace-install directory and
run "ant update"
4) After that is successful, I copy the webpass over to tomcat
5) Restart tomcat
6) Go to view the system
The system comes up and I have access to the database records, but all browses
and searches generate the index lock error.
George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CUL-IT)
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
From: Andrea Schweer [mailto:schw...@waikato.ac.nz]
Sent: Wednesday, March 25, 2015 5:03 PM
To: George Stanley Kozak; dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Error after install of DSpace 5.1
Hi George,
On 26/03/15 03:42, George Stanley Kozak wrote:
So, I double checked the permissions on my solr index and tomcat. They are
both owned by the DSpace user. If I bring my system up in DSpace 4.2 (after a
restore), I have no problems. If I bring it up in 5.1, I get the error:
"SolrCore 'search' is not available due to init failure: Index locked for write
for core search,trace=org.apache.solr.common.SolrException: SolrCore 'search'
is not available due to init failure: Index locked for write for core search"
I can't even do an re-index.
I have to say that I'm kind of stumped here. Works OK in 4.2, doesn't work in
5.1
How odd. Are you running the ant step (with the 5.1 code) as the same user as
tomcat? Also, when you run ant for the first time using the 5.1 code, tomcat
must not be running -- ant will upgrade the solr indexes to the version used in
DSpace 5.1 and it needs to have exclusive access to the index while that runs
(and the mechanism for that is the write lock, which makes me suspect it's
involved in the problem you're seeing).
You have presumably checked already that the ant step with the 5.1 code doesn't
throw any errors.
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
