Just a footnote,

ntpd will not update the time if the offset is more than 1000 seconds. e.g. the clock is more than 15 minutes off.

You have to stop ntpd, run ntpdate, restart ntpd.

regards,

Drew



Bruce N wrote:
Thanks for the input both to Lloyd and Rafael,



This is not a VPs and it's real Quad Core server.



I just did a "service ntpd statud" and it shows running. I don't want to do an 
ntpd restart or update until past office hours due to all recording now being recorded 
under the name June-01 and I don't want to mix everything up. But I definitly want to 
find the root of this problem. Could it have been that the ntp pool servers from CentOS 
misbehaved?





Also, the contents of /etc/ntp.conf is as following:



# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery

# Permit all access over the loopback interface.  This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
restrict -6 ::1

# Hosts on local network are less restricted.
#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
server 0.centos.pool.ntp.org
server 1.centos.pool.ntp.org
server 2.centos.pool.ntp.org




#broadcast 192.168.1.255 key 42         # broadcast server
#broadcastclient                        # broadcast client
#broadcast 224.0.1.1 key 42             # multicast server
#multicastclient 224.0.1.1              # multicast client
#manycastserver 239.255.254.254         # manycast server
#manycastclient 239.255.254.254 key 42  # manycast client

# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available.
server  127.127.1.0     # local clock
fudge   127.127.1.0 stratum 10

# Drift file.  Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
driftfile /var/lib/ntp/drift

# Key file containing the keys and key identifiers used when operating
# with symmetric key cryptography.
keys /etc/ntp/keys

# Specify the key identifiers which are trusted.
#trustedkey 4 8 42

# Specify the key identifier to use with the ntpdc utility.
#requestkey 8

# Specify the key identifier to use with the ntpq utility.
#controlkey 8




From: [email protected]
Date: Wed, 2 Jun 2010 16:24:32 -0400
Subject: Re: [on-asterisk] What could do an automatic Date and Time change on 
CentOS?
To: [email protected]
CC: [email protected]


Hi Bruce


I assume you are using CentOS.

yum -y install ntp


chkconfig ntpd on


service ntpd start

ntpdate pool.ntp.org


It is recommended every time after install os setup the ntpd


Thanks
Lloyd


On Wed, Jun 2, 2010 at 3:42 PM, Bruce N<[email protected]>  wrote:


Hi Guys,



Weired problem here. System clock shifted back by less than a day. I checked the DD-WRT 
router shows proper time. "timeconfig" shows Toronto and uses UTC.



Any idea what could have caused this and how to fix it?



r...@pbx:/var/spool/asterisk/monitor $ clock
Tue 01 Jun - 08:15:45 PM EDT  -0.000278 seconds



Instead of today's time:
Wed 02 Jun - 3:35 P.M.





Thanks,

Bruce


_________________________________________________________________
30 days of prizes: Hotmail makes your day easier! Enter Now.
http://go.microsoft.com/?linkid=9729710
                                        
_________________________________________________________________
Win $10,000 from Hotmail! Enter Here.
http://go.microsoft.com/?linkid=9729708

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to