Error: Threat database handler failed (Module: device)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

Error: Threat database handler failed (Module: device)

L3 Networker

I got two devices 3020 and is running with HA Active/Passive.

First, I have download and install "Application version 384-1877 (07/18/13) and Threat version 384-1877 (07/18/13)" on the Active device and I select Syns ... to peer.

After that, I issue "request restart system" on the passive device.

Next, when the passive device reboot sussesfully, the HA feature is fail and HA is not enable on the passive device.

When I set disable HA Feature on the passive device and re-enable it, but it issue an error

"Error: Threat database handler failed  (Module: device) and commit fail "

Please view figure : threat-database error.png.

Please help me fix this problems

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions

Hello,

You have to re-install the latest content manually, after the reverting to a previous content release.


1.Downgrade the content to any previous version - upload & install the package manually.

2.Try a commit on the device.

3. Re-install the latest content version and test the commit.

Aditi

View solution in original post

10 REPLIES 10

L5 Sessionator

Error requires downgrade of content to a previous version.

Download Content off site via the support portal.

Please initiate the content upload/install manually using the GUI.

https://live.paloaltonetworks.com/docs/DOC-1064 -step 6

Another question :

My Outside L3 Interface can not ping to one IP in the same subnet but ping to one orther is OK ?

I have the same issue. Obviously something is wrong with the current Content update. WTF? Is there no quality control?

Which version should we install to get around this? If we install an older version, the firewall will auto-update to the broken version unless we disable auto-update.

Hello,

You have to re-install the latest content manually, after the reverting to a previous content release.


1.Downgrade the content to any previous version - upload & install the package manually.

2.Try a commit on the device.

3. Re-install the latest content version and test the commit.

Aditi

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!