Trying to run the Proxy Deployment Manager on an Avamar v7.5 system and it throws an “Internal Error” when trying to create a recommendation – log has the following entries:
2018-02-19T09:58:42.399-0600 TRACE [TaskExecutor-10][ impl.ConnectionManagerService# isValidTicket]: Checking if connection manager ticket is valid: b287fcab-7278-4729-809e-2923fbbf2e68
2018-02-19T09:58:42.401-0600 TRACE [TaskExecutor-10][ impl.ConnectionManagerService# waitForMcSession]: Requesting connection manager mc session
2018-02-19T09:58:42.404-0600 TRACE [TaskExecutor-10][ impl.ConnectionManagerService# waitForMcSession]: Acquired MC session: …f3a17fc39615
2018-02-19T09:58:42.405-0600 INFO [TaskExecutor-10][ util.LockboxUtil# initializeCST]: Initializing CST Lockbox: /etc/vcs/cst
2018-02-19T09:58:42.410-0600 ERROR [TaskExecutor-10][ impl.LockboxService#DefaultMcPassword]: Unexpected exception
com.emc.csp.error.IOException: The Lockbox stable value threshold was not met because the system fingerprint has changed. To reset the system fingerprint, open the Lockbox using the passphrase. : File : /etc/vcs/cst/csp.clb
I can’t figure out what “lockbox” they are talking about. And I thought Avamar got rid of its lockbox?
We have used the PDM at this site to deploy proxies before without any issues.
There hasn’t been anything done recently that I can think of to change anything siginificant with respect to the Avamar and its vCenter integration that would cause this – not sure what might have been done in the VMware environment.
FWIW – VM backups completed successfully over the weekend, and I was able to browse the vCenter by “pretending” to add a new VM client using the same Avamar GUI I am running the PDM from.
Anyone seen this before?
All comments/feedback appreciated – thanks.