NeophyteOn 12/22/2021 at 5:15 AM, Michael Baker said:Yesterday when attempting to upgrade a Windows collector we hit an issue:
Errors found in agent.conf. Please check the following configurations: file=agent.conf, key=credential, expected=...., actual=....
This morning when attempting to upgrade a Linux collector.. Same issue again
Errors found in agent.conf. Please check the following configurations: file=agent.conf, key=credential, expected=...., actual=...
We opened a support case and the reply was pretty much reinstall the collector this is not a easy solution when we have 74 collectors deployed in several locations that are not always easily accessible and its very time consuming eg 31.002 I done the install (Windows)) it wanted proxy I gave it proxy it refused to accept it so i said configure later.. Then open the configure agent application.. Put proxy in there press save "Cannot decrypt credentials".. Last resort I had to open the agent.conf and manually put the proxy settings in place.
Maybe someone can shed light on a way to force the credentials to update or something?
Merry Xmas to you all btw!
Hi Michael,
I just joined LM COMMUNITY & saw ur post , when collector upgrade fails from LM UI sometime the reason
Is carbon black security issue , in this case login into windows collector uninstall the LM S/W THEN download the
Collector file from LM UI and transfer it to collector jost andbinstall it there , if carbon block u here then u hav to
Mark carbon black policy to Low enforcement the. Only u wil b able to upgrade collector
