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 update

Discussion in 'General Discussion' started by mickalo, Sep 27, 2008.

  1. mickalo

    mickalo Well-Known Member

    Joined:
    Apr 16, 2002
    Messages:
    765
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    N.W. Iowa
    We update our mysql from 4.1+ to the recent 5.0.51a installed by Cpanel update. We did have InnoDB enabled in the 4.1 version, but now we can't get InnoDB enabled. Everytime we attempt to restart MySQL we get this error:

    Code:
    080927 10:34:54  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
    InnoDB: Setting log file ./ib_logfile0 size to 5 MB
    InnoDB: Database physically writes the file full: wait...
    InnoDB: Error: log file ./ib_logfile1 is of different size 0 67108864 bytes
    InnoDB: than specified in the .cnf file 0 5242880 bytes!
    
    Is there something we need to change for the newer version now to enable InnoDB. We have a bunch of databases that used the InnoDB table handlers.

    I'm sure this may have been discussed before, but I've been away for sometime and just got back managing our servers and I'm probably a bit behind on these newer releases.

    Appreciate any help,

    Thx's
    Mike
     
  2. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    From that message, it appears you have something in /etc/my.cnf specific to InnoDB that is preventing this:

    Try this:

    1. Comment out all InnoDB related entries in /etc/my.cnf
    2. Restart MySQL
    3. If MySQL starts successfully, then:
    3a. Uncomment one InnoDB related entry in /etc/my.cnf
    3b. Restart MySQL
    3c. Repeat steps 3a and 3b until you find the entry that causes problems

    The idea of the above is isolating which entry causes the problem. Once that is known you can research the entry in the MySQL manual to determine what the cause is.


    If none of the above works, please open a support ticket at https://tickets.cpanel.net/submit/ and our techs will gladly help you sort this out.
     
Loading...

Share This Page