diff --git a/content/posts/2019-03.md b/content/posts/2019-03.md index 1bef6a2fa..3cc40e1be 100644 --- a/content/posts/2019-03.md +++ b/content/posts/2019-03.md @@ -320,5 +320,7 @@ java.util.EmptyStackException - After restarting Tomcat, Solr was giving the "Error opening new searcher" error for all cores - I stopped Tomcat, added `ulimit -v unlimited` to the `catalina.sh` script and deleted all old locks in the DSpace `solr` directory and then DSpace started up normally - I'm still not exactly sure why I see this error and if the `ulimit` trick actually helps, as the `tomcat7.service` has `LimitAS=infinity` anyways (and from checking the PID's limits file in `/proc` it seems to be applied) + - Then I noticed that the item displays were blank... so I checked the database info and saw there were some unfinished migrations + - I'm not entirely sure if it's related, but I tried to delete the old migrations and then force running the ignored ones like when we upgraded to [DSpace 5.8 in 2018-06]({{< relref "2018-06.md" >}}) and then after restarting Tomcat I could see the item displays again diff --git a/docs/2019-03/index.html b/docs/2019-03/index.html index 2ebe44380..683ca78cd 100644 --- a/docs/2019-03/index.html +++ b/docs/2019-03/index.html @@ -25,7 +25,7 @@ I think I will need to ask Udana to re-copy and paste the abstracts with more ca - + @@ -55,9 +55,9 @@ I think I will need to ask Udana to re-copy and paste the abstracts with more ca "@type": "BlogPosting", "headline": "March, 2019", "url": "https://alanorth.github.io/cgspace-notes/2019-03/", - "wordCount": "1996", + "wordCount": "2061", "datePublished": "2019-03-01T12:16:30+01:00", - "dateModified": "2019-03-17T18:46:27+02:00", + "dateModified": "2019-03-17T19:13:53+02:00", "author": { "@type": "Person", "name": "Alan Orth" @@ -505,6 +505,8 @@ java.util.EmptyStackException
ulimit -v unlimited
to the catalina.sh
script and deleted all old locks in the DSpace solr
directory and then DSpace started up normallyulimit
trick actually helps, as the tomcat7.service
has LimitAS=infinity
anyways (and from checking the PID’s limits file in /proc
it seems to be applied)