Vault Migration - CP/OPM Agents

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Vault Migration - CP/OPM Agents

L2 Linker

We are in the process of migrating the vault from an older OS to a newer OS. In preparation for this, we edited the Vault.ini file for all of our agents (~300 CP agents & ~150 OPM agents) to have an ADRESS= a cname referencing the vault. We have confirmed that this setup is working correctly before any migration took place. The goal is to migrate the Vault, and swap the cname to reference the NEW vault (different ip).

 

This seemed to work for the core components (PVWA, PSM, CPM), but for some reason the Agents all showed up as disconnected with the following error messages in the logs:

 

OPMConsole.log:

OMPAP289E Connection to the Vault has failed. Further attempts to connect to the Vault will be avoided for [1] minutes.

OPMAP097I Connection to the Vault has been restored

OMPAP289E Connection to the Vault has failed. Further attempts to connect to the Vault will be avoided for [1] minutes.

OPMAP097I Connection to the Vault has been restored

 

APPConsole.log:

APPAP289E Connection to the Vault has failed. Further attempts to connect to the Vault will be avoided for [1] minutes.

APPAP097I Connection to the Vault has been restored

APPAP289E Connection to the Vault has failed. Further attempts to connect to the Vault will be avoided for [1] minutes.

APPAP097I Connection to the Vault has been restored

 

And this goes on forever until the agent is killed and restarted. Given that we have ~450 agents, is there a way to migrate vaults without having to restart EVERY agent?

2 REPLIES 2

L5 Sessionator

Hi Vadim,

 

Thank you for raising this issue in our community!

 

Can you please let us know if this issue was resolved?

If not, I would highly advise raising this with our support. More then likely, to reach the root cause of this behavior an in-depth investigation into your logs will be required.

 

Thanks,

Gil

L1 Bithead

Hi Vadim,

 

Were you able to resolve this error? we are facing the same issue.

  • 577 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!