[SOLVED] Upgrade failing - 5.0.9->5.0.18

[Baylink]

This is what I get:

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

Shutting down zimbra mail

Backing up the ldap database...done.

Removing existing packages

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

Removing deployed webapp directories
Installing packages

    zimbra-core......zimbra-core-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done
    zimbra-ldap......zimbra-ldap-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done
    zimbra-logger......zimbra-logger-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done
    zimbra-mta......zimbra-mta-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done
    zimbra-snmp......zimbra-snmp-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done
    zimbra-store......zimbra-store-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done
    zimbra-apache......zimbra-apache-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done
    zimbra-spell......zimbra-spell-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done
    zimbra-archiving......zimbra-archiving-5.0.18_GA_3011.RHEL5-20090707151729.i386.rpm...done

Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
   HOSTNAME=benjamin.vicimarketing.com
   LDAPHOST=benjamin.vicimarketing.com
   LDAPPORT=389
   SNMPTRAPHOST=benjamin.vicimarketing.com
   SMTPSOURCE=admin@vicimarketing.com
   SMTPDEST=admin@vicimarketing.com
   SNMPNOTIFY=yes
   SMTPNOTIFY=yes
   LDAPROOTPW=Znp_fEfgty
   LDAPZIMBRAPW=Znp_fEfgty
   LDAPPOSTPW=Znp_fEfgty
   LDAPREPPW=Znp_fEfgty
   LDAPAMAVISPW=Znp_fEfgty
   LDAPNGINXPW=Znp_fEfgty
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.07112009-165657.log
Starting ldap...done.
Setting defaults...done.
Upgrading from 5.0.9_GA_2533 to 5.0.18_GA_3011
Stopping zimbra services
Stop failed - exiting
UPGRADE FAILED - exiting

and while starting the service does appear to bring up large chunks of the system, not all:

Jul 11 17:00:59 benjamin zmmailboxdmgr[32156]: status requested
Jul 11 17:00:59 benjamin zmmailboxdmgr[32156]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Jul 11 17:00:59 benjamin zmmailboxdmgr[32156]: assuming no other instance is running
Jul 11 17:00:59 benjamin zmmailboxdmgr[32156]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jul 11 17:00:59 benjamin zmmailboxdmgr[32156]: assuming no other instance is running
Jul 11 17:00:59 benjamin zmmailboxdmgr[32156]: no manager process is running

is what I see in the logs.

This is a machine that was moved, as 5.0.9NE, from one box to another using AJCody's rsync plan, and it came up ok on the new box on 5.0.9 first, and passed my tests.

If I rerun the upgrade, it says it's upgrading from 5.0.18 to 5.0.18...

Any go-to things to check, here?

[uxbod]

What does the install file say in /tmp ?

[Baylink]

Appreciably the same thing:

