Forum Discussion
7 hours ago, Mike Moniz said:That is a odd one I haven't seen. The credential field I believe is the encrypted creds/password that the collector uses to communicate with the portal. The creds changes every 24 hours when the collector restarts itself so you don't need to force it. I've had to manually fix it in the past when a collector was rolled back from a DR test or VM snapshot. Was something like that done? You can fix that by copying it from the portal's collector config page to the actual config files on the collector server. But if you are running into that problem, I would expect your collectors to eventually go offline regardless of the upgrade. What version are the collectors now? Are the collectors able to rotate their credentials daily without issue with the current version? Does the cred value in the portal match the creds in the actual collector config files?
Hey Mike,
Even post 24 hours still the same issue, these boxes have never had a restore done whats even more strange the collecotr config page for agent.conf is the exact same credentials as whats on the agent it self if I SSH/RDP in and check.
One was 29.003 the other was 30.001
I do understand they go offline briefly during upgrade as they gotta extract data ect