Commit Error "commit operation aborted as all daemons are not available"

[robert.hoffmann]

What does it mean and how to solve it?

Regards Robert

[hyadavalli]

Hello Robert,

I'd recommend opening case with support with tech support file attached.

Regards,

Hari Yadavalli

[BenjaminArbab]

I'm having same exact issue now in 8.0.5 and 8.0.4

admin@DC-mgmt-fw1# commit

Server error : Commit job was not queued. All daemons are not available.
[edit]
admin@DC-mgmt-fw1# commit force

Server error : Commit job was not queued. All daemons are not available.

[AMS-IX]

Apologies for posting through space in time, but someone might have gotten a clue in the mean time, before we opened a case with our partner.

We encountered the same error in our 8.1.2 running Panorama KVM VM (legacy mode). I'm not sure if it's correlated somehow, but the problem appeared after we mounted a large NFS volume for log storage. Before that commits were working without any issues. 

Adding insult to injury, generating a tech support file seems to get stuck at 10%, regardless of whether it's generated via the GUI or the CLI.

Any pointers or ideas would be greatly appreciated!

UPDATE: We confirmed it's the NFS store, and probably its large size (8TB). When we added a temporary ACL entry in an intermediate router to block access to the NFS store from Panorama, and after rebooting Panorama, commits were working fine again. HTH someone! 

[MPI-AE]

same here on a PA 3020 with 8.0.7.

Any hints?

[AMS-IX]

Hi @MPI-AE,

We got the following command from PAN TAC, please use at own risk though:

debug management-server client disable cord

[SimonT]

I had this and it was /opt/panlogs full:

admin@panorama> show system disk-space
Filesystem Size Used Avail Use% Mounted on
/dev/sda8 91G 91G 0 100% /opt/panlogs

Emptied some logs:

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSjCAK