Results 1 to 2 of 2

Thread: Bad 5.0b2 upgrade

Hybrid View

  1. #1
    Join Date
    Nov 2005
    Posts
    477
    Rep Power
    10

    Default Bad 5.0b2 upgrade

    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.

  2. #2
    Join Date
    Nov 2005
    Posts
    477
    Rep Power
    10

    Default


    [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.

Similar Threads

  1. Upgrade 4.5.4 to 4.5.5 questions
    By dlochart in forum Zimbra Connector for Outlook
    Replies: 11
    Last Post: 05-14-2007, 03:44 AM
  2. Upgrade gone bad
    By kechols in forum Administrators
    Replies: 8
    Last Post: 04-04-2007, 01:31 PM
  3. Replies: 5
    Last Post: 03-01-2007, 03:20 AM
  4. 4.01 to 4.02 upgrade problem (with solution)
    By criley in forum Migration
    Replies: 2
    Last Post: 09-29-2006, 12:36 AM
  5. M1 -> M2 Upgrade Scripts
    By KevinH in forum Announcements
    Replies: 57
    Last Post: 12-15-2005, 10:10 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •