Hi George, On 4/7/2015 1:09 PM, George Stanley Kozak wrote: > Hi, Tim: > > 1) I did the "lucene-core-3.5.0.jar" manual update of the indexes. For the > search index, I got no errors, but for the statistics core, I got: > Exception in thread "main" org.apache.lucene.index.IndexNotFoundException: > org.apache.lucene.store.MMapDirectory@/cul/app/dspace/solr/statistics/data/index > lockFactory=org.apache.lucene.store.NativeFSLockFactory@2e888d65 > at > org.apache.lucene.index.IndexUpgrader.upgrade(IndexUpgrader.java:118) > at org.apache.lucene.index.IndexUpgrader.main(IndexUpgrader.java:85)
This would imply that the "search" index upgraded fine (no errors). But, the error for your "statistics" index almost implies that it's not a valid Solr index. Do you use the "statistics" index? Is there anything in the "/cul/app/dspace/solr/statistics/data/index" directory or is it empty? > 2) I deleted the statistics core and did the ant update. I brought up my > DSpace 5.1 test system and when I tried to do a search, I got no results. > When I went to do a browse, I got: > ERROR org.dspace.app.xmlui.aspect.discovery.SidebarFacetsTransformer @ > anonymous:session_id=5749DBA88953D8B0ABDDA3FFD1DFF5F2:ip_addr=128.84.117.195:Error > in Discovery while setting up date facet range:date facet\colon; > dateIssued.year > 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 > > 3) I stopped tomcat, deleted the search index (as you suggested) and did the > mvn build and ant update and then copied the new webapps over to tomcat. > Everything looked good. I started tomcat and my site came up. Before doing > anything more I ran "./dspace index-discovery -b". It ran to completion, but > all searches return no hits and the browses give me the same write lock error > as above. > I made sure the permissions are correct (dspace user owns the solr indexes > and tomcat) and removed the write lock and tried again, but again I get the > same error. These other two errors seem rather odd to me...like something else is accessing Solr at the same time in which you are trying to reindex, and those multiple simultaneous "writes" are throwing errors. Can you try something even more simplistic than what you've done above? 1. Stop Tomcat 2. Copy your 1.8.3 data over to where you will install DSpace 5 3. Immediately delete *everything* under "/cul/app/dspace/solr/" (including the entire "statistics" and "search" subdirectories). This will wipe out all existing indexes, obviously. 4. Build DSpace 5.1 (mvn package). Then run "ant update". This should complete, as you'll have no existing Solr indexes for it to complain about. 5. Finally, start Tomcat back up. Now, sit back and wait. Don't run any other commands. But, feel free to check the logs for any issues as Tomcat boots up. Behind the scenes, DSpace should *automatically* be reindexing your content (and recreating the "search" index from nothing). You won't need to manually run anything (like 'index-discovery -b'), as this is all automated in DSpace 5 on the first bootup. (After the first bootup though, 'index-discovery -b' is the way to force a reindex.) I'm just curious if starting from *completely empty* indexes and installing DSpace 5 (without running 'index-discovery' manually) will act any different. If you still hit problems here, I'd recommend sending us a full stacktrace of the error messages you encounter. - Tim > > George Kozak > Digital Library Specialist > Cornell University Library Information Technologies (CUL-IT) > 218 Olin Library > Cornell University > Ithaca, NY 14853 > 607-255-8924 > > > -----Original Message----- > From: Tim Donohue [mailto:tdono...@duraspace.org] > Sent: Tuesday, April 07, 2015 11:52 AM > To: George Stanley Kozak; dspace-tech@lists.sourceforge.net > Subject: Re: [Dspace-tech] Error after install of DSpace 5.1 (Additional > information) > > Hi George, > > What happens if you do the following against your old 1.8.2 indexes: > > 1. wget > "http://search.maven.org/remotecontent?filepath=org/apache/lucene/lucene-core/3.5.0/lucene-core-3.5.0.jar"; > > 2. java -cp lucene-core-3.5.0.jar org.apache.lucene.index.IndexUpgrader > /cul/app/dspace/solr/statistics/data/index > > 3. java -cp lucene-core-3.5.0.jar org.apache.lucene.index.IndexUpgrader > /cul/app/dspace/solr/search/data/index > > Do either of those "IndexUpgrader" commands succeed against your *old* > 1.8.2 indexes? If not, could you send along the exception stacktrace? > > I'm just trying to determine if the issue is actually in these old 1.8.2 > indexes. It may be either they are indexes from an unexpected, older version > of Solr, or there's some minor index corruption here. > ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ 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
