Why was my process killed?

When working with Senzing on Linux if you receive similar output to the following, it is likely the Linux kernel killed the Senzing process(s). In addition to Killed you may see ERROR: Thread Shutdown!, depending on operating system levels and distribution. 

This is a result of the Linux Out Of Memory (OOM) manager killing processes in a last ditch effort to keep the system as a whole running when memory is exhausted. This signifies there is a lack of memory configured on the machine running Senzing, or other processes are consuming the resources and Senzing was singled out to be terminated. This is not a bug.

The total amount of memory required to run Senzing will depend on the number of threads configured and the characteristics of the data.

To confirm the Linux OOM killed the process you can check the kernel message buffer with the dmesg command

• dmesg -e 

Note, you may need sudo/root privileges to use dmesg or for a full output, if you are unsure use sudo/root or ask your system administrator. 

Towards the end of the dmesg output check for messages similar to the following for the G2Loader utility as used above, or other similar messages for Senzing processes. 

Please review the minimum system requirements.

If you are seeing "Cannot allocate memory" for the address parser review Error Allocating Memory on Linux - Address Parser.