Topic: Time Sync

[Teviot]

I was reading either in the forums or bugzilla about a time sync problem and smeserver.pool.ntp.org

I have since changed the server that SME looks at and I am not sure that I am reading the logs correctly.

I believe that is is now in sync with the selected time server. Could someone advise me?

Code: [Select]

2008-02-28 21:57:25.577292500 Error : Temporary failure in name resolution
2008-02-28 21:57:25.577298500 28 Feb 21:57:25 ntpdate[3940]: can't find host smeserver.pool.ntp.org
2008-02-28 21:57:25.577302500
2008-02-28 21:57:25.577305500 28 Feb 21:57:25 ntpdate[3940]: no servers can be used, exiting
2008-02-28 21:57:25.763442500 28 Feb 21:57:25 ntpd[3929]: logging to file /dev/stdout
2008-02-28 21:57:25.763612500 28 Feb 21:57:25 ntpd[3929]: ntpd 4.2.0a@1.1190-r Sat May  5 12:55:34 EDT 2007 (1)
2008-02-28 21:57:25.928492500 28 Feb 21:57:25 ntpd[3929]: precision = 3.000 usec
2008-02-28 21:57:25.934657500 28 Feb 21:57:25 ntpd[3929]: Listening on interface wildcard, 0.0.0.0#123
2008-02-28 21:57:25.934790500 28 Feb 21:57:25 ntpd[3929]: Listening on interface lo, 127.0.0.1#123
2008-02-28 21:57:25.934884500 28 Feb 21:57:25 ntpd[3929]: Listening on interface eth0, 192.168.1.3#123
2008-02-28 21:57:25.934959500 28 Feb 21:57:25 ntpd[3929]: Listening on interface eth1, 192.168.0.2#123
2008-02-28 21:57:25.935094500 28 Feb 21:57:25 ntpd[3929]: kernel time sync status 0040
2008-02-28 21:58:45.988454500 28 Feb 21:58:45 ntpd[3929]: frequency initialized -10.480 PPM from /etc/ntp/drift
2008-02-28 22:02:01.159478500 28 Feb 22:02:01 ntpd[3929]: synchronized to LOCAL(0), stratum 10
2008-02-28 22:02:01.159484500 28 Feb 22:02:01 ntpd[3929]: kernel time sync disabled 0041
2008-02-28 22:03:05.213012500 28 Feb 22:03:05 ntpd[3929]: kernel time sync enabled 0001
2008-02-29 13:03:22.675722500 29 Feb 13:03:22 ntpd[3929]: ntpd exiting on signal 15
2008-02-29 13:06:07.901164500 Error : Temporary failure in name resolution
2008-02-29 13:06:07.901168500 29 Feb 13:06:07 ntpdate[4140]: can't find host smeserver.pool.ntp.org
2008-02-29 13:06:07.901172500
2008-02-29 13:06:07.901174500 29 Feb 13:06:07 ntpdate[4140]: no servers can be used, exiting
2008-02-29 13:06:07.979151500 29 Feb 13:06:07 ntpd[4134]: logging to file /dev/stdout
2008-02-29 13:06:07.979325500 29 Feb 13:06:07 ntpd[4134]: ntpd 4.2.0a@1.1190-r Sat May  5 12:55:34 EDT 2007 (1)
2008-02-29 13:06:08.134058500 29 Feb 13:06:08 ntpd[4134]: precision = 2.000 usec
2008-02-29 13:06:08.140223500 29 Feb 13:06:08 ntpd[4134]: Listening on interface wildcard, 0.0.0.0#123
2008-02-29 13:06:08.140359500 29 Feb 13:06:08 ntpd[4134]: Listening on interface lo, 127.0.0.1#123
2008-02-29 13:06:08.140458500 29 Feb 13:06:08 ntpd[4134]: Listening on interface eth0, 192.168.1.3#123
2008-02-29 13:06:08.140536500 29 Feb 13:06:08 ntpd[4134]: Listening on interface eth1, 192.168.0.2#123
2008-02-29 13:06:08.140659500 29 Feb 13:06:08 ntpd[4134]: kernel time sync status 0040
2008-02-29 13:07:28.169515500 29 Feb 13:07:28 ntpd[4134]: frequency initialized -10.480 PPM from /etc/ntp/drift
2008-02-29 13:10:43.364376500 29 Feb 13:10:43 ntpd[4134]: synchronized to LOCAL(0), stratum 10
2008-02-29 13:10:43.364381500 29 Feb 13:10:43 ntpd[4134]: kernel time sync disabled 0041
2008-02-29 13:11:15.471496500 29 Feb 13:11:15 ntpd[4134]: ntpd exiting on signal 15
2008-02-29 13:11:16.145983500 29 Feb 13:11:16 ntpdate[6402]: step time server 202.78.240.38 offset -0.668304 sec
2008-02-29 13:11:16.153966500 29 Feb 13:11:16 ntpd[6399]: logging to file /dev/stdout
2008-02-29 13:11:16.154138500 29 Feb 13:11:16 ntpd[6399]: ntpd 4.2.0a@1.1190-r Sat May  5 12:55:34 EDT 2007 (1)
2008-02-29 13:11:16.164049500 29 Feb 13:11:16 ntpd[6399]: precision = 2.000 usec
2008-02-29 13:11:16.170148500 29 Feb 13:11:16 ntpd[6399]: Listening on interface wildcard, 0.0.0.0#123
2008-02-29 13:11:16.170269500 29 Feb 13:11:16 ntpd[6399]: Listening on interface lo, 127.0.0.1#123
2008-02-29 13:11:16.170348500 29 Feb 13:11:16 ntpd[6399]: Listening on interface eth0, 192.168.1.3#123
2008-02-29 13:11:16.170455500 29 Feb 13:11:16 ntpd[6399]: Listening on interface eth1, 192.168.0.2#123
2008-02-29 13:11:16.170595500 29 Feb 13:11:16 ntpd[6399]: kernel time sync status 0040
2008-02-29 13:11:18.217281500 29 Feb 13:11:18 ntpd[6399]: frequency initialized -10.480 PPM from /etc/ntp/drift
2008-02-29 13:14:35.373317500 29 Feb 13:14:35 ntpd[6399]: synchronized to 192.189.54.17, stratum 2
2008-02-29 13:14:35.373323500 29 Feb 13:14:35 ntpd[6399]: kernel time sync disabled 0041
2008-02-29 13:14:36.398179500 29 Feb 13:14:36 ntpd[6399]: synchronized to 203.171.85.237, stratum 1
2008-02-29 13:14:36.398185500 29 Feb 13:14:36 ntpd[6399]: kernel time sync enabled 0001
2008-02-29 13:15:37.408737500 29 Feb 13:15:37 ntpd[6399]: synchronized to 198.142.76.162, stratum 2
2008-02-29 13:15:44.389737500 29 Feb 13:15:44 ntpd[6399]: synchronized to 203.171.85.237, stratum 1

