Hi, Tim (and everyone else): I checked the Tomcat logs and saw only the following problems when things are starting up: WARN [org.dspace.services.email.EmailServiceImpl] Couldn't get an email session from environment: Name [mail/Session] is not bound in this Context. Unable to find [mail]. and [WARN] deprecation - The 'component-configurations' section in the sitemap is deprecated. Please check for alternatives.
Everything else looks OK, but when I try to execute a Discovery search, I see: IO Exception In the DSpace log, everything looks OK until I try a search, and then I see: ERROR org.dspace.app.xmlui.aspect.discovery.SidebarFacetsTransformer @ anonymous:session_id=433A509643A83865CCA1B39998E40CE0:ip_addr=128.84.117.195:Error in Discovery while setting up date facet range:date facet\colon; dateIssued.year The actual error is then displayed in the logs as raw HTML because I am also getting: org.dspace.discovery.SearchServiceException: Expected mime type application/octet-stream but got text/html. And that error is: org.apache.solr.common.SolrException: SolrCore 'search' is not available due to init failure: Index locked for write for core search I see in the Solr index the write.lock. I should add that both the Solr index and tomcat are owned by the DSpace user (as is the write.lock) Since, I seem to have hit an impasse, I am going to try and restart the whole upgrade again. 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: Thursday, March 26, 2015 10:04 AM To: George Stanley Kozak; Andrea Schweer; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Error after install of DSpace 5.1 George, Just a note: you may want to see if any other errors occur in the DSpace or Tomcat logs when you restart tomcat (your step #5). I'm especially curious if any errors are thrown besides those index lock errors. They may provide hints as to what may be going on. - Tim On 3/25/2015 4:55 PM, George Stanley Kozak wrote: > 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 > ------------------------------------------------------------------------------ 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
