08-17-2018 02:09 AM
I just update to PANOS 8.1.3 yesterday and found a error when commit the change today. The error message is 'Commit job was not queued. All daemons are not available.'. I tried reboot the firewall and the error still exists when I click on the commit. So no change can apply because it cannot commit the change. Now I rollback to 8.1.2 and it can commit the change.
Anyone have that problem?
08-19-2018 10:45 PM
08-19-2018 10:48 PM
It is PA820.
08-19-2018 10:54 PM
@simonleung, thanks for replying. we will also test this in our PA850.
i suggest you report it to palo alto support. so that if it is a bug; it can be resolved asap
08-20-2018 01:11 AM
08-20-2018 10:01 PM
08-21-2018 08:54 PM
Upgraded one of the lab units to 8.1.3 and it appears to be stable; however note that this particular lab device isn't used much, so take that with plenty of grains of salt 😉
08-28-2018 11:23 AM
Updated our 3060 Cluster to 8.1.3. It works till now.
08-28-2018 11:13 PM - edited 08-29-2018 06:33 AM
I have this working.
In my case logrcv process was in "stopped" state.
You can see that when issuing "show system software status" command.
After restarting the process, I was able to commit. ("debug software restart process log-receiver")
I also had to revert all changes made prior the process restart before I could commit.
*** UPDATE ***
The issue is back.
I also noticed, there are no new logs being created, and no data can be seen in ACC and dashboard.
09-22-2018 05:20 AM
09-24-2018 01:09 PM
I upgraded two 3220s from 8.1.0 (factory) directly to 8.1.3. Then pasted a bunch of config into both and HA-paired them w/o issue 7 days ago.
06-18-2019 09:42 PM
My vm virtual machine has the same problem. The virtual machine version is esx 6.1.2.ova.but I restat the machine was ok.
05-29-2021 09:03 PM
Hi Guys this is my quick solution to the above "commit" error. exit the configuration mode and retur back to it by typing configure then retype "commit" the firewall will allow to commit the changes.
admin@PA-VM# Server error : Commit job was not queued. All daemons are not available.
Unknown command: Server
Exiting configuration mode
Entering configuration mode
Commit job 2 is in progress. Use Ctrl+C to return to command prompt
Configuration committed successfully
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!