Chapter 7. Command-Line Scripts
318
Option
Alternate Options
Description
the cleartext
passwords
supplied during
setup. Use
appropriate caution
and protection with
this file.
--logfile
name
-l
This parameter specifies a
log file to which to write the
output. If this is not set, then
the setup information is written
to a temporary file. To not use
a log file, set the file name to
/
dev/null
.
--update
-u
This parameter updates
existing Directory Server
instances. If an installation
is broken in some way, this
option can be used to update
or replace missing packages
and then re-register all of
the local instances with the
Configuration Directory.
7.4.21. verify-db.pl (Check for Corrupt Databases)
Verifies the backend database files. If the server crashes because of a corrupted database, this script
can be used to verify the integrity of the different database files to help isolate any problems.
IMPORTANT
Never
run
verify-db.pl
when a modify operation is in progress. This command calls
the BerkeleyDB utility
db_verify
and does not perform any locking. This can lead to
data corruption if the script is run at the same time as a modify. If that occurs, an entry will
be recorded in the error log:
DB ERROR: db_verify: Page 3527: out-of-order key at entry 42
DB ERROR: db_verify: DB->verify: db/mstest2/uid.db4: DB_VERIFY_BAD: Database
verification failed
Secondary index file uid.db4 in db/mstest2 is corrupted.
Please run db2index(.pl) for reindexing.
Run
db2index -t uid
to avoid rebuilding all of the indexes or export and reimport all of
the databases using
db2ldif
and
ldif2db
.
Syntax
verify-db.pl
[ -a
/path/to/database_directory
] [ -? ]
Содержание 8.1
Страница 8: ...viii ...
Страница 14: ...xiv ...
Страница 16: ...2 ...
Страница 250: ...236 ...
Страница 334: ...320 ...
Страница 372: ...358 ...