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 upgrade question

Discussion in 'General Discussion' started by Valuehosted, Aug 13, 2008.

  1. Valuehosted

    Valuehosted Well-Known Member

    Joined:
    Dec 12, 2002
    Messages:
    124
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Sweden
    Hi there,

    I have run into a peculiar bug in cpanel's current mysql version (5.0.51a-community) and need to upgrade to a later, or better yet, latest version of mysql.

    My question is fairly simple, how would I go about doing that and is it safe to stray from cpanel 'approved' mysql versions?

    I am running: Linux version 2.6.9-67.0.1.ELsmp (brewbuilder@hs20-bc1-6.build.redhat.com) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-9))

    Thanks,

    Tony
     
  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    It is important to note that the latest version of MySQL we support is 5.0.51a-2cp. Note, STABLE is the only build that is not yet supporting 5.0.51a-2cp.
     
  3. Valuehosted

    Valuehosted Well-Known Member

    Joined:
    Dec 12, 2002
    Messages:
    124
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Sweden
    Thanks David (WOW - impressive response time!),

    The error I am refering to is the "reversed" post order bug in 5.0.51 that cannot handle query_posts() command properly and it makes posts ordered in a reverse manner in WordPress 2.x.

    It only happens if a theme uses the query_posts() command, which unfortunately mine does.

    Do you know if the cp2 version fixes this bug or if I am simply SOL until cpanel goes to the next version of mysql? Any idea what kind of time reference we would talk about? weeks, months?

    Thanks again for your quick reply,

    --Tone
     
  4. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Actually that issue was resolved in the version we supported immediately before 5.0.51a-2cp IIRC. In any case, that is not an issue in 5.0.51a-2cp.
     
  5. Valuehosted

    Valuehosted Well-Known Member

    Joined:
    Dec 12, 2002
    Messages:
    124
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Sweden
    excellent - so if I understand correctly - this would be fixed by going to release instead of stable?

    As I understand it too is that release is basically as 'safe' as stable, is that right?

    If I change to release, is it possible to go back to stable in the future?

    Again, totally blown away with the response time!

    Thanks!

    --Tone
     
  6. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    As a rule of thumb, our fixes generally propagate from EDGE to CURRENT to RELEASE then eventually to STABLE.

    STABLE is a very conservative build for those that require stability more than anything else. Being on RELEASE still ensures a production quality product but speedier fixes as they do not go through as extensive a quality assurance process to get to RELEASE that STABLE goes through.

    Yes, just go to WHM -> Server Configuration -> Update Config and select STABLE then go through the procedure to update cPanel to revert back to STABLE.
     
  7. Valuehosted

    Valuehosted Well-Known Member

    Joined:
    Dec 12, 2002
    Messages:
    124
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Sweden
    I changed to release and did the update, I even ran:

    /scripts/mysqlup --force

    and I am still getting:


    mysql> select version();
    +-------------------+
    | version() |
    +-------------------+
    | 5.0.51a-community |
    +-------------------+
    1 row in set (0.00 sec)

    Any idea what I might be doing wrong?
     
  8. Valuehosted

    Valuehosted Well-Known Member

    Joined:
    Dec 12, 2002
    Messages:
    124
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Sweden
    WHM 11.23.2 cPanel 11.23.4-R26138
    REDHAT Enterprise 4 i686 on standard - WHM X v3.1.0
     
  9. Valuehosted

    Valuehosted Well-Known Member

    Joined:
    Dec 12, 2002
    Messages:
    124
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Sweden
    I even went to

    WHM 11.23.2 cPanel 11.23.5-C26602
    REDHAT Enterprise 4 i686 on standard - WHM X v3.1.0

    and in the update:

    Updating MySQL Server...MySQL Setup Script Version 7.0
    Fetching http://httpupdate.cpanel.net/mysqlinstall/CURRENT/cPpkgversion (0)....@72.233.42.250......connected......receiving...100%......Done
    Loaded cPPkgs::MySQL ok!
    This is the cPPkgs::MySQL 5.0.51a installer for Linux.
    MySQL 5.0.51a is up to date
    Install Complete
    ...Done

    no changes in mysql update, I am now running release again however.

    looking at CPpkgversion for each version, it appears that they are all using the same version ('MySQL-shared-5.0.51a-2.glibc23) but it still does not fix the reverse post order bug of 5.0.51.

    http://httpupdate.cpanel.net/mysqlinstall/STABLE/cPpkgversion
    http://httpupdate.cpanel.net/mysqlinstall/RELEASE/cPpkgversion
    http://httpupdate.cpanel.net/mysqlinstall/CURRENT/cPpkgversion
    http://httpupdate.cpanel.net/mysqlinstall/EDGE/cPpkgversion

    Any help would be greatly appreciated!

    --Tone
     
    #9 Valuehosted, Aug 14, 2008
    Last edited: Aug 14, 2008
  10. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,460
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    We don't do anything to alter the internal version string. You can tell the version you are running by using RPM to query the RPM database:

    Code:
    rpm -qa | grep -i mysql
    
     
Loading...

Share This Page