ric@cs.arizona.edu (Ric Anderson) (10/10/90)
In article <665@malgudi.oar.net>, henryc@oar.net (Henry Clark) writes: > > I'm trying to run ntpd on a Sun 4/40 (IPC) and ntpd will continuously > (well, in cycles of about 10 minutes or so) sync to a well-known ntp > server (such as truechimer at uiuc), and almost immediately after > selecting a site issue a message "Lost NTP Peer". Is it normal for > ntp to lose/pick up time servers over a relatively short period of > time? Any ideas? I'm seeing similar behavior on a sun 4/490, running sunOS 4.1, viz: Oct 9 00:24:00 Lost NTP peer 128.196.128.234 Oct 9 00:28:16 clock: select peer 128.196.128.234 stratum 2 was UNSYNCED Oct 9 01:56:48 Lost NTP peer 128.196.128.234 Oct 9 02:01:04 clock: select peer 128.196.128.234 stratum 2 was UNSYNCED Oct 9 02:57:40 Lost NTP peer 128.196.128.234 Oct 9 03:01:56 clock: select peer 128.196.128.234 stratum 2 was UNSYNCED Oct 9 03:55:16 Lost NTP peer 128.196.128.234 Oct 9 03:59:32 clock: select peer 128.196.128.234 stratum 2 was UNSYNCED Prior to the installation of a campus time server (time.telcom.arizona.edu), I saw similar noise trying to hold synch wwvb.isi.edu, ncarfuzz.ucar.edu, and fuzz.sdsc.edu... I also discovered that ntpd would lose track of the time base system (as in, ntpdc would no longer list the "master system"). My solution to this was to restart ntpd on my primary department system (the 4/490) every night... Ric Ric Anderson Bitnet: Ric@Arizrvax Member of the Technical Staff Internet: ric@cs.arizona.edu University of Arizona UUCP: uunet!arizona!ric Department of Computer Science AT&T: (602) 621-4048 Gould-Simpson Room 721 Tucson, Arizona 85721