This article details a procedure for troubleshooting and resolving IDP security-package update issues.
The IDP security-package update fails with the error below when the IDP database or some files are corrupted:
Failed in opening security database
The corruption can occur because the SRX is booting up from a backup image, a power failure, or some other issue.
> show security idp security-package-version Error; Failed in opening security database
> show security idp security-package-version
Error; Failed in opening security database
Failed in opening database /var/db/idpd/db/secdb_01.db : Invalid format or unexpected end of file
> request security idp security-package install Error; Failed in opening security database
> request security idp security-package install
If the answer to this question is "yes," the IDP DB is probably corrupted. If that is the case, perform the steps below to fix the problem:
Deactivate IDP configuration, if active:
# deactivate security idp # commit
# deactivate security idp
# commit
From the shell prompt, navigate to the directory /var/db/idpd/db/ and list the files present there:
/var/db/idpd/db/
% cd /var/db/idpd/db/ % ls -l
% cd /var/db/idpd/db/
% ls -l
This should show the files secdb_01.db , secdb_02.db , and so on.
secdb_01.db
secdb_02.db
Among the files listed, the IDP consults the file secdb_01.db when looking up the security-package version. Move this file to a temporary location:
% mv secdb_01.db /var/tmp/
Check the security-package-version, which should now show as N/A:
Attack database version: N/A(N/A) Detector version :12.6.160140626 Policy template version :N/A
Download (full-update) and install the security-package on the device:
> request security idp security-package download full-update > request security idp security-package install
> request security idp security-package download full-update
Confirm that the IDP includes the latest attack DB:
Activate the IDP configuration, followed by a commit.