Support for MySQL 5.1 and PHPMyAdmin 3

[cPanelDon]

you may want to rename your my.cnf to something else before doing this upgrade - as it seems that an older my.cnf can cause problems with the WHM upgrade script / mysql upgrade.

Any comments from cpanel techs on this?

Excluding commented lines and empty space, what are the contents of the older MySQL configuration file (i.e., "my.cnf" in the directory "/etc")?

Via root SSH access, here is an example command that could be used to help obtain the above information, assuming the suspect MySQL configuration is at the default path:

# grep -v "^#\|^$" /etc/my.cnf

[cpanelkenneth]

you may want to rename your my.cnf to something else before doing this upgrade - as it seems that an older my.cnf can cause problems with the WHM upgrade script / mysql upgrade.

Any comments from cpanel techs on this?

As the MySQL Release Notes detail some configuration options were removed, renamed or deprecated in MySQL 5.1. It behooves you as the system administrator to compare your customized /etc/my.cnf file versus the release notes to determine what changes need made.

cPanel itself makes very few changes to /etc/my.cnf. During testing it was determined one entry we add, skip-bdb could cause problems. Therefore we changed the product to:

1. No longer add that entry; and
2. Remove it if found during the MySQL upgrade

[jacampbe]

A few days ago I upgraded from MySQL v5.0.89 to v5.1.40 using WHM.
The migration went very well and even incorporated a re-build of Apache and PHP.
In the past, I have also had to manually rebuild the Perl MySQL libraries using the somewhat obscure command ......
/scripts/perlinstaller --force Bundle:BD::mysql

Questions:
1. Do I still need to do that or is it rolled into the MySQL upgrade process ?
2. If not, could it be added as an option for the MySQL upgrade process ?
3. Is there a way to initiate the rebuild of Perl MySQL from within the WHM menus - rather than using the command above ?

Thx

[cpanelkenneth]

A few days ago I upgraded from MySQL v5.0.89 to v5.1.40 using WHM.
The migration went very well and even incorporated a re-build of Apache and PHP.
In the past, I have also had to manually rebuild the Perl MySQL libraries using the somewhat obscure command ......
/scripts/perlinstaller --force Bundle:BD::mysql

Questions:
1. Do I still need to do that or is it rolled into the MySQL upgrade process ?
2. If not, could it be added as an option for the MySQL upgrade process ?
3. Is there a way to initiate the rebuild of Perl MySQL from within the WHM menus - rather than using the command above ?

Thx

/scripts/mysqlup performs an update of DBD::mysql after MySQL is updated. This has been it's behavior for at least the last four years. /scripts/mysqlup is what performs the actual installation of the MySQL RPMs ( or packages/port install on FreeBSD ). There should be no need for you to manually perform an update of DBD::mysql.

In WHM you can install/update CPAN modules via the following interface:

Main >> Software >> Module Installers >> Perl Module