Bug #45937 server 'down' reported from mismatching UTC date/time of server and agent
| Submitted: | 3 Jul 2009 12:44 | Modified: | 21 Jul 2009 14:34 |
|---|---|---|---|
| Reporter: | Carsten Segieth | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Server | Severity: | S3 (Non-critical) |
| Version: | 2.1.0.1073 | OS: | Any |
| Assigned to: | Eric Herman | CPU Architecture: | Any |
[3 Jul 2009 12:44]
Carsten Segieth
[3 Jul 2009 14:36]
Eric Herman
Now track a "Reporting Delay (ms)": the difference (in milliseconds) between the MEM Dashboard's time when it receives the agent request, and the data in the "utc" field of the agent's request packet. Added the "Reporting Delay (ms)" to the UI both on the main dashboard page with a single server highlighted, as well as the Manage Servers page. Logs a warning once (per agent restart) if more than 1/2 hour out-of-synch.
[6 Jul 2009 21:45]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch applied in versions => 2.1.0.1074.
[9 Jul 2009 21:11]
Enterprise Tools JIRA Robot
Carsten Segieth writes: tested OK in 2.1.0.1075, the log message shows the difference and also the Meta Info now contains this info.
[21 Jul 2009 14:34]
Tony Bedford
An entry was added to the 2.1.0 changelog: If the Agent and monitored server had time settings that were out of sync the Enterprise Dashboard reported the server as “down”.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.