Hi,
we have a problem with massive logging of information in cmc.log. How could we disable the entries of ‘Executing external command: UPDATE_SHADOW_SERVICE_STATE’?
We tried ‘cmc_log_level = 0’, but that doesn’t changed anything.
We don’t need that information and the cmc.log use a lot of space on our monitoring machine, because we have a lot of running sites.
Kind Regards
Thorsten Bruhns
Hi Thorsten,
how is “WATO → Global settings → Check_MK Micro Core → Log level” set? I think you should restart (not reload) CMC after changing its settings.
Regards,
Marcel
Thorsten Bruhns thorsten.bruhns@googlemail.com schrieb am Mi., 30. Dez. 2015 um 10:12 Uhr: > Hi, > we have a problem with massive logging of information in cmc.log. How could we disable the entries of ‘Executing external command: UPDATE_SHADOW_SERVICE_STATE’?
We tried ‘cmc_log_level = 0’, but that doesn’t changed anything.
We don’t need that information and the cmc.log use a lot of space on our monitoring machine, because we have a lot of running sites.
Kind Regards
Thorsten Bruhns
checkmk-en mailing list
Hi Marcel,
WATO creates the cmc_log_level = 0’ in OMD_SITE/etc/check_mk/conf.d/waro/global.mk, which we already changed. A restart doesn’t reduce the logging of the logging of the remote execution events.
Check_MK is 1.2.7i3p4.cee
2015-12-30 10:42 GMT+01:00 Marcel Schulte schulte.marcel@gmail.com:
Hi Thorsten,
how is “WATO → Global settings → Check_MK Micro Core → Log level” set? I think you should restart (not reload) CMC after changing its settings.
Regards,
Marcel
Thorsten Bruhns thorsten.bruhns@googlemail.com schrieb am Mi., 30. Dez. 2015 um 10:12 Uhr:
Hi,
we have a problem with massive logging of information in cmc.log. How could we disable the entries of ‘Executing external command: UPDATE_SHADOW_SERVICE_STATE’?
We tried ‘cmc_log_level = 0’, but that doesn’t changed anything.We don’t need that information and the cmc.log use a lot of space on our monitoring machine, because we have a lot of running sites.
Kind Regards
Thorsten Bruhns
checkmk-en mailing list
Hi Thorsten,
we’re running 1.2.6p2. Setting cmc_log_level from 6 (Informational) to 4 (Warning) and restarting cmc (via “cmk -R”) caused the cmc.log to print “2015-12-30 11:31:53 [5] This is the end. Good bye and thanks for running me.” as last entry. That’s the last level 5 message. Executing external command is always level 5 (Notice) here and includes forces svc schedules (like clicking the reschedule icon of the Check_MK service. Those log messages do not appear anymore after changing log_level to 4…
Good luck with your innovation release (remember: it’s not meant for production use 
and greatings to the MK guys - in case you contact them for fixing your issue…
Regards,
Marcel
2015-12-30 10:42 GMT+01:00 Marcel Schulte schulte.marcel@gmail.com:
Hi Thorsten,
how is “WATO → Global settings → Check_MK Micro Core → Log level” set? I think you should restart (not reload) CMC after changing its settings.
Regards,
Marcel
Thorsten Bruhns thorsten.bruhns@googlemail.com schrieb am Mi., 30. Dez. 2015 um 10:12 Uhr:
Hi,
we have a problem with massive logging of information in cmc.log. How could we disable the entries of ‘Executing external command: UPDATE_SHADOW_SERVICE_STATE’?
We tried ‘cmc_log_level = 0’, but that doesn’t changed anything.We don’t need that information and the cmc.log use a lot of space on our monitoring machine, because we have a lot of running sites.
Kind Regards
Thorsten Bruhns
checkmk-en mailing list