General software, Operating Systems, and Programming discussion.
Everything from software questions, OSes, simple HTML to scripting languages, Perl, PHP, Python, MySQL, VB, C++ etc.
Been trying to get MySQl running for a couple days now, msot problems are fixed, The only problem's that left is that when I try to start the server, I get this error...
ERROR 2002: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)
Does anyone know how I can fix this and get MySQl up and running?
Three Rivers Designs wrote:America! Love it or give it back!
UGH...still can't get it working, when I try to run it, it says:
Sorry, the host 'equalizer' could not be looked up.
Please configure the 'hostname' command to return a correct hostname.
If you want to solve this at a later stage, restart this script with
the --force option
Three Rivers Designs wrote:America! Love it or give it back!
Hmm. Does the name equalizer mean anything to you?
The error you received (ERROR 2002) is often caused by the hostname not resolving/existing or mysqld (did you verify that it is running?) not running (often for the aforementioned reason).
With MYSQL it's often easier to reinstall. I would remove the mysql user and group (assuming you followed the INSTALL doc), remove the slink to mysql, yadayada - follow the install in reverse to clean up.
I have to admit, there's a part of me that always wants to figure out why it doesn't work. When the install for MySQL goes bad it goes bad. You save a lot of time (and hair) starting over.
Skye
EDIT: Read through the INSTALL doc completely. Understand why you are taking each step (the detailed section gets deep enough).
Second EDIT: What version and which build are you running? I assumed 3.23
anything is possible - nothing is free
Blisster wrote:It *would* be brokeback bay if I in fact went and hung out with Skye and co (did I mention he is teh hotness?)
K. That's a devleopment build still. If you are building a next-generation app, that's cool. Otherwise, I'd go stable. Same way I'd suggest apache 1.3.27 over 2.x. Let them mature a bit.
Not that the version is the problem. It should still work. One more time, tho -
1. is mysqld running?
2. was a host named equalizer ever involved?
anything is possible - nothing is free
Blisster wrote:It *would* be brokeback bay if I in fact went and hung out with Skye and co (did I mention he is teh hotness?)
Originally posted by cyberskye K. That's a devleopment build still. If you are building a next-generation app, that's cool. Otherwise, I'd go stable. Same way I'd suggest apache 1.3.27 over 2.x. Let them mature a bit.
Not that the version is the problem. It should still work. One more time, tho -
1. is mysqld running?
2. was a host named equalizer ever involved?
equalizer was the original host name, it's since been changed.
I've never been able to get mysqld running.
Three Rivers Designs wrote:America! Love it or give it back!
Is <IP Address> testbocks.<domain name> testbocks added to your /etc/hosts file? From what I can see and understand in the posts your hostname doesn't resolve. Look at the hosts file, read 'man hosts' to learn how to add the info you need to it.
Originally posted by cyberskye ...or you could replace equalizer with testbocks in the /etc/hosts file. mysqld is trying to run on a host named "equalizer".
How did you change the hostname to testbocks? What specific steps?
Host name was changed after the drive failed....
Three Rivers Designs wrote:America! Love it or give it back!
Did you check by looking for the mysqld process via ps? My point was that it may have been running, just not servicing requests or in an otherwise unstable state. This simple step would rule that out.
Host name was changed after the drive failed....
Sorry, the host 'equalizer' could not be looked up.
I asked what steps you took to change the hostname. There are a couple of ways that you can change the hostname - some more effective than others. The hostname command calls GetHostName() or setHostName() system calls, you can also modify system files like /etc/hosts, or through a reinstall/sysinstall...
I don't mean to be short, but getting the info from you required to help is fairly difficult. Your answers are vague when they need to be kinda specific. mysql is referencing the old hostname, but you say you changed it - again, HOW?!
I would again suggest you start over. It would take more time tracking down the system-wide configuration errors on your box that could affect this than to roll-back and start over.
Here's a good arctile on issues with the FreeBSD>MySQL combo. http://jeremy.zawodny.com/blog/archives/000203.html It explains how to over-ride the hostname look up that mysql performs. You can manually run the ./mysqld command with the options described in this link. I would be worried about future issues.
anything is possible - nothing is free
Blisster wrote:It *would* be brokeback bay if I in fact went and hung out with Skye and co (did I mention he is teh hotness?)
Originally posted by cyberskye I asked what steps you took to change the hostname. There are a couple of ways that you can change the hostname - some more effective than others. The hostname command calls GetHostName() or setHostName() system calls, you can also modify system files like /etc/hosts, or through a reinstall/sysinstall...
I don't mean to be short, but getting the info from you required to help is fairly difficult. Your answers are vague when they need to be kinda specific. mysql is referencing the old hostname, but you say you changed it - again, HOW?!
I would again suggest you start over. It would take more time tracking down the system-wide configuration errors on your box that could affect this than to roll-back and start over.
I had to reinstall on a new drive because the first drive failed.
Three Rivers Designs wrote:America! Love it or give it back!
That is odd. Did you format or just reinstall overtop? Seems that something iis left over or maybe you backed-up data then changed the hostname when restoring...
in your hostfile the line that contains
127.0.0.1 localhost xxx xxx xxx
What are the other names (the xxx's) in order?
Do you have any other entries for a specific ip address - don't need the ip addresses themselves, just verify that the aliases are valid.
In that link I posted above the guys tells you how to force mysql to use whatever name you wish. safe_mysql is a wraper that tries to understand the best variables to use - it clearly isn't working in your case. You might want to give it a try.
anything is possible - nothing is free
Blisster wrote:It *would* be brokeback bay if I in fact went and hung out with Skye and co (did I mention he is teh hotness?)
A quote from that link
"
Based on our testing, the only truly safe way to operate is to use the --skip-name-resolve flag for starting mysqld AND specifying the IP address of the master instead of the hostname. That virtually eliminates the need for MySQL to call gethostbyname().
"
Skye
anything is possible - nothing is free
Blisster wrote:It *would* be brokeback bay if I in fact went and hung out with Skye and co (did I mention he is teh hotness?)