Bug #38672 agent logging of mysqld instance connection problems inadequate
Submitted: 8 Aug 2008 15:07 Modified: 16 Sep 2008 10:25
Reporter: Sloan Childers Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version:2.0.0.7021 OS:Any
Assigned to: Kay Roepke CPU Architecture:Any

[8 Aug 2008 15:07] Sloan Childers 
Description:
I re-installed the dashboard but still had no luck. After working with JohanI and #merlin we determined that the agent was only sending OS data, it was unable to connect to mysql. After changing "localhost" to "127.0.0.1" things started working. Even with the agent log level set to debug this was not obvious. 

How to repeat:
Use the wrong IP address in the agent mysqld instance connection configuration and look for an appropriate log message.

Suggested fix:
Review agent startup configuration logging and make sure everything that can go wrong is logged at an appropriate level.
[16 Sep 2008 10:25] Carsten Segieth 
tested OK with 2.0.0.7049
- both problems with wrong IP and wrong user/pwd are logged in default mode.