View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 10 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Mon Feb 13, 2006 8:09 pm 
Offline
Joined: Mon Feb 13, 2006 7:10 pm
Posts: 36
Location: Australia
Does anyone have any idea why ntpdate consistently updates my system time 103 seconds slow (give or take a few seconds)? Same result occurs when using different servers too... What's going on?


Top
 Profile  
 
 Post subject:
PostPosted: Mon Feb 13, 2006 8:28 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
You're not providing a lot of details here, which makes it kind of hard to draw any useful conclusions... The ntp update on my system seems to be dead on when I compare it to the atomic clock page at http://www.time.gov/. This is default configuration that new releases set up automatically with no monkeying around.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Feb 13, 2006 8:59 pm 
Offline
Joined: Mon Feb 13, 2006 7:10 pm
Posts: 36
Location: Australia
More specifically...
If I set the correct time manually (referenced against an XP machine syncing to time.windows.com) and then run ntpdate, the time sets back 103 seconds. Ntp-server is set to run at boot, and ntpd seems to result in the same thing - 103 seconds out. I've tried various ntp servers both in Australia and internationally, as well as trying the pool.ntp.org servers.

Being an nVidia chipset mobo I looked into a time sync problem to do with nForce 2 chipsets, but it didn't seem to apply to the nForce 4.

System:
Knoppmyth R5A30.1
Athlon 64 3200
Gigabyte GA-K8NF-9 M/B (nForce 4 chipset)
1Gb RAM
Winfast nVidia PCI-E video


Top
 Profile  
 
 Post subject:
PostPosted: Mon Feb 13, 2006 10:02 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Have you checked the Windows time source against other references and checked the time that you system is set to by NTP against them as well? Also have you made sure that the hardware clock and the system clock agree? It looks like the Aus. equivalent of the NIST is NMI which has a Cesium clock and an ntp server, and I would guess that it should be pretty definitive.

I definitely don't think your hardware has anything to to with it (other than the time setting in your BIOS). None of the clock drift issues I know of don't instantly swittch the time by 103 seconds. I think you're comparing apples to durian.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 14, 2006 7:54 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
So you sync your time against the time on XP them run ntpdate. The time gets corrected and shows a drift of 103 seconds. Did you consider that the time issue is on the XP system and not your set-top box? It isn't like Microsoft is know for thier strict adherence to standards.

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 14, 2006 11:58 pm 
Offline
Joined: Mon Feb 13, 2006 7:10 pm
Posts: 36
Location: Australia
I didn't do a very good job of explaining that part. Mythbox and the XP machine aren't connected - if I use time.windows.com (for example) as the NTP server for both the XP machine and Mythbox, XP has the correct time (verified by a call to the tireless talking clock!) but Myth end up 103 seconds out.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 15, 2006 1:52 am 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
I stand by my original statement. If you have an issue syncing time w/ time.windows.com, then I suggest you use another time server. By the way, this isn't a Windows support forum. I don't care for the discussion of anything Mircosoft on this forum. You've been warned.

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 15, 2006 2:03 am 
Offline
Joined: Mon Mar 21, 2005 1:43 pm
Posts: 388
Location: Nanaimo BC
are we actually worried about 1 min 43 seconds whats the worst that might happen you miss the credits of a show. Sorry I come from the school of "don't sweat the small stuff"


Top
 Profile  
 
 Post subject:
PostPosted: Thu Feb 16, 2006 9:14 am 
Offline
Joined: Mon Feb 13, 2006 7:10 pm
Posts: 36
Location: Australia
Like I pointed out initially, this behaviour occurs on whichever of the 6 or so NTP servers I try to sync to, including several stratum 2 servers. So I'm satisfied that it's not due to my choice of servers - as illustrated by the fact that my *gasp* XP machine syncs to the correct time on the servers and Myth does not.

Any more constructive suggestions from the great massed gurus of Linux on the forum?


Top
 Profile  
 
 Post subject:
PostPosted: Thu Feb 16, 2006 10:30 am 
Offline
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location: Germany
You might try the verbose mode of ntpdate to see if anything interesting shows up. "ntpdate -qv" should tell you what it would do if it was going to do an update (without actually doing it).

Cheers,

Allen

(I think those are the options.... why do we have so many flavours of unix??? If those aren't the options, check the man page)

_________________
ASUS AT3N7A-I (Atom 330)
TBS 8922 PCI (DVB-S2)


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 10 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu