topic Re: Stuck on auto commit in General Topics

Stuck on auto commit

inderjit21 — Mon, 06 Jun 2016 08:39:34 GMT

I had PA200 in active/passive. Upgraded from 7.0.2 to 7.0.6. Rebooted passive unit. Keeps on failing auto commit. Which happned around 10 times and then just sitting there . Interfaces down. Rebooted again same thing.

I tries commit force. Disconnected HA port still same issue.

Re: Stuck on auto commit

Remo — Mon, 06 Jun 2016 09:30:21 GMT

Do you have any more informations/details about a possible reason (provided by your firewall)?

Re: Stuck on auto commit

reaper — Mon, 06 Jun 2016 12:11:27 GMT

unless your passive link state is set to auto it would be normal for the interfaces to stay down. if you do a

> show jobs id <ID_of_autocommit>

, does it provide additional details why it failed ?

Re: Stuck on auto commit

KotreshaMC — Tue, 07 Jun 2016 12:30:51 GMT

I hope below process helps you

https://live.paloaltonetworks.com/t5/Management-Articles/How-to-upgrade-a-High-Availability-HA-pair/ta-p/57081

Regards,

Kotresha

Re: Stuck on auto commit

pulukas — Fri, 10 Jun 2016 23:19:18 GMT

I remember this happening once from low disk space during an upgrade. Check the disk usage and possibly remove old update files.

https://live.paloaltonetworks.com/t5/Management-Articles/How-to-Free-Up-Disk-Space-in-PAN-OS-5-0/ta-p/63151

Re: Stuck on auto commit

Amitchauhan70 — Mon, 26 Jun 2017 22:50:37 GMT

I faced a similar issue while moving from 7.0.8 to 7.1.9

Turned out the captive portal was enabled & did not had the "authentication profile" linked to it. We did not use captive portal on this firewall thats the reason no one cared to check , but that costed some serious HA issues.

CP was later disabled & auto commit went through fine.

Re: Stuck on auto commit

MohamedSharief — Tue, 27 Jun 2017 09:34:56 GMT

I had this issue before, auto commit kept failing without showing any error. I was reverting back to old configurations one by one till the commit was successfull, I turned out that during migration the NAT rule was not properly configured.

Regards,

Sharief