Agent Problems after update to 2.1.0

Troubleshooting
, ,
41

Hi,
So i discovered today when deploying a new agent that there is now 4 services running for the agent.
SELinux should be either disabled or configured else the new agent fail.
Early editions of the agent would not enable the new services nor start them.
You have to go on each of them and run this :

systemctl enable --now check-mk-agent-async.service
systemctl enable --now check-mk-agent.socket
systemctl enable --now cmk-agent-ctl-daemon.service
systemctl enable --now cmk-update-agent.timer
42

Hello together,

now that I have set up a new server, there was one less. Since today I was able to connect the last server with TLS. So now all servers are running normally again.

Thanks everyone for the support.

Bye, Sascha

43

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.