May, 2019
+ +2019-06-02
+ +-
+
- Merge the Solr filterCache and XMLUI ISI journal changes to the
5_x-prod
branch and deploy on CGSpace
+ - Run system updates on CGSpace (linode18) and reboot it +
diff --git a/content/posts/2019-06.md b/content/posts/2019-06.md new file mode 100644 index 000000000..711dc109c --- /dev/null +++ b/content/posts/2019-06.md @@ -0,0 +1,15 @@ +--- +title: "May, 2019" +date: 2019-05-06T10:30:43+03:00 +author: "Alan Orth" +tags: ["Notes"] +--- + +## 2019-06-02 + +- Merge the [Solr filterCache](https://github.com/ilri/DSpace/pull/425) and [XMLUI ISI journal](https://github.com/ilri/DSpace/pull/426) changes to the `5_x-prod` branch and deploy on CGSpace +- Run system updates on CGSpace (linode18) and reboot it + + + + diff --git a/docs/2015-11/index.html b/docs/2015-11/index.html index 6a53a9513..87315c1fe 100644 --- a/docs/2015-11/index.html +++ b/docs/2015-11/index.html @@ -282,12 +282,12 @@ db.statementpool = true
I see the following error in the DSpace log when the user tries to log in with her CGIAR email and password on the LDAP login:
+ +2019-05-30 07:19:35,166 INFO org.dspace.authenticate.LDAPAuthentication @ anonymous:session_id=A5E0C836AF8F3ABB769FE47107AE1CFF:ip_addr=185.71.4.34:failed_login:no DN found for user sa.saini@cgiar.org
+
For now I just created an eperson with her personal email address until I have time to check LDAP to see what’s up with her CGIAR account:
+ +$ dspace user -a -m blah@blah.com -g Sakshi -s Saini -p 'sknflksnfksnfdls'
+
5_x-prod
branch and deploy on CGSpaceDSpace 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