R1Lover
Verified User
- Joined
- Feb 24, 2007
- Messages
- 446
During a recent update using custom build, one of the items was mysql going from 5.1.55 to 5.1.56, not a big update I assumed etc.. Well after mysql was updated it failed to start throwing the following error.
I was able to track this down to the following in my.cnf file... while I wasn't using innob on this server, this line was still in the config.. and was the cause of the error.
I'm not sure why this line above didn't cause any issues with 5.1.55 and threw 5.1.56 into a frizzy... however I wanted to mention this in case anyone else run into this issue.
I would also like to Thank Jeff @ NoBaloney for his warm voice and a few quick jokes while speaking with him on the phone.
It's always a laugh or three when talking to Jeff and since this was a critical server (high traffic) I thought first to call him to see if he has hit this yet... and in fact he had, however it would be nice to understand the exact details here and how we can prevent this for the common user in the future.
Code:
Starting MySQL..Manager of pid-file quit without updating f[ERROR!]I was able to track this down to the following in my.cnf file... while I wasn't using innob on this server, this line was still in the config.. and was the cause of the error.
Code:
innodb_buffer_pool_size (>= 21M)I'm not sure why this line above didn't cause any issues with 5.1.55 and threw 5.1.56 into a frizzy... however I wanted to mention this in case anyone else run into this issue.
I would also like to Thank Jeff @ NoBaloney for his warm voice and a few quick jokes while speaking with him on the phone.
It's always a laugh or three when talking to Jeff and since this was a critical server (high traffic) I thought first to call him to see if he has hit this yet... and in fact he had, however it would be nice to understand the exact details here and how we can prevent this for the common user in the future.