Under UNIX/linux use syslog, for me /var/log/messages shows login/auth error
Mar 6 05:39:11 orion pdns[1865]: gmysql Connection failed: Unable to
connect to database: Access denied for user 'root'@'localhost' (using
password: NO)
Now for dropped sockets/connections you need to enable logging for this kind
of thing in your connector and/or pooling software. I don't think this
exists on the server side as it is not so simple to determine the actual
cause.
Let's say your router/switch drops connections, to server this looks like
TCP socket timeouts and eventually will try to close the connection as such,
but was it dropped or was it just left open and not closed properly by the
client.
This is why it makes sense to track these things in your data
connector/pooling, with your kind of load you should have this kind of
connection tracing/logging enabled in the client side and/or middle tier
anyway.
Just my $0.02 worth.
-Daniel.
-Original Message-
From: Michael Loftis [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 08, 2005 2:45 PM
To: mysql@lists.mysql.com
Subject: mysql error logging
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]
!DSPAM:422e00ff75662101317344!
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
