No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


1 hour time delay between alarm at device and eSight HA SuSe Linux edition

Publication Date:  2016-06-30 Views:  776 Downloads:  0
Issue Description

We use eSight eSight V300R003C20SPC101  HA edition, based on  SuSe Linux 11 SP3.

We noticed that alarm report time at device (AC6605) is right and real, but eSight showed the same alarm and logs with 1 hour delay.

Handling Process

We checked SuSe system time and timezone (Moscow). It was correct.

YaST2 Control Center, choose System and click Data and Time.

 Checked device current time (display clock) it was also correct and the same as at Linux.

Used several CLI commands at Linux terminal.


Root Cause


 Moscow has changed time from UTC+4 to UTC+3 at 26.10.2014.

         Two parts from SUSE, time doesn’t match. Linux with time UTC+4; JRE with time UTC +3 ( eSight get time form JRE interface).

         Current time zone configure is UTC+4:



Install SUSE time zone patch at : ( 2 files)

         Install guide:

                   1, Change both eSight server’s time into UTC+4. That means 1 hour faster than your local time.

                   2, Using rpm -Uvh --nodeps *.rpm command to install both attached patches at 2 servers.

                   3, Using date –R to see if it’s changed successfully


                   4,Restart esight.

After applying patch time at eSight logs and device logs became the same.