Bad 5.0b2 upgrade

[JoshuaPrismon]

Bad 5.0B2 Install problem....

The system performed the upgrade just fine. However, the administration interface wasn't working right. I went back to take a look at it again, and rerun the install, and watched the log a bit closer:

Jul 26 22:46:28 technicaldetails slapd[25762]: @(#) $OpenLDAP: slapd 2.3.34 (Mar 28 2007 13:47:44) $ root@wolfowitz.liquidsys.com:/home/build/p4/main/ThirdParty/openldap/openldap-2.3.34/servers/slapd
Jul 26 22:46:28 technicaldetails slapd[25763]: bdb_db_open: DB_CONFIG for suffix has changed. Performing database recovery to activate new settings.
Jul 26 22:46:28 technicaldetails slapd[25763]: bdb_db_open: cannot recover, database must be reinitialized.
Jul 26 22:46:28 technicaldetails slapd[25763]: backend_startup_one: bi_db_open failed! (-1)
Jul 26 22:46:28 technicaldetails slapd[25763]: bdb_db_close: alock_close failed
Jul 26 22:46:28 technicaldetails slapd[25763]: slapd stopped.
Jul 26 22:46:28 technicaldetails slapd[25763]: connections_destroy: nothing to destroy.
Jul 26 22:46:28 technicaldetails slapd[25762]: @(#) $OpenLDAP: slapd 2.3.34 (Mar 28 2007 13:47:44) $ root@wolfowitz.liquidsys.com:/home/build/p4/main/ThirdParty/openldap/openldap-2.3.34/servers/slapd

......

Jul 26 22:47:01 technicaldetails zimbramon[26494]: 26494:info: Stopping ldap
Jul 26 22:47:01 technicaldetails slapd[25782]: daemon: shutdown requested and initiated.
Jul 26 22:47:01 technicaldetails slapd[25782]: slapd shutdown: waiting for 0 threads to terminate
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 1/2435612 past current end-of-log of 1/64037
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 1/2435612 past current end-of-log of 1/64037
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 1/2008937 past current end-of-log of 1/64120
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 1/2008937 past current end-of-log of 1/64120
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 1/4981524 past current end-of-log of 1/64212
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 1/4981524 past current end-of-log of 1/64212
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 2/7896306 past current end-of-log of 1/64298
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 2/7896306 past current end-of-log of 1/64298
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): DB_ENV->log_flush: LSN of 1/2435612 past current end-of-log of 1/64387
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): cn.bdb: unable to flush page: 0
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb(): txn_checkpoint: failed to flush the buffer cache Invalid argument
Jul 26 22:47:01 technicaldetails slapd[25782]: bdb_db_close: txn_checkpoint failed: Invalid argument (22)
Jul 26 22:47:01 technicaldetails slapd[25782]: slapd stopped.
Verifying /opt/zimbra/conf/my.cnf

This is really really bad because it means my backup is just as corrupt as the version I upgraded. Anyone seen this before? I am aware that this occurs outside of the upgrade, but I am more curious if anyone has seen in in a 5b2 upgrade.

[JoshuaPrismon]

[root@technicaldetails openldap-data]# /opt/zimbra/sleepycat/bin/db_recover -v
db_recover: Finding last valid log LSN: file: 1 offset 64387
db_recover: Recovery starting from [1][28]
db_recover: Log sequence error: page LSN 1 63536; previous LSN 2 7740360
db_recover: Recovery function for LSN 1 415 failed on forward pass
db_recover: PANIC: Invalid argument
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery

DBRecover -v doesn't help at all either.