<4.5.2 Upgrade Notice

[jholder]

It has been discovered that due to a MySQL bug (#23669), that an upgrade from 4.0.4 or higher can fail when you upgrade to 4.5.

It appears that somewhere during the upgrade, that the proc table can disappear. Because the installer script takes a look at the table, it will fail when it doesn't find it.

We believe that this will only affect users that did their initial install withZCS 4.0.4 or greater and may affect customers regardless of platform.

We are currently investigating a workaround, and when it is ready, we will post it here. Additionally, we will include this in future release notes.

Additional information can be found here: http://bugzilla.zimbra.com/show_bug.cgi?id=14146

Thanks to Brian and Sean who helped us track this down!

This thread will be updated/edited as needed.

[jholder]

For those users concerned with their current installs, please be aware that this only affects upgrades.

We have a workaround for this problem. This work around should be done *PRIOR* to the 4.5 upgrade.

Log in as the zimbra user.

mysql -f -Dmysql -u root --password=`zmlocalconfig -s -m nokey
mysql_root_password` < /opt/zimbra/mysql/share/mysql/mysql_fix_privilege_tables.sql 

After that finishes, execute the following and make sure you have an entry for "proc"

mysql -f -Dmysql -u root --password=`zmlocalconfig -s -m nokey

We plan on automating the above check script on the 4.5.2 release. It will also be included in the release notes.

As always, we encourage our users to keep current backups of their system on a regular basis. . .even if its just a copy.

[jholder]

If you have any problems with the upgrade in relation to the proc table mysql bug, please post them here.

[easytouch]

Initial installation was a zcs-4.0.4_GA_457.FC4.tgz on Fedora Core 4.

I tried the workaround on zcs-4.0.4_GA_457.FC4.tgz (OS Version on Fedora Core4)
then I upgraded to zcs-4.0.5_GA_518.FC4.tgz (OS Version on Fedora Core4)
and tried again.

Both times the following results, and I see no proc table after running the .sql.
So I am unsure if i should try the Upgrade to zcs-4.5.0_GA_612.FC4.tgz?
What else can I try to create the proc table as needed, or patch the 4.5.0 install scripts?

step 1 list tables
[root@aws]$ su zimbra
[zimbra@aws]$ zmlocalconfig -s | grep mysql (to fetch the mysql root-password ********)
[zimbra@aws]$ mysql -f -Dmysql -u root --password=******** -e "show tables"

+---------------------------+
| Tables_in_mysql           |
+---------------------------+
| columns_priv              |
| db                        |
| func                      |
| help_category             |
| help_keyword              |
| help_relation             |
| help_topic                |
| host                      |
| tables_priv               |
| time_zone                 |
| time_zone_leap_second     |
| time_zone_name            |
| time_zone_transition      |
| time_zone_transition_type |
| user                      |
+---------------------------+

step 2 run .sql
[zimbra@aws]$ mysql -f -Dmysql -u root --password=************ < /opt/zimbra/mysql/share/mysql/mysql_fix_privilege_tables.sql

ERROR 1060 (42S21) at line 22: Duplicate column name 'File_priv'
@hadGrantPriv:=1
1
1
1
1
1
1
1
1
ERROR 1060 (42S21) at line 28: Duplicate column name 'Grant_priv'
ERROR 1060 (42S21) at line 29: Duplicate column name 'Grant_priv'
ERROR 1060 (42S21) at line 30: Duplicate column name 'Grant_priv'
ERROR 1060 (42S21) at line 41: Duplicate column name 'ssl_type'
ERROR 1054 (42S22) at line 87: Unknown column 'Type' in 'columns_priv'
ERROR 1060 (42S21) at line 93: Duplicate column name 'type'
@hadShowDbPriv:=1
1
1
1
1
1
1
1
1
ERROR 1060 (42S21) at line 103: Duplicate column name 'Show_db_priv'
ERROR 1060 (42S21) at line 120: Duplicate column name 'max_questions'
ERROR 1060 (42S21) at line 130: Duplicate column name 'Create_tmp_table_priv'
ERROR 1060 (42S21) at line 133: Duplicate column name 'Create_tmp_table_priv'
ERROR 1061 (42000) at line 141: Duplicate key name 'Grantor'

step 3 list tables again - brings the sameresult as in step 1 - no proc table
[zimbra@aws]$mysql -f -Dmysql -u root --password=***** -e "show tables"

+---------------------------+
| Tables_in_mysql           |
+---------------------------+
| columns_priv              |
| db                        |
| func                      |
| help_category             |
| help_keyword              |
| help_relation             |
| help_topic                |
| host                      |
| tables_priv               |
| time_zone                 |
| time_zone_leap_second     |
| time_zone_name            |
| time_zone_transition      |
| time_zone_transition_type |
| user                      |
+---------------------------+

[easytouch]

I just wanted to add, that besides the error messages above, the upgrade from 4.0.5 to 4.5.0 now was OK (I ran the .sql injection as described above BEFORE the Upgrade to 4.5.0).

Can I perform any further troubleshooting before I try this Update procedure on a production server?

[brained]

I've can duplicate easytouch's results. Glancing through the mysql_fix_privilege_tables.sql nowhere do I see a CREATE TABLE for the proc table.

I did run the mysql_fix_privilege_tables.sql from the 4.5.0 which did create the missing proc table, however attempting to upgrade after that results in:

ERROR 1051 (42S02) at line 10368: Unknown table 'open_conversation,appointment,mail_item,tombstone'
mysql invication failed, exit code = 1:  at /opt/zimbra/libexec/scripts/migrate20060911-MailboxGroup.pl line 84, 
 line 117.
Thu Feb  1 23:05:20 2007: Script failed with code 1 - exiting
UPGRADE FAILED - exiting

[mcevoys]

I got similar results (but different line)

ERROR 1146 (42S02) at line 31: Table 'mysql.proc' doesn't exist
mysql invication failed, exit code = 1: at /opt/zimbra/libexec/scripts/migrate20060911-MailboxGroup.pl line 84,

line 43.
Fri Feb 2 20:03:15 2007: Script failed with code 1 - exiting
UPGRADE FAILED - exiting

[su_A_ve]

Our small test box (32bit) was at 4.04. We upgraded that to 4.5.0. No problems. BTW, this is Network edition...

We are ready to upgrade production (64bit) from a 4.05 to 4.5.1 as well as upgrade our 4.5.0 test to 4.5.1 and today I found this thread.

The thing is that I'm looking at the tables in both 4.5.0 (test) and 4.0.5 (prod) and I do not see any 'proc' table:

+---------------------------+
| Tables_in_mysql           |
+---------------------------+
| columns_priv              |
| db                        |
| func                      |
| help_category             |
| help_keyword              |
| help_relation             |
| help_topic                |
| host                      |
| tables_priv               |
| time_zone                 |
| time_zone_leap_second     |
| time_zone_name            |
| time_zone_transition      |
| time_zone_transition_type |
| user                      |
+---------------------------+

So the thing is, should I worry about this before our 4.0.5 to 4.5.1 upgrade or what ?

TIA...

[jholder]

No, we're going to fix the proc table issue in 4.5.2

It can fail on some, but not on others, so it's a good idea to run these commands before upgrading just in case.

[su_A_ve]

No, we're going to fix the proc table issue in 4.5.2

It can fail on some, but not on others, so it's a good idea to run these commands before upgrading just in case.

I'm still not clear - should I have a 'proc table' on 4.0.x prior to the upgrade? On our prod. box, I don't have one...

Should I have a 'proc table' on 4.5.x AFTER the upgrade ? On our dev. box which was upgraded, I don't have one either...

TIA...