Re: ntp: not synchronized?
ktb wrote:
>
> On Sat, Aug 04, 2001 at 05:33:53AM -0700, Erik Steffl wrote:
> > ktb wrote:
> > >
> > > On Fri, Aug 03, 2001 at 11:25:02PM -0700, Erik Steffl wrote:
> > > > I have the ntp running and see no error messages while it's running
> > > > but ntptime returnes error, the time is few minutes off and ntpdc says
> > > > 'not synchronized'. How do I go about troubleshooting? any help
> > > > appreciated.
> > > >
> > >
> > > Kind of a guess but I'd try running -
> > > /usr/sbin/ntpdate ntp.server.name
> > > Maybe your clock is too far off for ntp to sync.
> >
> > jojda:/var/log# ntpdate time.ultimeth.net
> > 4 Aug 04:23:17 ntpdate[5379]: no server suitable for synchronization
> > found
> >
> > that doesn't look good... looks like there's something wrong with the
> > server...
> >
> > does it mean I have to look for some other server or is it possible
> > there is something wrong with my settings?
> >
>
> Erik contacted me off line about this. I asked him if he was behind a
> firewall and to make sure dns was resolving correctly. So if someone
> else has anything else to add....
>
> Can you ping time.ultimeth.net ?
yes, it looks like they no longer offer ntp service (telnet to port
123 says Unable to connect to remote host: Connection refused).
I picked some other servers from
http://www.eecis.udel.edu/~mills/ntp/clock2.htm, all of them respond to
ntpdate:
jojda:/home/erik# ntpdate cuckoo.nevada.edu
4 Aug 06:13:07 ntpdate[11054]: adjust time server 131.216.1.218 offset
-0.002573 sec
but when I use them in /etc/ntp.conf I get following log messges
(after restarting ntpd):'
4 Aug 06:20:35 ntpd[11128]: frequency initialized -141.594 from
/var/lib/ntp/ntp.drift
4 Aug 06:20:35 ntpd[11128]: using kernel phase-lock loop 0041
4 Aug 06:20:35 ntpd[11128]: system event 'event_restart' (0x01) status
'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010)
4 Aug 06:20:35 ntpd[11131]: signal_no_reset: signal 17 had flags
4000000
4 Aug 06:20:52 ntpd[11128]: peer 63.192.96.2 event 'event_reach' (0x84)
status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:52 ntpd[11128]: peer 131.144.4.27 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:53 ntpd[11128]: peer 165.227.1.1 event 'event_reach' (0x84)
status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:53 ntpd[11128]: peer 158.121.104.4 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:53 ntpd[11128]: peer 140.221.9.20 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:53 ntpd[11128]: peer 130.126.24.53 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:53 ntpd[11128]: peer 128.46.103.93 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:54 ntpd[11128]: peer 198.68.212.30 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:54 ntpd[11128]: peer 132.239.255.209 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:55 ntpd[11128]: peer 192.73.48.1 event 'event_reach' (0x84)
status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:55 ntpd[11128]: peer 131.216.1.218 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:55 ntpd[11128]: peer 199.240.130.12 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:20:55 ntpd[11128]: peer 128.101.101.101 event 'event_reach'
(0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
4 Aug 06:25:12 ntpd[11128]: system event 'event_peer/strat_chg' (0x04)
status 'sync_alarm, sync_ntp, 2 events, event_restart' (0xc621)
4 Aug 06:25:12 ntpd[11128]: system event 'event_sync_chg' (0x03) status
'leap_none, sync_ntp, 3 events, event_peer/strat_chg' (0x634)
4 Aug 06:25:12 ntpd[11128]: system event 'event_peer/strat_chg' (0x04)
status 'leap_none, sync_ntp, 4 events, event_sync_chg' (0x643)
any ideas what those mean? It is not even clear whether those are
fatal errors, warnings, normal operation or something else...
TIA
erik
Reply to: