Jump to content

Recommended Posts

Good evening all,

 

I upgraded a server today from php 5.1 to 5.3, and attempted to upgrade mysql to 5.1 at the same time.  There server runs red hat 5, so I used remi's repository for the upgrade (which I have done many times in the past without issue), but it seems to have caused all sorts of issues with mysql.

 

Initially I was unable to access mysql at all, so I uninstalled the remi version and installed whatever the default gave me, which seems to be somewhat incompatible with php, as I get this in phpymyadmin: Your PHP MySQL library version 5.1.40 differs from your MySQL server version 5.0.77. This may cause unpredictable behavior.  This isn't such a big issue yet though, the real problem is that all my innodb tables are now unable to be read.

 

I tried moving the logfiles and letting mysql rebuild them, moving them back, changing the size in my.cnf to match the file size, but none of this seems to work.  I would be totally cool with just pulling the data out of one of them and then using the new files and restoring from backups, but one of the databases has no backup and I'm not sure how to get it!

 

Mysql says: #1033 - Incorrect information in file: './my-database/my-table.frm' when attempting accessing from the client, mysqld.log says things like this:

 

InnoDB: Error: log file ./ib_logfile0 is of different size 0 268435456 bytes

InnoDB: than specified in the .cnf file 0 5242880 bytes!

 

over and over again.  I'm quite uncertain how to proceed!  I can easily set up a virtual server for purposes of pulling this data from the files I have.  I can get the server to a point where I can create new innodb tables, just not to where I can read the old ones!

 

Thanks, I hope someone has some ideas.

Link to comment
https://forums.phpfreaks.com/topic/178696-upgrade-with-innodb-issues/
Share on other sites

Your PHP MySQL library version 5.1.40 differs from your MySQL server version 5.0.77. This may cause unpredictable behavior.

 

Just ignore this warning.

 

Check your my.cnf file for any errors in InnoDB variables. This seems to be quite common reason for such behaviour.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.