Bug #46926 mysql-monitor-agent -- agent-generate-uuid tries to open proxy socket
Submitted: 26 Aug 2009 5:54 Modified: 9 Jan 2015 14:39
Reporter: Andrew Dalgleish Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version:2.0.5, 2.1.0, 2.0.6 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[26 Aug 2009 5:54] Andrew Dalgleish
Description:
If the agent is currently running or port 4040 is already in use, you can't generate a new UUID.
The agent aborts with the following error:
(critical) network-socket.c.464: bind(:4040) failed: Address already in use (98)

One work-around is to use a temporary mysql-monitor-agent.ini file containing only this:
[mysql-agent]
proxy-address=

shell> /opt/mysql/enterprise/agent/bin/mysql-monitor-agent --defaults-file=temp.ini --agent-generate-uuid

How to repeat:
Install and run the agent on port 4040, generate a new UUID by running

shell> /opt/mysql/enterprise/agent/bin/mysql-monitor-agent --agent-generate-uuid

Suggested fix:
Don't try to open the proxy port when generating a UUID.
[28 Aug 2009 10:19] Sveta Smirnova
Thank you for the report.

Verified as described. It does not report failure also.
[28 Aug 2009 13:50] Jan Kneschke
instead of using:

  --default-file=... (which may load the proxy plugin)

just start the agent like:

  $ mysql-monitor-agent --plugins=agent --agent-generate-uuid

That will only load the agent plugin and all generate the UUID.
[11 Sep 2009 19:11] Enterprise Tools JIRA Robot
Gary Whizin writes: 
Need to:
1) document the workaround (not just in the change log but in the main docs)
2) have installer use the workaround (will create separate bug)