Bruce,
Take a look at this
http://www.linux.org/docs/ldp/howto/Clock-3.html
You are probably getting the time of the onboard real time clock.
To sync the two, type hwclock -w
or do a man hwclock to get all the options.
Martin
On 06/02/2010 03:53 PM, Bruce N wrote:
Thanks for that. Here is what I am getting:
r...@pbx:~ $ service ntpd stop
Shutting down ntpd: [ OK ]
r...@pbx:~ $ ntpdate pool.ntp.org
2 Jun 17:47:20 ntpdate[4349]: step time server 209.167.68.100 offset
70370.4485
33 sec
r...@pbx:~ $ service ntpd start
Starting ntpd: [ OK ]
r...@pbx:~ $ clock
Tue 01 Jun 2010 10:14:38 PM EDT -0.000768 seconds
Offset by 70370 really!!!! and then back to June 1st again?!
Thanks for the input.
-Bruce
Date: Wed, 2 Jun 2010 17:45:28 -0400
Subject: Re: [on-asterisk] What could do an automatic Date and Time change on
CentOS?
From: [email protected]
To: [email protected]
Bruce,
You need to stop ntp and then try the ntpdate (ntpdate won't run if ntpd is
running), and if that goes well you can then start ntp again.
Rafael
On Wed, Jun 2, 2010 at 5:28 PM, Bruce N<[email protected]> wrote:
Thanks for the input.
Amazing how these very important aspects of the server just go bad all a
sudden. You kind of appreciate Nortel at times...
r...@pbx:/sbin $ service ntpd restart
Shutting down ntpd: [ OK ]
Starting ntpd: [ OK ]
r...@pbx:/sbin $ clock
Tue 01 Jun 2010 09:55:49 PM EDT -0.000717 seconds
Seems it didn't do the trick either. I am guessing something in the configs is
wrong even though I didn't change anything.
-Bruce
Date: Wed, 2 Jun 2010 17:18:35 -0400
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [on-asterisk] What could do an automatic Date and Time change on
CentOS?
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
_________________________________________________________________
30 days of prizes to be won with Hotmail. Enter Here.
http://go.microsoft.com/?linkid=9729709
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
