Bug #46449 Add option for force ipv4 or ipv6 communications between agent and dashboard
Submitted: 29 Jul 2009 13:03 Modified: 20 Apr 2010 14:55
Reporter: Mark Leith Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S4 (Feature request)
Version:2.1.0 OS:Any
Assigned to: Michael Schuster CPU Architecture:Any
Tags: ipv4, ipv6

[29 Jul 2009 13:03] Mark Leith 
Description:
The agent and server both support ipv6, however if ipv6 support is enabled but not configured on the agent server, and enabled and configured properly on the dashboard server, the agent gets a full list of the interfaces available via a DNS lookup, and tries to connect to the ipv6 address without having the transport available locally, leading to errors such as:

2009-07-28 11:46:28: (critical) network-io.c:220: curl_easy_perform('http://agent:*****@monitor.domain.com:18080/heartbeat';) failed: Failed to connect to 2001:a18:1:6::221: Network is unreachable (curl-error = 'Couldn't connect to server' (7))

How to repeat:
o Install the dashboard on a server with ipv4 and ipv6 fully enabled and configured
o Install the agent on a server with ipv4 full enabled, and ipv6 enabled but not configured
o Use a domain name instead of IPv4 address for the dashboard hostname from the agent
o Try and start the agent

Suggested fix:
o Provide an option to force either ipv4 or ipv6 communications
o By default, attempt ipv6, and if that fails, fall back to the ipv4 address listed from the DNS server
[6 Jan 2010 0:06] Enterprise Tools JIRA Robot 
Keith Russell writes: 
Patch installed in versions => 2.2.0.1595.
[15 Jan 2010 18:44] Enterprise Tools JIRA Robot 
Diego Medina writes: 
Is there any log entry that confirms that the agent is using ipv[4|6] ?

I tried using invalid values (like 7) and I saw no error message telling me I had the wrong value.
[25 Mar 2010 18:41] Enterprise Tools JIRA Robot 
Keith Russell writes: 
Patch installed in versions => 2.2.0.1611.
[30 Mar 2010 13:44] Enterprise Tools JIRA Robot 
Diego Medina writes: 
Verified fixed on  2.2.0.1665
[20 Apr 2010 14:55] MC Brown 
Fix is in pre-release version; no changelog entry required.

Agent options are already documented.