Restarted checkmk agent every 5 minutes

[usermk]

Hi,

Every minute appears the following traces on /var/log/messages
This is a normal situation? Why is started the service every minute?

==> /var/log/messages <==
Jan 14 22:23:15 SRV01 systemd[1]: Started Checkmk agent (81.61.155.22:39532).
Jan 14 22:23:17 SRV01 systemd[1]: check_mk@37-176.58.115.63:6556-81.61.155.22:39532.service: Succeeded.
Jan 14 22:24:17 SRV01 systemd[1]: Started Checkmk agent (81.61.155.22:47454).
Jan 14 22:24:18 SRV01 systemd[1]: check_mk@38-176.58.115.63:6556-81.61.155.22:47454.service: Succeeded.
Jan 14 22:25:18 SRV01 systemd[1]: Started Checkmk agent (81.61.155.22:37413).
Jan 14 22:25:20 SRV01 systemd[1]: check_mk@39-176.58.115.63:6556-81.61.155.22:37413.service: Succeeded.

It’s possible to hide this?

Thanks in advance

[lkoenig (Lorenz Koenig)]

Hello @usermk,

this is perfectly normal if your agent is configured to run via systemd, which is the default when installed on a system with systemd and no xinetd installed.
You see a message every time your monitoring-server connects to the hosts checkmk-agent (the lines containing “Started Checkmk agent”) and when that request is finished (the “Succeeded” lines).
In this case the host 81.61... should be your monitoring-server.
The default configuration is that your host is checked once every minute.
As far as i know there is currently no way to suppress these messages.
You can however migrate the checkmk-service (back) to xinetd, then you won’t have these messages in your syslog from systemd but then there could be messages from xinetd for the same reasons.
Again, this is perfectly normal and just a message that your monitoring-server is contacting your host.
Hope that helps.

Cheers,
Lorenz

[usermk]

@lkoenig

this is perfectly normal if your agent is configured to run via systemd, which is the default when installed on a system with systemd and no xinetd installed.
You see a message every time your monitoring-server connects to the hosts checkmk-agent (the lines containing “Started Checkmk agent”) and when that request is finished (the “Succeeded” lines).
In this case the host 81.61... should be your monitoring-server.
The default configuration is that your host is checked once every minute.
As far as i know there is currently no way to suppress these messages.
You can however migrate the checkmk-service (back) to xinetd, then you won’t have these messages in your syslog from systemd but then there could be messages from xinetd for the same reasons.
Again, this is perfectly normal and just a message that your monitoring-server is contacting your host.
Hope that helps.

how can I can migrate the checkmk-service (back) to xinetd?

[lkoenig (Lorenz Koenig)]

I think the easiest way would be to install xinetd on your system, then remove the checkmk-agent and install it again. During the installation the checkmk-agent checks if you have xinetd installed and installs the appropriate config-files. When xinetd is found the systemd-socket and service also won’t be activated.

[misilot (Tom)]

Is there a way to squelch these messages from the log, without switching to xinetd?

[tosch (Tobias Schönau)]

This is the normal logging from systemd and not specific to the checkmk agent. If you don’t like these messages inside you main syslog you can take a look at syslogd or syslog-ng (or which logging service active on your system) and how to configure such log messages to another logfile or throw them away.
But i my opinion this messages belong there and are useful in case problems to reconstruct what happend.