Mongo pod coming down abruptly after receiving a control signal on the SignalHandler

Ops and Admin
1

{“t”:{"$date":“2021-10-01T07:18:28.358+00:00”},“s”:“I”, “c”:“STORAGE”, “id”:22262, “ctx”:“initandlisten”,“msg”:“Timestamp monitor starting”}
{“t”:{"$date":“2021-10-01T07:18:28.613+00:00”},“s”:“I”, “c”:“CONTROL”, “id”:23377, “ctx”:“SignalHandler”,“msg”:“Received signal”,“attr”:{“signal”:15,“error”:“Terminated”}}
{“t”:{"$date":“2021-10-01T07:18:28.613+00:00”},“s”:“I”, “c”:“CONTROL”, “id”:23378, “ctx”:“SignalHandler”,“msg”:“Signal was sent by kill(2)”,“attr”:{“pid”:0,“uid”:0}}
{“t”:{"$date":“2021-10-01T07:18:28.613+00:00”},“s”:“I”, “c”:“CONTROL”, “id”:23381, “ctx”:“SignalHandler”,“msg”:“will terminate after current cmd ends”}

2

Welcome to the MongoDB Community Forums @balaji_swaroop !

Received signal”,“attr”:{“signal”:15,“error”:“Terminated”}}

Signal 15 (aka SIGTERM) indicates that the process was sent a signal to terminate.

“SignalHandler”,“msg”:“will terminate after current cmd ends”}

This log entry means the process will terminate normally after the current command (i.e. not an abrupt/unexpected shutdown). A SIGTERM signal is one of the common ways to Stop mongod Processes.

So far that all looks as expected. What is your question or concern? Please provide more details on your scenario.

Regards,
Stennie