Werk #5806: Periodic service discovery: Fixed scenario where process could get stuck

Component	Checks & agents
Title	Periodic service discovery: Fixed scenario where process could get stuck
Date	May 8, 2018
Level	Trivial Change
Class	Bug Fix
Compatibility	Compatible - no manual interaction needed
Checkmk versions & editions	1.6.0b1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.6.0b1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.6.0b1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.6.0b1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.6.0b1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.6.0b1 Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.5.0b7 Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)

The process discovery (cmk --discover-marked-hosts) triggered by the cronjob had no timeout handling implemented. The python process could get stuck if the connection to the remote host was never closed. This could consume lots of memory over time, since the discovery process is triggered every 5 minutes.

To the list of all Werks