Thanks
Adrian

[stephen noble]

bugzilla -> 'smeserver.pool.ntp.org'

[cactus]

I was reading either in the forums or bugzilla about a time sync problem and smeserver.pool.ntp.org

I have since changed the server that SME looks at and I am not sure that I am reading the logs correctly.

I believe that is is now in sync with the selected time server. Could someone advise me?

Try

Code: [Select]

ntpq -npThis should output something like this:

Code: [Select]

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+194.109.64.200  192.87.106.2     2 u   16   64  377   32.925   -1.219   0.253
-194.88.2.88     130.88.200.98    3 u   47   64  377   33.022   -2.462   0.128
*192.87.106.2    .GPS.            1 u   62   64  377   32.668   -0.253   0.652
+192.87.106.3    .PPS.            1 u   48   64  377   33.468   -0.084   0.407
 127.127.1.0     LOCAL(0)        10 l   50   64  377    0.000    0.000   0.004
For more information: http://www.cis.udel.edu/~mills/ntp/html/ntpq.html.

[Teviot]

Try

Code: [Select]

ntpq -npThis should output something like this:

Code: [Select]

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+194.109.64.200  192.87.106.2     2 u   16   64  377   32.925   -1.219   0.253
-194.88.2.88     130.88.200.98    3 u   47   64  377   33.022   -2.462   0.128
*192.87.106.2    .GPS.            1 u   62   64  377   32.668   -0.253   0.652
+192.87.106.3    .PPS.            1 u   48   64  377   33.468   -0.084   0.407
 127.127.1.0     LOCAL(0)        10 l   50   64  377    0.000    0.000   0.004
For more information: http://www.cis.udel.edu/~mills/ntp/html/ntpq.html.

Thanks Cactus

Thank you for reading my question and providing me with information to help me sort the problem.  Its a shame that OTHERS just say to see bugziller or similar.

Thanks again
Teviot