Commit error after version upgrade to v. 10.1.3

[aerspa]

Hi all,

after an upgrade of my VM-100 from 9.1.12 to 10.1.3 version I receive a commit error.

The fw is in HA configuration, but this is down. The other fw is ooperating in 9.1.12 version.

On KB and communities I not have found a solution for this problem.

On commit force, I receive Server error: Commit job was not queued. Client logrcvr not connected. All daemons are not available.

I have restarted management process and logrcvr process without results.

After reboot of vm nothing change.

I think not have conflict of commit queues by different users.

Any suggestion is appreciated.

Many thanks.

Max

Thi is the tasks manager screenshot:

[PavelK]

Thank you for the post and sorry to hear you are facing an issue @aerspa

Based on your screen shot, the Auto Commit is failing. Without Auto Commit to be completed, your data plane interfaces / HA will be not functional.

It looks like you are using an EDL. If you are using custom EDL potentially you might be hitting what has been discussed in this thread: https://live.paloaltonetworks.com/t5/general-topics/auto-commit-failing-interfaces-down-not-able-to-...

If the above is not the case, then I would try to downgrade to 10.0.8-h4.

Kind Regards

Pavel

[TomYoung]

Hi @aerspa ,

I have run into similar issues before where the auto-commit fails.  I usually do a commit force on the CLI and troubleshoot from there.  In this case, it looks like your auto-commit is stuck.  Could you try clicking "Stop Job" for the auto-commit and then "commit force" on the CLI?

Thanks,

Tom

[aerspa]

Thanks to Pavel and Tom,

I have tried a downgrade but it's not work for incompatibility of config file version.

And I have tried to execute e commit force via CLI, but not work with an error on logrcvr functionality.

The EDL is used with Minemeld and I thought to disable it but I can't commit this change: it' a diabolic loop...

Best reagards.

Max

[JoshuaSanders]

Did you ever resolve this? What was your path to get past this bug? We are trying to upgrade multiple 220s from 9.1.13 to 10.0.X and it's failing on the auto-commit