Bug #678 Sporadic Privilege Errors
Submitted: 19 Jun 2003 0:26 Modified: 3 Jul 2003 7:31
Reporter: Tim Leonard Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:4.0.13.max OS:Windows (Windows)
Assigned to: CPU Architecture:Any

[19 Jun 2003 0:26] Tim Leonard
I've been trying to connect to mysql (4.0.13.max) on windows via a remote website.  2/3rds of the time, everything seems fine, even on pages that require 4 or 5 connections.  It seems that connections can sometimes get through successfully, but occasionally a query will respond with "SQLState: S1000 ; Native Error Code: 1045 ; [TCX][MyODBC]Access denied for user: 'user@domain' (Using password: YES)" 

(the same connection string sometimes works and sometimes doesn't!!!)

I've increased timeouts and max connections in mysql and recoded pages so that no more that 5 connections are ever used but it's made little difference.

Have looked for others with a similar problem for the last 2 days and had a look on forums but not found anything useful so I thought I'd post to see if anyone had any suggestions as to whether this a bug or just bad configuration.  (I'm using default settings apart from increasing timeouts to 20 and max connections to 500.  Sorry if this has been brought up elsewhere before.

How to repeat:
If I just use the site making the connections for a few minutes, it occurs.

Have been checking mysql processes at time of errors but there are no more than 5-8 at a time.
[3 Jul 2003 7:31] Michael Widenius
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

To help us find out what is wrong, try to do:

- Start mysqld with --warnings and examine the \mysql\data\mysql.err file for clues.
- Try to simulate this without a web server
- Run the debug version of mysqld with the --debug option and upload the trace file in \mysqld.trace when you get the error to: