mcgraw@SUNSPOT.SUNSPOT.NOAO.EDU (Robert McGraw) (11/27/90)
Below is a script file. I tried running ntpq and xntpdc today and have started getting these unknow service messages. I have not run these commands for a couple weeks (out of town) so I am not sure when this started happening. I killed xntpd and restarted and still having the same problem but ps shows xntpd running and it seem to start up ok. Does anyone out their have the answer to what is causing this????? Famous last words "I have not modified any thing on the system for several months". Script started on Mon Nov 26 17:10:14 1990 sunspot# ntpq ntpq: ntp/udp: unknown service sunspot# xntpdc xntpdc: ntp/udp: unknown service sunspot# script done on Mon Nov 26 17:10:31 1990 Robert
katz@MERIT.EDU (Dave Katz) (11/27/90)
Looks like somebody broke your /etc/services file. Make sure the following line is in there: ntp 123/udp
k2@charly.bl.physik.tu-muenchen.de (Klaus Steinberger) (11/27/90)
mcgraw@SUNSPOT.SUNSPOT.NOAO.EDU (Robert McGraw) writes: >Below is a script file. I tried running ntpq and xntpdc today and have >started getting these unknow service messages. I have not run these >commands for a couple weeks (out of town) so I am not sure when this >started happening. I killed xntpd and restarted and still having the >same problem but ps shows xntpd running and it seem to start up ok. >Does anyone out their have the answer to what is causing this????? >Famous last words "I have not modified any thing on the system for >several months". >Script started on Mon Nov 26 17:10:14 1990 >sunspot# ntpq >ntpq: ntp/udp: unknown service >sunspot# xntpdc >xntpdc: ntp/udp: unknown service >sunspot# >script done on Mon Nov 26 17:10:31 1990 Maybe that is a funny thing in YP. Are you running YP? We are troubled through YP problems looking like this. Sometimes ypserv returns NULL on a getservbyname. We were troubled through this problem on our PCS/Cadmus with a Implementation of NFS3.0, until PCS found the problem. It was a bug in ypserv caused by simultaneous accesses. Now we have a new server machine (CDC4330/CDC4680) with NFS 4.0, and the bug has reappeared. I suppose that this bug runs through all YP-Implementations which are derived from SUN code. The bug will be reproducible by a simple programm calling getservbyname in and endless loop. Run it twice, and the bug appears. Sincerely, Klaus Steinberger Klaus Steinberger Beschleunigerlabor der TU und LMU Muenchen Phone: (+49 89)3209 4287 Hochschulgelaende, D-8046 Garching, West Germany BITNET: K2@DGABLG5P Internet: k2@charly.bl.physik.tu-muenchen.de
jerry@olivey.olivetti.com (Jerry Aguirre) (11/30/90)
In article <k2.659693555@woodstock> k2@charly.bl.physik.tu-muenchen.de (Klaus Steinberger) writes: >Sometimes ypserv returns NULL on a getservbyname. >The bug will be reproducible by a simple programm calling getservbyname >in and endless loop. Run it twice, and the bug appears. I have also seen the same problem. Does anyone have a fix for ypserv?
louie@SAYSHELL.UMD.EDU ("Louis A. Mamakos") (11/30/90)
While I have no (constructive) advice relating to YP, one approach that I took in the ntpd distribution is to revert to "hard coded" a port number in the include file if getservbyname() doesn't return anything useful. This really isn't all that clean, but what the heck? louie
jeff@KESTREL.KESTREL.EDU (Jeff Kitson) (11/30/90)
I saw this problem after upgrading to SunOS 4.1. The /etc/services file
had:
ntp 123/tcp # Network Time Protocol
^^^
I changed the tcp to udp and everything was back to normal