<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: System Health Dashboard — Status Update Latency in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404877#M82120</link>
    <description>&lt;P&gt;Will the status eventually change to "Disconnected" on its own, or does it remain "Connected" indefinitely?&lt;/P&gt;</description>
    <pubDate>Fri, 27 Mar 2026 20:07:31 GMT</pubDate>
    <dc:creator>A.Tepore152377</dc:creator>
    <dc:date>2026-03-27T20:07:31Z</dc:date>
    <item>
      <title>System Health Dashboard — Status Update Latency</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404875#M82118</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2026 07:59:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404875#M82118</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-03-27T07:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: System Health Dashboard — Status Update Latency</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404876#M82119</link>
      <description>&lt;P&gt;Hi @Joyce Ebrado​&amp;nbsp;&lt;/P&gt;&lt;P&gt;What version are you on?&lt;/P&gt;&lt;P&gt;Have you checked the CPM logs for any errors or unusual messages?&lt;/P&gt;&lt;P&gt;Could you try recreating the credential file (user.ini) as a test to see if the behavior persists?&lt;/P&gt;&lt;P&gt;When you stop the services, have you also set the startup type from Automatic to Manual to prevent them from coming back up?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2026 20:05:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404876#M82119</guid>
      <dc:creator>A.Tepore152377</dc:creator>
      <dc:date>2026-03-27T20:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: System Health Dashboard — Status Update Latency</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404877#M82120</link>
      <description>&lt;P&gt;Will the status eventually change to "Disconnected" on its own, or does it remain "Connected" indefinitely?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2026 20:07:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404877#M82120</guid>
      <dc:creator>A.Tepore152377</dc:creator>
      <dc:date>2026-03-27T20:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: System Health Dashboard — Status Update Latency</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404878#M82121</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 07:18:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404878#M82121</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-03-30T07:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: System Health Dashboard — Status Update Latency</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404879#M82122</link>
      <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;From the&amp;nbsp;https://docs.cyberark.com/pam-self-hosted/14.0/en/content/pas%2520inst/cpm-install-requirements.htm#Vault&lt;/P&gt;&lt;P&gt;&lt;I&gt;"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&amp;nbsp;1858."&lt;/I&gt;&lt;/P&gt;&lt;P&gt;Additionally, the same document states:&lt;/P&gt;&lt;P&gt;&lt;I&gt;"The CPM Scanner also requires network access to the PVWA server in order to process scans and scan tasks."&lt;/I&gt;&lt;/P&gt;&lt;P&gt;Based on this, I would suggest verifying&amp;nbsp;both&amp;nbsp;network flows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CPM → Vault	Vault	TCP/1858&lt;/P&gt;&lt;P&gt;CPM → PVWA	PVWA	TCP/443&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 08:03:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/system-health-dashboard-status-update-latency/m-p/1404879#M82122</guid>
      <dc:creator>A.Tepore152377</dc:creator>
      <dc:date>2026-03-30T08:03:13Z</dc:date>
    </item>
  </channel>
</rss>

