Perpetual full sync of security roles in universe.log of nodes declared on UVMS Subordinate

Products

• Automic Dollar Universe

Issue/Introduction

Introduction

In a Master/Subordinate Univiewer Management Server (UVMS) architecture, users may observe a high cyclical rate of security roles synchronization on subordinate nodes. This behavior results in a full sync being triggered repeatedly (e.g., every 10 minutes), leading to increased network traffic and audit trail bloat.

Symptoms

The following symptoms are observed in the universe.log on the Subordinate UVMS:

• Repetitive messages indicating a full sync of security roles: | DATE |INFO |X|IO |pid=####.####| io_sync_roles | Full sync of X security roles
• These messages appear consistently every 10 to 15 minutes.
• The synchronization never transitions to a 'Partial' or 'Up-to-date' status despite no changes on the Master UVMS.

Environment

• Product: CA Automic Dollar Universe
• Component: Univiewer Management Server (UVMS)
• Versions: 7.0.x, 7.1.x (prior to 7.1.31)

Cause

The issue is caused by a logic flaw in the incremental security synchronization process. When a security object (such as a Role or Group) is deleted on the Master UVMS, the Subordinate UVMS correctly detects a version mismatch. However, the synchronization method fails to explicitly advance the Subordinate's internal version tracking to match the Master's deletion version. Consequently, the Subordinate remains perpetually 'behind' the Master, re-triggering the full sync cycle indefinitely.

Resolution

Solution:

This issue is confirmed as a product defect (DE183419).

Fix Status: Targeted to be fixed in release UVMS 7.1.31.

 

Workaround (Debug JAR): 

If you are experiencing this issue on a version prior to 7.1.31, please contact Broadcom Support to obtain a patched central.jar (available for versions 7.0.11, 7.1.21).

Steps to apply the debug JAR:

1. Stop the UVMS node on both the Master and Subordinate servers.
2. Navigate to the UVMS installation directory and locate the existing central.jar file.
3. Take a backup of the existing central.jar outside of the UVMS directory.
4. Replace the existing file with the patched central.jar provided by Support.
5. Restart the UVMS node.

Note: After the restart, the Subordinate will perform one final full sync to align its version tracking, after which the repetitive sync loop will stop.

Users are encouraged to subscribe to this article to be updated on the official fix status: How to subscribe to Knowledge Base Articles.