Update notes for 2019-02-25

content/posts/2019-02.md

@@ -1203,5 +1203,19 @@ Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed
 - On a hunch I tried adding `ulimit -v unlimited` to the Tomcat `catalina.sh` and now Solr starts up with no core errors and I actually have statistics for January and February on [some communities](https://cgspace.cgiar.org/handle/10568/16814), but not [others](https://cgspace.cgiar.org/handle/10568/1)
 - I wonder if the address space limits that I added via `LimitAS=infinity` in the systemd service are somehow not working?
 - I did some tests with calling a shell script from systemd on DSpace Test (linode19) and the `LimitAS` setting does work, and the `infinity` setting in systemd does get translated to "unlimited" on the service
+- I thought it might be open file limit, but it seems we're nowhere near the current limit of 16384:
+
+```
+# lsof -u dspace | wc -l
+3016
+```
+
+- For what it's worth I see the same errors about `solr_update_time_stamp` on DSpace Test (linode19)
+- Update DSpace Test to [Tomcat 7.0.93](https://tomcat.apache.org/tomcat-7.0-doc/changelog.html#Tomcat_7.0.93_(violetagg))
+- Something seems to have happened (some Atmire scheduled task, perhaps the CUA one at 7AM?) on CGSpace because I checked a few communities and collections on CGSpace and there are now statistics for January and February
+
+![CGSpace statlets working again](/cgspace-notes/2019/02/statlets-working.png)
+
+- I still have not figured out what the *real* cause for the Solr cores to not load was, though
 
 <!-- vim: set sw=2 ts=2: -->