The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MySQL broken on latest update 26/AUG

Discussion in 'General Discussion' started by johnchan, Aug 26, 2008.

  1. johnchan

    johnchan Active Member

    Joined:
    Jun 29, 2003
    Messages:
    40
    Likes Received:
    0
    Trophy Points:
    6
    Hi.

    The latest /scripts/mysqlup

    seriously breaks MySQL
    -rwxr-xr-x 1 root root 23537 Aug 26 14:10 mysqlup*

    It forced a downgrade of our MySQL version from MySQL5 to MySQL4! This has caused all databases to go down and all DB driven websites to go down as well.

    Ticket was launched regarding this #298938, but hopefully someone else has seen this happen JUST today?

    You'll also see the following errors:

    If you get an 'Access denied' error, you should run this script again and
    give the MySQL root user password as an argument with the --password= option
    /usr/local/apache/modules/libphp4.so: /usr/lib64/libmysqlclient.so.15: version `libmysqlclient_15' not found (required by /usr/local/apache/modules/libphp4.so)
    /usr/local/apache/modules/libphp5.so: /usr/lib64/libmysqlclient.so.15: version `libmysqlclient_15' not found (required by /usr/local/apache/modules/libphp5.so)


    Probably because the mysqlup script forced a downgrade to MySQL4.

    Hope someone can provide feedback on this, as it presumably is just being rolled out, and hopefully hasn't hit too many people yet.
     
  2. johnchan

    johnchan Active Member

    Joined:
    Jun 29, 2003
    Messages:
    40
    Likes Received:
    0
    Trophy Points:
    6
    Additional information:-

    The /scripts/mysqlup script was reading some Cpanel configuration file that told it to install mySQL 4.

    So we went back into "Tweak Settings" in WHM, and found that the MySQL version was listed as 4! In fact, after you upgrade to 5, it shouldn't even be possible to go back to 4, since the checkbox/checkbutton only shows MySQL 5 afterwards.

    Not only that, but all the settings were showing " ** " on the left, indicating ALL the settings were new, AND also the settings we had before were GONE and seemed to have defaulted to original settings!

    We are going through the entire system now to see what other settings were reverted to the originals...

    but this only occurred today during the automatic update. We use the Release Tree, so you might watn to beware and disable it temporarily or check what was changed, because this caused serious problems.

    We are are now changing "Tweak Settings" to MySQL 5 again, and running /scripts/mysqlup --force seems to getting the correct MySQL 5 now.

    We hope it will resolve this, but please check and update.
     
Loading...

Share This Page