Date: Mon, 25 Feb 2008 08:07:25 -0800 From: Jeremy Chadwick <koitsu@freebsd.org> To: freebsd-stable@freebsd.org Subject: Re: ntpd fails to synchronize on FreeBSD 6.3-STABLE Message-ID: <20080225160725.GA91945@eos.sc1.parodius.com> In-Reply-To: <20080225150756.GA1747@gmail.com> References: <20080225150756.GA1747@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 25, 2008 at 10:07:56PM +0700, Pongthep Kulkrisada wrote: > Last week I upgraded from source to FreeBSD 6.3-STABLE (buildworld). > I found that I can not get sync with any NTP servers both IPv4 and IPv6. > The followings are my information. > > # cat /etc/ntp.conf > server time.navy.mi.th prefer > server asia.pool.ntp.org > server ntp.nict.jp > driftfile /etc/ntp.drift > > # ntpdc -c peers > remote local st poll reach delay offset disp > ======================================================================= > =122.154.11.67 192.168.1.10 16 1024 0 0.00000 0.000000 0.00000 > =starlite.ispwor 192.168.1.10 16 1024 0 0.00000 0.000000 0.00000 > =ntp-b2.nict.go. 192.168.1.10 16 1024 0 0.00000 0.000000 0.00000 > > messages from syslog > Feb 25 20:00:36 bsdhost ntpd[711]: ntpd 4.2.0-a Mon Feb 18 21:23:47 ICT 2008 (1) > Feb 25 20:00:36 bsdhost ntpd[711]: bind() fd 10, family 28, port 123, addr 2001:5c0:8fff:fffe::42ad, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address I can't help you with the IPv6 stuff; I don't use IPv6. Please do not define driftfile in /etc/ntp.conf. The /etc/rc.d/ntpd framework will take care of that for you by using -f /var/db/ntpd.drift. If I were you, I'd try sniffing traffic on your LAN segment to see if you're even getting responses from the remote NTP servers. Using tcpdump, you should be able to achieve this by doing: # tcpdump -l -n -s 8192 -p "port 123" I'm willing to bet you're not even getting responses from the remote servers, which would imply firewall rules on your gateway, or the machine itself. > (2) > My next problem after buildworld is ``man pages are not updated''. > They are still FreeBSD 6.2. What happen? How to fix it? These won't be taken care of until you do an installworld. And if you did do an installworld and your manpages are still outdated, it's being caused by the fact that there's two sets of pages: manpages located in /usr/share/man/man*, and catpages (which are manpages which have been pre-formatted, thus saving CPU time, but taking up extra disk, stored in /usr/share/man/cat*). The catpages can sometimes become outdated because of this. # find /usr/share/man/cat* -type f -delete And then enable weekly creation of the catman pages via the weekly periodic script, by placing this in /etc/periodic.conf: weekly_catman_enable="yes" You can also create those catman pages right now by setting the above variable in periodic.conf and doing the following: /etc/periodic/weekly/330.catman Keep something in mind, however: by enabling this, you're also prone to get a lot of nasty messages from groff/troff/nroff every week. A lot of manpages are not 100% syntactically correct or compatible with the version of troff FreeBSD uses, so they emit warnings. Finally, when you upgraded from 6.2 to 6.3, did you follow all of the instructions in /usr/src/Makefile perfectly? See the 10-11 steps listed under "For individuals wanting to upgrade their sources...". I'm left wondering if you didn't do the mergemaster step. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080225160725.GA91945>