Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

Can't do a commit ! Auto-commit failing

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Can't do a commit ! Auto-commit failing

L1 Bithead

Hi

Have got a Pa-3020 Demo box to use for a POC, but I cant commit anything as "commit operation aborted as auto-commit not done yet"

In the Task view several auto-commit antries are failed.

Any one has any suggestions ??

 

Best Regards Jens W

1 accepted solution

Accepted Solutions

Community Team Member

Hi @JensWilladsen,

 

The Threat database handler is a 'known' commit failure.

 

In most cases a corrupt AV signature database or Content database will cause these type of auto commit failures.   AV update process or Content update process might have been terminated abruptly without any indication to the user leaving the AV signature database corrupt  or Content database corrupt.

 

Usually a manual Anti-Virus install from the CLI will serve as a workaround for this issue.  Download the Anti-Virus file manually from https://support.paloaltonetworks.com and upload the same to the firewall. After the upload, use the following command to do the manaul AV install from the CLI.

 

> request anti-virus upgrade install file

 

If the manual install workaround fails for some reason, then another workaround for this issue is described below:

 

  1. Remove the contents of the following folders (root access might be required ... contact Support for this):
    /opt/pancfg/mgmt/updates/curav/
    /opt/pancfg/mgmt/updates/oldav/
    Remove only the contents of the folder and leave the folders intact.
  2. Restart the device server process.
  3. Do a commit force. 

Below are some articles and discussions that discuss this behaviour and offer possible workaround/solution :

 

Threat Database Handler Failed Commit Error

Error Threat database handler failed Module device

 

Cheers !

-Kim.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

View solution in original post

4 REPLIES 4

Community Team Member

Hi @JensWilladsen,

 

Autocommit failures can have many reasons.

Can you check the autocommit job details and verify exactly why they are failing ?

 

Cheers !

-Kim.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

Hi @kiwi

The task view looks like this:

auto-commit.PNG

Regards Jens

 

Community Team Member

Hi @JensWilladsen,

 

The Threat database handler is a 'known' commit failure.

 

In most cases a corrupt AV signature database or Content database will cause these type of auto commit failures.   AV update process or Content update process might have been terminated abruptly without any indication to the user leaving the AV signature database corrupt  or Content database corrupt.

 

Usually a manual Anti-Virus install from the CLI will serve as a workaround for this issue.  Download the Anti-Virus file manually from https://support.paloaltonetworks.com and upload the same to the firewall. After the upload, use the following command to do the manaul AV install from the CLI.

 

> request anti-virus upgrade install file

 

If the manual install workaround fails for some reason, then another workaround for this issue is described below:

 

  1. Remove the contents of the following folders (root access might be required ... contact Support for this):
    /opt/pancfg/mgmt/updates/curav/
    /opt/pancfg/mgmt/updates/oldav/
    Remove only the contents of the folder and leave the folders intact.
  2. Restart the device server process.
  3. Do a commit force. 

Below are some articles and discussions that discuss this behaviour and offer possible workaround/solution :

 

Threat Database Handler Failed Commit Error

Error Threat database handler failed Module device

 

Cheers !

-Kim.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

@kiwi Thx i will try that!

 

Regards Jens

  • 1 accepted solution
  • 29476 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!