<?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: Which Daemons are responsible for Commit in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/which-daemons-are-responsible-for-commit/m-p/259133#M73480</link>
    <description>&lt;P&gt;Many Thanks for answering.&lt;/P&gt;&lt;P&gt;You gave me very useful info which is very hard to find elsewhere.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 29 Apr 2019 19:31:55 GMT</pubDate>
    <dc:creator>MP18</dc:creator>
    <dc:date>2019-04-29T19:31:55Z</dc:date>
    <item>
      <title>Which Daemons are responsible for Commit</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/which-daemons-are-responsible-for-commit/m-p/258867#M73413</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When we do the commit&amp;nbsp; and it is failing which daemon we need to check?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 14:21:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/which-daemons-are-responsible-for-commit/m-p/258867#M73413</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-04-26T14:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: Which Daemons are responsible for Commit</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/which-daemons-are-responsible-for-commit/m-p/259041#M73465</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/75039"&gt;@MP18&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;There is a useful command, "&lt;/SPAN&gt;&lt;FONT face="courier new,courier"&gt;show management-clients&lt;/FONT&gt;&lt;SPAN&gt;". &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This command shows the status of all of running daemons that are used during the commit process. &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;admin@PA-VM&amp;gt; show management-clients

              Client PRI    State Progress
-------------------------------------------------------------------------
              routed  30 P1-abort        0               
            ha_agent  25 P1-abort        0               
              device  20 P1-abort        0   *           
              ikemgr  10 P1-abort        0               
              keymgr  10     init        0    (op cmds only)
             logrcvr  10 P1-abort        0               
               dhcpd  10 P1-abort        0               
             varrcvr  10 P1-abort        0               
              sslvpn  10 P1-abort        0               
              rasmgr  10 P1-abort        0               
             useridd  10 P1-abort        0               
                satd  10 P1-abort        0               
             websrvr  10 P1-abort        0               
              sslmgr  10 P1-abort        0               
               authd  10 P1-abort        0               
              pppoed  10 P1-abort        0               
           dnsproxyd  10 P1-abort        0               
             cryptod  10 P1-abort        0               
              dagger  10     init        0    (op cmds only)
             l2ctrld  10 P1-abort        0               

Overall status: P1-abort. Progress: 0
Warnings:
Errors:
device: vsys1
device:     Error: Fail to count address groups
device: (Module: device)&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;Notice the * at the end of the 'device' line, indicating there was an issue with the device server during our commit. &amp;nbsp;In some cases the problem can be resolved by restarting the daemon that experienced an issue.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Useful blog written a while ago:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Community-Blog/Why-is-this-commit-not-working/bc-p/191834#M469" target="_blank" rel="noopener"&gt;Why-is-this-commit-not-working ?&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope this helps !&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-Kiwi.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV id="ConnectiveDocSignExtentionInstalled" data-extension-version="1.0.4"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Mon, 29 Apr 2019 12:01:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/which-daemons-are-responsible-for-commit/m-p/259041#M73465</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2019-04-29T12:01:54Z</dc:date>
    </item>
    <item>
      <title>Re: Which Daemons are responsible for Commit</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/which-daemons-are-responsible-for-commit/m-p/259133#M73480</link>
      <description>&lt;P&gt;Many Thanks for answering.&lt;/P&gt;&lt;P&gt;You gave me very useful info which is very hard to find elsewhere.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2019 19:31:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/which-daemons-are-responsible-for-commit/m-p/259133#M73480</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-04-29T19:31:55Z</dc:date>
    </item>
  </channel>
</rss>

