[Date Prev][Date Next] [Chronological] [Thread] [Top]

good time to learn how to fix problems

Before I go live with this server 2.2.19 

from my slapd.log

Feb 11 23:40:38 srv1 slapd[9257]: conn=13 op=1 DEL
Feb 11 23:40:38 srv1 slapd[9257]: => bdb_dn2id_delete: delete failed:
DB_NOTFOUND: No matching key/data pair found -30990
Feb 11 23:40:38 srv1 slapd[9257]: conn=13 op=1 RESULT tag=107 err=80
text=DN index delete failed

OK - no problemo 

stop slapd

# cd /usr/local/var/openldap-data
# db_recover

# db_recover
db_recover: Ignoring log file: /usr/local/var/openldap-
logs/log.0000000001: magic number 0, not 40988
db_recover: Invalid log file: log.0000000001: Invalid argument
db_recover: PANIC: Invalid argument
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database

I do have slapcat output and can reload but am wondering wtf

# Set the database in memory cache size.
set_cachesize   0       52428800        0

# Set database flags.
# (for database loading/reindexing)
#set_flags       DB_TXN_NOSYNC

# Set log values.
set_lg_regionmax        1048576
set_lg_max              10485760
set_lg_bsize            2097152
set_lg_dir              /usr/local/var/openldap-logs

I have only been using this system minimally as I am preparing things to
go live and have now earnestly started to finish things up.

Is there something wrong with my db setup? 4.2.52 (with Quanah reference
patches 1 & 2 & transactions patch) 

Is the proper thing to do to simply nuke the log file and the data files
slapadd the DSA again, fix the file ownership and start it up? 

Am I missing something?  

Does the above DB_CONFIG look good? It's a somewhat small non-profit