Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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'

...

register und update all remote hosts from a remote site, now you can add the slave site here:

Info

Image Added



Now you can bake, sign and register the agent:

Code Block
root@ip-172-31-40-131:/home/ubuntu#133:~# cmk-update-agent register Our-v
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-40-131:/home/ubuntu# cmk-update-agent -v 

+-------------------------------------------------------------------+
|
+-------------------------------------------------------------------+
|                                                                   |
|  Check_MK Agent Updater v2.0.0b5 - Registration                   |
|                | |  Check_MK Agent Updater v2.0.0b4 - Update                         | |                 |
|  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     |
|
+-------------------------------------------------------------------+
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

...

Setup → General → Global settings → AUTOMATIC AGENT UPDATES → Connection to the central agent bakery

Info

Image Removed

Now you can register and update the host

...

  that server.                                                     |
|                                                                   |
+-------------------------------------------------------------------+

...

Our host name in the monitoring: 
slave1

WATO user with admin permissions: 
cmkadmin     

Password: 


Going to register agent at deployment server
Applying new update URL http://172.31.40.133/slave1/check_mk/ from deployment server
Successfully registered agent of host "slave1" for deployment.
You can now update your agent by running 'cmk-update-agent -v'
Saved your registration settings 

...

to /etc/cmk-update-agent.state.


If you want to run the agent updater this will not work.

Code Block
root@ip-172-31-40-133:/home/ubuntu# cmk-update-agent -v 

+-------------------------------------------------------------------+
|                                                                   |
|  

...

Check_MK 

...

Agent 

...

Updater v2.0.0b5 - Update                         |
|  

...

 

...

                                                     

...

 

...

          

...

|
+-------------------------------------------------------------------

...

+
Getting 

...

target 

...

agent 

...

configuration 

...

for host 'slave1' 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

  1. Configure the connection to the central agent bakery
    1. Setup → General → Global settings → AUTOMATIC AGENT UPDATES → Connection to the central agent bakery

      Info

      Image Added


    2. Now you can update the host

      Code Block
      root@ip-172-31-40-133:~# cmk-update-agent -v
      
      
      +-------------------------------------------------------------------+
      |                                                                   |
      |  Check_MK Agent Updater v2.0.0b40b5 - 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-40-131:/home/ubuntu# 
      
Info

In 'Setup → General → Global settings → AUTOMATIC AGENT UPDATES' there is a second new option for the distributed agent bakery:

Image Removed

Configure an alternative URL for the connection from host to remote agent bakery. If not configured here, the URL from distributed monitoring configuration is used instead. In many cases, you might want to make this a site specific global setting at the distributed monitoring configuration, because this URL is likely different for every remote site.

Functionality

This feature is realized as follows: Update requests to the remote sites get forwarded to the central site – The entire configuration and the agent baking process is done on the central site. Agent packages that got requested once at a remote site will get cached (as long as they are valid) there to save unnecessary traffic. Additionally, the requested data will be checked for consistency on the remote site, again to save unnecessary traffic to the central site.

Registration

...

    1. ---------+
      Getting target agent configuration for host 'slave1' from deployment server
      Target state (from deployment server):
        Agent Available:     True
        Signatures:          1
        Target Hash:         1ef2302ca00a9b89
      Agent 1ef2302ca00a9b89 already installed.
      


Info

In 'Setup → General → Global settings → AUTOMATIC AGENT UPDATES' there is a second new option for the distributed agent bakery:

Image Added

Configure an alternative URL for the connection from host to remote agent bakery. If not configured here, the URL from distributed monitoring configuration is used instead. In many cases, you might want to make this a site specific global setting at the distributed monitoring configuration, because this URL is likely different for every remote site.


Functionality


This feature is realized as follows: Update requests to the remote sites get forwarded to the central site – The entire configuration and the agent baking process is done on the central site. Agent packages that got requested once at a remote site will get cached (as long as they are valid) there to save unnecessary traffic. Additionally, the requested data will be checked for consistency on the remote site, again to save unnecessary traffic to the central site.

Registration


