Bug #47376 Agent is unable to start shouldn't affect proxy and more proxy logging
Submitted: 16 Sep 2009 13:30 Modified: 9 Jan 2015 10:36
Reporter: Roger David Nay Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S4 (Feature request)
Version:2.0+ OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[16 Sep 2009 13:30] Roger David Nay
Description:
Please ensure that if the agent is unable to start all instances that this does not directly affect the behaviour of the proxy. 

How to repeat:
N/A

Suggested fix:
It would also be convenient to log that the proxy port is "up" and to where it will send incoming connections.

Current logging shows:

2009-09-16 10:45:26: (critical) network-io.c:217: curl_easy_perform('https://merlin_agent:xxxxxx@d-merlin-v.dqs.lhr1.bbb.com:443/heartbeat') failed: SSL connection timeout (curl-error = 
'Timeout was reached' (28), os-error = 'Connection refused' (111))
2009-09-16 10:45:42: (critical) last message repeated 1 times
2009-09-16 10:45:42: (critical) network-io.c:257: successfully reconnected to dashboard at https://merlin_agent:xxxxxx@d-merlin-v.dqs.lhr1.bbb.com:443/heartbeat
2009-09-16 10:45:47: (critical) scheduler.c:778: in list_known_data_items state
2009-09-16 10:45:47: (critical) agent_mysqld.c:643: successfully connected to database at avpprod-vip3:3306 as user merlin_agent_dev (with password: YES)
2009-09-16 10:45:47: (critical) agent_mysqld.c:643: successfully connected to database at d-merlin-v:3306 as user merlin_agent_dev (with password: YES)
2009-09-16 10:45:47: (critical) job_collect_mysql.c:720: [avrdbprod-vip3->avpprod-vip:3306] (master-uuid) mysql_real_query(SELECT value FROM mysql.inventory WHERE name='uuid') on the slave's m
aster failed: SELECT command denied to user 'repl'@'dc01mdb-03.dqs.lhr1.bbb.com' for table 'inventory' (1142)
Check that mysql.inventory exists on this slave's master, if it does, run on the master:
GRANT SELECT ON mysql.inventory TO 'repl'@'%';
2009-09-16 10:47:00: (critical) last message repeated 2 times

Please add something like:

proxy configuration: up and listening on ":4041"
proxy configuration: connections will be sent to: "d-merlin-v.dqs.lhr1.bbb.com:3306"

If the proxy "decides" not to start up please add something like:

proxy configuration: failed to startup proxy, reason: .....................