I am just wondering how many people have upgraded to MySQL 4.1 by selecting MySQL 4.1 in Tweak Settings and updating. Any problems? Is it worth the upgrade yet or should I wait? I am interested in trying out the new features and heard it is greatly improved in performance. Does the WHM upgrade maintain the current databases properly?

Well in WHM it says 4.1 is still experimental. I would first wait until that warning goes away lol.

Just want to let everyone know I upgraded to 4.1 and it went flawlessly.

oooo, you daredevil you...

Haha, yes I am. Just wish cpanel would update their mysqlup scripts to use 4.1.9 now (not 4.1.. But wow...amasing performance enhancements!

Haven't tested this, so I hope you don't mind me asking...whgat is your OS, and server? Also, how is the phpMyAdmin functionality? Have you had issues with any of the add-ons software, like phpbb, invision, etc? Thanks, Jim

I'm running it on my own server (P2800) with Red Hat Enterprise 3 (Taroon Update 4).

I'm also running it on 2 servers I help manage, one with over 700 accounts, the other with about 350. #50 account server is running Red Hat 9, and the 700 account server is Fedora Core 1.

phpMyAdmin is fully functional with 4.1 and includes all the necessary extras for the new features.

My server and the other two servers are running multiple phpBB, vB, IPB, and other common script installs with no problems.

xenneo from these forums also put 4.1 on his server...(although that one had a little trouble, but we fixed it all pretty easily).

Woah, over 700 accounts on a P4 2.8 !...

Actually...it's an AMD AthlonXP 3000+ (2.1GHz)

What is the load !?!...

Before I became admin, about 2.0, after I became admin, less than 0.3 (except when stats programs run...then it goes to about 0.5).

I got here a CASH KILLER !...

finaly iti is working with cpanel ?

It is still considred "experiemtnal" however 3 running servers that I admin (1 being my own), and helped many others upgrade from 4.0 to 4.1, and most went without problem. Some had a few, bu were resolved pretty quickly with my skills (I picked up from these forums )

I also migrated..it is ok ..

What sort of problems did you encounter and what were the solutions?

Well on my pwn system...absolutely nothing. On other people's systems I helped upgrade, all went fine, but 2.

Both had same problem: MySQL root password became corrupted and WHM would not change it or reset it. In turn, chkservd thought mysql was down cause it couldn't connect. This caused tons of those mysql restart scripts coming up in ps -ax.

To fix the problem you have to do the following:
service chkservd stop
service mysql stop
killall mysql
ps -ax (and kill any remaining mysql restarting scripts)
Edit cPanel Tweak Settings to use MySQL 4
/scripts/mysqlup (this downgrades back to 4.0)
service mysql restart
Change mysql root password in WHM
Edit cPanel Tweak Settings to use MySQL 4.1
/scripts/mysqlup (This puts 4.1 back in)
Change mysql root password in WHM and ensure it worked
service chkservd start

Thank you for sharing that; now others with the same problem can have some directions to go by.

As for myself, I'm still waiting to upgrade because I want to see what all, if anything, could go wrong.

I upgraded, caused too many problems ... well ish seemed to work, then websites failed to connect ...

upon downgrading back, it all failed, cant start mysql service now

After selecting the new version each time did you run '/scripts/mysqlup' and then recompile PHP via 'WHM's Update Apache' or '/scripts/easyapache'?

yup done that

/usr/bin/mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)' Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists! mysql has failed, please contact the sysadmin (result was "Warning, no valid mysql.sock file found.mysql has failed").

i get that when i try to restart the service

you get that when you try to *restart* the service? interesting. anyway, stopping the service, killing all the processes, waiting about 10 seconds and then restarting mysql should fix that up and recreate the sock file. failing that, a reboot should recreate it in a jiffy.

i so wish you was right, just rebooted and didnt solve it

It's due to the MySQL root password being different in /root/.my.cnf from the new install. To fix this, go to Set MySQL Root Password (or something along those lines) in WHM under MySQL, and type in a root pass you want for MySQL. Make it a hard to guess one, as always. If it fails, downgrade to 4.0 again, set root pass, then upgrade again to 4.1 and set root pass. This was the problem I had on a few servers I upgraded.

I've been running mysql 4.1 in production for quite some time now, no issues really, as long as the client is kept in sync as well

I attempted an upgrade and now my php files (only the ones that use MySQL) do not execute. I think mySQL is running okay. Not sure if this problem is related to a connection problem to MySQL or what. Any thoughts?

Tried all the above, thanks. However, due to the upgrade all tables changed to Latin1.

So manually uploaded the old db's and changed the system Collate to UTF8 (I'm using multiple languages).

Noticed that:
character_set_results, character_set_server etc., are still in Latin1 format.

How to change this to utf? I tried this statement in mysql but had no luck since it doesn't recognise " ":

./configure --with-charset=utf8 --with-collation=utf8_general_ci

./mysqld --default-character-set=utf8 --default-collation=utf8_general_ci

The password problem when upgrading MySQL is often related to the new password hashing function that version 4.1 uses. However, I have found a quirk that is often overlooked. Sometimes the 'mysql.user' table is not properly upgraded with the database server. If you run into this problem, start MySQL without any privilege security.



As many of you know, the new encrypted passwords in MySQL 4.1 are much longer than the older passwords. So check out the 'mysql.user' table.



This will print out all of the fields for this table. You are looking for the Password field. It will look something like this.



The key is the char(16). No matter how many times you reset your root password, it will not fit into that field. Exit the MySQL client and run this command.



Hop into MySQL and your Password field should now look like this (Notice the 41)



Reset your password and restart MySQL. After that you should be good to go.



Hope this can help someone out.

Hi,
I'm on RHE3 with WHM 10.8.0 cPanel 10.9.0-S35
I experience overload problems, and I wanted to update Mysql from 4 to 4.1

This thread is one year old, and is all still applicable ?

Is it safe to update mysql from whm ?

According to this thread, I'm afraid of encountering your problems (charset table, passwords, or with apache)
Is it safe to do it ?

is there a standalone detailed procedure to follow not to get problems and help newbies, to dump the entire DB, upgrade, recompile etc. ?

thank you

It worked for me when I did the upgrade. Everything worked fine, but I noticed that the password field was short, so I lengthened it using kfukasawa's suggestions. It's all been running fine for a while now. I did dump a full database backup though, just to be sure.

I did have issues with some old old ISAM tables disappearing though. But I figured out how to convert those over to MYISAM. It just would have been easier beforehand. So just make sure you don't have any really old format tables around.

I did have issues with some old old ISAM tables disappearing though. But I figured out how to convert those over to MYISAM. It just would have been easier beforehand. So just make sure you don't have any really old format tables around.

Why should "old" isam tables disapear ? what do you mean by "old" ?

When you say "it worked", you mean that you've done it from WebHostManager, doing what they say ? :