Code Block
Going to register agent at deployment server
2021-02-04 16:18:08,715 DEBUG: Authenticating at Check_MK Server (using requests): http://172.31.40.133/slave1/check_mk/login.py
2021-02-04 16:18:09,034 DEBUG: Fetching content (using requests): http://172.31.40.133/slave1/check_mk/register_agent.py
2021-02-04 16:18:09,070 DEBUG: Response from agent bakery:
{"result_code": 0, "result": {"host_secret": "rlkaihuoazcdcnseimvfpzaocsjitoabpieyzubuictninlfdtgciztydmkmfrfj", "update_url": "http:\/\/172.31.40.133\/slave1\/check_mk\/", "monitored": true}}
2021-02-04 16:18:09,070 INFO: Applying new update URL http://172.31.40.133/slave1/check_mk/ from deployment server
2021-02-04 16:18:09,071 DEBUG: No state file found yet. New state data will be saved to /etc/cmk-update-agent.state
2021-0102-1904 1316:3518:0209,376073 DEBUG: Successfully readSaved deployment status to /etc/check_mk/cmk-update-agent.cfg.state.
2021-02-04 16:18:09,073 INFO: Successfully registered agent of host "slave1" for deployment.
2021-0102-1904 1316:3518:0209,377073 DEBUG: StartingSecret Registrationis Moderlkaihuoazcdcnseimvfpzaocsjitoabpieyzubuictninlfdtgciztydmkmfrfj.
2021-0102-1904 1316:3518:0209,377073 DEBUG: StartingSuccessfully interactive Registrationread /etc/cmk-update-agent.state.
2021-0102-1904 1316:3518:1009,552075 INFODEBUG: GoingSaved to register agent at deployment serverdeployment status to /etc/cmk-update-agent.state.
2021-0102-1904 1316:3518:1009,590076 DEBUGINFO: AuthenticatingSaved atyour Check_MKregistration Server (using requests): http://172.31.46.5/master/check_mk/login.py
2021-01-19 13:35:10,939 DEBUG: Fetching content (using requests): http://172.31.46.5/master/check_mk/register_agent.py
2021-01-19 13:35:10,963 DEBUG: Response from agent bakery:
{"result_code": 0, "result": {"host_secret": "zewqptluwgrjzamdvwjplosjhrwqpboxqjtxogreibeqkadfhswhotzifjqqramw", "update_url": "http:\/\/172.31.40.131\/slave2\/check_mk\/", "monitored": true}}
2021-01-19 13:35:10,963 INFO: Applying new update URL http://172.31.40.131/slave2/check_mk/ from deployment server
...
...
...

The host is using the master for registration!

Update

Code Block
2021-01-19 13:35:14,440settings to /etc/cmk-update-agent.state.
2021-02-04 16:18:09,076 DEBUG: Successfully scheduled an automatic update with next Check_MK Agent execution.
2021-02-04 16:18:09,076 DEBUG: Done.


The host is using the master for registration!

Update


