The exact command line is this: cmk-agent-ctl register -v -H HOSTNAME -P 'PASSWORD' -s SUBDOMAIN. Upon first try, “cmk-agent-ctl register. Jun 17 10:57:15 nc systemd[1]: cmk-agent-ctl-daemon. WARNING: The Agent Controller is operating in an insecure mode! To secure the connection run cmk-agent-ctl register. 1 using the Agent Controller. target. via journalctl -u cmk-agent-ctl-daemon. windows. If you want to use the agent in legacy mode, you need to disable cmk-agent-ctl in bakery rules. OK, please also stop cmk-agent-ctl-daemon. Ok, so the user I’m using to do the agent registration. 0p24 to 2. So if you make any changes to the config file then you need to reload configuration or restart the agent. 4. For more information try --helpcmk-agent-ctl register --server cmkserver:443 --trust-cert --site cmksite --user username --password password --hostname monitoringhost On Debian 11 if got the following outputTo register the agent, I ran: sudo cmk-agent-ctl register --hostname localhost --server localhost:8001 --site cmk --user cmkadmin That gives: > sudo cmk-agent-ctl status Version: 2. So if you make any changes to the config file then you need to reload configuration or restart the agent. 1. Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins) I have registered over 100 hosts successfull but something is wrong with this one when I use that command: & 'C:\Program Files (x86)\checkmk\service\cmk-agent-ctl. Wenn ich aber beim Registrieren den richtigen Port mitgebe, dann gehts…. For more information try --help Command for registration. 0 adds the Agent Controller and new features to the agent script. B. I created the folder manually and changed ownership, and now the registration is working! ERROR [cmk_agent_ctl] Something seems wrong with the agent socket (/run/check-mk-agent. exe' register -s checkmk. server --site Main --user cmkadmin --verbose erscheint folgendes: image 1902×257 114 KB. I’m running 2. On a related note, I’ve been following the beginner’s guide on setting up Checkmk and found that registering the Checkmk Agent for monitoring the monitoring server itself not working. You already entered the right command with openssl s_client -connect SLAVE01:443. If the server you want to monitor and register is the monitoring docker. socket systemctl status cmk-agent-ctl-daemon. Create MSI file for windows 2019 server. The agent-receiver of the first checkmk instance usually listens on port 8000, this is the port you need the agent to register against. The Windows agent of Checkmk version 2. Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins) sudo: cmk: command not found. 1 server? You have to run the cmk-agent-ctl on the machine running the agent, not from the server. check_für das Abfragen von Webseiten. socket systemctl status cmk-agent-ctl-daemon. 0 2. So now you must de-register, on the host: cmk-agent-ctl delete-all --enable-insecure-connections Then on the CMK server: Properties of host, then menu entry Host > Remove TLS registration Afterwards connections should work albeit insecure. The controller is executed under the cmk-agent user, which has limited privileges, e. Version: 2. 0p11 on Debian 11. Registration indeed is good. serviceThe Agent Controller cmk-agent-ctl is the component within the agent that is responsible for transporting the data collected by the agent script. com--site FOO --user BAR -. If you use the bakery, the agent was baked with enabled cmk-agent-ctl. Home ; Categories ;Registration indeed is good. In order to register at a Checkmk site, the agent controller ( cmk-agent-ctl) needs to know, among others, the name of the server where the site is running and a. 1. This is realized by a new component on the monitored hosts: The Checkmk agent controller cmk-agent-ctl. Finally, in Bake agent packages, activate. cmk-update-agent –v. cre default. As suggested in another post i read i checked:-that port 8000 is open-omd config show | grep AGENT_RECEIVER show port 8000Jun 17 10:57:15 nc systemd[1]: cmk-agent-ctl-daemon. cmk-update-agent register -v -H COMPUTERNAME -U register -S xxxxxxxxxxxxxxxxx. Another gotcha I came across was trying to run the register, make sure you are using admin cmd ( which you are ), then cut and paste the command in full : “C:Program Files (x86)checkmkservicecmk-agent-ctl. 1. Monitoring Windows - The new agent for Windows in detail. Checkmk Community Trouble after upgrading to 2. 0 did not yet use TLS, so port 8000 didn’t need to be exposed back then. Back on server, Add server under hosts. 0 RAW OS: Windows Server 2019 Agent controller not registered After multiple clean installations specifically on this server I can’t get CheckMK to work. This might be a bug. As suggested in another post i read i checked:-that port 8000 is open-omd config show | grep AGENT_RECEIVER show port 8000cmk-agent-ctl register --server cmkserver:443 --trust-cert --site cmksite --user username --password password --hostname monitoringhost On Debian 11 if got the following outputCMK version: 2. $ sudo cmk-agent-ctl register --hostname localhost --server checkmk. exe” register --site yousitename --server yourcmkserver --user automation --hostname windows_box_hostname --password1. For example, the registration crashed with "500 Internal Server Error" for users without the permission "Write access to all hosts and folders". cmk-agent-ctl. Der Linux-Agent der Checkmk-Version 2. This port can be found out via omd config > Basics > AGENT_RECEIVER_PORT Of course, this port has to be exposed for the. The added executable is called cmk-agent-ctl. TLD -i SITE-NAME -U USERNAME. OS is Ubuntu 22. 2 Delete all directories/files of the agent controller from the host. Thanks for your responses! @cyr0nk0r I rebaked the Agent using HTTP only and got rid of the. The folder /var/lib/cmk-agent was missing on my SUSE Linux Enterprise Micro 5. sh script. 04 Command used for registration: cmk-agent-ctl. 4:8000 --site cmk --user cmkadmin --password password. In case it is left out, the agent controller tries to query the port from the REST API. Ob der Host dabei für den Pull-Modus (alle Editionen) oder den Push-Modus (nur Cloud Edition) konfiguriert ist, macht für die Befehlsbeispiele keinen Unterschied. cmk-agent-ctl register -v -H HOSTNAME -P 'PASSWORD' -s SUBDOMAIN. One of my hosts is producing this error, while most others register fine: root@sshgateway:~# cmk-agent-ctl register --hostname gateway. Anders (Anders) November 27, 2022, 4:25pm 1 CMK version: 2. 0) master 1. 0p10 Agent socket: operational IP allowlist: any Connection: localhost:8001/cmk UUID: 186f71b9-8d6f-41c6-be44-bb1f7c23ae7b Local: Connection. g. cmk-agent-ctl register --server cmkserver:443 --trust-cert --site cmksite --user username --password password --hostname monitoringhost On Debian 11 if got the following outputTo register the agent, I ran: sudo cmk-agent-ctl register --hostname localhost --server localhost:8001 --site cmk --user cmkadmin That gives: > sudo cmk-agent-ctl status Version: 2. 0 did not yet use TLS, so port 8000 didn’t need to be exposed back then. CMK 2. 2 system. If it is xinetd remove the. 2. New replies are no longer allowed. 1. Whether the host is configured for the pull mode (all editions) or the push mode (only the Cloud Edition) makes no difference for the command examples. 1 server? You have to run the cmk-agent-ctl on the machine running the agent, not from the server. Nun hast Du 2 Möglichkeiten: Entweder den controller für TLS registrieren (cmk-agent-ctl register -h für die Hilfe) oderCheckmk Enterprise Edition 2. Hello. DEBUG [cmk_agent_ctl::modes::pull] handle_request starts DEBUG [rustls::server::hs] decided upon suite TLS13_AES_256_GCM_SHA384 WARN [rustls::conn] Sending fatal alert HandshakeFailure DEBUG [cmk_agent_ctl::modes::renew_certificate] Checking registered connections for certificate expiry. , I had to put the public hostname). folgenden Register Befehl benutzt. CMK version: 2. The client must set the version 0 for the CSRThe register command cmk-agent-ctl register often gets confused with the Agent update registration cmk-agent-update register, but these are two different registration types: one for TLS encryption and one for registering automatic updates (Agent Bakery, cee). Upon first try, “cmk-agent-ctl register. I dont know why this folder could not be created during cmk agent installation from the cmk-agent-useradd. rs:14: st… As mentioned in another thread, you actually ran into a newly implemented CSR version check that’s. The register command cmk-agent-ctl register often gets confused with the Agent update registration cmk-agent-update register, but these are two different registration types: one for TLS encryption and one for registering automatic updates (Agent Bakery, cee). I confused the keyword register on cmk-agent-ctl register with cmk-update-agent register or perhaps on some subconscious level assumed the first would handle both. Or if you have a specific role for a admin user, go to: Roles & permissions and see this permissions. 0. From its very beginning, monitoring Windows servers has been one of the most important tasks performed by Checkmk. CMK version: 2. Agent auf allen Monitored Hosts installiert. Added new host in CMK. 1. exe register --hostname xxx --server checkmk:8000 --site monitoring --user automation --… Hi, in the register-command use --server checkmk without the port, maybe there is a formatting problem with that. agent_pairing”) to his/her role. 1. How to Contact. 1. The docker run command from the documentation is using -p 8000:8000 to bind that port externally. WalterH (Walter Hofstädtler) May 30, 2022, 5:42pm 31. service I see this error: ERROR [cmk_agent_ctl] Failed to listen on TCP socket for incoming pull connections. a re-register has the same effect, even with a cmk-agent-ctl delete and a “remove TLS registration”. I dont know why this folder could not be created during cmk agent installation from the cmk-agent-useradd. As for all other server operating systems, Checkmk therefore also provides its own agent for Windows, an agent program that is both minimalistic and secure. 0 onwards), you have to add the following rights (internal name "general. The server and the host are on the same network, the same virtualization cluster. 0 did not yet use TLS, so port 8000 didn’t need to be exposed back then. Ich registriere den Agent : sudo cmk-agent-ctl register --hostname hlcmk --server 10. I created the folder manually and changed ownership, and now the registration is working! Agent Controller is not running, no config files can be found in the systemd directory and within xinetd. Reload check_mk configuration using below command –. OS version: TrueNAS SCALE 22. 0. exe – register --trust-cert’ USAGE: cmk-agent-ctl. Jun 17 10:57:15 nc systemd[1]: cmk-agent-ctl-daemon. We’ll come back to you to ask for. If I try to register (not register-new) a server, which has been in the monitoring since yea…The agent control use the port 8000 for communication. 1. If I try to register it with the command: cmk-agent-ctl register --detect-proxy --hostname FOO --server bla. 1. agent_pairing") to their role. Contact an admin if you think this should be re-opened. 1 Like. cme and I’m no longer able to register new hosts with an automation user “cmkautomation” that I created a while ago (with role “agent_registration”). 1. Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins) sudo: cmk: command not found. 1. socket systemctl status cmk-agent-ctl-daemon. 0 or earlier. 0. I was using 8101 so after i set this it worked perfectly. Contact an admin if you think this should be re-opened. 1. slice (loaded active) and check_mk. domain. rs:41: Loaded config from. Reload check_mk configuration using below command –. local:8000 -s checkmk. com:8000/cmk. net -i STAR -P 'XXXXX' -U automation -H sys-vbr02Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins) I have registered over 100 hosts successfull but something is wrong with this one when I use that command: & 'C:Program Files (x86)checkmkservicecmk-agent-ctl. Upon first try, “cmk-agent-ctl register. 6 Likes. B. Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins) I have registered over 100 hosts successfull but something is wrong with this one when I use that command: & 'C:Program Files (x86)checkmkservicecmk-agent-ctl. checkmk-v2-1. deb. 0p22 agent by running cmk-agent-ctl on the 2. Hi, Some days ago i was testing this software, do a few tests and lately installed on a VM runing linux mint 20. What I already tried: I tried only listening on ports 80 and 443 for caddy, with {"serverDuration": 24, "requestCorrelationId": "464b55cee9f74460a402ac4a40d2b489"} Checkmk Knowledge Base {"serverDuration": 18, "requestCorrelationId. Redirecting to /bin/systemctl reload xinetd. The Agent Controller cmk-agent-ctl is the component within the agent that is responsible for transporting the data collected by the agent script. CMK version: 2. Bei der Registrierung wurde in den Anleitungen von chekmk mit dem “automation” User gearbeitet, ich habe es mit dem cmkadmin gemacht was bei den. pem. After a reboot the cmk-agent-ctl-daemon and the check-mk-agent. 0p20 Debian 11. The new TLS feature is need to register with cmk-agent-ctl register command. This is the command we used to register the agent: C:Windowssystem32> "C:Program Files (x86)checkmkservicecmk-agent-ctl. 0. 0b4_0 raw OS: Ubuntu 20. To register the agent, I ran: sudo cmk-agent-ctl register --hostname localhost --server localhost:8001 --site cmk --user cmkadmin That gives: > sudo cmk-agent-ctl status Version: 2. You might apt-get remove the old Checkmk package when no site is using it any more. I try with: cmk-agent-ctl register --hostname MYHOST --server CMKHOST --site MYSITE --user cmkadmin --password ‘MYPASSWORD’ Then I get the message: Thx for the quick reply, adding the port gives still the same result: root@paperless-ngx:~# cmk-agent-ctl register --trust-cert -H paperless-ngx. exe” register. After the installation everything worked. NOTE: A registered host will refuse all unencrypted connections. Thx for the quick reply, adding the port gives still the same result: root@paperless-ngx:~# cmk-agent-ctl register --trust-cert -H paperless-ngx. In the following Monitoring agents box, you specify two important options for the auto-registration. 1 Like. For example, the registration crashed with "500 Internal Server Error" for users without the permission "Write access to all hosts and folders". CMK version: 2. To register a host, users need the following permissions: Agent pairing. 0 Zeiten registriert) Registrierung über den Servernamen “checkmk” meines CheckMK Servers und der Instanz “lexx”. 1. The cmk-agent user was sucessfully created. 0p10 Agent socket: operational IP allowlist: any Connection: localhost:8001/cmk UUID: 186f71b9-8d6f-41c6-be44-bb1f7c23ae7b Local: Connection. On every host I register that way I don’t get any agent data because of the Issue Host is registe. Hosts, services and agents. ourcompany. 1. The user used for registering has admin privileges at checkmk and is able to see the global setting at the webui. Checkmk. Only after I manually ran “cmk-agent-ctl register” it listened again. socket. You also need a --hostname flag, like --hostname test. When I try to register the client to the server (which is inside of docker) I try the following line: (I only have IP addresses and firewall is open) cmk-agent-ctl register --hostname ip_of_client --server 1. Install went fine. DOMAIN. Upon first try, “cmk-agent-ctl register. 0p2 RAW Edition. XXX. CMK Checkmk Enterprise Edition 2. 2. rs:14: starting [2023-02-10 12:54:18. There were some user permission issues with the agent registration (cmk-agent-ctl register. My server proxmox follow the guide from checkmk, where create the user, policy, open port 6556, special agent. If there are leftovers from 2. For Debian remove the cmk-agent and purge the configuration, than reinstall the agent, this purges the xinetd configuration. I have purged checkmk, rebooted and reinstalled the agent on the one hosts but this is not a procedure I really want to do on all my hosts because even 60 seconds of downtime will require careful planning in advance, which will turn the mass registration. 0p20 Ubuntu 20. This was not expected as I created rules in “Agent controller” {'agent_ctl_enabled': True}. Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins) I have registered over 100 hosts successfull but something is wrong with this one when I use that command: & 'C:Program Files (x86)checkmkservicecmk-agent-ctl. 0 adds the Agent Controller and new features to the agent program. Here it makes sense to pass the required registration information directly via the command. service should work as expected. mschlenker (Mattias Schlenker) July 8, 2022, 8:12am 4. Agent Victoria, British Columbia 1970's Members Murray Acton ~ Guitar, Vocals Steve Andreas ~ Bass, Vocals Peter Bryant ~ Drums, Vocals Wayne Darling ~. Die Registrierung der Agents in der Version 2. ” failed with this error: "Request failed with code 500 Internal Server Error: Internal Server Error"The folder /var/lib/cmk-agent was missing on my SUSE Linux Enterprise Micro 5. I am trying to register an agent installed on a Windows Server 2019. 1 gave 404 Not Found: Host 127. Monthly Promotions Product Specials and Monthly Flyers Emailed Right to You! Online Ordering Check Price and. no login shell, and is used only for data transfer. net -i STAR -P 'XXXXX' -U automation -H sys-vbr02The hosts agent supports TLS, but it is not being used. The agents' Agent Controller makes a request for registration to the server’s Agent Receiver, transmitting the data required to create the host. 2. This morning all Windows Agents were suddenly no longer registered. Become root. Yes I did use the” cmk-agent-ctl register command, after that I got this message. When I try to register the agent on the host system with: cmk-agent-ctl register --hostname some_hostname --server 127. service - Checkmk agent controller daemonIt seams you use a Debian system. 6 I have an external cloud host that I would like to monitor with in-house CMK server. 0p10 OS: linux The hosts agent supports TLS, but it is not being used. If I try to register it with the command: cmk-agent-ctl register --detect-proxy --hostname FOO --server bla. Now the service is active and listening. 0p10 Agent socket: operational IP allowlist: any Connection: localhost:8001/cmk UUID: 186f71b9-8d6f-41c6-be44-bb1f7c23ae7b Local: Connection. redacted. To register the agent, I ran: sudo cmk-agent-ctl register --hostname localhost --server localhost:8001 --site cmk --user cmkadmin That gives: > sudo cmk-agent-ctl status Version: 2. serviceThe REST in the name of the REST API stands for REpresentational State Transfer, and it describes an architecture for the exchange of data on distributed systems — especially for web. com--site FOO --user BAR -. If you want to use the agent in legacy mode, you need to disable cmk-agent-ctl in bakery rules. I confused the keyword register on cmk-agent-ctl register with cmk-update-agent register or perhaps on some subconscious level assumed the first would handle both. error: The subcommand ‘register --trust-cert’ wasn’t recognized Did you mean ‘register’? If you believe you received this message in error, try re-running with ‘cmk-agent-ctl. I installed the CheckMK Agent on a TrueNAS SCALE host. Are you trying to register the 2. Join thousands of sysadmins and receive free professional tips and tricks to help you monitor your IT-infrastructure. 0p20 Debian 11. scheint mir noch nicht ganz ausgereift. XXX. 0p20 Debian 11. Just in case: We are prepared for cases where the agent controller cannot be started or. 02. serviceSo now you must de-register, on the host: cmk-agent-ctl delete-all --enable-insecure-connections Then on the CMK server: Properties of host , then menu entry Host > Remove TLS registration Afterwards connections should work albeit insecure. In your case doing proxy. If there are leftovers from 2. 1:8655 --site cmk --user cmk_admin. C:\ProgramData\checkmk\agent\config\cas\all_certs. 1. I have the server up and running and ~50 VMs online, all is working well. 0) master 1. 1. cmk-update-agent register -s monitor2 -i mysite -H monitor2 -U cmkadmin. 1. deb Now the cmk-agent-ctl-daemon. TLD -i SITE-NAME -U USERNAME This worked perfectly fine in CMK 2. Checkmk Server: Checkmk version: 2. domain. TLD -i SITE-NAME -U USERNAME. 4. deb The monitored system is in a local network and have. 5. For some reason I am no longer able to register my agents with TLS. (We used cmk-agent-ctl proxy-register → deploy json to host → cmk-agent-ctl import . I had to add the checkmk user again. To register the agent, I ran: sudo cmk-agent-ctl register --hostname localhost --server localhost:8001 --site cmk --user cmkadmin That gives: > sudo cmk-agent-ctl status Version: 2. For this, however, the Agent Controller must be started as a background process (daemon) by the init system on the host on which it is to be installed. com --site FOO --user BAR --password FOO. $ sudo systemctl restart cmk-agent-ctl-daemon. CMK 2. 2. the check-mk-agent is running (in xinetd mode) - trying to register a client is not possible because the cmk controller is looking for a socket (systemd) [root@jumphost]# cmk-agent-ctl status Version: 2. Password for user ‘cmkadmin’: Successfully registered agent of host “monitor2” for deployment. slice (loaded active) and check_mk. Warning: This version breaks the agent receiver on IPv4-only Checkmk servers which have completely disabled IPv6 support on kernel level. For Debian remove the cmk-agent and purge the configuration, than reinstall the agent, this purges the xinetd configuration. cmk-agent-ctl register --server cmkserver:443 --trust-cert --site cmksite --user username --password password --hostname monitoringhost On Debian 11 if got the following outputYes I did use the” cmk-agent-ctl register command, after that I got this message. XXX. Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins) sudo: cmk: command not found. 0. Here is what I have done roughly: Added and configured the agent rules. Bulk Consent Manager. B. 04 LTS. Das funktioniert und auch eventuelle Fehler: TLS is not activated on monitored host verschwinden. Checkmk Enterprise Edition 2. Now the cmk-agent-ctl-daemon. 04 - CMK RAW) where communication with the agent keeps giving errors "[agent] Communication failed: [Errno 104] Connection reset by peer - Got no information from host - execution time 0. deb. xyz:9800 --site cmk --user BAR --password FOO. rs:14: starting [2023-02-10 12:54:18. mictlancihuatll. root@waw1-monitor2:/omd# cmk-update-agent -v. domain. 10. 1. CMK agent is up and running, host is added to Check MK server and now I want to set up TLS connection. 488899 +01:00] INFO [cmk_agent_ctl] srcmain. g. 0p15 OS version: TrueNAS SCALE 22. I created the folder manually and changed ownership, and now the registration. The hosts agent supports TLS, but it is not being used. Hello. consorzioburana. 0 adds the Agent Controller and new features to the agent script. apt remove --purge check-mk-agent dpkg -i check-mk-agent_2. For Debian remove the cmk-agent and purge the configuration, than reinstall the agent, this purges the xinetd configuration. OS: linux. TLD -i SITE-NAME -U USERNAME. Host can telnet on port 8000 of the server and a curl request works. service --now $ sudo systemctl restart check-mk-agent. $ cmk-update-agent register $ cmk-agent-ctl register. CMK 2. Disable TLS registration on the CMK server: Properties of host, menu entry Host > Remove TLS registration; Afterwards, ss should show xinetd claiming the connection test should work. com. 02. 0b4-1 OS: Ubuntu 20. Whether the host is configured for the pull mode (all editions) or the push mode (only the Cloud Edition) makes no difference for the command examples. To register the agent, I ran: sudo cmk-agent-ctl register --hostname localhost --server localhost:8001 --site cmk --user cmkadmin That gives: > sudo cmk-agent-ctl status Version: 2. 1 Like. You can learn how to use the agent here. Yes I did use the” cmk-agent-ctl register command,. After a reboot the cmk-agent-ctl-daemon and the check-mk-agent. sh script. Whether the host is configured for the pull mode (all editions) or the push mode (only the Cloud Edition) makes no difference for the command examples. service: Scheduled restart job, restart counter is at 2. sh script. 0p10 Agent socket: operational IP allowlist: any Connection: localhost:8001/cmk UUID: 186f71b9-8d6f-41c6-be44-bb1f7c23ae7b Local: Connection. Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins) sudo: cmk: command not found. Thank you again Anders! My humility and I will go back into the. So now you must de-register, on the host: cmk-agent-ctl delete-all --enable-insecure-connections Then on the CMK server: Properties of host, then menu entry Host > Remove TLS registration Afterwards connections should work albeit insecure. Hi everyone, below is the output of the “cmk-agent-ctl. apt remove --purge check-mk-agent dpkg -i check-mk-agent_2. 1. cmk-agent-ctl register -v -H HOSTNAME -P 'PASSWORD' -s SUBDOMAIN. service: Scheduled restart job, restart counter is at 2. 0. CMK 2. I dont know why this folder could not be created during cmk agent installation from the cmk-agent-useradd. Rg, ChristianThe Agent Controller cmk-agent-ctl is the component within the agent that is responsible for transporting the data collected by the agent script. 0. 0 did not yet use TLS, so port 8000 didn’t need to be exposed back then. 2. So now you must de-register, on the host: cmk-agent-ctl delete-all --enable-insecure-connections Then on the CMK server: Properties of host, then menu entry Host > Remove TLS registration Afterwards connections should work albeit insecure. I am using the Raw edition of CheckMK for my (rather large) Hobbyist stuff. 0. 0 2. The service is started. 0p9. MichaelI’m running 2. First, to add a new host to monitor we have to go to the Hosts menu in the WATO - Configuration menu on the left. 3. 4. service systemctl disable check-mk-agent. XXX. mschlenker (Mattias Schlenker) July 8, 2022, 8:12am 4. net:8000--site cmk –user automation --password MYTOKEN sudo reboot (To verify it continues to work post-reboot) andreas-doehler August 15, 2022, 7:25pm 6. Become a Dealer. For this, I’m running following command on client # cmk-agent-ctl register --hostname `hostname -f` --server mon. 1. mit cmk-agent-ctl help register.