From owner-freebsd-stable@FreeBSD.ORG Tue Mar 13 23:03:35 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F70016A402 for ; Tue, 13 Mar 2007 23:03:35 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id 1037513C43E for ; Tue, 13 Mar 2007 23:03:35 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay5.apple.com (a17-128-113-35.apple.com [17.128.113.35]) by mail-out3.apple.com (8.13.8/8.13.8) with ESMTP id l2DN3FU9002846; Tue, 13 Mar 2007 16:03:15 -0700 (PDT) Received: from relay5.apple.com (unknown [127.0.0.1]) by relay5.apple.com (Symantec Mail Security) with ESMTP id 4166D29C002; Tue, 13 Mar 2007 16:03:15 -0700 (PDT) X-AuditID: 11807123-9f920bb000004462-67-45f72db332a8 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay5.apple.com (Apple SCV relay) with ESMTP id 2DD4730400B; Tue, 13 Mar 2007 16:03:15 -0700 (PDT) In-Reply-To: <45F729B6.2040908@daleco.biz> References: <45F70631.2010404@daleco.biz> <45F729B6.2040908@daleco.biz> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0AF6B2DA-81CE-41CB-BDCD-ED34F6B253A4@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Tue, 13 Mar 2007 16:03:14 -0700 To: Kevin Kinsey X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: stable@freebsd.org Subject: Re: ntpd(8) exits quietly after fork() X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2007 23:03:35 -0000 On Mar 13, 2007, at 3:46 PM, Kevin Kinsey wrote: > The ktrace is on "ntpd -C /etc/ntp.conf -l $HOME/ntp.log" --- I'd > seen nothing at all in /var/log/messages (was running tail on it > while restarting it several times), so I pointed it there. The > full ktrace is rather long, any point to posting it? It did > complain about some missing files, but seemed to accept others and > go on. Here's most of the complaints in snippage form.... > > > 12195 ktrace NAMI "/sbin/ntpd" > 12195 ktrace RET execve -1 errno 2 No such file or directory > 12195 ktrace CALL execve(0xbfbfe710,0xbfbfec5c,0xbfbfec74) > 12195 ktrace NAMI "/bin/ntpd" > 12195 ktrace RET execve -1 errno 2 No such file or directory > > 12195 ntpd CALL open(0x280a2c48,0,0x1b6) > 12195 ntpd NAMI "/etc/libmap.conf" > 12195 ntpd RET open -1 errno 2 No such file or directory > > 12195 ntpd NAMI "/etc/malloc.conf" > 12195 ntpd RET readlink -1 errno 2 No such file or directory > > These don't seem to be related, but IANAE ;-) It seems to be having problems locating the ntpd binary to fork/exec it as a child? Is it possible the path in the /etc/rc.d/ntpd script isn't sane? ntpd should be in /usr/sbin/ntpd.... > Grepping "ntp" in /etc/syslog.conf returns nada, so that would > explain why there's nothing there. I did get "status 2040" in > $HOME/ntp.log, so I'm guessing bad driftfile was the issue? > >> Showing your ntp.conf file would also help, but if you'd like to >> see an example of a working stratum-2 conf file which has been in >> use for quite some time: > > Nice, ty. Mine's simple: > > $ cat /etc/ntp.conf > server time.nist.gov > server navobs1.wustl.edu > driftfile /var/ntpd.drift > > I've got it running fine now in FG (-n) option, and the slaves are > happy ATM. I guess I could give it a "&" ;-) > > It did complain that sanity limit was exceeded after I started it > with -n, which would explain this, maybe? You might try checking "ntpq -p" and seeing whether your offset is too large. In that case, killing ntpd, running "ntpdate -b time.nist.gov", and then restarting ntpd might help. > However, it was exiting prior to any mention of this previously, > and I was *quite certain* that this box did the DST thing just > fine, aside from sendmail logging behind as discussed in a thread > on questions. ntpd operates against GMT/UTC, and doesn't care about DST issues at all, fortunately. :-) > Either way, thanks for the reply! You're welcome... -- -Chuck