Hide Forgot
Description of problem: verify-db.pl has option '-a 'which can specify path to DB. https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Configuration_Command_and_File_Reference/Perl_Scripts.html#verify-db.pl But if verify-db.pl run with -a option, it does not verify DB files under DB directory which is specified by option '-a', but it alreays verify instance DB instead. Steps to Reproduce: 1. take backup by db2bak 2. run DB verify against backup DB with -a option e.g. ./verify-db.pl -a /var/lib/dirsrv/slapd-test/bak/test-2015_07_06_16_32_07 Actual results: DB files unser instance's DB directory always get verified. Expected results: DB files under DB directory specified -a option is verified. Additional info: Easy workaround: N/A
Tested build: 389-ds-base-1.2.11.15-69.el6.x86_64 [root@test-machine test]# /usr/lib64/dirsrv/slapd-test-machine/db2bak.pl -v -D "cn=directory manager" -w Secret123 Back up directory: /var/lib/dirsrv/slapd-test-machine/bak/test-machine-2015_12_3_10_57_48 ldap_initialize( ldap://test-machine.redhat.com:389 ) add objectclass: top extensibleObject add cn: backup_2015_12_3_10_57_48 add nsArchiveDir: /var/lib/dirsrv/slapd-test-machine/bak/test-machine-2015_12_3_10_57_48 add nsDatabaseType: ldbm database adding new entry "cn=backup_2015_12_3_10_57_48, cn=backup, cn=tasks, cn=config" modify complete [root@test-machine test]# /usr/lib64/dirsrv/slapd-test-machine/verify-db.pl -a /var/lib/dirsrv/slapd-test-machine/bak/test-machine-2015_12_3_10_57_48 ***************************************************************** verify-db: This tool should only be run if recovery start fails and the server is down. If you run this tool while the server is running, you may get false reports of corrupted files or other false errors. ***************************************************************** Verify log files in /var/lib/dirsrv/slapd-test-machine/bak/test-machine-2015_12_3_10_57_48 ... Good Verify db files ... Good Marking as VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0737.html