Bug #46045 wrong log message "time mis-match" in "Agent Monitoring" log

• Submitted: 8 Jul 2009 16:28
• Modified: 9 Jul 2009 11:55
• Reporter: Carsten Segieth
• Status: Can't repeat
• Category: MySQL Enterprise Monitor: Server
• Severity: S3 (Non-critical)
• Version: 2.1.0.1074
• OS: Any
• Assigned to: Carsten Segieth
• CPU Architecture: Any

[8 Jul 2009 16:28] Carsten Segieth

Description:
After starting the agent that monitors the MEM DB itself I get a message into the "Agent Monitoring" log that the agent's and the server's box are 2 h out of sync:

  Warning  	07.07.2009 12:15:30  	qa-merlin time mis-match of: -7199962 milliseconds. Our time: Tue Jul 07 12:15:30 CEST 2009. Agent time: Tue Jul 07 14:15:30 CEST 2009. Agent UUID: 65b3adf3-2dc2-4c2f-a6b9-7e01e21ca879

The time the server detected was the correct time as the server was first time started at ~ 12:07 CEST.

How to repeat:
Not sure whether these steps exact lead again to the problem, but that's what I did:
- install and start a service manager
- install and start an agent on the same that monitors the MEM DB, using TCP/IP (not socket)
- check the "Agent Monitoring" log

[9 Jul 2009 11:55] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
added the an agent with same steps in 2.1.0.1075 did not show this problem. Will open it again if problem occures again.