Hello again, I wanted to provide a follow-up to this issue in case anyone has further insight. In order to address the issues outlined below, we ended up doing a full upgrade from our 5.5 code base (with 5.6 and 5.7 security patches) to 5.8. After the rebuild everything seemed to work as expected, and the timeouts during submissions didn’t occur.
However, the day after, my colleague realized that new items are not showing up in author browse. The new author(s) information is indeed available in Solr, but when you try to browse by author in DSpace, nothing comes up. Authors that were available before the upgrade are still viewable via author browse. Any idea as to what is causing the problem, in the migration from 5.5 to 5.8? I notice a lot of “context.turnOffAuthorisationSystem()” and “context.restoreAuthSystemState()” calls in 5.8 – are they possibly related? Again, any pointers in the right direction are greatly appreciated! Cheers, Graham From: [email protected] [mailto:[email protected]] On Behalf Of Graham Faulkner Sent: September 25, 2017 11:17 AM To: [email protected] Subject: [dspace-tech] submissions time out but still work Hi all, Starting around last Tuesday users have been experiencing problems with submitting their theses to our DSpace (v5.5, PostgreSQL, Ubuntu 14.04 with DS 5.6 and 5.7 patches). What happens is they complete the submission information (name, abstract, file upload, license agreement, etc.) but when they press the final submit button after the last step it takes 1-2 minutes to either submit successfully or, most frequently, to get a 500 error. We haven’t touched the source code in the last month, so we’re not sure what happened as of last week. Looking at the logs, I have noticed a few things: - We are/were getting lots of traffic from Google, Bing and Baidu spiders – I have since implemented the Crawler Session Manager Valve in Tomcat7, which was mentioned by Alan Orth at https://wiki.duraspace.org/display/cmtygp/DCAT+Meeting+April+2017. We are now getting fewer sessions reported in Tomcat, but the upload/submission problem persists. - In /dspace/log/dspace.log.<date> we are getting lots of “Failed DNS Lookup for IP:<IP address>”. - In /dspace/log/dspace.log.<date> were are getting lots of “ERROR org.dspace.app.xmlui.cocoon.DSpaceCocoonServletFilter @ Client closed the connection before file download was complete” - In /dspace/log/cocoon.log.<date> we are getting lots of errors like “Caused by: org.xml.sax.SAXException: An error was encountered while processing the 'aspect.general.PageNotFoundTransformer' Wing based component: org.dspace.app.xmlui.aspect.general.PageNotFoundTransformer” The odd thing is that the user’s submission usually does go through successfully, even if the “Internal Server Error” page comes up. If they return to the home page, logout and login and go to their submissions they will set it there. Unfortunately, most people don’t know to do that and keep resubmitting their thesis. Any pointers in the right direction are greatly appreciated! Cheers, Graham ----------------------------------------- Graham Faulkner Information Technology Specialist/Developer Digital Initiatives, Library University of Waterloo Waterloo, Ontario N2L 3G1 CANADA 519-888-4567 x32461 [email protected]<mailto:[email protected]> -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
