Results 1 to 3 of 3

Thread: Migration to VM blocked by LDAP error

  1. #1
    dionrowney is offline Active Member
    Join Date
    Mar 2008
    Posts
    31
    Rep Power
    7

    Default Migration to VM blocked by LDAP error

    I am trying to migrate my Community Edition Zimbra installation from a physical box to a VM.

    I have done a transfer of the OS and current Zimbra config in a shutdown state.

    When try to start up and also when trying an upgrade it reports this error:

    Apr 24 04:40:01 mail postfix/postqueue[12105]: fatal: Queue report unavailable - mail system is down
    Apr 23 22:40:01 mail zimbramon[12079]: 12079:info: 2012-04-23 22:40:01, QUEUE: 0 0
    Apr 23 22:40:03 mail slapd[12262]: @(#) $OpenLDAP: slapd 2.4.18 (Nov 11 2009 16:13:09) $ build@build10.lab.zimbra.com:/home/build/p4/GNR-603/ThirdParty/openldap/openldap-2.4.18.2z/servers/slapd
    Apr 23 22:40:03 mail slapd[12272]: bdb(): file id2entry.bdb has LSN 28/4461092, past end of log at 28/3832118
    Apr 23 22:40:03 mail slapd[12272]: bdb(): Commonly caused by moving a database from one database environment
    Apr 23 22:40:03 mail slapd[12272]: bdb(): to another without clearing the database LSNs, or by removing all of
    Apr 23 22:40:03 mail slapd[12272]: bdb(): the log files from a database environment
    Apr 23 22:40:03 mail slapd[12272]: bdb(): /opt/zimbra/data/ldap/hdb/db/id2entry.bdb: unexpected file type or format
    Apr 23 22:40:03 mail slapd[12272]: hdb_db_open: database "": db_open(/opt/zimbra/data/ldap/hdb/db/id2entry.bdb) failed: Invalid argument (22).
    Apr 23 22:40:03 mail slapd[12272]: backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22)
    Apr 23 22:40:03 mail slapd[12272]: bdb_db_close: database "": alock_close failed
    Apr 23 22:40:03 mail slapd[12272]: slapd stopped.


    Failed to start slapd. Attempting debug start to determine error.
    4f963c10 hdb_db_open: database "": db_open(/opt/zimbra/data/ldap/hdb/db/id2entry.bdb) failed: Invalid argument (22).
    4f963c10 backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22)
    4f963c10 bdb_db_close: database "": alock_close failed


    I have tried a db_recover but no avail.

    My production has system has no problems.

    dion

    __________________
    --
    Zimbra 6.0.3
    CentOS 5.3
    --
    Zimbra 6.0.3
    CentOS 5.3

  2. #2
    justdave is offline Trained Alumni
    Join Date
    Nov 2008
    Location
    Grand Rapids, MI
    Posts
    123
    Rep Power
    6

    Default

    Is the VM a different architecture than the original machine by any chance? (32bit vs 64bit for example)

  3. #3
    dionrowney is offline Active Member
    Join Date
    Mar 2008
    Posts
    31
    Rep Power
    7

    Default

    Both are 32 bit. They are full clones - os and all. I have had this working in the past but when we actually went to perform the cutover it decided to throw this error.
    --
    Zimbra 6.0.3
    CentOS 5.3

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Zimbra Crashes every day
    By feiticeir0 in forum Administrators
    Replies: 10
    Last Post: 10-13-2011, 06:53 AM
  2. MySQL errors
    By mludwig in forum Administrators
    Replies: 1
    Last Post: 07-11-2011, 03:40 AM
  3. [SOLVED] Zimbra 7.0.1 Database Issue after upgrade
    By n.bochev in forum Administrators
    Replies: 3
    Last Post: 03-16-2011, 01:07 AM
  4. Replies: 6
    Last Post: 03-14-2011, 04:21 AM
  5. LDAP error code 49 - invalid credentials
    By fieze in forum Installation
    Replies: 8
    Last Post: 05-09-2008, 05:12 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
  •