Code Block
2021-02-04 16:18:19,630 DEBUG: Starting Check_MK Agent Updater v2.0.0b5
2021-02-04 16:18:19,630 DEBUG: Successfully read /etc/cmk-update-agent.state.
2021-02-04 16:18:19,630 DEBUG: Successfully read /etc/check_mk/cmk-update-agent.cfg.
2021-02-04 16:18:19,630 INFO: Starting Update mode as plugin.
2021-02-04 16:18:19,631 INFO: Getting target agent configuration for host 'slave2slave1' from deployment server
2021-0102-1904 1316:3518:1419,476657 DEBUG: Fetching content (using requests): http://172.31.40.131133/slave2slave1/check_mk/deploy_agent.py
2021-0102-1904 1316:3518:1419,532717 DEBUG: Response from agent bakery:
{"result_code": 0, "result": {"update_url": "http:\/\/172.31.40.131133\/slave2slave1\/check_mk\/", "AgentAvailable": true, "TargetHash": "67f84ee7e41b73aa1ef2302ca00a9b89", "Signatures": [{"certificate": "-----BEGIN CERTIFICATE-----\nMIIC2jCCAcICAQEwDQYJKoZIhvcNAQEFBQAwMjEdMBsGA1UECgwUQ2hlY2tfTUsg\nU2l0ZSBtYXN0ZXIxETAPBgNVBAMMCGNta2FkbWluMCAXDTIxMDExOTExNTMxMVoY\nDzIwNTEwMTEyMTE1MzExWjAyMR0wGwYDVQQKDBRDaGVja19NSyBTaXRlIG1hc3Rl\ncjERMA8GA1UEAwwIY21rYWRtaW4wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK\nAoIBAQDWbh45st1xnzhsVzMjBBXzO7+5qz3\/HPezvaOeUpSSIYHns2DnuDlwpLCO\nXTdyfRUamgRtiOrzbUsSsARmMF9AqExao1+yM1rbEfcXP6mtBqMkqShlDw3n0L7F\nHGGYG2CNqcRSmgxFe2Eck0ydv\/p4cJONHIw4UFwqDnHfIC1L3tCnTQJagCig\/Jvk\nkZSZZqgkrjl4TuwRkFxdrnwURjm2hQGg+TkJcxpPHqSutbdnQrXnuuAEdx\/ZIpFL\nivmjLDATjGzCy0LPZsVtjHZu5Lz4WWOZsA1BCZLecT81PI5edWs0RZ9mRH7QC+E8\nCkIdlLgMUbfB093SGx3YEP8u+RtRAgMBAAEwDQYJKoZIhvcNAQEFBQADggEBAAU\/\nDtXHbs3cUPBGDs\/Go0PgfqhwiZjn1aprCSh8O\/RBLWA\/jep65eU2pzsuoiKWT5CE\nP\/xc7pKXWmxQpyA4KA1Fz9BS80QHq5heXkG2FSLMFunDLxzDcbQI7QXH4oskIDkV\nzzYio3VDXXDyhMBHd25XKKCQT3L9ou3bD7Esh\/Cf\/8Y2GQHkRvIWOpwLEknq0ovy\njkJ0o7Gx8GrqJYG5gUW44TJU\/IhYFCxfhTS09RW842Z10iDSYiBPKoZLonM6F3SY\nSLVRDn3vhnCpbkiO0Dc1op+0d9b5Wc+UCVW02G+l+G+aRw89L7v2xERXNPczCZgV\ng+9DtIl5cu1fl4qVqmc=\n-----END CERTIFICATE-----\n", "signature": "c0dVyUsS06qlIEds2LJ6cXvzC713zn6zNutuDi8AbeU4gbF67BlioAhXsnZI36WoHHW0husT5nPEoIRUlkgNdYzGOLNE\/LKA38ymOZeKU1aSERzBT2RlU2BURnFa6rDL5HEF\/4svhz2xZDBqkkEcPS3VIooaSxMVu45vO5MIjhjowI9hvl0q\/tbGMg88z3fmCmGEom9kWk\/UDAsq+R\/w2lIf3ms\/bX8UQ1tjVLiivFj1B4LvsX6oZ23veWLIVYy7Au4A5Dxs3sAxlRcxECX6zQM1QO1ZJeDK815yuTpF\/7nTCKvY9kiBUQXm6ueSxd\/LgUu9O2maRBiKVxH64rYocg=="}]}}
2021-01-19 13:35:14,532 DEBUG: Successfully read /etc/cmk-update-agent.state.
2021-01-19 13:35:14,535 DEBUG: Saved deployment status to /etc/cmk-update-agent.state.
2021-01-19 13:35:14,536 DEBUG: Successfully read /etc/cmk-update-agent.state.
2021-01-19 13:35:14,538 DEBUG: Saved deployment status to /etc/cmk-update-agent.state.
2021-01-19 13:35:14,538 INFO: Target state (from deployment server):
2021-01-19 13:35:14,538 INFO:   Agent Available:     True
2021-01-19 13:35:14,538 INFO:   Signatures:          1
2021-01-19 13:35:14,538 INFO:   Target Hash:         67f84ee7e41b73aa
2021-01-19 13:35:14,566 DEBUG: Fetching content (using requests): http://172.31.40.131/slave2/check_mk/deploy_agent.py
2021-01-19 13:35:15,219 INFO: Downloaded agent has size 13111604 bytes.
2021-01-19 13:35:15,235 INFO: Signature check OK.
2021-01-19 13:35:15,245 INFO: Invoking package manager: dpkg -i /tmp/check-mk-agent-x11mz6mx
2021-01-19 13:35:16,207 INFO: Output from dpkg:
  (Reading database ... 158559 files and directories currently installed.)
  Preparing to unpack /tmp/check-mk-agent-x11mz6mx ...
  Disable Checkmk agent in systemd (if active)...
  Unpacking check-mk-agent (2.0.0b4-20.67f84ee7e41b73aa) over (2.0.0b4-20.67f84ee7e41b73aa) ...
  Reloading xinetd...
  Setting up check-mk-agent (2.0.0b4-20.67f84ee7e41b73aa) ...
  Reloading xinetd...
  Enable Checkmk agent in systemd...
  Created symlink /etc/systemd/system/sockets.target.wants/check-mk-agent.socket → /etc/systemd/system/check-mk-agent.socket.
  
