[SOLVED] Upgrade to 6.0.4 hangs: Starting mysql...

[faizel]

I try to upgrade an 6.0.2 installation to 6.04, but it fails with 'Starting mysql...'
The zmsetup.log says:

Tue Jan 5 21:06:18 2010 Verifying /opt/zimbra/conf/my.cnf
Tue Jan 5 21:06:19 2010 Starting mysql...
Tue Jan 5 21:06:19 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
Starting mysqld...done.
Tue Jan 5 21:06:31 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:06:42 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:06:54 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:07:05 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:07:17 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:07:29 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:07:41 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:07:52 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:08:04 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:08:16 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:08:28 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:08:40 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832
Tue Jan 5 21:08:52 2010 *** Running as zimbra user: /opt/zimbra/bin/mysql.server start
mysqld_safe already running with pid 8832

It appears that the installer is unable to detect that it has started mysql.
Anyone knows how to proceed ?

[LMStone]

We've done a slew of 6.0.4 upgrades in the past few weeks on our own systems and on a number of clients' systems.

We too see that the 6.0.4 installer doesn't always "get" that mysql is running.

On one upgrade, we ran the installer after we had issued a zmcontrol stop.

The installer launched MySQL to run the mailbox database integrity check, but borked trying to run the logger database check. MySQL was already running and the logger database check was trying to start another instance of MySQL.

So, we hit "CTRL-C" to kill the Zimbra installer, ran it again and just skipped doing the mailbox database check. This time, the logger database check completed OK, but the installer hung again at the next point where it wanted to launch MySQL.

Once again, we hit "CTRL-C" to kill the installer, then ran it again--this time skipping both the mailbox and logger database checks. The installer completed successfully this time with no issues, and the upgrade results were fine.

Hope that helps,
Mark

[faizel]

Mark, thanks for your extensive reply. I already tried to skip the integrity check, but no results here. Then i thought that the installer maybe wants to log in into the database. After searching for the password i noticed that the localconfig.xml in /opt/zimbra/conf was almost empty somehow. I replaced this file with a -correct- previous version from /opt/zimbra/.saveconfig and this time the installer proceeded.

[FlyingFish]

It looks to be a bug in the installer. The localconfig.xml gets blanked out under certain conditions. For me, I accidentally hit CTRL-C during the upgrade it appears after the package removal and before the zimbra-core .rpm was fully installed, and it went all to hell from there. Based on what you tried, I grabbed a previous version localconfig.xml and restored it. It solved my issues as well.

[rmvg]

Thanks for the post my localconfig.xml got blanked as well by pressing ctrl ^ c at the wrong time too. Replaced it with a backup and all seem well, however the upgrade did complain about not being able to determine how many users i had. Warning me about how if it exceeded my license i would not be able to add any.

Anyways thank