...
Also you need to configure the distributed agent bakery.
With Checkmk 2.0, there is a new option for the Agent Updater:
Usage: In case of "Registration and fallback", the agent updater will use this information only on registration and rely on the update URL provided by the agent bakery afterwards. If the connection fails, the agent updater will additionally use this information as a fallback. In case of "Use for all connections", the agent updater will ignore the update URL provided by the agent bakery.
If you want to use the distributed Agent bakery, you need to select 'Registration and fallback'
| Info |
|---|
|
Now you can bake, sign and register the agent:
| Code Block |
|---|
root@ip-172-31-34-134:/home/ubuntu# cmk-update-agent register
Our host name in the monitoring:
slave2
WATO user with admin permissions:
cmkadmin
Password:
Successfully registered agent of host "slave2" for deployment. |
If you want to run the agent updater this will not work.
| Code Block |
|---|
root@ip-172-31-34-134:/home/ubuntu# cmk-update-agent -v
+-------------------------------------------------------------------+
| |
| Check_MK Agent Updater v2.0.0b4 - Update |
| |
+-------------------------------------------------------------------+
Getting target agent configuration for host 'slave2' from deployment server
Agent Bakery: Registering/updating at remote site but found no URL to central site. Please provide it in "automatic agent updates" section at global settings.
See syslog or Logfile at /var/lib/check_mk_agent/cmk-update-agent.log for details. |
To get the updater working, please follow the Step-by-step guide!
Step-by-step guide
- Configure the connection to the central agent bakery
Setup → General → Global settings → AUTOMATIC AGENT UPDATES → Connection to the central agent bakery
Info 
Now you can register and update the host
Code Block root@ip-172-31-34-134:/home/ubuntu# cmk-update-agent register -v +-------------------------------------------------------------------+ | | | Check_MK Agent Updater v2.0.0b4 - Registration | | | | Activation of automatic agent updates. Your first step is to | | register this host at your deployment server for agent updates. | | For this step you need an administration account on WATO for | | that server. | | | +-------------------------------------------------------------------+ Using previous settings from /etc/cmk-update-agent.state. Password for user 'cmkadmin': Going to register agent at deployment server Successfully registered agent of host "slave2" for deployment. You can now update your agent by running 'cmk-update-agent -v' Saved your registration settings to /etc/cmk-update-agent.state. root@ip-172-31-34-134:/home/ubuntu# cmk-update-agent -v +-------------------------------------------------------------------+ | | | Check_MK Agent Updater v2.0.0b4 - Update | | | +-------------------------------------------------------------------+ Getting target agent configuration for host 'slave2' from deployment server Target state (from deployment server): Agent Available: True Signatures: 1 Target Hash: 67f84ee7e41b73aa Agent 67f84ee7e41b73aa already installed. root@ip-172-31-34-134:/home/ubuntu#
...