C.5.2. Common Errors When Using Mysql Programs - Oracle 5.0 Reference Manual

• Please examine your system log file
If you think the problem is in MySQL, you should also examine MySQL's log files. See
"MySQL Server
• If you do not think you have hardware problems, you should try to find out which program is causing
problems. Try using top, ps, Task Manager, or some similar program, to check which program is
taking all CPU or is locking the machine.
• Use top, df, or a similar program to check whether you are out of memory, disk space, file
descriptors, or some other critical resource.
• If the problem is some runaway process, you can always try to kill it. If it does not want to die, there
is probably a bug in the operating system.
If after you have examined all other possibilities and you have concluded that the MySQL server or a
MySQL client is causing the problem, it is time to create a bug report for our mailing list or our support
team. In the bug report, try to give a very detailed description of how the system is behaving and what
you think is happening. You should also state why you think that MySQL is causing the problem. Take
into consideration all the situations in this chapter. State any problems exactly how they appear when
you examine your system. Use the "copy and paste" method for any output and error messages from
programs and log files.
Try to describe in detail which program is not working and all symptoms you see. We have in the
past received many bug reports that state only "the system does not work." This provides us with no
information about what could be the problem.
If a program fails, it is always useful to know the following information:
• Has the program in question made a segmentation fault (did it dump core)?
• Is the program taking up all available CPU time? Check with top. Let the program run for a while, it
may simply be evaluating something computationally intensive.
• If the
mysqld
root ping
• What does a client program say when you try to connect to the MySQL server? (Try with mysql, for
example.) Does the client jam? Do you get any output from the program?
When sending a bug report, you should follow the outline described in
Bugs or Problems".

C.5.2. Common Errors When Using MySQL Programs

This section lists some errors that users frequently encounter when running MySQL programs.
Although the problems show up when you try to run client programs, the solutions to many of the
problems involves changing the configuration of the MySQL server.
C.5.2.1.
Access denied
An
Access denied
accounts that the server permits client programs to use when connecting. See
MySQL Access Privilege
C.5.2.2.
Can't connect to [local] MySQL server
A MySQL client on Unix can connect to the
socket file to connect through a file in the file system (default /tmp/mysql.sock), or by using TCP/IP,
which connects through a port number. A Unix socket file connection is faster than TCP/IP, but can be
used only when connecting to a server on the same computer. A Unix socket file is used if you do not
specify a host name or if you specify the special host name localhost.
Common Errors When Using MySQL Programs
Logs".
server is causing problems, can you get any response from it with
or
mysqladmin -u root
error can have many causes. Often the problem is related to the MySQL
System", and
(/var/log/messages
processlist?
Section 6.2.7, "Causes of Access-Denied
server in two different ways: By using a Unix
mysqld
2946
or similar) for reasons for your problem.
mysqladmin -u
Section 1.7, "How to Report
Section 6.2, "The
Errors".
Section 5.2,