The dspace does not work #9

Activity

1. firecyberice commented on Jun 28, 2018

   

   firecyberice

   on Jun 28, 2018

   Contributor

   More actions

   I cannot reproduce this.
   I executed:

   wget https://raw.githubusercontent.com/4Science/dspace-docker/master/docker-compose.yml
   docker-compose up -d
   

   and it just worked.

   What is your output of docker ps -a?
   Please have a look at docker-compose logs -f nextcloud.
2. lexnat187 commented on Sep 6, 2018

   

   lexnat187

   on Sep 6, 2018

   More actions

   I have the same issue, running docker-compose up -d brings up the postgres and dspace containers but eventually the dspace container shuts down. Running docker ps -a shows it with a status of Exited (137)

   I've ran some commands to see if it was a memory issue as I was using a small instance on AWS, I'm not convinced its a memory issue though. Can someone look through the logs below and tell me if I am missing something on it?

   journalctl -k | grep -i -e memory -e oom
   Sep 05 18:10:37 ubuntu kernel: Scanning 1 areas for low memory corruption
   Sep 05 18:10:37 ubuntu kernel: Base memory trampoline at [ffff880000096000] 96000 size 28672
   Sep 05 18:10:37 ubuntu kernel: Early memory node ranges
   Sep 05 18:10:37 ubuntu kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
   Sep 05 18:10:37 ubuntu kernel: PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
   Sep 05 18:10:37 ubuntu kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
   Sep 05 18:10:37 ubuntu kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
   Sep 05 18:10:37 ubuntu kernel: Memory: 2030712K/2096756K available (8372K kernel code, 1281K rwdata, 3888K rodata, 1504K init, 1264K bss, 66044K reserved, 0K cma-reserved)
   Sep 05 18:10:37 ubuntu kernel: Initializing cgroup subsys memory
   Sep 05 18:10:37 ubuntu kernel: Freeing initrd memory: 12412K
   Sep 05 18:10:37 ubuntu kernel: Scanning for low memory corruption every 60 seconds
   Sep 05 18:10:37 ubuntu kernel: Freeing unused kernel memory: 1504K
   Sep 05 18:10:37 ubuntu kernel: Freeing unused kernel memory: 1856K
   Sep 05 18:10:37 ubuntu kernel: Freeing unused kernel memory: 208K
   Sep 05 18:37:27 ip-172-31-47-215 kernel: java invoked oom-killer: gfp_mask=0x24280ca, order=0, oom_score_adj=0
   Sep 05 18:37:27 ip-172-31-47-215 kernel: [] oom_kill_process+0x202/0x3c0
   Sep 05 18:37:27 ip-172-31-47-215 kernel: [] out_of_memory+0x219/0x460
   Sep 05 18:37:27 ip-172-31-47-215 kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
   Sep 05 18:37:27 ip-172-31-47-215 kernel: Out of memory: Kill process 5753 (java) score 839 or sacrifice child
   Sep 05 23:28:49 ip-172-31-47-215 kernel: java invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
   Sep 05 23:28:49 ip-172-31-47-215 kernel: [] oom_kill_process+0x202/0x3c0
   Sep 05 23:28:49 ip-172-31-47-215 kernel: [] out_of_memory+0x219/0x460
   Sep 05 23:28:49 ip-172-31-47-215 kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
   Sep 05 23:28:49 ip-172-31-47-215 kernel: Out of memory: Kill process 6697 (java) score 855 or sacrifice child
   Sep 06 03:52:00 ip-172-31-47-215 kernel: postgres invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
   Sep 06 03:52:00 ip-172-31-47-215 kernel: [] oom_kill_process+0x202/0x3c0
   Sep 06 03:52:00 ip-172-31-47-215 kernel: [] out_of_memory+0x219/0x460
   Sep 06 03:52:00 ip-172-31-47-215 kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
   Sep 06 03:52:00 ip-172-31-47-215 kernel: Out of memory: Kill process 8697 (java) score 846 or sacrifice child

   inspecting the container shows:
   "State": {
   "Status": "exited",
   "Running": false,
   "Paused": false,
   "Restarting": false,
   "OOMKilled": false,
   "Dead": false,
   "Pid": 0,
   "ExitCode": 137,
   "Error": "",
   "StartedAt": "2018-09-06T03:29:14.807541343Z",
   "FinishedAt": "2018-09-06T03:52:01.00011945Z"
   },