- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-18-2013 08:48 PM
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
07-28-2013 04:25 PM
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
07-18-2013 10:39 PM
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.
07-18-2013 11:05 PM
Another question :
My Outside L3 Interface can not ping to one IP in the same subnet but ping to one orther is OK ?
07-27-2013 02:46 AM
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.
07-28-2013 04:25 PM
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
07-28-2013 08:30 PM
Thanks for all comment.
I have fixed it OK
08-01-2013 06:26 AM
Thanks! I just got a 3020 yesterday and after running updates I had this same issue. This fixed it for me!
11-05-2014 06:45 AM
I've found another weird situation when I get the same error message. I was testing DLP. After I finally managed to get rid of "pattern must be at least 7 bytes" configuration check I tried to commit the configuration. but I got "Error: Threat database handler failed (Module: device) Commit failed." message. I've tried reverting threat database, upgrading, reinstalling... but nothing helped. Then I deleted my "Data Filtering" profile and "Data Patterns" object and commit was succesful.
There is probably a configuration check missing and the commit fail message is a bit misleading. Or is it just a bug. Btw this happened on PAN-OS 6.1.
12-17-2014 02:09 AM
hey
I tried doing the steps mentioned it still not resolved, What can be done more on this.
06-28-2020 05:02 PM
Hi guys,
I had this same problem over the weekend however it wasn't the content packages that were at fault.
Panorama was pushing to a device group and in my instance, the firewall wasn't getting the config and showing as "failed error: threat database handler failed"
There was a piece of config on Panorama that was pushing out to the firewall that it didn't like. Once this was resolved in the device group, I was then able to re-push again.
To test this you can push to a singular device to see if the error comes back.
04-21-2022 10:46 PM
Hello,
It seems we are running into a similar one, it isn't the threat update but the policies. Could you let me know how did you arrive at the policy /object that was causing the error?
Thanks,
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!