OK I've honestly banged my head against everying, but as far as I can tell MySQL has *NO* real logging support. You have three options, log everything as text, log all queries as binary, or nothing.

What I want/NEED is connection logging and some sort of ERROR logging. I'm getting an increasingly large amount of client connections that get apparently dropped during queries to the mysql server (error 2013) but the timeout issue is not possible (first it's default hour long timeout, secondly the connections are NOT persistent)

Is there anything that can be done to get mysql to log the errors as they occur with the clients? Or to get it to log when it opens/closes a connection with the client and the disposition of that connection? Something would be better than what it does now which is all-or-nothing. Makes diagnosing anything impossible since I'm handling ~2k queries/sec. We have a binary log (necessary for our slave replica) and aren't under any load crunch nor I/O crunch on the DB drives, we're not experiencing ANY performance issues, just theres a goodly number of these connection dropped by server messages being reported.

There has *GOT* to be SOME sort of useful logging in MySQL without having to turn on *full* text logging, which completely kills the server.

All I need are connect/disconnect and disconnect reasons, I also *NEED* authentication failures but the thing doesn't log those EITHER. I'm starting to have a hard time believing I'm the only one complaining about this so I must be missing something, but the only logging options I've found cause full logging which can not be done.

MySQL Version is 4.0.23

--
Michael Loftis
Modwest Operations Manager
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to