« Partial Page Caching with ColdFusion | Main | As Computers Evolve, Our Standards for Computing Don't »
February 15, 2005
If You're Having Trouble Starting and Stopping MySQL...
The first thing you want to do, I learned today, is look for a left-over MySQL configuration file from a previous installation. I installed MySQL 4.1 on a brand new server today, and two hours later, I still was not able to get it to run. I kept getting error messages indicating that the mysql.sock and .pid files couldn't be found. I was just about to give up computers forever and pursue a career as a farmer when I found a mention of /etc/my.cnf which can be used to configure things like the location of your .pid and mysql.sock files. "That can't be my problem," thought I, "since I didn't even create one of those files." Then it hit me. I checked /etc, and there was the my.cnf file from the default RedHat Enterprise installation of MySQL. Renaming the configuration file and restarted fixed the problem, and made me realize how needlessly I wasted the last two hours of my life.
I really don't like default installations of things like Apache and MySQL where files are spread all over the file system. When I get my hands on a brand new box, I like to install brand new versions of software, and I like to install them where I like to install them. Anyway, hopefully this post will rescue someone out there from the same fate.
Posted by cantrell at February 15, 2005 6:33 PM
Comments
Tips from a MySQL empoyee
http://www.livejournal.com/users/peter_zaitsev/12083.html
Posted by: Alex Aguilar at February 15, 2005 10:27 PM
Yeah, the previous installation causes problems many times (in my case, when starting the service, my firewall app ask for promision and if i dont answer in 1 seconds, the my sql cant 'register' the service and it fails)
Another problem is (still, after reading all technotes and updating drivers) with MySQL 4.1 and CFMX 6.0
Posted by: Vesa at February 16, 2005 7:30 AM
One thing that you might want to look at is do you have the current directory, "." in your path? Do you run things just by typing the command and rely on the shell finding the program that you would like to execute in your path?
On any UNIX system I always remove the current directory from the path and run things by either typing the absolute path or (more often) by:
./safe_mysql
or whatever command I'm looking to run. In a way it can be seen as an advantage to be able to keep multiple versions with multiple configurations on one box. It does require a bit more care on the part of the user however. Hopefully these clues can help you with this.
Good luck!
--
Dan Glauser
Director of Serverside Development
dan@roundboxmedia.com
Posted by: Dan Glauser at February 16, 2005 10:52 AM
I had this EXACT same issue, after installing a brand-new fresh version of Red Hat v9.0. What a total nightmare it is to upgrade MySQL from the verison installed by the CDs. It's still not working 100%...we get all kinds of issues trying to use the Windows Administration tool. Any ideas?
Email: beatinger@edenhosting.net
Posted by: Bjorgen T. Eatinger at November 9, 2005 12:28 AM