Results 1 to 8 of 8

Thread: Unsuccessfull upgrade from ZCS OSE 7.2.1 to 8.0 due to interruption

  1. #1
    damjanster is offline Junior Member
    Join Date
    May 2009
    Posts
    8
    Rep Power
    6

    Unhappy Unsuccessfull upgrade from ZCS OSE 7.2.1 to 8.0 due to interruption

    After a successful migration from RHEL5 to RHEL6 (both 64bit) of zimbra 7.2.1. I went ahead and tried to upgrade ZCS to version 8.0.
    During the upgrade someone else connected to the server and ran "service zimbra restart" - this interfered with the upgrade and made it fail with this error:

    Sun Oct 7 08:18:55 2012 Schema upgrade required from version 90 to 91.
    Sun Oct 7 08:18:55 2012 Running /opt/zimbra/libexec/scripts/migrate20120410-BlobLocator.pl
    Sun Oct 7 08:18:57 2012 Sun Oct 7 08:18:57 2012: Verified schema version 90.
    Sun Oct 7 08:19:18 2012 ERROR 1054 (42S22) at line 1: Unknown column 'volume_id' in 'mail_item'
    Sun Oct 7 08:19:18 2012 Sun Oct 7 08:19:18 2012: Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=QUlKJ8JX7.FsAZXaUTzQqiaw --database=zimbra --batch --skip-column-names'.
    Sun Oct 7 08:19:18 2012 Script failed with code 256: - exiting
    Sun Oct 7 08:19:18 2012 UPGRADE FAILED - exiting.
    Now I'm running ZCS version 7.2.1. on RHEL6 with the /opt/zimbra/store folder that was in use during the failed upgrade procedure. Zimbra server works fine with this "store" folder, but there's no chance to successfully upgrade to version 8. Errors I get are the following:

    Sun Oct 7 10:25:27 2012 Checking ldap status...
    Sun Oct 7 10:25:27 2012 *** Running as zimbra user: /opt/zimbra/bin/ldap status
    Sun Oct 7 10:25:27 2012 not running.
    Sun Oct 7 10:25:27 2012 Starting ldap...
    Sun Oct 7 10:25:27 2012 *** Running as zimbra user: /opt/zimbra/bin/ldap start
    Failed to start slapd. Attempting debug start to determine error.
    50713c9c lt_dlopenext failed: (back_hdb.la) file not found
    50713c9c config error processing cn=module{0},cn=config: <olcModuleLoad> handler exited with 1

    Sun Oct 7 10:26:04 2012 failed with exit code: 256.
    Sun Oct 7 10:27:40 2012 UPGRADE FAILED - exiting.
    I don't know if the two are related - something happened during mysql upgrade, now I get errors when starting ldap during upgrade procedure. I don't know where to begin solving this issue. The command "sh -X /opt/zimbra/bin/ldap start" gives me the same error (tried running this command after the failed upgrade).

    BR,
    Damien

  2. #2
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    You need to modify your /opt/zimbra/.install_history file and remove all lines related to upgrading to 8.0, so that the 8.0 upgrade process can start from the beginning.
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  3. #3
    damjanster is offline Junior Member
    Join Date
    May 2009
    Posts
    8
    Rep Power
    6

    Default

    I cannot do this, since I have discarded the complete migration and started anew. I have been successful in migrating zimbra from RHEL5 to RHEL6 once again and using "store" folder that went through the failed upgrade process. The file /opt/zimbra/.install_history was erased during the "./install.sh -u" command (I have only moved the store folder to another location before running uninstall).

    I have then retried the upgrade process and it always fails with the second error mentioned in the original post.

  4. #4
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    The error you note *only* occurs if the installer detects that an 8.0 upgrade has already been attempted on the server at some point.
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  5. #5
    damjanster is offline Junior Member
    Join Date
    May 2009
    Posts
    8
    Rep Power
    6

    Default

    I understand. As I've mentioned I use the "store" folder that was active during the failed upgrade. Perhaps zimbra upgrade now sees that the schema got upgraded from the files in that folder. I don't know the inner relations of zimbra to know exactly what schema upgrade does and where. I can confirm that during the upgrade, zimbra checks for the version of schema and it finds version 90, not the origination 65 that's in use with ZCS 7.2.1.

    BR.

  6. #6
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    Hi,

    I'm sorry, but you do not understand. I will explain further. The error you are encountering only occurs if the installer detects a previous attempt at upgrading to 8.0 by reading the /opt/zimbra/.install_history file. That file tracks what version upgrades have been done and/or attempted. Part of that, is whether or not the LDAP upgrade steps necessary for going from any version less than 8 TO 8 have occurred. If it detects that the upgrade steps have already occurred, it will not run them again. And then you will hit the error that you have reported. So again, please fix your /opt/zimbra/.install_history file.

    --Quanah
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  7. #7
    damjanster is offline Junior Member
    Join Date
    May 2009
    Posts
    8
    Rep Power
    6

    Default

    Thank you for your help.
    I have corrected the file and will proceed with the upgrade ASAP.

    Will post result when I'm done.

  8. #8
    n3tz666 is offline Starter Member
    Join Date
    May 2013
    Posts
    1
    Rep Power
    2

    Default

    Hello, I have a similar problem this is the error:

    Fri May 10 01:50:33 2013: Verified schema version 90.
    ERROR 1054 (42S22) at line 1: Unknown column 'volume_id' in 'mail_item'
    Fri May 10 01:50:56 2013: Error while running '/ opt / zimbra / bin / mysql - user = zimbra - password = xxxxxxx - database = zimbra - batch - skip-column-names'.
    Script failed with code 256: - exiting
    UPGRADE FAILED - exiting.

    I tried to edit the file. install_history as recommended but not resolved what else can I try?

    I'm doing an update on

    7.1.3_GA_3346 NE to NE 8.0.3_GA_5664
    S.O. Ubuntu 10.04 LTS

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Zimbra-Upgrade and Server-Move inkl. Ubuntu-Dist-Upgrade
    By karl.kowald in forum Administrators
    Replies: 5
    Last Post: 10-25-2011, 10:24 AM
  2. Replies: 1
    Last Post: 09-17-2010, 04:14 PM
  3. Replies: 7
    Last Post: 02-15-2010, 08:55 PM
  4. 5.0.4 upgrade backup procedure; prevent new mail during upgrade?
    By adam.vollrath in forum Administrators
    Replies: 6
    Last Post: 04-11-2008, 07:51 AM
  5. Replies: 1
    Last Post: 01-03-2008, 11:58 AM

Tags for this Thread

Posting Permissions

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