Upgrade 3.1.3 to 4.0.3 -FAILED

[rrojas]

Two Weeks ago, i've tried to make this upgrade , but it's fails.... That's what i made;

In my Zimbra Store server (Zimbra version 3.1.3)

1.- Shut Down Zimbra Services
2.- Backup /opt/zimbra, /mailbox (here is store, db, log, logger)
3.- Run 4.0.2 installer and got this error message:

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

Install zimbra-mta [Y] N
    Upgrading zimbra-snmp
    Upgrading zimbra-store
    Upgrading zimbra-apache
    Upgrading zimbra-spell

Installing:
    zimbra-core
    zimbra-ldap
    zimbra-logger
    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-snmp...done
   zimbra-store...done
   zimbra-spell...done
   zimbra-apache...done
   zimbra-core...done

Removing deployed webapp directories
Installing packages

  zimbra-core......zimbra-core-4.0.2_GA_362.RHEL4-20060924201056.i386.rpm...done
    zimbra-ldap......zimbra-ldap-4.0.2_GA_362.RHEL4-20060924201056.i386.rpm...done
    zimbra-logger......zimbra-logger-4.0.2_GA_362.RHEL4-20060924201056.i386.rpm...done
    zimbra-snmp......zimbra-snmp-4.0.2_GA_362.RHEL4-20060924201056.i386.rpm...done
    zimbra-store......zimbra-store-4.0.2_GA_362.RHEL4-20060924201056.i386.rpm...done
    zimbra-apache......zimbra-apache-4.0.2_GA_362.RHEL4-20060924201056.i386.rpm...done
    zimbra-spell......zimbra-spell-4.0.2_GA_362.RHEL4-20060924201056.i386.rpm...done

Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
   HOSTNAME=canelo.midomimio.cl
   LDAPHOST=
   LDAPPORT=
   SNMPTRAPHOST=canelo.midomimio.cl
   SMTPSOURCE=admin@midomimio.cl
   SMTPDEST=admin@midomimio.cl
   SNMPNOTIFY=yes
   SMTPNOTIFY=yes
   LDAPROOTPW=ZZZZZZ
   LDAPZIMBRAPW=ZZZZZ
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
chown: no se puede acceder a «/opt/zimbra/conf/smtpd.key»: No existe el fichero o el directorio
chown: no se puede acceder a «/opt/zimbra/conf/smtpd.crt»: No existe el fichero o el directorio
Operations logged to /tmp/zmsetup.log.23794
Setting defaults...Setting defaults from existing config...Done
Upgrading from 3.1.3_GA_474 to 4.0.2_GA_362
Sat May 12 14:25:45 2007: Stopping zimbra services
Sat May 12 14:25:50 2007: Starting mysql
UPGRADE FAILED - exiting

After that i've tried to start the server but it does not start:

[root@canelo zcs]# su - zimbra
[zimbra@canelo ~]$ zmcontrol status
Cannot determine services - exiting
[zimbra@canelo ~]$ zmcontrol start 
Host canelo.conaf.cl
        Starting ldap...Done.
        Starting logger...Done.
        Starting mailbox...Done.
        Starting snmp...Done.
        Starting spell...Done.
[zimbra@canelo ~]$ zmcontrol status 
Host canelo.conaf.cl
        ldap                    Running
        logger                  Stopped
                logmysql.server is not running
                zmlogswatchctl is not running
        mailbox                 Stopped
                mysql.server is not running
        snmp                    Running
        spell                   Running

After Hours triying to fix this, i downloaded the backup and i got the same errors, so , i have rebuild the logger mysql db and add the following line in sudo config (visudo), because, when i run zmcontrol start, its promt for a password:

root ALL=(ALL) ALL

[jholder]

Looks like the mysql password was out of sync when the installer was started.
I'm happy you had a backup. You should restore, then reset all the the passwords (LDAP, MYSQL, and Logger) before running the upgrade.

The instructions for how to do this can be found here:
http://wiki.zimbra.com/index.php?tit...ySQL_Passwords

Good luck, and let us know if you need help
john

[rrojas]

I've already restored my system. What can be the reason for its fails (passwords sync)?

Looks like the mysql password was out of sync when the installer was started.
I'm happy you had a backup. You should restore, then reset all the the passwords (LDAP, MYSQL, and Logger) before running the upgrade.

The instructions for how to do this can be found here:
http://wiki.zimbra.com/index.php?tit...ySQL_Passwords

Good luck, and let us know if you need help
john

[jholder]

Various reasons. It's something that we have improved upon in latter versions.

Make sure that you reset those passwords, then do the upgrade.

[rrojas]

I've tried to make de upgrade again , following your recomendations but it's fails again.

The frist thing that i made (after backup) was reset the ldap password, mysql-logger password and mysql paswords. In this step the ldap password was not works, i check the localconfig.xml and the password are the same that i got when i run zmlocalconfig -s. So, i have to add the %zimbra ALL=(ALL) ALL line un sudo config to get the ldap started. After that i tried to run the 4.0.2 zimbra intaller but it's fails again:

Setting defaults...
Setting defaults from existing config...
Getting local config zimbra_server_hostname

Getting local config ldap_url

Getting local config ldap_port

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

Done

Upgrading from 3.1.3_GA_474 to 4.0.2_GA_362

UPGRADE FAILED - exiting

I'ts seem to be a problem with the mysql initialization problem. I think it is possible because i moved some directories from /opt/zimbra to another location the i made symbolic links, that's for disk space problems:

db -> /mailbox/db/
index -> /mailbox/index/
log -> /mailbox/respaldo/log
logger -> /mailbox/respaldo/logger/
store -> /mailbox/store/


Any suggestions