原因分析：If a process is consuming too much memory then the kernel "Out of Memory" (OOM) killer will automatically kill the offending process. It sounds like this may have happened to your job. The kernel log should show OOM killer actions, so use the "dmesg" command to see what happened, e.g.
dmesg | less #或者更精准地使用下面命令 dmesg | grep -i kill #get datetime dmesg -e | grep -i kill
或者
we can inspect the kernel logs /var/log/kern.log*
The default virtual memory setting for Linux is to over-commit memory. This means the kernel will allow one to allocate more memory than is available, allowing processes to memory map large regions because normally not all the pages in the allocation are used. However, sometimes a process will read/write to all the pages that are over committed and the kernel cannot provide enough physical memory + swap, so the OOM killer attempts to find the best candidate overcommitted process and kill it.
grep /var/log/kern.log* -ie kill
参考：
How to find out why process was killed on server
标签：kernel,log,process,Ubuntu,Terminal,kill,memory,killed From： https://www.cnblogs.com/carsonzhu/p/16829338.html