Re: [SLE] ntp update frequency
Darryl Gregorash wrote:
On 01/11/06 08:55, Hylton Conacher(ZR1HPC) wrote:
Carlos E. R. wrote:
The fact that the daemon doesn't log anything doesn't mean that it hasn't checked the time in the interval. It may have done it hundreds of times for all you know.
And you can not modify when ntp sees fit to check the time.
This ^^^^ ............ .....answers my question about changing its frequency between updates.
Did I put you into information overload with my first reply? It would seem so or it was too late to be reading it :) You can change the frequency of updates, if you add maxpoll (and maybe also minpoll) options to the server directives in /etc/ntp.conf. I don't, however, think that what you describe is an excessively long update interval. What you are seeing is probably just the hourly log of current clock stats by ntp, lines like this one:
1 Nov 13:57:04 ntpd[6769]: offset 0.002634 sec freq 80.858 ppm error 0.010031 poll 9 Mine doesn't look like yours :) see below. <snip>
Is there actually anything at all that suggests to you that your system time is not being properly kept? No, I am just fanatical about the time I send messages and it would seem to be the one part of my Linux system I 'can control' and know how it works. :)
If this configuration is not available, what command could I issue to initiate an ntp time check against the internet ntp servers ie after I have enabled the net connection?
Do not use the ntp daemon unless your connection is permanent.
I hear you however I do have an ADSL cnx. I am a very cautious person and I shut the machine down each night mainly due to unreliable power. When I start the machine in the morning, I leave kinternet connected so that the ntp daemon can sync. When I see it has I 'hang-up' on kinternet.
How are you determining that the system clock has been synced to any external source? From the /var/log/ntp file I have extracted the below snapshot:
2 Nov 15:32:20 ntpd[4652]: synchronized to LOCAL(0), stratum 10 2 Nov 15:32:20 ntpd[4652]: kernel time sync disabled 0041 2 Nov 15:33:25 ntpd[4652]: synchronized to 202.135.38.18, stratum 2 2 Nov 15:33:25 ntpd[4652]: kernel time sync enabled 0001 Besides the 'kernel time sync disabled/enabled messages, to me it looks like the clock is being synced. Would I be right?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-11-02 at 15:55 +0200, Hylton Conacher(ZR1HPC) wrote:
From the /var/log/ntp file I have extracted the below snapshot:
2 Nov 15:32:20 ntpd[4652]: synchronized to LOCAL(0), stratum 10 2 Nov 15:32:20 ntpd[4652]: kernel time sync disabled 0041 2 Nov 15:33:25 ntpd[4652]: synchronized to 202.135.38.18, stratum 2 2 Nov 15:33:25 ntpd[4652]: kernel time sync enabled 0001
Besides the 'kernel time sync disabled/enabled messages, to me it looks like the clock is being synced. Would I be right?
Yes. Look for mesages like these: 2 Nov 11:39:51 ntpd[4353]: offset 0.052763 sec freq -60.075 ppm error 0.212924 poll 6 2 Nov 12:39:51 ntpd[4353]: offset 0.019353 sec freq -17.547 ppm error 0.264188 poll 7 2 Nov 13:39:51 ntpd[4353]: offset 0.003955 sec freq -10.496 ppm error 0.144315 poll 8 2 Nov 14:39:51 ntpd[4353]: offset 0.047911 sec freq -8.933 ppm error 0.029104 poll 10 2 Nov 15:39:51 ntpd[4353]: offset 0.037484 sec freq -8.706 ppm error 0.106007 poll 10 that show the actual error of my system clock. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFSgq6tTMYHG2NR9URAuKAAJ0Wc6vlSwnVLntqe0iRtCbTWYgurQCffkEV jnoE0rQ4OPHbvPz8TIP0RGg= =Ienz -----END PGP SIGNATURE-----
Carlos E. R. wrote:
The Thursday 2006-11-02 at 15:55 +0200, Hylton Conacher(ZR1HPC) wrote:
From the /var/log/ntp file I have extracted the below snapshot:
2 Nov 15:32:20 ntpd[4652]: synchronized to LOCAL(0), stratum 10 2 Nov 15:32:20 ntpd[4652]: kernel time sync disabled 0041 2 Nov 15:33:25 ntpd[4652]: synchronized to 202.135.38.18, stratum 2 2 Nov 15:33:25 ntpd[4652]: kernel time sync enabled 0001
Besides the 'kernel time sync disabled/enabled messages, to me it looks like the clock is being synced. Would I be right?
Yes. ....
Great so the NTP client seems to be working.
....Look for mesages like these:
2 Nov 11:39:51 ntpd[4353]: offset 0.052763 sec freq -60.075 ppm error 0.212924 poll 6 <snip> Haven't seen these for AGES so I would assume my clock is synced right and is keeping time and therefore doesn't need to be changed. You gotta love AMD boards and processors :) -- #!/bin/bash echo "=================================================================" echo "Using unpatched SuSE 9.2 Professional with KDE and Mozilla 1.7.2" echo "Linux user # 229959 at http://counter.li.org" uptime echo "================================================================="
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-11-04 at 16:20 +0200, Hylton Conacher(ZR1HPC) wrote:
2 Nov 11:39:51 ntpd[4353]: offset 0.052763 sec freq -60.075 ppm error 0.212924 poll 6 <snip> Haven't seen these for AGES so I would assume my clock is synced right and is keeping time and therefore doesn't need to be changed.
That report above shows that the clock is going fine. If you don't have it, there is something wrong, but it might be as simple as a different config option: logconfig =all - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFTLpptTMYHG2NR9URAicPAJsHVvmZZCmMOQZcp76W1ugDkOY/3QCdEOiA TBFI6GNtksRAPurFLWSQ62s= =7kxZ -----END PGP SIGNATURE-----
On 2006-11-02 07:55, Hylton Conacher(ZR1HPC) wrote:
<snip>From the /var/log/ntp file I have extracted the below snapshot:
2 Nov 15:32:20 ntpd[4652]: synchronized to LOCAL(0), stratum 10 2 Nov 15:32:20 ntpd[4652]: kernel time sync disabled 0041 2 Nov 15:33:25 ntpd[4652]: synchronized to 202.135.38.18, stratum 2 2 Nov 15:33:25 ntpd[4652]: kernel time sync enabled 0001
Besides the 'kernel time sync disabled/enabled messages, to me it looks like the clock is being synced. Would I be right?
I did give an example of such a thing in my first post -- buried in the middle of the tome :-) See Carlos's latest post for what should come next. Those are indicative of a properly functioning ntp client. If you keep seeing changes in the server you're synchronized to (the second last line in your log snippet above), then you have problems reaching the servers in your configuration, but it's not indicative of a problem with ntpd itself. You're last point is quite correct. In more detail (which I hope isn't overly confusing), the "kernel sync disabled" only means the daemon has no external source, and so does not ask the kernel to do anything to alter the clock rate. (Because, of course, any clock, no matter how poor it is, is always synchronized to itself! :-) ) The "enabled" line means that ntpd believes it has acquired a stable external time source, and the kernel can begin using the received data to make adjustments to the system clock rate, to keep the system and external clocks synchronized. I believe your ntp daemon is probably functioning quite well, but without the statistics logs (and I still do not know how to get those working again) I cannot prove it to you :-)
participants (3)
-
Carlos E. R.
-
Darryl Gregorash
-
Hylton Conacher(ZR1HPC)