MySQL Manual
A Problems and Common Errors
- A.2 Common Errors When Using MySQL
- A.2.1
Access deniedError - A.2.2
MySQL server has gone awayError - A.2.3
Can't connect to [local] MySQL serverError - A.2.4
Client does not support authentication protocolerror - A.2.5
Host '...' is blockedError - A.2.6
Too many connectionsError - A.2.7
Some non-transactional changed tables couldn't be rolled backError - A.2.8
Out of memoryError - A.2.9
Packet too largeError - A.2.10 Communication Errors / Aborted Connection
- A.2.11
The table is fullError - A.2.12
Can't create/write to fileError - A.2.13
Commands out of syncError in Client - A.2.14
Ignoring userError - A.2.15
Table 'xxx' doesn't existError - A.2.16
Can't initialize character set xxxerror - A.2.17 File Not Found
- A.2.1
A.2.4 Client does not support authentication protocol error
MySQL 4.1 uses an authentication protocal based on a password hashing algorithm that is incompatible with that used by older clients. If you upgrade the server to 4.1, attempts to connect to a it with an older client may fail with the following message:
shell> mysql Client does not support authentication protocol requested by server; consider upgrading MySQL client
To solve this problem, you need to either tell the server to use the older password hashing algorithm, or upgrade the client programs to use the 4.1 client library. For background on password hashing and authentication, see section 4.2.11 Password Hashing in MySQL 4.1.
