Hi,

I had got this problem when updating MySQL to version 5.1.x. It seems that you are running 64-bit with a both of mysql.i386 and mysql.x86-64 version. And you got this problem because of the mysql-server upgrade to new version but the mysql-client still keep the old version. And the solution is download the source code of right mysql-server version which you are running, extract it, and copy the errmsg.sys to the correlative path in the server.

The next time, you should remove the mysql.i386 version before updating.

That sounds reasonable. Since this is a test box I'm free to do just that. I'll give it a try when I get back to work Monday. Thanks for the tip I'll post to success or failure whichever comes first.

@quanta - good catch did not see that.

Hopefully that fixes the problem. Let us know.

Well I did manage to get MySQL working correctly and creating it sock with a reinstall. However for whatever reason php-mysql would not install. I downgraded from 5.3.4(remi's latest release) to the 5.3.3 release which also didn't work. I removed that version and managed to get it working via this http://www.webtatic.com/blog/2009/06...0-on-centos-5/

Thank you, so much. I registered just to say thanks. Been searching for hours with the same problem. I had added a non standard redhat repo to grab a php package from this century (seriously redhat, 5.1.6?). It pulled my mysql install from that repo and also carried over some x86 nonsense. I had to do the following:

- Wipe everything from the previous MySQL installs (including any conflicting files)
- Clean Yum
- Temporarily disable my custom repo

Worked just fine. Thank you for posting that and not just blowing the original poster off like almost every other forum thread found through google seems to be full of.

vi /etc/my.cnf
# For low memory, Berkeley DB should not be used so keep skip-bdb uncommented unless required
#skip-bdb

comment out of the "skip-bdb" section.
TRY it.

So, I was having the same issue. Exactly the same across the board -- all your posts and outputs matched my exactly. After hours or trolling google and beating my head against the wall I did something extraordinary.

I RTFM.... http://dev.mysql.com/tech-resources/...sql_intro.html

$ sudo mysql_install_db

It did some stuff... then when I started mysqld ($ sudo /sbin/service mysqld start) I got that wonderful... beautiful... [ OK ]

1 members found this post helpful.

I was backing up a database when this happened to me: mysqld would not restart, even after a system restart. What had happened in the middle of the backup was that the disk became 100% full and mysql could not even create its .pid file. Just run to check your disk space.

Thanks, mate! It solved my problem!

Thank you for posting that. I also removed and re-installed, but it wasn't 'til after I ran the install line that it started.

# mysql_install_db