Results 1 to 5 of 5

Thread: Script faield upgrading from 3.0.0_M2_746 to 3.1.0_GA_332

  1. #1
    Join Date
    Sep 2005
    Posts
    8
    Rep Power
    10

    Default Script failed upgrading from 3.0.0_M2_746 to 3.1.0_GA_332

    While upgrading, I got an error on the migrate.pm script. It looks like the schema changes failed. How do I recover/complete the installation?

    TIA,
    Michael.


    [root@mail zcs]# ./install.sh

    Operations logged to /tmp/install.log.1840
    Checking for existing installation...
    zimbra-ldap...FOUND zimbra-ldap-3.0.0_M2_746
    zimbra-logger...FOUND zimbra-logger-3.0.0_M2_746
    zimbra-mta...FOUND zimbra-mta-3.0.0_M2_746
    zimbra-snmp...FOUND zimbra-snmp-3.0.0_M2_746
    zimbra-store...FOUND zimbra-store-3.0.0_M2_746
    zimbra-apache...FOUND zimbra-apache-3.0.0_M2_746
    zimbra-spell...FOUND zimbra-spell-3.0.0_M2_746
    zimbra-core...FOUND zimbra-core-3.0.0_M2_746

    Saving existing configuration file to /opt/zimbra/.saveconfig


    PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE SOFTWARE.
    ZIMBRA, INC. ("ZIMBRA") WILL ONLY LICENSE THIS SOFTWARE TO YOU IF YOU
    FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY DOWNLOADING OR INSTALLING
    THE SOFTWARE, OR USING THE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY
    THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS
    AGREEMENT, THEN DO NOT DOWNLOAD, INSTALL OR USE THE PRODUCT.

    License Terms for the Zimbra Collaboration Suite:
    http://www.zimbra.com/license/collab...cense_1.0.html


    Press Return to continue

    Checking for prerequisites...
    NPTL...FOUND
    sudo...FOUND sudo-1.6.8p8-2.3
    libidn...FOUND libidn-0.5.15-1
    curl...FOUND curl-7.13.1-3
    fetchmail...FOUND fetchmail-6.2.5-7
    gmp...FOUND gmp-4.1.4-6
    /usr/lib/libstdc++.so.5...FOUND

    Checking for installable packages

    Found zimbra-core
    Found zimbra-ldap
    Found zimbra-logger
    Found zimbra-mta
    Found zimbra-snmp
    Found zimbra-store
    Found zimbra-apache
    Found zimbra-spell


    The Zimbra Collaboration Suite appears already to be installed.
    It can be upgraded with no effect on existing accounts,
    or the current installation can be completely removed prior
    to installation for a clean install.

    Do you wish to upgrade? [Y] Y

    Select the packages to install
    Upgrading zimbra-core
    Upgrading zimbra-ldap
    Upgrading zimbra-logger
    Upgrading zimbra-mta
    Upgrading zimbra-snmp
    Upgrading zimbra-store
    Upgrading zimbra-apache
    Upgrading zimbra-spell

    Installing:
    zimbra-core
    zimbra-ldap
    zimbra-logger
    zimbra-mta
    zimbra-snmp
    zimbra-store
    zimbra-apache
    zimbra-spell

    The system will be modified. Continue? [N] Y

    Shutting down zimbra mail

    Backing up ldap


    Removing existing packages

    zimbra-ldap...done
    zimbra-logger...done
    zimbra-mta...done
    zimbra-snmp...done
    zimbra-store...done
    zimbra-spell...done
    zimbra-apache...done
    zimbra-core...done

    Removing deployed webapp directories
    Installing packages

    zimbra-core......zimbra-core-3.1.0_GA_332.FC4-20060414123554.i386.rpm...done
    zimbra-ldap......zimbra-ldap-3.1.0_GA_332.FC4-20060414123554.i386.rpm...done
    zimbra-logger......zimbra-logger-3.1.0_GA_332.FC4-20060414123554.i386.rpm...done
    zimbra-mta......zimbra-mta-3.1.0_GA_332.FC4-20060414123554.i386.rpm...done
    zimbra-snmp......zimbra-snmp-3.1.0_GA_332.FC4-20060414123554.i386.rpm...done
    zimbra-store......zimbra-store-3.1.0_GA_332.FC4-20060414123554.i386.rpm...done
    zimbra-apache......zimbra-apache-3.1.0_GA_332.FC4-20060414123554.i386.rpm...done
    zimbra-spell......zimbra-spell-3.1.0_GA_332.FC4-20060414123554.i386.rpm...done

    Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
    HOSTNAME=mail.k12sa.net
    LDAPHOST=mail.k12sa.net
    LDAPPORT=389
    SNMPTRAPHOST=mail.k12sa.net
    SMTPSOURCE=admin@mail.k12sa.net
    SMTPDEST=admin@mail.k12sa.net
    SNMPNOTIFY=yes
    SMTPNOTIFY=yes
    LDAPROOTPW=pAwO4SWRbdfntJ_jWDGAY21hgwrE
    LDAPZIMBRAPW=GIiq46vjtH7MwN8wdSeUott9E
    Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
    Operations logged to /tmp/zmsetup.log.6915
    Setting defaults...Setting defaults from existing config...Done
    Upgrading from 3.0.0_M2_746 to 3.1.0_GA_332
    Tue Apr 25 11:34:55 2006: Stopping zimbra services
    Tue Apr 25 11:34:58 2006: Checking mysql status
    Tue Apr 25 11:34:58 2006: Starting mysql
    Tue Apr 25 11:34:59 2006: SELECT value FROM config WHERE name = 'db.version'
    Tue Apr 25 11:34:59 2006: Checking logger mysql status
    Tue Apr 25 11:35:00 2006: Starting logger mysql
    This appears to be 3.0.0_M2
    Schema upgrade required
    Tue Apr 25 11:35:00 2006: Running /opt/zimbra/libexec/scripts/migrate20051021-UniqueVolume.pl
    Tue Apr 25 11:35:01 2006: SELECT value FROM config WHERE name = 'db.version'
    Tue Apr 25 11:35:02 2006: Verified schema version 21.
    Tue Apr 25 11:35:02 2006: Updating volume table
    Tue Apr 25 11:35:02 2006: ALTER TABLE volume
    ADD UNIQUE i_name (name),
    ADD UNIQUE i_path (path(255));


    ERROR 1061 (42000) at line 1: Duplicate key name 'i_name'
    Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=W69q8p8QSaBXjdSXB__eZ6DUxrPi --database=zimbra --batch --skip-column-names'. at /opt/zimbra/libexec/scripts/Migrate.pm line 134, line 1.
    Tue Apr 25 11:35:02 2006: Script failed with code 1 - exiting
    UPGRADE FAILED - exiting
    [root@mail zcs]#
    Last edited by michaeleq; 04-25-2006 at 03:08 PM.
    Michael Quattlebaum
    q@interdirected.com

  2. #2
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    The easiest way will be to go back to your backup, remove the duplicate path (i_name) in the Volume table and then try the upgrade again.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  3. #3
    Join Date
    Sep 2005
    Posts
    8
    Rep Power
    10

    Default

    I don't understand what you mean. What went wrong to begin with? What ensures that when I restore to backup that I won't have the same problem again?
    Michael Quattlebaum
    q@interdirected.com

  4. #4
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    >ERROR 1061 (42000) at line 1: Duplicate key name 'i_name'

    There is a duplicate value in a table we are trying to add a unique index for. So restoring from backup and fixing the column to have no duplicates should let the upgrade continue the next time.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  5. #5
    Join Date
    Dec 2005
    Posts
    44
    Rep Power
    10

Similar Threads

  1. Replies: 210
    Last Post: 01-17-2012, 01:19 AM
  2. Error when upgrading from 3.1 -> 3.1.1
    By jeg1972 in forum Installation
    Replies: 2
    Last Post: 05-10-2006, 07: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
  •