Which Daemons are responsible for Commit

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

Which Daemons are responsible for Commit

Cyber Elite
Cyber Elite

 

When we do the commit  and it is failing which daemon we need to check?

MP

Help the community: Like helpful comments and mark solutions.
1 accepted solution

Accepted Solutions

Community Team Member

Hi @MP18 ,

 

There is a useful command, "show management-clients".  

This command shows the status of all of running daemons that are used during the commit process.  

 

admin@PA-VM> 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)

Notice the * at the end of the 'device' line, indicating there was an issue with the device server during our commit.  In some cases the problem can be resolved by restarting the daemon that experienced an issue.

 

Useful blog written a while ago:

Why-is-this-commit-not-working ?

 

Hope this helps !

-Kiwi.

 

 

 
LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

View solution in original post

2 REPLIES 2

Community Team Member

Hi @MP18 ,

 

There is a useful command, "show management-clients".  

This command shows the status of all of running daemons that are used during the commit process.  

 

admin@PA-VM> 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)

Notice the * at the end of the 'device' line, indicating there was an issue with the device server during our commit.  In some cases the problem can be resolved by restarting the daemon that experienced an issue.

 

Useful blog written a while ago:

Why-is-this-commit-not-working ?

 

Hope this helps !

-Kiwi.

 

 

 
LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

Many Thanks for answering.

You gave me very useful info which is very hard to find elsewhere.

 

MP

Help the community: Like helpful comments and mark solutions.
  • 1 accepted solution
  • 6191 Views
  • 2 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!