Bug #54002 | Agent can reach database but it shows down in the dashboard | ||
---|---|---|---|
Submitted: | 26 May 2010 16:01 | Modified: | 3 Aug 2010 7:46 |
Reporter: | Roger David Nay | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Agent | Severity: | S2 (Serious) |
Version: | 2.2.0.1709 | OS: | Any |
Assigned to: | Kay Roepke | CPU Architecture: | Any |
[26 May 2010 16:01]
Roger David Nay
[11 Jun 2010 11:59]
Enterprise Tools JIRA Robot
Kay Roepke writes: Reopening, as it does not seem to be related to EM-4320 / Bug#52952 as the latest debug log does not show timeouts.
[22 Jun 2010 19:04]
Enterprise Tools JIRA Robot
Andy Bang writes: In build 2.2.2.1727.
[30 Jun 2010 18:46]
Enterprise Tools JIRA Robot
Diego Medina writes: Making Carsten the QA as he has access to servers with network shared drives
[3 Aug 2010 7:46]
MC Brown
A note has been added to the 2.2.2 changelog: A &merlin_agent; could report the a MySQL instance as being down, even though the instance was available. This was related to the way local and remote filesystems were identified and reported by &merlin_agent;. A new option, <option>--agent-report-network-fs</option> has been added to indicate whether remote filesystems should be reported in the diskspace reports. By default, the &merlin_agent; no longer reports network filesystem information, only data for local filesystems.