Hi If it was a resolving issue than the -n switch would have absolved me from the problem. We have several Solaris and Linux servers on the same subnet with the same resolver (DNS) setup and none of them has the same problem. I also noticed from my first post that ntpd failed with segmentation fault (running it with ntpd with -d) and it's not a hardware issue (as other operating system (Linux/Windows) worked on this hardware for months without a problem. I reduced ntp.conf to the bare minimum (see below) and I'm still experiencing the slowness on the openbsd system. Running ntpq -pn from another linux (or solaris) server on the same subnet returns a reply immediately.
ntp.conf (reduced to the bare minimum): # # ntpd configuratoin file # server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 # write drift file driftfile /var/ntp/drift # broadcast to the lan ntp updates broadcast 192.168.19.255 the full ntp.conf (the configureation includes IP addresses as an attempt to see if it's a resolver issue): # # ntpd configuratoin file # server 192.114.62.249 server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 # peers: peer 192.168.19.11 peer 192.168.19.12 peer 192.168.19.25 peer 192.168.19.50 peer 192.168.19.51 peer 192.168.19.52 peer 192.168.19.100 # write drift file driftfile /var/ntp/drift # broadcast to the lan ntp updates broadcast 192.168.19.255 TIA Paolo On Mar 19, 1:43 am, Harlan Stenn <[EMAIL PROTECTED]> wrote: > >>> In article <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > >>> writes: > > vrkid0> Hi I've installed ntp 4.2.4p0 on an OpenBSD 4.0 box and I'm having > vrkid0> some problems: > vrkid0> 1. If I run the ntpd binary it, sometimes, doesn't > vrkid0> start and doesn't report about problems. When I run it with -d it > vrkid0> always works. If I run it with ktrace (strace equivalence) it always > vrkid0> works. > > What exactly do you mean by "doesn't start"? > > Just to ask, what does your ntp.conf file look like? > > vrkid0> 2. running ntp client commands (I tried ntpq and ntpdc), > vrkid0> regardless of switches, takes a very long time (about 5 > vrkid0> minutes). Even if ntpd isn't or if I run it with -n (ntpq) switch. > vrkid0> There aren't any resolution problems on the computer in question. > vrkid0> Anyone know why this is happening? > > I suspect a DNS problem on your machine. > > Assuming your machine gets low enough traffic, I have found that when I > start ntpd with debugging I can watch the ntpq or ntpdc packets arrive and > the responses get sent back. > > H _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
