I have one centos 5.8 Linux server. I am experiencing a bit strange issue and figured out it is something with system time. When I check date command, outputs are really strange. Here is example:
[root@web ~]# date
Thu Feb 19 21:21:59 JST 2015
[root@web ~]# date
Thu Feb 19 21:23:43 JST 2015
[root@web ~]# date
Thu Feb 19 21:22:02 JST 2015
[root@web ~]# date
Thu Feb 19 21:23:45 JST 2015
[root@web ~]#
As you can see each date command outputs different time. It seems there are two different system time? Does anybody know what causes this and potential fix to this?
UPDATE
This server is not virtual machine. It has two x64 Dual Core Processors. Same processors.
UPDATE 2
hwclock -r
result:
[root@web ~]# hwclock -r --utc
Mon Dec 29 21:37:14 2014 -101.846756 seconds
[root@web ~]# hwclock -r --utc
Mon Dec 29 21:37:15 2014 -101.908926 seconds
[root@web ~]# hwclock -r --utc
Mon Dec 29 21:37:16 2014 -102.393569 seconds
[root@web ~]# hwclock -r --utc
Mon Dec 29 21:37:19 2014 -101.846761 seconds
[root@web ~]# hwclock -r --utc
Mon Dec 29 21:37:20 2014 -101.846721 seconds
[root@web ~]# hwclock -r --utc
Mon Dec 29 21:37:21 2014 -102.065391 seconds
[root@web ~]# hwclock -r --utc
Mon Dec 29 21:37:22 2014 -102.581079 seconds
update 3
date; hwclock -r
result
[root@web ~]# date; hwclock -r --utc
Thu Feb 19 21:42:38 JST 2015
Mon Dec 29 21:42:38 2014 -0.016165 seconds
[root@web ~]# date; hwclock -r --utc
Thu Feb 19 21:42:38 JST 2015
Mon Dec 29 21:42:39 2014 -0.156442 seconds
[root@web ~]# date; hwclock -r --utc
Thu Feb 19 21:42:39 JST 2015
Mon Dec 29 21:42:40 2014 -0.125509 seconds
[root@web ~]# date; hwclock -r --utc
Thu Feb 19 21:42:40 JST 2015
Mon Dec 29 21:42:41 2014 101.812663 seconds
[root@web ~]# date; hwclock -r --utc
Thu Feb 19 21:42:42 JST 2015
Mon Dec 29 21:42:42 2014 -0.016169 seconds
[root@web ~]#
UPDATE 4
some logs related to ntpd:
Feb 19 20:01:33 web ntpd[1759]: time reset -103.081446 s
Feb 19 20:07:16 web ntpd[1759]: synchronized to 210.188.224.14, stratum 2
Feb 19 20:26:31 web ntpd[1759]: time reset -103.082073 s
Feb 19 20:31:36 web ntpd[1759]: synchronized to LOCAL(0), stratum 10
Feb 19 20:32:40 web ntpd[1759]: synchronized to 210.188.224.14, stratum 2
Feb 19 20:49:39 web ntpd[1759]: time reset -103.081776 s
Feb 19 20:54:50 web ntpd[1759]: synchronized to LOCAL(0), stratum 10
Feb 19 20:55:30 web ntpd[1759]: synchronized to 210.188.224.14, stratum 2
Feb 19 21:18:11 web ntpd[1759]: time reset -103.082092 s
Feb 19 21:23:43 web ntpd[1759]: synchronized to LOCAL(0), stratum 10
Feb 19 21:24:49 web ntpd[1759]: synchronized to 210.188.224.14, stratum 2
Feb 19 21:40:57 web ntpd[1759]: time reset -103.082297 s
Feb 19 21:46:05 web ntpd[1759]: synchronized to 210.188.224.14, stratum 2
UPDATE 5
I have another identical server with exact same setup, but only this one has this issue at this moment. The logs above only appears in the server with the issue.