![]() The corresponding options can be displayed when calling cmk-update-agent register-help. Here it makes sense to pass the required registration information directly via the command line – especially if you want to use an installation script. Register the host on the Checkmk server by invoking cmk-update-agent register. Note: Please check at this point that you have specified everything correctly before you re-bake the agents.Ĭopy the cmk-update-agent binary or the cmk_update_agent.py script to the host to be monitored (both can be found at ~/share/check_mk/agents/plugins on the Checkmk server). Lastly, in the agent updater rule on the old site, configure the fields for the update server and the name of the Checkmk site conforming to your new monitoring site, and bake the agents again. Import these signature keys from step 2 on the new monitoring site.Ĭonfigure the agent updater rule on the new monitoring site according to the instructions, and sign the baked agents with the imported signature key(s). The signature keys can be exported and imported using Setup > Agents > Windows, Linux, Solaris, AIX > Agents > Signature keys. Then copy the ~/var/check_mk/agent_deployment folder from the old to the new monitoring site.Įxport the signature key(s) that are accepted by the agents installed on the hosts. Make sure the hosts in the new site are monitored under the same name. 17:58:18,387 INFO: Ignoring signature #1 for certificate: certificate is unknown.įile "/build/enterprise/agents/plugins/cmk_update_agent.py", line 1733, in mainįile "/build/enterprise/agents/plugins/cmk_update_agent.py", line 714, in runįile "/build/enterprise/agents/plugins/cmk_update_agent.py", line 1372, in _run_modeįile "/build/enterprise/agents/plugins/cmk_update_agent.py", line 1071, in _do_update_as_commandįile "/build/enterprise/agents/plugins/cmk_update_agent.py", line 1150, in _do_update_agentįile "/build/enterprise/agents/plugins/cmk_update_agent.py", line 1221, in _check_signaturesįirst add all hosts whose registration information is to be migrated to the new site to the monitoring. 17:58:18,387 INFO: Target state (from deployment server): 17:58:18,322 DEBUG: Successfully read /etc/check_mk/cmk-update-agent.cfg. 17:58:18,322 DEBUG: Successfully read /etc/cmk-update-agent.state. More details on this can be found below at Viewing the local configuration. ![]() Options that are saved only in cmk-update-agent.state will be overwritten - options from cmk-update-agent.cfg, however, won’t. While the interactive mode only polls fields that are not yet in any configuration, the non-interactive mode allows all fields displayed in the help to be set and has the highest priority for this call. The password of the Checkmk administrator is not stored anywhere. On registration the agent and the server agree a secret key ( host secret) known only to this host. The login as Checkmk administrator is only required once. The authenticity of the agent is however ensured independently by the signature. ![]() Since the agent can theoretically contain passwords, HTTPS is the recommended method. HTTP is much easier here, but does not provide encryption of the transmission. To use HTTPS, HTTPS must also be set up on your monitoring server. The host name is then stored locally together with the key. This is not necessarily identical to the computer’s host name. When registering, the plug-in also needs the name of the host as it is known in the monitoring. Other architectures: If you have packages for other architectures such as arm or ppc, set this option manually to Python, since Checkmk does not intercept this automatically and no binaries are offered for these platforms. Checkmk will use the Python script even if you leave the default value on the 64-bit binary. ![]() Solaris: You do not have to modify anything here either. Note: Should you find a 64-bit binary of the agent updater on any of your Windows hosts, this version dates back to an older version of Checkmk and is not up-to-date. This rule is being ignored for Windows hosts. Windows: For Windows hosts Checkmk will always deploy a 32-bit-executable. Linux distributions have generally met these requirements since 2006. Important: For the binary you will need the glibc package (minimum the 2.5 version). You can also optionally select a 32-bit binary for legacy systems, or the old Python script. Linux (deb, rpm, tgz): You do not have to manually edit anything for these systems the agent updater is passed as a 64-bit binary.
0 Comments
Leave a Reply. |