--- title: "August, 2018" date: 2018-08-01T11:52:54+03:00 author: "Alan Orth" tags: ["Notes"] --- ## 2018-08-01 - DSpace Test had crashed at some point yesterday morning and I see the following in `dmesg`: ``` [Tue Jul 31 00:00:41 2018] Out of memory: Kill process 1394 (java) score 668 or sacrifice child [Tue Jul 31 00:00:41 2018] Killed process 1394 (java) total-vm:15601860kB, anon-rss:5355528kB, file-rss:0kB, shmem-rss:0kB [Tue Jul 31 00:00:41 2018] oom_reaper: reaped process 1394 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB ``` - Judging from the time of the crash it was probably related to the Discovery indexing that starts at midnight - From the DSpace log I see that eventually Solr stopped responding, so I guess the `java` process that was OOM killed above was Tomcat's - I'm not sure why Tomcat didn't crash with an OutOfMemoryError... - Anyways, perhaps I should increase the JVM heap from 5120m to 6144m like we did a few months ago when we tried to run the whole CGSpace Solr core - The server only has 8GB of RAM so we'll eventually need to upgrade to a larger one because we'll start starving the OS, PostgreSQL, and command line batch processes - I ran all system updates on DSpace Test and rebooted it