Error message: The installed agent needs to be updated
Hello,
Three weeks ago, I did post here where I was having trouble with an error called “not valid key signature”. @andreas was the one that the workaround worked (bake > sign > sign again).
I was adding some new services to some servers, so I had to bake the agents in order to get them updated and test if the service is configured correctly.
I did the bake > sign > sign again and this is what I see:
Again the same problem like before, some servers with that annoying warning, others don’t even update…
Last time (yeah because this is not the first time) to fix the issue of the hosts that wont get the update we use a SCCM to send a checkmk_agent.exe updater -rf command, which it worked well for most of them. The last ones we had to do a smaller list, because it seems like checkmk cant handle mass requests.
So I tried to run manually that command (checkmk_agent.exe updater -rf) and this is what I get now:
What is happening? The workaround with the SCCM was very inefficiency and doesn’t make any sense having to do it every time we need to trouble shoot or bake an agent.
This is agent rule that the host is placed in. It should be using the agent version number: …b5b7 but the print before shows otherwise.
I have 100% I have the hosts there if that’s the doubt you’re having. They were working before, why is that when I have to update them they don’t communicate?
Tried to change in lower case but it doesnt work, because the machine name is in upper case or else I have the invalid hostname secret.
EDIT: Actually, the machine is in lower case but for some reason it only works if the host Secret is in upper case. Could it be that the AD has the name in upper case? I dont have access to that part
Hi,
you have registered the host with a wrong hostname. You can delete the file cmk-update-agent.state. After this, let’s try to register with the correct hostname:
It seems like that worked, at least for this host.
I will try to check on more if the hostname on the file cmk-update-agent.state are messed up like this.
Is there any reason why it worked the first time then?
Even the computers that have their name in lower case are being changed to Upper Case.
Is this something maybe related to DNS ? I head checkmk is case sensitve to DNS?
I get a lower case host. Thats why I think something is wrong with CheckMK.
The script seems to work. I even put in the end of my script echo $hostname and it shows as lower case but checkmk takes it at higher case