[SOLVED] 4.5.9 to 4.5.10 ubuntu upgrade failed (os)

[jeffw]

I'm trying to upgrade my open source version at home and the upgrade failed. Any ideas of where I should go next?

*****

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]

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
Checking required space for zimbra-core
checking space for zimbra-store

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

./install.sh: line 148: /opt/zimbra/.install_history: No such file or directory
zimbra-core......zimbra-core_4.5.10_GA_1575.UBUNTU6_i386.deb...done
zimbra-ldap......zimbra-ldap_4.5.10_GA_1575.UBUNTU6_i386.deb...done
zimbra-logger......zimbra-logger_4.5.10_GA_1575.UBUNTU6_i386.deb...done
zimbra-mta......zimbra-mta_4.5.10_GA_1575.UBUNTU6_i386.deb...done
zimbra-snmp......zimbra-snmp_4.5.10_GA_1575.UBUNTU6_i386.deb...done
zimbra-store......zimbra-store_4.5.10_GA_1575.UBUNTU6_i386.deb...done
zimbra-apache......zimbra-apache_4.5.10_GA_1575.UBUNTU6_i386.deb...done
zimbra-spell......zimbra-spell_4.5.10_GA_1575.UBUNTU6_i386.deb...done
Restoring existing configuration file from ..../util/utilfunc.sh: line 816: $RF: ambiguous redirect
done
chown: cannot access `/opt/zimbra/tomcat/conf/keystore': No such file or directory
chown: cannot access `/opt/zimbra/conf/smtpd.key': No such file or directory
chown: cannot access `/opt/zimbra/conf/smtpd.crt': No such file or directory
chown: cannot access `/opt/zimbra/conf/slapd.crt': No such file or directory
chown: cannot access `/opt/zimbra/conf/perdition.pem': No such file or directory
chown: cannot access `/opt/zimbra/conf/perdition.key': No such file or directory
Operations logged to /tmp/zmsetup.log.26217
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
Setting defaults...Done
Setting defaults from existing config...Warning: null valued key 'mysql_logger_root_password'
Upgrading from to 4.5.10_GA_1575
Stopping zimbra services
Stop failed - exiting
UPGRADE FAILED - exiting

[mmorse]

Hey jeff,
Could you attach your zmsetup.log
(usually /tmp/zmsetup.log.####)

[jeffw]

Is it weird that it says "Upgrading from to 4.5.10_GA_1575" ?


Here it is:


Getting installed packages
Getting local config zimbra_server_hostname
Getting local config ldap_url
zimbra_server_hostname not in ldap_url not starting slapd
Getting installed services from ldap
checking isEnabled zimbra-core
zimbra-core not in enabled cache
enabled packages
Getting local config ldap_url
zimbra_server_hostname not in ldap_url not starting slapd
Getting enabled services from ldap
Marking zimbra-core as installed. Services for zimbra-core will be enabled.
Marking zimbra-ldap as installed. Services for zimbra-ldap will be enabled.
Marking zimbra-store as installed. Services for zimbra-store will be enabled.
Marking zimbra-mta as installed. Services for zimbra-mta will be enabled.
Marking zimbra-snmp as installed. Services for zimbra-snmp will be enabled.
Marking zimbra-logger as installed. Services for zimbra-logger will be enabled.
Marking zimbra-apache as installed. Services for zimbra-apache will be enabled.
Marking zimbra-spell as installed. Services for zimbra-spell will be enabled.
Setting defaults...
Setting local config zimbra_java_home to /opt/zimbra/java
*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_java_home='/opt/zimbra/java'
checking isEnabled zimbra-store
zimbra-store is enabled
checking isEnabled zimbra-ldap
zimbra-ldap is enabled
checking isEnabled zimbra-store
zimbra-store is enabled
Done
Setting defaults from existing config...
Getting local config zimbra_server_hostname
Getting local config ldap_master_url
Getting local config ldap_port
Getting local config ldap_host
Getting local config ldap_root_password
Getting local config mysql_root_password
Getting local config mysql_logger_root_password
Getting local config zimbra_mysql_password
Getting local config zimbra_logger_mysql_password
Getting local config tomcat_java_heap_memory_percent
Getting local config mysql_memory_percent
Getting local config tomcat_keystore_password
Getting local config tomcat_keystore_password
Getting local config tomcat_truststore_password
Getting local config tomcat_truststore_password
Upgrading from to 4.5.10_GA_1575
Stopping zimbra services
Stop failed - exiting
UPGRADE FAILED - exiting

[jholder]

Do you have a backup? If so, restore to that.

This is a case of multiple failed installs. Your very first install failed, and localconfig.xml was wiped. You reinstalled, and you have the:

Warning: null valued key 'mysql_logger_root_password'

Which indicates the value is null for the localconfig.

Now the installer is plain screwy.

We really should find out why it failed to begin with.

[jeffw]

Originally Posted by jholder

Do you have a backup? If so, restore to that.

This is a case of multiple failed installs. Your very first install failed, and localconfig.xml was wiped. You reinstalled, and you have the:

Warning: null valued key 'mysql_logger_root_password'

Which indicates the value is null for the localconfig.

Now the installer is plain screwy.

We really should find out why it failed to begin with.

It looks like the installer doesn't like /opt/zimbra to be a symlink (it was a symlink to /home/opt/zimbra). During the install it blew away the symlink and reinstalled there.

mmorse is on the box looking around.

[jeffw]

we reconfigured so that /opt was a symlink to /home/opt and the installer replaced /opt with a directory and reinstalled in /opt/zimbra.

[mmorse]

It broke the symlink because it thought it was a new install and therefore created a new dir - we'll see if we can investigate why

He's a NE customer (tufts.edu) and this is kinda his home testbox; even with nothing 100% cirtical on it we'll still get it .9>.10 perfectly fine/ok/won't loose a thing of his testing accounts. (a regular mount will solve it)

He had made a tar backup while there we're still plenty of zimbra processes running (instead of an rsync etc) so we're just finishing up on getting that that 4.5.9 backup restored and running.

! > Open Source Edition Backup Procedure - Zimbra :: Wiki

A couple of months back there was a cluster install case Bug 17032 - clarify cluster mountpoint symlink behavior
Bug 17891 - New-style cluster install: put zimbra home on shared disk

[jeffw]

We changed /opt to be a loopback/bind mount using:

/home/opt /opt none bind

in fstab, and that allowed the upgrade to work just fine. It's now running 4.5.10 just fine (special thanks to mmorse for his help!).

It seems that there's something wonky in the installer that can't deal with /opt or /opt/zimbra being a symlink.

I opened a bug: Bug 22104 - if /opt or /opt/zimbra is a symlink, upgrade will fail