I believe that will not be logged unless you have enabled log_warnings. Too
many
connections would normally mean that the number is going beyond the configured
limit and denying new sessions is an expected behavior and should not be an
error really.
Regards,
Nitin
________________________________
From: monloi perez <mlp_fol...@yahoo.com>
To: Ananda Kumar <anan...@gmail.com>
Cc: mysql mailing list <mysql@lists.mysql.com>
Sent: Sat, September 4, 2010 11:37:42 AM
Subject: Re: Logs not working
on the db server? meaning the mysqld log right? THere is really no data for
teh
current error. The last error they said was too much connections and shouldnt
that be logged in mysqld.log?
Thanks,
Mon
________________________________
From: Ananda Kumar <anan...@gmail.com>
To: monloi perez <mlp_fol...@yahoo.com>
Cc: mysql mailing list <mysql@lists.mysql.com>
Sent: Thu, September 2, 2010 6:14:26 PM
Subject: Re: Logs not working
Did u check the logs on the db server, to see what the issue was.
regards
anandkl
On Thu, Sep 2, 2010 at 6:25 AM, monloi perez <mlp_fol...@yahoo.com> wrote:
All,
>
>I'm not sure if this is the right mailing list since the specific mailing lists
>doesn't seem to meet my concern.
>
>For some reason mysql client stops logging to mysqd.log. We had an issue on Aug
>20. But when I checked the log, the latest was on Aug 2.
>Any idea on how to resolve this or what caused it?
>
>Thanks,
>Mon
>
>
>
>
