Hi,
the date jumps within 30 seconds to a wrong value. ntp service is stopped at the beginning.
Whereas hwclock seems more precise.
[root@kerio ~]# service ntpd stop
Shutting down ntpd: [ OK ]
[root@kerio ~]# ntpdate 0.centos.pool.ntp.org
13 Mar 07:04:48 ntpdate[23003]: step time server 131.234.137.24 offset -3450.678273 sec
[root@kerio ~]# hwclock
Fri 13 Mar 2009 07:04:59 AM GMT -0.014767 seconds
[root@kerio ~]# date
Fri Mar 13 07:05:02 GMT 2009
[root@kerio ~]# date
Fri Mar 13 07:05:14 GMT 2009
[root@kerio ~]# date
Fri Mar 13 08:03:01 GMT 2009
[root@kerio ~]# hwclock
Fri 13 Mar 2009 07:05:37 AM GMT -0.083628 seconds
[root@kerio ~]#
/etc/ntp.conf is in original configuration.
Remarks:
- most of our servers run without X-Windows, this uses X-Windows and Gnome.
- the server runs kerio mail services. Even the original from kerio configured VMWare server has had this behavior.
- stopping of keriomailserver does not help
Helmut
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Helmut Drodofsky Sent: Friday, March 13, 2009 8:25 AM To: centos@centos.org Subject: [CentOS] date differs permanent some 3450 sec.
Hi,
the date jumps within 30 seconds to a wrong value. ntp service is stopped at the beginning.
Daylight time savings in effect? The timeserver is incorrect (rather farfetched though)?
"Ntpdate 0.centos.pool.ntp.org" seems awfully specific. Normally those time pools use geoip or some such mechanism to connect to the right pool and usually connect you to a close mirror, or at least on the same continent. Perhaps you're checking with the wrong time-server? Can you try some other ntp-server?
Speculations, speculations...
From: Helmut Drodofsky drodofsky@internet-xs.de
the date jumps within 30 seconds to a wrong value. ntp service is stopped at the beginning. [root@kerio ~]# ntpdate 0.centos.pool.ntp.org 13 Mar 07:04:48 ntpdate[23003]: step time server 131.234.137.24 offset -3450.678273 sec
Not sure what is going on but maybe try ntpdate with -B...
JD
Ntpdate sets the correct time. Within 30 seconds, time will be resettet! >From who?
Helmut
-----Ursprüngliche Nachricht----- Von: centos-bounces@centos.org [mailto:centos-bounces@centos.org] Im Auftrag von John Doe Gesendet: Freitag, 13. März 2009 10:59 An: CentOS mailing list Betreff: Re: [CentOS] date differs permanent some 3450 sec.
From: Helmut Drodofsky drodofsky@internet-xs.de
the date jumps within 30 seconds to a wrong value. ntp service is stopped at the beginning. [root@kerio ~]# ntpdate 0.centos.pool.ntp.org 13 Mar 07:04:48 ntpdate[23003]: step time server 131.234.137.24 offset -3450.678273 sec
Not sure what is going on but maybe try ntpdate with -B...
JD
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
why don't you give any information about your system? If that is in a VM you better read the posts in centos-virt.
Kai
On Mar 13, 2009, at 3:24 AM, "Helmut Drodofsky" <drodofsky@internet-xs.de
wrote:
Hi,
the date jumps within 30 seconds to a wrong value. ntp service is stopped at the beginning.
Whereas hwclock seems more precise.
[root@kerio ~]# service ntpd stop
Shutting down ntpd: [ OK ]
[root@kerio ~]# ntpdate 0.centos.pool.ntp.org
13 Mar 07:04:48 ntpdate[23003]: step time server 131.234.137.24 offset -3450.678273 sec
[root@kerio ~]# hwclock
Fri 13 Mar 2009 07:04:59 AM GMT -0.014767 seconds
[root@kerio ~]# date
Fri Mar 13 07:05:02 GMT 2009
[root@kerio ~]# date
Fri Mar 13 07:05:14 GMT 2009
[root@kerio ~]# date
Fri Mar 13 08:03:01 GMT 2009
[root@kerio ~]# hwclock
Fri 13 Mar 2009 07:05:37 AM GMT -0.083628 seconds
[root@kerio ~]#
/etc/ntp.conf is in original configuration.
Remarks:
- most of our servers run without X-Windows, this uses X-Windows and
Gnome.
- the server runs kerio mail services. Even the original from kerio
configured VMWare server has had this behavior.
- stopping of keriomailserver does not help
If your hwclock stores local time and your BIOS adjusts it for DST that would cause a 3600 second time difference or if your hwclock stores UTC and the BIOS adds an hour to that...
Turn off any BIOS DST adjust feature if it's enabled.
-Ross
If your hwclock stores local time and your BIOS adjusts it for DST that would cause a 3600 second time difference or if your hwclock stores UTC and the BIOS adds an hour to that...
Turn off any BIOS DST adjust feature if it's enabled.
OP: Did the problem start when DST took affect?
If not, then the theory that DST hardware/software features/bugs seems to be invalidated. Of course, the inverse could be true as well.
Andy
-
Andrew Hull -
Helmut Drodofsky -
John Doe -
Kai Schaetzl -
Ross Walker -
Sorin Srbu