sepmd -n Gives "Subscriber exists in sync mode" Error
search cancel

sepmd -n Gives "Subscriber exists in sync mode" Error

book

Article ID: 278700

calendar_today

Updated On:

Products

CA Privileged Identity Management Endpoint (PIM)

Issue/Introduction

When trying to subscribe a child PMDB to a parent PMDB, the following error occurs.

# sepmd -n ParentPMDB ChildPMDB
CA Privileged Access Manager Server Control sepmd v14.10.40.182 - Policy Model management

Copyright (c) 2018 CA. All rights reserved.

The option you have selected will take a while to process.
 Meanwhile, the Policy Model will not be able
 to handle other requests or updates.

Now preparing the database rules to be sent to ChildPMDB...
Failed to subscribe ChildPMDB to Policy Model ParentPMDB: ERROR: Subscriber exists in sync mode.

Environment

Privileged Identity Manager, 12.8
PAM Server Control, 14.x

Cause

There was an issue when subscribing the child PMDB previously which left a file called ChildPMDB_updates behind, but the child PMDB did not get added to the list of subscribers.

# pwd
/opt/CA/PAMSC/policies/ParentPMDB

# ls -lh ChildPMDB*
-rw-r--r--. 1 root root 0 Jan 31 23:18 ChildPMDB_updates

# sepmd -L ParentPMDB
CA Privileged Access Manager Server Control sepmd v14.10.40.182 - Policy Model management
Copyright (c) 2018 CA. All rights reserved.
No subscribers found

 

Resolution

Remove the ChildPMDB_updates file from the parent PMDB's directory, then subscribe the child PMDB again.

# rm ChildPMDB_updates
rm: remove regular empty file ‘ChildPMDB_updates’? y

# sepmd -n ParentPMDB ChildPMDB
CA Privileged Access Manager Server Control sepmd v14.10.40.182 - Policy Model management

Copyright (c) 2018 CA. All rights reserved.

The option you have selected will take a while to process.
 Meanwhile, the Policy Model will not be able
 to handle other requests or updates.

Now preparing the database rules to be sent to ChildPMDB...
Subscribed ChildPMDB to Policy Model ParentPMDB

Additional Information

If sepmd -n continues to fail after removing the ChildPMDB_updates file, please note the new error and open a ticket with a support representative.