Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Problems with ntpd on 6.99.43?



Just a quick follow-up ...

This problem only occurs when I have ntpd_chrootdir defined in my /etc/rc.conf file. If I comment that line, everything works normally.

So, I'm wondering if there is some file missing from the chroot that causes this problem?


On Sun, 1 Jun 2014, Paul Goyette wrote:

I just installed 6.99.43 on one of my machines, and I am seeing some issues with getting ntpd to work.

Jun 1 06:24:46 bolt ntpd[651]: ntpd 4.2.7p404-o Fri Dec 27 19:28:17 EST 2013 (import): Starting Jun 1 06:24:46 bolt ntpd[651]: Command line: /usr/sbin/ntpd -u ntpd:ntpd -i /var/ntpd -p /var/run/ntpd.pid
Jun  1 06:24:46 bolt ntpd[450]: proto: precision = 0.488 usec (-21)
Jun  1 06:24:46 bolt ntpd[450]: Listen and drop on 0 v6wildcard [::]:123
Jun  1 06:24:46 bolt ntpd[450]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun  1 06:24:46 bolt ntpd[450]: Listen normally on 2 re0 50.193.51.17:123
Jun 1 06:24:46 bolt ntpd[450]: Listen normally on 3 re0 [fe80::ca60:ff:fe02:3047%1]:123 Jun 1 06:24:46 bolt ntpd[450]: Listen normally on 4 re0 [2001:470:1f05:80f::5]:123
Jun  1 06:24:46 bolt ntpd[450]: Listen normally on 5 lo0 127.0.0.1:123
Jun  1 06:24:46 bolt ntpd[450]: Listen normally on 6 lo0 [::1]:123
Jun  1 06:24:46 bolt ntpd[450]: Listen normally on 7 lo0 [fe80::1%3]:123
Jun 1 06:24:46 bolt ntpd[450]: Listening on routing socket on fd #28 for interface updates Jun 1 06:24:46 bolt ntpd[450]: running as non-root disables dynamic interface tracking Jun 1 06:24:46 bolt ntpd[450]: giving up resolving host clock.psu.edu: servname not supported for ai_socktype (9) Jun 1 06:24:46 bolt ntpd[450]: giving up resolving host clock.develooper.com: servname not supported for ai_socktype (9) Jun 1 06:26:17 bolt ntpd[450]: giving up resolving host ntp-1.vt.edu: servname not supported for ai_socktype (9)


ntpd is running in chroot, so I am not too concerned about the "running as non-root" line. But the inability to resolve the servers prevents ntpd from synching up the clock.

This was working correctly in an earlier 6.99.28 release. It appears to have broken sometime before 6.99.42 (May 18th).

Interestingly, ntpdate does not seem to be affected.


-------------------------------------------------------------------------
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------


-------------------------------------------------------------------------
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------


Home | Main Index | Thread Index | Old Index