MySQL Bugs: #27007: Agent does not log failed agent username/password combinations by default

Bug #27007	Agent does not log failed agent username/password combinations by default
Submitted:	9 Mar 2007 17:01	Modified:	30 May 2007 13:40
Reporter:	Harrison Fisk	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Agent	Severity:	S3 (Non-critical)
Version:	1.0.0	OS:	Linux (Linux 2.6.15 (Ubuntu 6.06 LTS))
Assigned to:	Jan Kneschke	CPU Architecture:	Any
Tags:	mer 111

Description:
The MySQL Network service agent does not log when it is setup with the wrong username/password for sending information to the tomcat server.  In the test case the agent was accidently setup with the administrator's username/password.

It is possible to get the information if you increase the log-level to debug, but the information should be logged by default.  Critical errors such as this, should be logged by default.

How to repeat:
1.  Setup an agent with an incorrect username/password
2.  Start it up
3.  Notice it never appears in the dashboard and nothing is logged
4.  Restart with log-level=debug
5.  Notice the error is now logged

Suggested fix:
Log the failed authentication by default.

a patch is applied in [5634].

Checked with build 1.1.1.5646, and it does not log error to agent log file unless log-level=debug.

fixed ... again in 1.1.1 [5702] and trunk/ [5701]

Verified that the agent will log the error and shut down in version 1.1.1.5725.

Added to the changelog. Also documented in the section on troubleshooting the agent.