Need URGENT help after upgrade from MySQL 3.23 to 4

saw · Unread post by **saw** » Sun Dec 11, 2005 2:52 pm

My dedicated server was running Plesk 7.5.4 and MySQL 3.23.

Not knowing better, I attempted to upgrade MySQL to version 4.0.26 using the following RPMs from mysql.com: shared-compat, server, client, devel.

After the upgade, MySQL will not start. I get the "can't connect mysql.sock" message. When I issue a stop command, I get a "No mysqld pid file found" message. When I issue a start command, nothing happens. When I issue "ps -aux" I do not see MySQL running.

I found this Web site after hours of pulling my hair out. I would like to remove the mess I created and upgrade using the ART mysql RPM but when I try to remove the ones I already installed I get "mysql-server >= 3.23.52 is needed by (installed) psa-7.5.4" and "mysql-server is needed by (installed) psa-qmail"

I did create mysqldumps of my data before the failed upgrade so I think I'm okay from that perspective. I need to know the proper way to proceed at this point. I imported the GPG key and am able to yum list the Atomic RPMs. What should I do next???

All of my Web sites and e-mail accounts are down now -- please help ASAP. Thanks in advance.

Unread post by **scott** » Sun Dec 11, 2005 6:19 pm

If you add the [atomic] archive to your yum.conf you should be able to run "yum update" and that will fix everything up for you.

saw · Unread post by **saw** » Sun Dec 11, 2005 10:33 pm

About an hour after my original post I tried this. It updated a number of things but also spit out a number of MySQL connection errors. It did not upgrade MySQL so I tried yum update mysql and it said no update was available. I ended up paying someone who connected and fixed it in about ten minutes. For obvious reasons he wasn't very forthcoming about what he did (

) but it's working now and I'm on 4.1. I will use yum/atomic from now on. Thanks for making this available.

Just curious........any idea off-hand why it said no updates were available for MySQL?

Thanks,

Unread post by **scott** » Mon Dec 12, 2005 3:27 pm

It might have already updated it. Take a look at the output of: rpm -qa |grep -i mysql

I'm sure all the guy really did was restart the daemon, its pretty touchy about starting up and shutting down.

philb · Unread post by **philb** » Wed Dec 14, 2005 2:21 am

saw wrote:For obvious reasons he wasn't very forthcoming about what he did ( )

You paid someone to work on your server and they wouldn't tell you what they did?

Did you ask? I mean, it's your money...