Waltet, I think you are not the only one shooting in the dark, in this case reading the manual can really help. aborted_connects is increased by a failed attempt to connect to MySQL (wrong password?) but NOT by a timed-out client. Could be a cron job setup with some credentials that were changed without updating it, or other similar things. There is a very bad habit of not setting the root password (or to put it in the my.cnf) so sometimes mysql client is considered just a bash command and included as it in scripts. As long as you dont experience problems the simple increase of the value is not a critical issue. Check the logs of the application(s) ,if any, to see if some part of it is actually affected.
Cheers Claudio On 30 dec 2009 20:31, "Walter Heck - OlinData.com" <li...@olindata.com> wrote: Random shot in the dark: I've seen this happen with some monitoring tools that just check to see if the database is up. Walter On Wed, Dec 30, 2009 at 17:13, Jeetendra Ranjan <jeetendra.ran...@sampatti.com> wrote: > Hi, > > My MySQL server Aborted_connects status is showing 8692 and is rapidly increasing. > > Wha... -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: ht...