2021-01-19 13:35:16,210 DEBUG: Successfully read /etc/cmk-update-agent.state.
2021-01-19 13:35:16,212 DEBUG: Saved deployment status to /etc/cmk-update-agent.state.
2021-01-19 13:35:16,212 INFO: Successfully installed agent 67f84ee7e41b73aa.
2021-01-19 13:35:16,213 DEBUG: Could not find and update cachefile.
2021-01-19 13:35:16,213 DEBUG: Done.\nU2l0ZSBtYXN0ZXIxETAPBgNVBAMMCGNta2FkbWluMCAXDTIxMDIwNDExNTExNVoY\nDzIwNTEwMTI4MTE1MTE1WjAyMR0wGwYDVQQKDBRDaGVja19NSyBTaXRlIG1hc3Rl\ncjERMA8GA1UEAwwIY21rYWRtaW4wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK\nAoIBAQDgFptynmaSVcnwqj69SDiJmHnSQAcb\/iMMXclptBo+7tcOOpU36COA0\/eL\nX7kp5V7Mu1zEfQq9wPmuQy+cVyWkMPj03tKZjly3Y+342WpFn\/hk8g0H72f+zTre\nebpM4d+UmkRWzo6\/aACgPTy0oPr4pDEiaPkzoGSrWtE+14jIIL5Cv+t8bIIs4uI0\n0VJ1HqR09FmuZhoYfV9hVoAEFYMRzo6BBweMIOz5cYEhJXa30VaGt9Fvk6FPwf9u\naKx25KxPHrz2oXgTnnP6afffx\/rl7oKQPGx6uT3LlNhkOJW\/R0RwVIKqQcjB66DB\njaESRa27L2vy7A5gO7muktMyIl73AgMBAAEwDQYJKoZIhvcNAQEFBQADggEBALSt\nz22vVZcBZ8RSy9ZX5nu4E+hBrZz\/84+U52UnL+ATbSKRA+VxltACezrBAXGB1pMO\nuCZ6YlKT6yMGqP0vyqhjAQnNJTlEr2V9MAh0IBuPUxCKTUbr6gzauAqT8FrVKgrY\nD2ZbCGKlls26tgbyyaH+Qqec9WsJQSDgEnIDoabR5Ip1hPjmWK0xG9kwQwFFZo+I\n3VMIOr52vys99TVBt4682560vO\/vhP1OQMmiyax\/\/M2fKuONo0zq7rWFiDbqvuL6\nTeuSSpANXEhfN\/42HCAqziWS85NYebUGLDbMYC6jJMfvBzOT\/uHrjbkop9dqOLfL\nnsIcFFkBV4e07TOLz6c=\n-----END CERTIFICATE-----\n", "signature": "vWcDferK6N7eVq7iVc7Ni++YS0GD9N25PWtT7dHbsykFGQ7QZJQ0kFEuAQz4sn3qy3T6feKgISOocXzSxZzpfQsWWlaWhPCpB4FXQ4pcDjcXuXsCN2Jd14dPKhEifTjLQyQ\/IuewwXVgezz63c5g+iyItQ2gA0GvxL6\/YRGTBV62r81ggafvmEnhswprS4WvykcO2+lS0pLfnkkVFGejFKKTIK0IfHoVNfnalyd1n2FD4\/ghRpwJlxafwPoZ1egG2xgtmzvTXBngHN7F+wG4oqpGImevDaDXu+pkJYqRu4IyFCK3OZFV3jlvn+5AX\/tP8LgU8D\/qNSHL36TMKEPAZw=="}]}}
2021-02-04 16:18:19,717 DEBUG: Successfully read /etc/cmk-update-agent.state.
2021-02-04 16:18:19,721 DEBUG: Saved deployment status to /etc/cmk-update-agent.state.
2021-02-04 16:18:19,721 DEBUG: Successfully read /etc/cmk-update-agent.state.
2021-02-04 16:18:19,723 DEBUG: Saved deployment status to /etc/cmk-update-agent.state.
2021-02-04 16:18:19,723 INFO: Target state (from deployment server):
2021-02-04 16:18:19,723 INFO:   Agent Available:     True
2021-02-04 16:18:19,723 INFO:   Signatures:          1
2021-02-04 16:18:19,723 INFO:   Target Hash:         1ef2302ca00a9b89
2021-02-04 16:18:19,749 DEBUG: Fetching content (using requests): http://172.31.40.133/slave1/check_mk/deploy_agent.py
2021-02-04 16:18:20,411 INFO: Downloaded agent has size 13116004 bytes.
2021-02-04 16:18:20,427 INFO: Signature check OK.
2021-02-04 16:18:20,436 INFO: Invoking package manager: dpkg -i /tmp/check-mk-agent-a8apxscl
2021-02-04 16:18:21,504 INFO: Output from dpkg:
  (Reading database ... 158728 files and directories currently installed.)
  Preparing to unpack /tmp/check-mk-agent-a8apxscl ...
  Disable Checkmk agent in systemd (if active)...
  Unpacking check-mk-agent (2.0.0b5-17.1ef2302ca00a9b89) over (2.0.0b5-17.1ef2302ca00a9b89) ...
  Reloading xinetd...
  Setting up check-mk-agent (2.0.0b5-17.1ef2302ca00a9b89) ...
  Reloading xinetd...
  Enable Checkmk agent in systemd...
  Created symlink /etc/systemd/system/sockets.target.wants/check-mk-agent.socket → /etc/systemd/system/check-mk-agent.socket.
  



The host fetches all updates from the slave!

...