Page 1 of 1

Error Upgrading from Zimbra 5.0.11 to Zimbra 5.0.12 OSS

Posted: Wed Jan 28, 2009 10:29 am
by jvsantosgt
Guys,
I'm having a problem upgrading Zimbra, below you will find the error.
An upgrade of the logger schema is necessary from version 0

Running /opt/zimbra/libexec/scripts/migrateLogger1-index.pl

Wed Jan 28 10:20:49 2009: Adding Indices

ERROR 1040 (08004): Too many connections

Running /opt/zimbra/libexec/scripts/migrateLogger2-config.pl

Wed Jan 28 10:20:51 2009: Adding Config

ERROR 1040 (08004): Too many connections

ERROR 1040 (08004): Too many connections

Running /opt/zimbra/libexec/scripts/migrateLogger3-diskindex.pl

ERROR 1040 (08004): Too many connections

Wed Jan 28 10:20:54 2009: Schema version mismatch. Expected version 2. Version in the database is 0.
Script failed with code 1 - exiting

UPGRADE FAILED - exiting
Is there anything that I can run to manually upgrade it.

Error Upgrading from Zimbra 5.0.11 to Zimbra 5.0.12 OSS

Posted: Wed Jan 28, 2009 10:35 am
by jholder
Looks like your logger db was corrupt before the upgrade started.
The quick and easy fix is to uninstall it (the logger)
If you're running RHEL or CentOS, then

rpm -qa | grep logger

get the name
rpm -e (name of the logger)

su - zimbra

zmprov ms `hostname` -zimbraServiceEnabled logger
Then rerun the installer. That'll get you upgraded. Note: You'll loose all your logger data...but my guess is that it hasn't been working for some time.

Error Upgrading from Zimbra 5.0.11 to Zimbra 5.0.12 OSS

Posted: Wed Jan 28, 2009 1:28 pm
by Service
I am getting the following errors trying to upgrade also and I have this is after the steps you supplied to fix, any other ideas?
Starting mysql

Starting logger mysql

ERROR 1040 (08004): Too many connections

This appears to be 5.0.11_GA

Redolog Version: 1.23 New Redolog Version: 1.23

Stopping mysql

An upgrade of the logger schema is necessary from version 0

Running /opt/zimbra/libexec/scripts/migrateLogger1-index.pl

Wed Jan 28 13:24:58 2009: Adding Indices

ERROR 1040 (08004): Too many connections

Running /opt/zimbra/libexec/scripts/migrateLogger2-config.pl

Wed Jan 28 13:25:00 2009: Adding Config

ERROR 1040 (08004): Too many connections

ERROR 1040 (08004): Too many connections

Running /opt/zimbra/libexec/scripts/migrateLogger3-diskindex.pl

ERROR 1040 (08004): Too many connections

Wed Jan 28 13:25:03 2009: Schema version mismatch. Expected version 2. Version in the database is 0.
Script failed with code 1 - exiting

UPGRADE FAILED - exiting

Error Upgrading from Zimbra 5.0.11 to Zimbra 5.0.12 OSS

Posted: Wed Jan 28, 2009 1:36 pm
by jholder
Did you uninstall the logger? It shouldn't try to upgrade a non-existent logger.

Error Upgrading from Zimbra 5.0.11 to Zimbra 5.0.12 OSS

Posted: Wed Jan 28, 2009 1:36 pm
by jholder
Run a ps aux | grep logger

kill any left over procs.

Error Upgrading from Zimbra 5.0.11 to Zimbra 5.0.12 OSS

Posted: Wed Jan 28, 2009 1:54 pm
by Service
OK, I removed the logger again using the commands you mentioned in note earlier and then upgraded and selected N on install logger question and upgrade completed fine and I am back up and running.
Now my question is how to I get the logger installed and working again?
Thanks for the help with this!

Error Upgrading from Zimbra 5.0.11 to Zimbra 5.0.12 OSS

Posted: Fri Jan 30, 2009 6:06 pm
by fabriccio_diaz
I got the same error, and follow the above steps and upgrade succesfully.
The only difference was that I selected Y on install logger question. Upgrade again with this in mind.
Hope this helps,

Error Upgrading from Zimbra 5.0.11 to Zimbra 5.0.12 OSS

Posted: Mon Feb 23, 2009 11:00 pm
by vidave
I also had the same problem - thanks much for the original post, jvsantosgt, and of course, thanks to jholder for the fix! :D
I've got several servers running, ALL but one of which lost zmlogger somewhere along the line, I think in 5.0.10.
After doing a "killall -9 zmlogger" and waiting for a few minutes, all the defunct processes died off and I was able to install/upgrade with zmlogger ON, and it seemed to have worked.
Looking forward to having logging again! Hopefully this time it won't get corrupted. :confused: