Agent hash question

running v2.1.0p33.cee

1st question )
I want an explanation why the shown hash 9f6a7657 in WATO

differs when I download the rpm package:

image

why the difference?

2nd question)
also, checking the cmd-line

[root@lnzsdfia02 ~]# cmk-update-agent -v

±------------------------------------------------------------------+
| |
| Checkmk Agent Updater v2.1.0p33 - Update |
| |
±------------------------------------------------------------------+
Getting target agent configuration for host ‘lnzsdfia02’ from deployment server
Target state (from deployment server):
Agent Available: True
Signatures: 1
Target Hash: 9f6a7657813832f2
Agent 9f6a7657813832f2 already installed.

and I compare this output to the panel:

that also doesn’t fit together. The installed agent hash in this picture is completely different than the target hash (the one, the checkmk server would deploy to the node).

btw, the node is error-free registered.

just a guess… as the node was renamed, the node was removed from checkmk server, and the agent was then re-deployed (removed, and re-installed). But this hash version difference is seen not only on this example node… I have a few.

thanks.

The hash its the same, the GUI only show the first part of the hash!

1 Like

me stupid, I was looking at the end of the hash string … :see_no_evil: