Results 1 to 10 of 17

Thread: Upgrade from 5.0.13 NE hangs

Hybrid View

  1. #1
    Join Date
    Dec 2008
    Location
    Orange County
    Posts
    65
    Rep Power
    7

    Default Upgrade from 5.0.13 NE hangs

    I have an old installation that I am trying to upgrade. I have Ubuntu 8.04 64bit and tried running the upgrade to both 6.x and 7.1.14 Both failed and hang at the starting mysql. I am working on a VMWare server so rolling back was quick and easy. My plan it to upgrade the install to 7.x then migrate to the appliance running on 8.x but I can't get off the ground.

    The 7.1.14 file was zcs-NETWORK-7.1.4_GA_2555.UBUNTU8_64.20120105094735


    This is what the log showed
    Code:
    Mon Sep 16 21:27:57 2013 done.
    Mon Sep 16 21:27:57 2013 Verifying /opt/zimbra/conf/my.cnf
    Mon Sep 16 21:27:57 2013 Getting local config zimbra_home
    Mon Sep 16 21:27:57 2013 Getting local config mysql_mycnf
    Mon Sep 16 21:27:58 2013 Getting local config zimbra_log_directory
    Mon Sep 16 21:27:58 2013 *** Running as zimbra user: /opt/zimbra/libexec/zminiutil --backup=.pre-7.1.4_GA --section=mysqld --key=ignore-builtin-innodb --set /opt/zimbra/conf/my.cnf
    Mon Sep 16 21:27:58 2013 *** Running as zimbra user: /opt/zimbra/libexec/zminiutil --backup=.pre-7.1.4_GA --section=mysqld --set --key=plugin-load --value='innodb=ha_innodb_plugin.so;innodb_trx=ha_innodb_plugin.so;innodb_locks=ha_innodb_plugin.so;innodb_lock_waits=ha_innodb_plugin.so;innodb_cmp=ha_innodb_plugin.so;innodb_cmp_reset=ha_innodb_plugin.so;innodb_cmpmem=ha_innodb_plugin.so;innodb_cmpmem_reset=ha_innodb_plugin.so' /opt/zimbra/conf/my.cnf
    Mon Sep 16 21:27:58 2013 *** Running as zimbra user: /opt/zimbra/libexec/zminiutil --backup=.pre-7.1.4_GA --section=mysqld --unset --key=log-long-format /opt/zimbra/conf/my.cnf
    Mon Sep 16 21:27:58 2013 *** Running as zimbra user: /opt/zimbra/libexec/zminiutil --backup=.pre-7.1.4_GA --section=mysqld --unset --key=log-slow-queries /opt/zimbra/conf/my.cnf
    Mon Sep 16 21:27:58 2013 *** Running as zimbra user: /opt/zimbra/libexec/zminiutil --backup=.pre-7.1.4_GA --section=mysqld --set --key=slow_query_log --value=1 /opt/zimbra/conf/my.cnf
    Mon Sep 16 21:27:58 2013 *** Running as zimbra user: /opt/zimbra/libexec/zminiutil --backup=.pre-7.1.4_GA --section=mysqld --set --key=slow_query_log_file --value=/opt/zimbra/log/myslow.log /opt/zimbra/conf/my.cnf
    Mon Sep 16 21:27:59 2013 Starting mysql...
    Mon Sep 16 21:27:59 2013 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
    Starting mysqld...done.
    Mon Sep 16 21:28:12 2013 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
    mysqld_safe already running with pid 9125
    Mon Sep 16 21:28:23 2013 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
    mysqld_safe already running with pid 9125
    That last line repeats lots.

    This is what the .install.sh shows
    Code:
    Removing deployed webapp directories
    Installing packages
    
        zimbra-core......zimbra-core_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-ldap......zimbra-ldap_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-logger......zimbra-logger_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-mta......zimbra-mta_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-snmp......zimbra-snmp_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-store......zimbra-store_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-apache......zimbra-apache_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-spell......zimbra-spell_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-convertd......zimbra-convertd_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-memcached......zimbra-memcached_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-proxy......zimbra-proxy_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
        zimbra-archiving......zimbra-archiving_7.1.4_GA_2555.UBUNTU8_64_amd64.deb...done
    
    Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
       HOSTNAME=mail2.dmrcom.com
       LDAPHOST=mail2.dmrcom.com
       LDAPPORT=389
       SNMPTRAPHOST=mail2.dmrcom.com
       SMTPSOURCE=admin@poboxdmr.com
       SMTPDEST=admin@poboxdmr.com
       SNMPNOTIFY=yes
       SMTPNOTIFY=yes
       LDAPROOTPW=zimbra
       LDAPZIMBRAPW=zimbra
       LDAPPOSTPW=zimbra
       LDAPREPPW=6kN8JFmF
       LDAPAMAVISPW=z1mbr4
       LDAPNGINXPW=6kN8JFmF
    Restoring existing configuration file from /opt/zimbra/.saveconfig/localconfig.xml...done
    Operations logged to /tmp/zmsetup.09162013-212754.log
    Installing LDAP configuration database...done.
    Upgrading from 5.0.13_GA_2791 to 7.1.4_GA_2555
    Stopping zimbra services...done.
    Verifying /opt/zimbra/conf/my.cnf
    Starting mysql...

    I then tried to start zimbra on its own using zmcontrol and ldap failed with an error about ldap, but my nslookups are correct and displayed below


    Code:
    zimbra@mail2:/tmp/zcs-NETWORK-7.1.4_GA_2555.UBUNTU8_64.20120105094735$ zmcontrol start
    Host mail2.dmrcom.com
            Starting ldap...Done.
    Unable to determine enabled services from ldap.
    Enabled services read from cache. Service list may be inaccurate.
            Starting zmconfigd...
    
    Done.
            Starting logger...Failed.
    Starting logswatch...ERROR: service.FAILURE (system failure: unable to lookup server by name: mail2.dmrcom.com message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    zimbra logger service is not enabled!  failed.
    
    
            Starting mailbox...Done.
            Starting antispam...Done.
            Starting antivirus...Done.
            Starting snmp...Done.
            Starting spell...Done.
            Starting mta...
    
    zmcontrol status
    Unable to determine enabled services from ldap.
    Enabled services read from cache. Service list may be inaccurate.
    Host mail2.dmrcom.com
            antispam                Stopped
                    zmamavisdctl is not running
            antivirus               Stopped
                    zmamavisdctl is not running
            ldap                    Running
            logger                  Stopped
                    zmlogswatchctl is not running
            mailbox                 Stopped
                    mysql.server is not running.
                    zmmailboxdctl is not running.
            mta                     Stopped
                    zmsaslauthdctl is not running
            snmp                    Running
            spell                   Running
            stats                   Stopped
            zmconfigd               Running
    zimbra@mail2:/tmp/zcs-NETWORK-7.1.4_GA_2555.UBUNTU8_64.20120105094735$ nslookup mail2.dmrcom.com
    Server:         69.28.108.8
    Address:        69.28.108.8#53
    
    Name:   mail2.dmrcom.com
    Address: 199.21.152.6
    
    zimbra@mail2:/tmp/zcs-NETWORK-7.1.4_GA_2555.UBUNTU8_64.20120105094735$ nslookup 199.21.152.6
    Server:         69.28.108.8
    Address:        69.28.108.8#53
    
    6.152.21.199.in-addr.arpa       name = mail2.dmrcom.com.
    
    zimbra@mail2:/tmp/zcs-NETWORK-7.1.4_GA_2555.UBUNTU8_64.20120105094735$ ifconfig
    bond0     Link encap:Ethernet  HWaddr 00:30:48:d4:e6:e0
              inet addr:199.21.152.6  Bcast:199.21.152.255  Mask:255.255.255.0
              inet6 addr: fe80::230:48ff:fed4:e6e0/64 Scope:Link
              UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
              RX packets:11599348097 errors:0 dropped:0 overruns:0 frame:0
              TX packets:4369701994 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:904872652237 (842.7 GB)  TX bytes:17815363811641 (16.2 TB)

  2. #2
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,285
    Rep Power
    10

    Default

    Why would you upgrade to 7.1.4, which is utterly ancient?

    Also, it appears you broke your localconfig.xml file so you lost all your ldap passwords...
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  3. #3
    Join Date
    Dec 2008
    Location
    Orange County
    Posts
    65
    Rep Power
    7

    Default

    Quote Originally Posted by quanah View Post
    Why would you upgrade to 7.1.4, which is utterly ancient?

    Also, it appears you broke your localconfig.xml file so you lost all your ldap passwords...
    I am going to 7.1.4 because per the release notes that is the highest version I can go to from the 5.x that I am currently on. Also the 8.x code says that it can not migrate data from 5.x and I will need to upgrade to something in the 7. range. My server runs Ubuntu 8.4 and I will not be able to install 8.x on it. I already have a zm 8.x appliance up and running ready to do a data migration once I move up

    After I ran the upgrade I checked the localconfig.xml file and there were things in it, It looked correct to me.

    I have never had a successful upgrade on zimbra. which is why I have not upgraded in a long time. All 3 upgrades, including minor patches have disabled my server for nearly a day each time.

  4. #4
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,285
    Rep Power
    10

    Default

    hm, I can't tell where in that sequence you ran zmcontrol start. Based on what you pasted, it would appear you ran it while the upgrade process was still running, which could well fail and break things to boot. I'm not really sure what your nslookup bits are about, nothing says DNS is failing, it says LDAP isn't running, which is probably expected given the significant modifications to the LDAP server made when going from ZCS5 to any later release. It is common for the upgrade process to start and stop specific processes multiple times during the upgrade process as well.

    Personally, I would go to ZCS6.latest and then ZCS7.latest rather than 5 -> 7.
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  5. #5
    Join Date
    Dec 2008
    Location
    Orange County
    Posts
    65
    Rep Power
    7

    Default

    Quote Originally Posted by quanah View Post
    hm, I can't tell where in that sequence you ran zmcontrol start. Based on what you pasted, it would appear you ran it while the upgrade process was still running, which could well fail and break things to boot. I'm not really sure what your nslookup bits are about, nothing says DNS is failing, it says LDAP isn't running, which is probably expected given the significant modifications to the LDAP server made when going from ZCS5 to any later release. It is common for the upgrade process to start and stop specific processes multiple times during the upgrade process as well.

    Personally, I would go to ZCS6.latest and then ZCS7.latest rather than 5 -> 7.

    I also tried going to the latest 6.x and got similar results, however I did not capture any logs. I put the nslookup parts because the ldap start error
    Code:
    Starting logswatch...ERROR: service.FAILURE (system failure: unable to lookup server by name: mail2.dmrcom.com message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    zimbra logger service is not enabled!  failed.

    The output of install.sh hung after the line Starting mysql... I waited 32 minutes before looking at the logs and killing the install.


    The staring mysql was in the logs several hundred times so I killed the install.sh after seeing many instances of this line
    Code:
    Mon Sep 16 21:27:59 2013 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
    Starting mysqld...done.
    Mon Sep 16 21:28:12 2013 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
    mysqld_safe already running with pid 9125
    Mon Sep 16 21:28:23 2013 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
    mysqld_safe already running with pid 9125

    Tonight I will try first going to
    zcs-NETWORK-5.0.25_GA_3360.UBUNTU8_64.20101110192742.tgz

    Then upgrading to
    zcs-NETWORK-6.0.16_GA_2998.UBUNTU8_64.20120404131657.tgz

    annd finally to
    zcs-NETWORK-7.1.4_GA_2555.UBUNTU8_64.20120105094735.tgz


    If I get there I will then start reading documentation on how to migrate data to the 8.x server I brought up on a new ip.

  6. #6
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,285
    Rep Power
    10

    Default

    Ok, best of luck. :/

    I will note again the ldap error doesn't indicate ldap wasn't running. In fact, it indicates LDAP *was* running. If ldap was not running, you would get an error code of -1, not 49. 49 means the password is invalid. The password is obtained from localconfig.xml.

    One problem may be that because you've run the upgrade before, that your .install_history contains data indicating that some upgrade steps have occurred when they actually haven't. That could break future upgrades.

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

Similar Threads

  1. zcs 5.0.9 to zcs 7.1.0 upgrade hangs
    By pnunn in forum Administrators
    Replies: 1
    Last Post: 05-10-2011, 01:41 PM
  2. zcs 5.0.9 to zcs 7.1.0 upgrade hangs
    By pnunn in forum Installation
    Replies: 0
    Last Post: 04-04-2011, 06:26 PM
  3. zmsetup.pl hangs in upgrade from 6.0.3 to 6.0.10
    By snorris09 in forum Administrators
    Replies: 0
    Last Post: 12-30-2010, 11:33 AM
  4. zmsetup.pl hangs in upgrade from 6.0.3 to 6.0.10
    By snorris09 in forum Installation
    Replies: 0
    Last Post: 12-30-2010, 11:33 AM
  5. [SOLVED] 5.0.23 upgrade hangs
    By aner in forum Installation
    Replies: 2
    Last Post: 04-08-2010, 11:14 PM

Posting Permissions

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