I’m using the latest version, 2.0.0p12 both on checkmk sever and on agent.
I used to have some cached plugins, as recommended, sshd_config and apt.
I noticed that the apt plugin wasn’t updating, it reported for many days that some updates were required but there were none, so I deleted the cache with rm /var/lib/check_mk_agent/cache/*
After that, those files were never recreated again, and I get the service problem “[agent] Version: 2.0.0p12, OS: linux, Missing monitoring data for check plugins: apt, sshd_configWARN, execution time 2.2 sec”
If I run, as root, check_mk_agent | grep -A 5 sshd_config the files are created (it doesn’t output them the first time, but if I run that again they are in the output)
So I thought it was a permission issue, I did a chmod 777 /var/lib/check_mk_agent/cache/ since I don’t know what user will write them, but nothing changes, the files aren’t created automatically…
Same issue happening in multiple servers, xinetd is running
To replicate the issue, you can download the mk_apt plugin inside /usr/lib/check_mk_agent/plugins/3600/
This is how cached plugins used to work, now I don’t see much documentation about this feature
I have no idea, I have the /etc/xinetd.d/check_mk created by checkmk, I only changed the only_from line:
service check_mk
{
type = UNLISTED
port = 6556
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/bin/check_mk_agent
# To avoid intentional or unintentional overload due to too many parallel
# queries from one source we set this parameter. It limits the number of
# concurrent connections per source address. If you need more requests
# per source system, you can of course increase or remove this value
# (https://github.com/tribe29/checkmk/pull/157)
per_source = 3
# listen on IPv4 AND IPv6 when available on this host
#flags = IPv6
# If you use fully redundant monitoring and poll the client
# from more then one monitoring servers in parallel you might
# want to use the agent cache wrapper:
#server = /usr/bin/check_mk_caching_agent
# configure the IP address(es) of your Nagios server here:
only_from = xxx.xxx.xxx.xxx 127.0.0.1
# Don't be too verbose. Don't log every check. This might be
# commented out for debugging. If this option is commented out
# the default options will be used for this service.
log_on_success =
disable = no
}
I never did anything else and they always worked, is there something else to do?
In the default configuration the check_mk_agent should be managed by systemd (as the socket suggests). Not sure why the xinetd config has not been removed. Try removing the xinetd service manually.
You should have three Checkmk related systemd unit files: “check-mk-agent-async.service” (enabled and active), “check-mk-agent.socket” (enabled and active), and the template “check-mk-agent@.service”.
I think they’re called “check_mk” instead of “check-mk-agent” in the RawEdition.
I think this is a very old file from before 1.4 which remained on the system. Today this file is called /etc/xinetd.d/check_mk_agent. I hae ssen similar occasions where this file was left over from an old agent installation.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.
