Dyntex.net Support Centre: MySQL Reference Manual p.628

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

628 MySQL Technical Reference for Version 4.0.3 If after you have examined all other possibilities and you have concluded that it's the MySQL server or a MySQL client that is causing the problem, it's time to do 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 it's MySQL that is causing the problems. Take into consideration all the situations in this chapter. State any problems exactly how they appear when you examine your system. Use the 'cut and paste' method for any output and/or error messages from programs and/or log les! 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 just state "the system doesn't work". This doesn't provide us with any information about what could be the problem. If a program fails, it's always useful to know: Has the program in question made a segmentation fault (core dumped)? Is the program taking up the whole CPU? Check with top. Let the program run for a while, it may be evaluating something heavy. If it's the mysqld server that is causing problems, can you do mysqladmin -u root ping or mysqladmin -u root processlist? What does a client program say (try with mysql, for example) when you try to connect to the MySQL server? Does the client jam? Do you get any output from the program? When sending a bug report, you should of follow the outlines described in this manual. See Section 1.6.2.2 [Asking questions], page 25. A.2 Common Errors When Using MySQL This section lists some errors that users frequently get. You will nd descriptions of the errors, and how to solve the problem here. A.2.1 Access denied Error See Section 4.2.6 [Privileges], page 197, and especially. See Section 4.2.11 [Access denied], page 208. A.2.2 MySQL server has gone away Error This section also covers the related Lost connection to server during query error. The most common reason for the MySQL server has gone away error is that the server timed out and closed the connection. By default, the server closes the connection after 8 hours if nothing has happened. You can change the time limit by setting the wait_timeout variable when you start mysqld. Another common reason to receive the MySQL server has gone away error is because you have issued a \close" on your MySQL connection and then tried to run a query on the closed connection.

MySQL Reference Manual

Our Partners

SpiritHost - web hosting for spiritual and education sites
SpiritHit.com - Religious and Spiritual Portal

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide