UNIX accounts not verifing after upgrading to 3.3.2
Article ID: 188986
Updated On:
Products
CA Privileged Access Manager (PAM)
CA Privileged Access Manager - Cloakware Password Authority (PA)
CA Privileged Access Manager - Server Control (PAMSC)
Issue/Introduction
After upgrading our TESTNET environment to 3.3.2 we are seeing a lot of accounts 1200+ not being verified. We use a master account on our servers and it seems those accounts are not able to verify. Getting this error in logs Error Code: 15212.
Not sure what is going on but we need to find out out why this is going on before we can upgrade production.
Environment
Release : 3.3
Component : PRIVILEGED ACCESS MANAGEMENT
Resolution
What happens if you break the cluster while a scheduled task is running.
One rotation job starts early in the morning and takes some time to complete.
testnet's cluster was broken during the run, so some passwords out of synch and had to be put back in place from the server.
Roll password scheduled task was running.
Q: is it orphaned? does it report back?
A: no, the server does not attempts to stop any currently running tasks when you place this into maintenance mode. they will be left running.
One rotation job starts early in the morning and takes some time to complete.
testnet's cluster was broken during the run, so some passwords out of synch and had to be put back in place from the server.
Roll password scheduled task was running.
Q: is it orphaned? does it report back?
A: no, the server does not attempts to stop any currently running tasks when you place this into maintenance mode. they will be left running.
Feedback
Yes
No
Powered by
