Thanks for the hint about /var/log. Indeed, you are correct as the OOM
(Out of memory) error is there:
username@computername:~$ grep nlvdw /var/log/syslog
Feb 23 19:05:39 computername kernel: [105834.424171] [26474] 1000
26474 2170623 645513 17096704 617348 0 nlvdw
Feb 23 19:05:39 computername kernel: [105834.424178] Out of memory: Kill
process 26474 (nlvdw) score 713 or sacrifice child
Feb 23 19:05:39 computername kernel: [105834.424199] Killed process
26474 (nlvdw) total-vm:8682492kB, anon-rss:2582048kB, file-rss:4kB,
shmem-rss:0kB
Feb 23 19:05:39 computername kernel: [105835.094146] oom_reaper: reaped
process 26474 (nlvdw), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
On 2/23/2020 9:03 PM, Laurence Marks wrote:
Sounds like it was an OOM error [1]. There should be something in the
system logs (e.g. /var/log). Since OOM handling is performed by the
kernel it is not simple to trap this.
[1] e.g. https://en.m.wikipedia.org/wiki/Out_of_memory
_____
Professor Laurence Marks
"Research is to see what everybody else has seen, and to think what
nobody else has thought", Albert Szent-Gyorgi
www.numis.northwestern.edu <http://www.numis.northwestern.edu>
_______________________________________________
Wien mailing list
Wien@zeus.theochem.tuwien.ac.at
http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
SEARCH the MAILING-LIST at:
http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html
