Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

An alert message that the Manager Node clock is no in sync with the database clock appears in Deep Security

    • Updated:
    • 11 Sep 2015
    • Product/Version:
    • Deep Security 8.0
    • Deep Security 9.0
    • Deep Security 9.5
    • Deep Security 9.6
    • Platform:
    • Windows 2000 Advanced Server
    • Windows 2000 Datacenter Server
    • Windows 2000 Professional
    • Windows 2000 Server
    • Windows 2000 Small Business Server
    • Windows 2003 Compute Cluster Server
    • Windows 2003 Datacenter Server
    • Windows 2003 Datacenter Server Edition 64-bit
    • Windows 2003 Enterprise Server
    • Windows 2003 Home Server
    • Windows 2003 Small Business Server
    • Windows 2003 Standard Server Edition
    • Windows 2003 Standard Server Edition 64-bit
    • Windows 2003 Storage Server
    • Windows 2003 Web Server Edition
    • Windows 2008 Datacenter Server
    • Windows 2008 Datacenter Server Edition 64-bit
    • Windows 2008 Enterprise Server
    • Windows 2008 Enterprise Server Edition 64-bit
    • Windows 2008 Essential Business Server
    • Windows 2008 Small Business Server
    • Windows 2008 Standard Server Edition
    • Windows 2008 Standard Server Edition 64-bit
    • Windows 2008 Storage Server
    • Windows 2008 Web Server Edition
    • Windows 2008 Web Server Edition 64-bit
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows NT 4.0 Server
    • Windows NT 4.0 Workstation
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Home
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary
You receive an alert similar to the following:
The clock Manager Node must be synchronized with the clock on the database. If the clocks are too far out of sync (more than 30 seconds) the Manager Node will not perform its tasks correctly. Synchronize the clock on your Manager Node with the clock on the database.
This is an issue with the Java Virtual Machine (JVM) that the Deep Security Manager (DSM) is using.
Details
Public
To resolve this, verify the system on each box. Their time difference should be within 30 seconds.
If the two system times are within 30 seconds away from each other, then it is possible that the computer's time zone was set to GMT when the DSM service started, and the time zone was changed while the DSM was running.
In this case, the DSM and database machines can be out of sync and the DSM will generate an alert.
You should restart the DSM for you not to receive the alert.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1056540
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.