Hi there,
we’re using checkmk CEE v2.4.0p30
since which release is the command cmk-update-agent gone ?
I also couldn’t find a note here Checkmk 2.4 Release Notes
Thanks
It’s still there. Just look at the Werks: Werks .
However, it might be elsewhere, especially when switching to/back from single folder/non-root deployment.
ok but what about this picture then?
root@lnzdev01:~ # rpm -ql check-mk-agent
/etc/check_mk
/etc/check_mk/super-server.cfg
/etc/check_mk/xinetd-service-template.cfg
/usr/bin/check_mk_agent
/usr/bin/check_mk_caching_agent
/usr/bin/mk-job
/usr/bin/waitmax
/usr/lib/check_mk_agent
/usr/lib/check_mk_agent/agent_info.json
/usr/lib/check_mk_agent/local
/usr/lib/check_mk_agent/plugins
/var/lib/check_mk_agent
/var/lib/check_mk_agent/cache
/var/lib/check_mk_agent/job
/var/lib/check_mk_agent/spool
/var/lib/cmk-agent/cmk-agent-ctl.gz
/var/lib/cmk-agent/cmk-agent-ctl.toml
/var/lib/cmk-agent/scripts/manage-agent-user.sh
/var/lib/cmk-agent/scripts/manage-binaries.sh
/var/lib/cmk-agent/scripts/migrate.sh
/var/lib/cmk-agent/scripts/super-server/0_systemd/check-mk-agent-async.service
/var/lib/cmk-agent/scripts/super-server/0_systemd/check-mk-agent.socket
/var/lib/cmk-agent/scripts/super-server/0_systemd/check-mk-agent.socket.fallback
/var/lib/cmk-agent/scripts/super-server/0_systemd/check-mk-agent@.service
/var/lib/cmk-agent/scripts/super-server/0_systemd/cmk-agent-ctl-daemon.service
/var/lib/cmk-agent/scripts/super-server/0_systemd/setup
/var/lib/cmk-agent/scripts/super-server/1_xinetd/setup
/var/lib/cmk-agent/scripts/super-server/setup
root@lnzdev01:~ #
root@lnzdev01:~ # cmk-agent-ctl status
Version: 2.4.0p30
Agent socket: operational
here I’m simply missing cmk-update-agent.
I also didn’t change the agent directory in the package.
how did I get this package? The rpm file is a baked and signed rpm package, which is then picked up by all Linux hosts after we upgrade checkmk server.
And additionally saved on our on-prem repomirror for a fresh installation.
The files shown look like a completely unconfigured Linux agent package, without any plugins or local checks or other configuration.
I agree. I also see now that I only have the vanilla available agent configurationleft :
in the past, I had at least one additional agent configuration.
This disappeared now (with an update ?), and basically must be reproduced again. But this is not the problem.
side-effect: we work with ansible, and it’s a 2-step process: 1st installs the agent via repomirror, 2nd step would run cmk-update-agent register..., and this works not anymore. I need to find out why cmk-update-agent does not exist in the package anymore 
. And this on every linux host meanwhile.
I noticed also the following. Last week I upgraded checkmk server from 2.4.0p26 to p30.
No problem seen. I expected that the agent also update themself (after baking the agent), which happened. So fine, so good.
but the current picture I see is the following
so although all agents were updated to Version: 2.4.0p30 , it still shows need an update.
Strange. I need to escape from this weird situation 
