Comments on: How to track down the source of Aborted_connects http://www.mysqlperformanceblog.com/2008/08/23/how-to-track-down-the-source-of-aborted_connects/ Everything about MySQL Performance Sat, 21 Nov 2009 05:23:57 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: peter http://www.mysqlperformanceblog.com/2008/08/23/how-to-track-down-the-source-of-aborted_connects/comment-page-1/#comment-348454 peter Sun, 24 Aug 2008 17:04:18 +0000 http://www.mysqlperformanceblog.com/?p=475#comment-348454 Baron, Antony Indeed Audit extensions are must to have in MySQL. At least very basics it would be good to split Aborted_connects to network related and Authentication_Failures as these are very different events. Aborted_clients may also benefit splitting somehow because unexpected aborts (network related) are not the same as aborts when client exists without closing connection or because wait_timeout seconds passed. Baron, Antony

Indeed Audit extensions are must to have in MySQL.
At least very basics it would be good to split Aborted_connects to network related and Authentication_Failures as these are very different events.
Aborted_clients may also benefit splitting somehow because unexpected aborts (network related) are not the same as aborts when client exists without closing connection or because wait_timeout seconds passed.

]]> By: Arjen Lentz http://www.mysqlperformanceblog.com/2008/08/23/how-to-track-down-the-source-of-aborted_connects/comment-page-1/#comment-348327 Arjen Lentz Sun, 24 Aug 2008 11:38:19 +0000 http://www.mysqlperformanceblog.com/?p=475#comment-348327 Many things that are not being built in/for proxy and enterprise monitor should be direct server features or plugins. That not being the case is not a technical decision but one of product marketing. And I *DO NOT LIKE IT*. IMHO the "but we need to make money" argument is a wussy cop-out. It's just so that people don't have to use their imagination a bit more. What a pity. Such good things could come of looking for real opportunities. Many things that are not being built in/for proxy and enterprise monitor should be direct server features or plugins.
That not being the case is not a technical decision but one of product marketing. And I *DO NOT LIKE IT*.
IMHO the “but we need to make money” argument is a wussy cop-out. It’s just so that people don’t have to use their imagination a bit more. What a pity. Such good things could come of looking for real opportunities.

]]> By: Baron Schwartz http://www.mysqlperformanceblog.com/2008/08/23/how-to-track-down-the-source-of-aborted_connects/comment-page-1/#comment-348113 Baron Schwartz Sat, 23 Aug 2008 19:44:03 +0000 http://www.mysqlperformanceblog.com/?p=475#comment-348113 It's too bad it's not in the server! There's no possibility of patching the server in most cases like this. It’s too bad it’s not in the server! There’s no possibility of patching the server in most cases like this.

]]> By: Antony Curtis http://www.mysqlperformanceblog.com/2008/08/23/how-to-track-down-the-source-of-aborted_connects/comment-page-1/#comment-348108 Antony Curtis Sat, 23 Aug 2008 19:36:44 +0000 http://www.mysqlperformanceblog.com/?p=475#comment-348108 If you were to dig out one of my earlier Audit patches for MySQL, you could have hooked a plugin on the aborted connect event and no need to mess about with tcpdump. If you were to dig out one of my earlier Audit patches for MySQL, you could have hooked a plugin on the aborted connect event and no need to mess about with tcpdump.

]]>