topic Re: Commit job was not queued. All daemons are not available in General Topics

Commit job was not queued. All daemons are not available

Demong — Fri, 07 Mar 2025 09:32:47 GMT

Hey!
I still use a PA-200 which one was out of work since broken power supply. Now it's start up and after upgrade PANOS from 8.1.23 to 8.1.26-h1 I can't commit any changes with error:
Commit job was not queued. All daemons are not available
I already read every the same cases here but nothing helps

though system software status looks pretty :

admin@PA-200> show system software status

Slot 1, Role mp
----------------------------------------

Type Name State Info
Group all running
Group base running
Group batch running
Group batch_secondary running
Group chassis running
Group data_plane running
Group dsms running
Group fips running
Group gdb running
Group ha_ssh running
Group mgmt_services running
Group ntlm-grp running
Group services running
Group supervisor running
Group tasks running
Group third_party running
Process all_task running (pid: 2738)
Process appweb running (pid: 3793)
Process authd running (pid: 3810)
Process brdagent running (pid: 2581)
Process chasd running (pid: 2583)
Process comm running (pid: 2734)
Process crypto running (pid: 2827)
Process dagger running (pid: 2560)
Process devsrvr running (pid: 11212)
Process dha running (pid: 2735)
Process dhcp running (pid: 3806)
Process dnsproxy running (pid: 3807)
Process ehmon running (pid: 2582)
Process ha-sshd running (pid: 2836)
Process ha_agent running (pid: 3803)
Process ikemgr running (pid: 3797)
Process keymgr running (pid: 3800)
Process l2ctrl running (pid: 3802)
Process l3svc running (pid: 3821)
Process logrcvr running (pid: 3798)
Process masterd running (pid: 2482)
Process mgmtsrvr running (pid: 3766)
Process monitor running (pid: 2561)
Process monitor-dp running (pid: 2740)
Process mprelay running (pid: 2733)
Process pppoe running (pid: 3808)
Process rasmgr running (pid: 3799)
Process routed running (pid: 3809)
Process satd running (pid: 3804)
Process snmpd running (pid: 3816)
Process sshd running (pid: 2858)
Process sslmgr running (pid: 3805)
Process sslvpn running (pid: 3796)
Process sslvpn_ngx running (pid: 3826)
Process sysd running (pid: 2502)
Process sysdagent running (pid: 2564)
Process tund running (pid: 2736)
Process useridd running (pid: 3745)
Process varrcvr running (pid: 3801)
Process websrvr running (pid: 3791)

Please helps, I realy need this stuff to bring up to work!

Re: Commit job was not queued. All daemons are not available

BPry — Sun, 09 Mar 2025 05:41:35 GMT

@Demong,

Just looking at the screenshot that you have shared, it looks like you very well could have just not given the thing enough time to boot fully. It looks like your commit was attempted when the PA-200 would have had a recorded uptime of ~40 minutes; on a PA-200 at the tail end of 8.1 that really is at the point where I would just be expecting it to be coming back online and fully operational. It doesn't look like you've tried to commit since that point looking at what the screenshot provides, have you tried to commit since then and still encountered issues?

Re: Commit job was not queued. All daemons are not available

Demong — Sun, 09 Mar 2025 18:24:58 GMT

@BPry Thanks a lot for your answer. Unfortunately today is 9th of March, device last rebooted last friday and I see the same behaviour:

Re: Commit job was not queued. All daemons are not available

Demong — Mon, 10 Mar 2025 05:51:13 GMT

I also forgot to say that the status LED is orange

Re: Commit job was not queued. All daemons are not available

Brandon_Wertz — Mon, 10 Mar 2025 12:54:07 GMT

PA-200s are EOS as of Oct '23 and 8.1 is EOS as of Mar '22. The 200s were ok 10 years ago, but were very finicky. With both software and hardware being sooooooo beyond EOS/EOL there's no value in continuing to run a product that isn't contemporary in current threats or device capabilities.