Sat Jul 11 16:56:57 2009 Operations logged to /tmp/zmsetup.07112009-165657.log
Sat Jul 11 16:56:57 2009 Getting installed packages
Sat Jul 11 16:56:58 2009 Getting local config zimbra_server_hostname
Sat Jul 11 16:56:58 2009 Getting local config ldap_url
Sat Jul 11 16:56:59 2009 zimbra_server_hostname contained in ldap_url checking ldap status
Sat Jul 11 16:56:59 2009 Checking ldap status.
Sat Jul 11 16:56:59 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
Sat Jul 11 16:56:59 2009 Starting ldap...
Sat Jul 11 16:56:59 2009 *** Running as zimbra user: /opt/zimbra/sleepycat/bin/db_recover -h /opt/zimbra/openldap-data
Sat Jul 11 16:56:59 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
Sat Jul 11 16:57:07 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
slapd running pid: 26075
Sat Jul 11 16:57:07 2009 done.
Sat Jul 11 16:57:07 2009 Getting installed services from ldap
Sat Jul 11 16:57:08 2009 checking isEnabled zimbra-core
Sat Jul 11 16:57:08 2009 zimbra-core not in enabled cache
Sat Jul 11 16:57:08 2009 enabled packages
Sat Jul 11 16:57:08 2009 zimbra_server_hostname contained in ldap_url checking ldap status
Sat Jul 11 16:57:08 2009 Checking ldap status.
Sat Jul 11 16:57:08 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
slapd running pid: 26075
Sat Jul 11 16:57:09 2009 slapd already running.
Sat Jul 11 16:57:09 2009 Getting enabled services from ldap
Sat Jul 11 16:57:11 2009 Marking zimbra-apache as installed. Services for zimbra-apache will be enabled.
Sat Jul 11 16:57:11 2009 Marking zimbra-archiving as disabled.
Sat Jul 11 16:57:12 2009 Setting defaults...
Sat Jul 11 16:57:12 2009 Setting local config zimbra_java_home to /opt/zimbra/java
Sat Jul 11 16:57:12 2009 *** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_java_home='/opt/zimbra/java' 2> /dev/null
Sat Jul 11 16:57:12 2009 checking isEnabled zimbra-cluster
Sat Jul 11 16:57:12 2009 zimbra-cluster not in enabled cache
Sat Jul 11 16:57:12 2009 enabled packages zimbra-logger zimbra-store zimbra-mta zimbra-core zimbra-archiving zimbra-apache zimbra-snmp zimbra-spell zimbra-ldap
Sat Jul 11 16:57:12 2009 zimbra_server_hostname contained in ldap_url checking ldap status
Sat Jul 11 16:57:12 2009 Checking ldap status.
Sat Jul 11 16:57:12 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
slapd running pid: 26075
Sat Jul 11 16:57:12 2009 slapd already running.
Sat Jul 11 16:57:12 2009 Getting enabled services from ldap
Sat Jul 11 16:57:15 2009 Marking zimbra-apache as installed. Services for zimbra-apache will be enabled.
Sat Jul 11 16:57:16 2009 checking isEnabled zimbra-store
Sat Jul 11 16:57:16 2009 zimbra-store is enabled
Sat Jul 11 16:57:16 2009 checking isEnabled zimbra-ldap
Sat Jul 11 16:57:16 2009 zimbra-ldap is enabled
Sat Jul 11 16:57:16 2009 checking isEnabled zimbra-store
Sat Jul 11 16:57:16 2009 zimbra-store is enabled
Sat Jul 11 16:57:16 2009 checking isEnabled zimbra-mta
Sat Jul 11 16:57:16 2009 zimbra-mta is enabled
Sat Jul 11 16:57:16 2009 done.
Sat Jul 11 16:57:16 2009 Upgrading from 5.0.9_GA_2533 to 5.0.18_GA_3011
Sat Jul 11 16:57:17 2009 Stopping zimbra services
Sat Jul 11 16:57:25 2009 Stop failed - exiting
Sat Jul 11 16:57:25 2009 UPGRADE FAILED - exiting

[uxbod]

Okay, what I would recommend is that you shutdown ZCS prior to performing the upgrade and ensure that all zimbra processes have indeed stopped. If they haven't then try killing them off nicely. Then perform the upgrade.

[veronica]

Well the upgrade process requires all the zimbra services to be up and running :-) . What is the error in install.log in /tmp directory ?

[phoenix]

Unless I'm misunderstanding you post I think you'll find that an upgrade can be run with all the Zimbra services stopped, it never has required them to be running.

[uxbod]

Indeed Phoenix ... The upgrade process will start SLAPD so that it can dump the current configuration, and will then start MySQL as required, especially to check the message store/logger integrity.

[veronica]

any of LDAP attribute assignment will never happen unless LDAP service is up and running. MYSQL service is anyhow taken up/down depending on what action is being performed internally in upgrade process.

[veronica]

Having said that i agree with uxbox that upgrade process will start LDAP service before any upgrade process.

[phoenix]

All the required services are started and stopped as needed by the install script, it's not necessary to have Zimbra running when you start the running the install - it never has been.