RE: [SLE] xntpd does not sync to time server
Let me know what you find out as I am having similar problems. ------Mike Michael Waite Global Partnering Solutions, Marlboro Center Compaq Computer Corporation TEL: (508)467-2289 EMAIL: michael.waite@compaq.com
---------- From: Volker Kuhlmann[SMTP:kuhlmav@elec.canterbury.ac.nz] Sent: Thursday, September 30, 1999 2:37 AM To: suse-linux-e@suse.com Subject: [SLE] xntpd does not sync to time server
After I didn't get much of a (useful) response from SuSE's installation support I might try again here. I am still somewhat curious about the following:
After configuring the xntpd (which is very simple) I found that it does in fact not synchronise to the time server. Looking through the log files shows that xntpd synchronises to teh LOCAL clock (i.e. itself) instead, thinking the time server is not reachable. That is however nonsense, as ntpdate correctly retrieves the time from the time server.
Here are the details:
/etc/ntp.conf: server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized server cantva.canterbury.ac.nz driftfile /etc/ntp.drift # path for drift file logfile /var/log/ntp # alternate log file logconfig =all # VK enable stats statsdir /var/log/ statistics loopstats clockstats filegen loopstats file ntploopstats type month link enable filegen clockstats file ntpclockstats type month link enable
/var/log/messages: Sep 30 18:26:25 ruru xntpd[30918]: ntpd 4.0.93a Sat Aug 7 13:08:17 GMT 1999 (1) Sep 30 18:26:25 ruru xntpd[30918]: signal_no_reset: signal 13 had flags 4000000 Sep 30 18:26:25 ruru xntpd[30918]: precision = 21 usec Sep 30 18:26:25 ruru xntpd[30918]: using kernel phase-lock loop 0041 Sep 30 18:26:25 ruru xntpd[30918]: frequency initialized 12.192 from /etc/ntp.drift Sep 30 18:26:25 ruru xntpd[30918]: using kernel phase-lock loop 0041
ntpq -c pe remote refid st t when poll reach delay offset jitter ========================================================================== ==== *LOCAL(0) LOCAL(0) 10 l 54 64 17 0.000 0.000 0.000 cantva.canterbu 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00
ruru|root[1]:/etc> ntpq -c as ind assID status conf reach auth condition last_event cnt =========================================================== 1 17316 9614 yes yes none sys.peer reachable 1 2 17317 8000 yes no
/var/log/ntp: 30 Sep 18:26:25 xntpd[30918]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010) 30 Sep 18:26:25 xntpd[30919]: signal_no_reset: signal 17 had flags 4000000 30 Sep 18:26:43 xntpd[30918]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 30 Sep 18:29:56 xntpd[30918]: system event 'event_peer/strat_chg' (0x04) status 'sync_alarm, sync_local_proto, 2 events, event_restart' (0xc521) 30 Sep 18:29:56 xntpd[30918]: system event 'event_sync_chg' (0x03) status 'leap_none, sync_local_proto, 3 events, event_peer/strat_chg' (0x534) 30 Sep 18:29:56 xntpd[30918]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_local_proto, 4 events, event_sync_chg' (0x543)
The funny thing is: if I copy the SuSE 6.2 binary xntpd onto a Red Hat 6.0 machine, it doesn't work either. If I copy the binary xntpd from a Red Hat 6.0 machine onto the SuSE 6.2 all things are well.
Either the xntpd on SusE 6.2 (which is version 4) does not work, or I am missing something which has changed from version 3.
Any ideas? I am simply using the RH xntpd, but am curious anyway...
Volker
Oh yes, SuSE's sdb has nothing to show, and all the docs on the system don't give me a hint.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi, you use IP address 127.x.x.x is this range not reserved? your routing should not work the way you expect it, especially if 255.0.0.0 netmask is used. i maybe wrong here, but this is what i would expect. -alexm On Thu, 30 Sep 1999, Waite, Michael wrote:
Let me know what you find out as I am having similar problems.
------Mike
Michael Waite Global Partnering Solutions, Marlboro Center Compaq Computer Corporation TEL: (508)467-2289 EMAIL: michael.waite@compaq.com
---------- From: Volker Kuhlmann[SMTP:kuhlmav@elec.canterbury.ac.nz] Sent: Thursday, September 30, 1999 2:37 AM To: suse-linux-e@suse.com Subject: [SLE] xntpd does not sync to time server
After I didn't get much of a (useful) response from SuSE's installation support I might try again here. I am still somewhat curious about the following:
After configuring the xntpd (which is very simple) I found that it does in fact not synchronise to the time server. Looking through the log files shows that xntpd synchronises to teh LOCAL clock (i.e. itself) instead, thinking the time server is not reachable. That is however nonsense, as ntpdate correctly retrieves the time from the time server.
Here are the details:
/etc/ntp.conf: server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized server cantva.canterbury.ac.nz driftfile /etc/ntp.drift # path for drift file logfile /var/log/ntp # alternate log file logconfig =all # VK enable stats statsdir /var/log/ statistics loopstats clockstats filegen loopstats file ntploopstats type month link enable filegen clockstats file ntpclockstats type month link enable
/var/log/messages: Sep 30 18:26:25 ruru xntpd[30918]: ntpd 4.0.93a Sat Aug 7 13:08:17 GMT 1999 (1) Sep 30 18:26:25 ruru xntpd[30918]: signal_no_reset: signal 13 had flags 4000000 Sep 30 18:26:25 ruru xntpd[30918]: precision = 21 usec Sep 30 18:26:25 ruru xntpd[30918]: using kernel phase-lock loop 0041 Sep 30 18:26:25 ruru xntpd[30918]: frequency initialized 12.192 from /etc/ntp.drift Sep 30 18:26:25 ruru xntpd[30918]: using kernel phase-lock loop 0041
ntpq -c pe remote refid st t when poll reach delay offset jitter ========================================================================== ==== *LOCAL(0) LOCAL(0) 10 l 54 64 17 0.000 0.000 0.000 cantva.canterbu 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00
ruru|root[1]:/etc> ntpq -c as ind assID status conf reach auth condition last_event cnt =========================================================== 1 17316 9614 yes yes none sys.peer reachable 1 2 17317 8000 yes no
/var/log/ntp: 30 Sep 18:26:25 xntpd[30918]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010) 30 Sep 18:26:25 xntpd[30919]: signal_no_reset: signal 17 had flags 4000000 30 Sep 18:26:43 xntpd[30918]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 30 Sep 18:29:56 xntpd[30918]: system event 'event_peer/strat_chg' (0x04) status 'sync_alarm, sync_local_proto, 2 events, event_restart' (0xc521) 30 Sep 18:29:56 xntpd[30918]: system event 'event_sync_chg' (0x03) status 'leap_none, sync_local_proto, 3 events, event_peer/strat_chg' (0x534) 30 Sep 18:29:56 xntpd[30918]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_local_proto, 4 events, event_sync_chg' (0x543)
The funny thing is: if I copy the SuSE 6.2 binary xntpd onto a Red Hat 6.0 machine, it doesn't work either. If I copy the binary xntpd from a Red Hat 6.0 machine onto the SuSE 6.2 all things are well.
Either the xntpd on SusE 6.2 (which is version 4) does not work, or I am missing something which has changed from version 3.
Any ideas? I am simply using the RH xntpd, but am curious anyway...
Volker
Oh yes, SuSE's sdb has nothing to show, and all the docs on the system don't give me a hint.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Mike, Volker, Try puting the word prefer after the remote ntp servers name. I'm not familiar with the new version of xntp, I'm still running 6.1. But if it hasn't changed much then this should work. It looks to me thatsince your internal clock source is listed first it is the prefered source until something happens that would remove that source. Then xntp will try the next server listed. Since you have the ntp internal address listed first the only thing that will remove that source is shutting down xntpd, kind of defeats the purpose :) I use an external source as my prefered source and the internal source as the fallback on my machine here at home and xntpd switches back and forth when I dial in on a periodic basis. Below is the change that I think will solve your problem: erver 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized server cantva.canterbury.ac.nz prefer Please let us know if this helps. Richard "Waite, Michael" wrote:
Let me know what you find out as I am having similar problems.
------Mike
Michael Waite Global Partnering Solutions, Marlboro Center Compaq Computer Corporation TEL: (508)467-2289 EMAIL: michael.waite@compaq.com
---------- From: Volker Kuhlmann[SMTP:kuhlmav@elec.canterbury.ac.nz] Sent: Thursday, September 30, 1999 2:37 AM To: suse-linux-e@suse.com Subject: [SLE] xntpd does not sync to time server
After I didn't get much of a (useful) response from SuSE's installation support I might try again here. I am still somewhat curious about the following:
After configuring the xntpd (which is very simple) I found that it does in fact not synchronise to the time server. Looking through the log files shows that xntpd synchronises to teh LOCAL clock (i.e. itself) instead, thinking the time server is not reachable. That is however nonsense, as ntpdate correctly retrieves the time from the time server.
Here are the details:
/etc/ntp.conf: server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized server cantva.canterbury.ac.nz driftfile /etc/ntp.drift # path for drift file logfile /var/log/ntp # alternate log file logconfig =all # VK enable stats statsdir /var/log/ statistics loopstats clockstats filegen loopstats file ntploopstats type month link enable filegen clockstats file ntpclockstats type month link enable
/var/log/messages: Sep 30 18:26:25 ruru xntpd[30918]: ntpd 4.0.93a Sat Aug 7 13:08:17 GMT 1999 (1) Sep 30 18:26:25 ruru xntpd[30918]: signal_no_reset: signal 13 had flags 4000000 Sep 30 18:26:25 ruru xntpd[30918]: precision = 21 usec Sep 30 18:26:25 ruru xntpd[30918]: using kernel phase-lock loop 0041 Sep 30 18:26:25 ruru xntpd[30918]: frequency initialized 12.192 from /etc/ntp.drift Sep 30 18:26:25 ruru xntpd[30918]: using kernel phase-lock loop 0041
ntpq -c pe remote refid st t when poll reach delay offset jitter ========================================================================== ==== *LOCAL(0) LOCAL(0) 10 l 54 64 17 0.000 0.000 0.000 cantva.canterbu 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00
ruru|root[1]:/etc> ntpq -c as ind assID status conf reach auth condition last_event cnt =========================================================== 1 17316 9614 yes yes none sys.peer reachable 1 2 17317 8000 yes no
/var/log/ntp: 30 Sep 18:26:25 xntpd[30918]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010) 30 Sep 18:26:25 xntpd[30919]: signal_no_reset: signal 17 had flags 4000000 30 Sep 18:26:43 xntpd[30918]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 30 Sep 18:29:56 xntpd[30918]: system event 'event_peer/strat_chg' (0x04) status 'sync_alarm, sync_local_proto, 2 events, event_restart' (0xc521) 30 Sep 18:29:56 xntpd[30918]: system event 'event_sync_chg' (0x03) status 'leap_none, sync_local_proto, 3 events, event_peer/strat_chg' (0x534) 30 Sep 18:29:56 xntpd[30918]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_local_proto, 4 events, event_sync_chg' (0x543)
The funny thing is: if I copy the SuSE 6.2 binary xntpd onto a Red Hat 6.0 machine, it doesn't work either. If I copy the binary xntpd from a Red Hat 6.0 machine onto the SuSE 6.2 all things are well.
Either the xntpd on SusE 6.2 (which is version 4) does not work, or I am missing something which has changed from version 3.
Any ideas? I am simply using the RH xntpd, but am curious anyway...
Volker
Oh yes, SuSE's sdb has nothing to show, and all the docs on the system don't give me a hint.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
alexm＠pycckue.org -
Michael.Waite＠compaq.com -
rowf＠xnet.com