Bug #74101 Error monitoring a pacemaker cluster
Submitted: 26 Sep 2014 8:57 Modified: 10 Apr 2015 4:56
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Monitor Severity:S2 (Serious)
Version:3.0.14 OS:Any
Assigned to: CPU Architecture:Any

[26 Sep 2014 8:57] Daniël van Eeden 
Description:
Situation:
pacemaker cluster with MySQL listening on the cluster ip.
the agent is running on the first node in the cluster and is monitoring the cluster ip.

When the database became unavailable I would expect an EMERGENCY or CRITICAL alert, but none came.

In MEM the status was 'Bad Connection' / 'No route to host'.

How to repeat:
Monitor via a virtual IP on a pacemaker cluster.
[26 Sep 2014 9:33] Daniël van Eeden 
Eventually a 'MySQL server is UNREACHABLE' alert was generated.

Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
Caused by: java.net.NoRouteToHostException: No route to host
[12 Feb 2015 14:54] Mark Matthews 
Hi Daniel,

Would it be possible for us to see a copy of the logs from the agent monitoring this target? I'd like to see the sequence of events so we can see why it took us longer to convert this to "instance down" than I'd like.

You can attach them here, or you can file an SR with Oracle Support and attach them to the SR.

Thanks!

  -Mark