topic Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed in General Topics

Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

paloalto.nis — Thu, 25 Apr 2013 13:13:54 GMT

Hello,

My device is a PA-2020 in version 4.0.5.

I upgraded the device in 4.1.12 (I have downloaded the basic version 4.1.0)

The installation went well and also reboot.

But when the device performs its AUTOCOMMIT, there is an error.

At each failure a AUTOCOMMIT, but every time there is an error.

I noticed two errors:

"Error: failed to handle TDB_UPDATE_BLOCK"

"Autocommit: failed to commit policy to device"

As AutoCommit is never OK, the device is down and stays in "Not Ready".

Thank you in advance for your help.

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

Retired Member — Thu, 25 Apr 2013 13:16:49 GMT

if you have a config backup I recommend factory reset

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

paloalto.nis — Thu, 25 Apr 2013 13:32:39 GMT

Thank you for your quick return.

I went back to version 4.0.5. I have not had any problems for the downgrade.

You advise me to do a factory reset once I go back to 4.1.12 and now I'm in 4.0.5?

Is this the only way to you?

Also, the config backup of 4.0.5 can be installed on 4.1.12 without problems or compatibility errors?

Thank you again for your help.

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

ericgearhart — Thu, 25 Apr 2013 13:35:41 GMT

bulent wrote:

if you have a config backup I recommend factory reset

Wait a second here... have you opened a ticket and sent a tech support file to PA support yet? There might be a simple fix that lets the commit complete, or at least some debug command on the commit that provides more detail

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

Retired Member — Thu, 25 Apr 2013 13:38:38 GMT

if you factory reset and upgrade to 4.1.12

then you can import your config

this will be a qucik solution

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

paloalto.nis — Thu, 25 Apr 2013 13:40:04 GMT

Yes, I opened a support ticket and I sent them tech support but so far no return ..

Thank you.

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

ericgearhart — Thu, 25 Apr 2013 13:41:07 GMT

Hmm. I suppose. I wonder if doing a factory reset and then importing a config should be more or less a "best practice" then...

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

paloalto.nis — Thu, 25 Apr 2013 13:55:27 GMT

Thank you to you two for your feedback.

If other people have other suggestions, it is with pleasure ..

I'll expect a return of support, but if I decide to do a factory reset then upgrade, you confirm that there will be no problems when importing conf between 4.0.5 to 4.1.12 (or 5.0.4)?

Thank you again for your help.

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

gswcowboy — Thu, 25 Apr 2013 17:31:38 GMT

Ok so let me understand this and correct me if I'm wrong. You encounter the autocommit failure multiple times upon upgrading to 4.1.12. You've downgraded back to 4.0.5 since. If so, here's what I suggest per your output of the autocom failure

Download 4.1.0 image once more

Back up 4.0.5 config snapshot if not done already

Install 4.1.2 image and reboot

If you encounter the failure once more w/ following output - "Autocommit: failed to commit policy to device", perform the next step

admin@PA-200> configure

admin@PA-200# load config from running-config.xml

admin@PA-200> commit force

Please call into Support if the issue persists given the steps performed above.

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

paloalto.nis — Fri, 26 Apr 2013 08:29:33 GMT

I'll try your recommendation next week.

I would say if it went well.

Thank you again for your help.

Re: Failure Upgrade 4.0.5 to 4.1.12 with Auto Commit Failed

paloalto.nis — Tue, 07 May 2013 12:39:37 GMT

HelIo,

I opened a box to support, and that's what they found

> show system logdb-quota

Quotas:

traffic: 32.00%, 38.123 GB

Disk usage:

traffic: Logs: 32G, Index: 39G

As you can see the traffic log plus the quota is way above the quota. This causes issues as it requires more memory to be used than expected. The logs will need to be deleted before they will be handled correctly.

I made the upgrade on their recommendation and no worries, I even succeeded in upgrade to 4.1.12 -> 5.0.4
Thank you again for your help.