MySQL Bugs: #42044: agent msqld connect failure should be critical log level

Bug #42044	agent msqld connect failure should be critical log level
Submitted:	12 Jan 2009 10:54	Modified:	28 Jan 2009 17:02
Reporter:	Oli Sennhauser	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Agent	Severity:	S3 (Non-critical)
Version:	2.0.0.7111	OS:	Any
Assigned to:	MC Brown	CPU Architecture:	Any

Description:
Customer had problems with the agent but there was no message in the agent log file.

After increasing log-verbosity to message the following message came up:

2009-01-12 13:34:43: (warning) agent_mysqld.c:600: agent connecting to mysql-server failed: mysql_real_connect(host = '127.0.0.1', port = 3306, socket = ''): Lost connection to MySQL server at 'reading initial communication packet', system error: 0 (mysql-errno = 2013)

How to repeat:
n.a.

Suggested fix:
IMHO by default at least warning and higher should appear in a log file.

Fix pushed to 2.0 branch, should make next 2.0.3 build.

Verified fixed on 2.0.3.7134

We now see a message like

2009-01-22 11:08:00: (critical) agent_mysqld.c:606: agent connecting to mysql-server failed: mysql_real_connect(host = '127.0.0.1', port = 43308, socket = ''): Can't connect to MySQL server on '127.0.0.1' (61) (mysql-errno = 2003)

Did you change the default level of messages that appear in the log file, or did you just change that particular message level from 'warning' to 'critical' in order to make it appear?

An entry was added to the 2.0.3 changelog:

The Service Agent failed to connect to the server, and no error message was displayed in the log file.

However, when the log verbosity level was set to message, the following message was recorded:

2009-01-12 13:34:43: (warning) agent_mysqld.c:600: agent connecting to mysql-server
failed: mysql_real_connect(host = '127.0.0.1', port = 3306, socket = ''): Lost connection
to MySQL server at 'reading initial communication packet', system error: 0 (mysql-errno =
2013)