Bug #46929 /etc/init.d/mysql-monitor-agent does not detect failures
Submitted: 26 Aug 2009 6:55 Modified: 28 Aug 2009 10:13
Reporter: Andrew Dalgleish Email Updates:
Status: Verified Impact on me:
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version:2.0.5, 2.1.0, 2.0.6 OS:Linux
Assigned to: Assigned Account CPU Architecture:Any

[26 Aug 2009 6:55] Andrew Dalgleish
If mysql-monitor-agent fails to start, /etc/init.d/mysql-monitor-agent still prints a green "OK" and creates the redhat subsys lock files.

How to repeat:
Create an error in the mysql-monitor-agent.ini file so that the agent fails to start.

For example, specifying a proxy-address port which is already in use.
[28 Aug 2009 10:14] Sveta Smirnova
Thank you for the report.

Verified as described.
[22 Sep 2009 16:01] Enterprise Tools JIRA Robot
Jan Kneschke writes: 
Either add a new startup phase and try out the config-options before we turn into a daemon or the daemon reports in some way it is "ready" now.