mysql acts strange after stable update

[MMarko]

Everytime mysql is updated via WHM / cPanel updater to new version it start to act very strange.

Does anybody else experienced this problem? What's causing it?

 

[chirpy]

That's way too vague. What, exactly are the problem that you are seeing?

 

[MMarko]

Mysql doesn't want to exit normaly. Then some db went corupted and when trying to restart mysql it becomes unpossible.

Before mysql returned some errors about not having enough memory (which was false because there is always enough memory).

 

[MMarko]

I manage to fix this by killing all mysql processes manualy and then restart it. This time there were no corupted dbs (they can be repaired via WHM or phpMyAdmin).

 

[chirpy]

One thing to check is that if you have a separate /tmp partition make sure it has plenty of free space as MySQL will, by default, store temporary data in there.

 

[MMarko]

One more interesting thing about mysql.


Release version uses mysql v 4.1.18 and stable uses 4.1.19

 

[MMarko]

One thing to check is that if you have a separate /tmp partition make sure it has plenty of free space as MySQL will, by default, store temporary data in there.

Yes there is plenty of space there.



Right now I'm unable to update to latest release. There seems to be problem with cpanel update server?

 

[Canadahost2]

We are having similar problems with mysql on at least two of our servers requiring repeated restarts after the update. I've had to restart mysql numerious times in the last couple hours on two different servers (both had previously been running fine for months).

 

[cooldude7273]

Release version uses mysql v 4.1.18 and stable uses 4.1.19

Release actually does use 4.1.19 - x86 that is, x64 is still on 4.1.18