Oracle 5.0 Reference Manual page 2968

really exists. The fix in this case is to change the
the socket file somewhere else. See
Socket File".
• You have started the
forgotten to tell client programs the new name of the socket file. If you change the socket path
name for the server, you must also notify the MySQL clients. You can do this by providing the same
--socket
permission to access the
shell> netstat -ln | grep mysql
See Section C.5.4.5, "How to Protect or Change the MySQL Unix Socket
• You are using Linux and one server thread has died (dumped core). In this case, you must kill the
other
mysqld
the MySQL server. See
• The server or client program might not have the proper access privileges for the directory that holds
the Unix socket file or the socket file itself. In this case, you must either change the access privileges
for the directory or socket file so that the server and clients can access them, or restart
a
--socket
it and where client programs can access it.
If you get the error message
following things to find out what the problem is:
• Check whether the server is running on that host by executing
pressing the Enter key a couple of times. (3306 is the default MySQL port number. Change the value
if your server is listening to a different port.) If there is a MySQL server running and listening to the
port, you should get a response that includes the server's version number. If you get an error such as
telnet: Unable to connect to remote host: Connection
server running on the given port.
• If the server is running on the local host, try using
connect using the Unix socket file. Verify the TCP/IP port number that the server is configured to
listen to (it is the value of the
• If you are running under Linux and Security-Enhanced Linux (SELinux) is enabled, make sure you
have disabled SELinux protection for the
C.5.2.2.1.
Connection to MySQL Server Failing on Windows
When you're running a MySQL server on Windows with many TCP/IP connections to it, and you're
experiencing that quite often your clients get a
reason might be that Windows does not allow for enough ephemeral (short-lived) ports to serve those
connections.
The purpose of
been closed. This is because Internet routing can cause a packet to take a slow route to its destination
and it may arrive after both sides have agreed to close. If the port is in use for a new connection, that
packet from the old connection could break the protocol or compromise personal information from the
original connection. The
until after some time has been permitted for those delayed packets to arrive.
It is safe to reduce
arriving at very long delays, as they could through the Internet with its comparatively large distances
and latencies.
Windows permits ephemeral (short-lived) TCP ports to the user. After any port is closed it will remain
in a
TIME_WAIT
Common Errors When Using MySQL Programs
server with the
mysqld
[232] option when you run client programs. You also need to ensure that clients have
mysql.sock
threads (for example, with
Section C.5.4.2, "What to Do If MySQL Keeps
[422] option that specifies a socket file name in a directory where the server can create
Can't connect to MySQL server on
port
is to keep a connection accepting packets even after the connection has
TIME_WAIT
TIME_WAIT
greatly on LAN connections because there is little chance of packets
TIME_WAIT
status for 120 seconds. The port will not be available again until this time expires. The
job to not remove
cron
Section C.5.4.5, "How to Protect or Change the MySQL Unix
--socket=/path/to/socket
file. To find out where the socket file is, you can do:
or with the
kill
mysqladmin -h localhost variables
[482] variable.)
process.
mysqld
Can't connect to MySQL server
delay prevents this by ensuring that the port cannot be reused
2948
mysql.sock
[422]
File".
script) before you can restart
mysql_zap
Crashing".
some_host, you can try the
telnet some_host 3306
refused, then there is no
or to place
option, but
with
mysqld
and
to
error, the