System Health Dashboard — Status Update Latency

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

System Health Dashboard — Status Update Latency

L3 Networker

Despite stopping the CPM service over 15 minutes ago in preparation for the upgrade, the System Health dashboard still displays a 'Connected' status. Which specific connection or heartbeat mechanism should be verified here? Unlike the PSM or Secrets Manager, which update their status immediately upon service stoppage, the CPM is still showing as connected.

4 REPLIES 4

L4 Transporter

Hi @Joyce Ebrado​ 

What version are you on?

Have you checked the CPM logs for any errors or unusual messages?

Could you try recreating the credential file (user.ini) as a test to see if the behavior persists?

When you stop the services, have you also set the startup type from Automatic to Manual to prevent them from coming back up?

 

Will the status eventually change to "Disconnected" on its own, or does it remain "Connected" indefinitely?

The environment is running on version 14.2. Based on our tnc tests, connectivity between the CPM and PVWA on Port 1858 is currently failing. I suspect this network blockage is causing the status reporting delay, as the System Health only updated after a full restart of the PVWA server.

Thank you for the update. Based on the official documentation for CPM installation requirements, I would recommend verifying the network flows to ensure proper communication.

From the https://docs.cyberark.com/pam-self-hosted/14.0/en/content/pas%2520inst/cpm-install-requirements.htm#Vault

"The CPM uses a TCP connection to communicate with the CyberArk Vault. Therefore, any type of network protection on the machine where the CPM is installed must allow TCP communication with the Vault’s IP address. The default TCP port number for communication to the Vault is 1858."

Additionally, the same document states:

"The CPM Scanner also requires network access to the PVWA server in order to process scans and scan tasks."

Based on this, I would suggest verifying both network flows:

 

CPM → Vault Vault TCP/1858

CPM → PVWA PVWA TCP/443

 

The failure you observed on port 1858 during your TNC test is significant—this port must be open for the CPM to properly communicate with the Vault. 

  • 101 Views
  • 4 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!