From owner-freebsd-questions@freebsd.org Tue Oct 27 15:28:49 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C36E7A1F26D for ; Tue, 27 Oct 2015 15:28:49 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fileserver.home.qeng-ho.org", Issuer "fileserver.home.qeng-ho.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 503561241; Tue, 27 Oct 2015 15:28:48 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.15.2/8.15.2) with ESMTP id t9RFSkIR001986; Tue, 27 Oct 2015 15:28:46 GMT (envelope-from freebsd@qeng-ho.org) Subject: Re: ntpd crashing after update To: Matthew Seaman , freebsd-questions@freebsd.org References: <562F38D5.40107@qeng-ho.org> <562F55AD.7020405@freebsd.org> <562F6CAB.8030205@qeng-ho.org> From: Arthur Chance Message-ID: <562F982E.1090007@qeng-ho.org> Date: Tue, 27 Oct 2015 15:28:46 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <562F6CAB.8030205@qeng-ho.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2015 15:28:49 -0000 On 27/10/2015 12:23, Arthur Chance wrote: > On 27/10/2015 10:45, Matthew Seaman wrote: >> On 10/27/15 08:41, Arthur Chance wrote: >>> I updated my systems yesterday in response to FreeBSD-SA-15:25.ntp, and >>> now ntpd crashes on SEGV, but only on 2 out of 3 of the machines running >>> it. I have no idea whether it's relevant, but the one that doesn't crash >>> is the only one with source installed. Anyone else seeing this? >> >> Yes -- I've seen that on the one machine I've tried to update so far. >> ntpd crashes for me after freebsd-update(8). >> >> Anecdotal evidence is that rebooting apparently causes the updated ntpd >> to function normally. I'd be interested in hearing if people can >> confirm that, because it means there is system state somehow carrying >> over from one invocation of ntpd to another. > > I can confirm that it worked for me. I rebooted the two problem machines > and ntpd started OK. However, the ntpds on both rebooted machines appear > not to be talking to the other machine which initially appeared to have > no problem - ntpq -p shows it as in .INIT. state and unreachable on the > rebooted machines and it sees the other machines as in INIT and > unreachable. I can't reboot the final machine until later today, but > restarting ntpd on it without rebooting has no effect. I'll get back to > you after I've had a chance to reboot it. > > For reference > > freebsd-version -ku > 10.2-RELEASE > 10.2-RELEASE-p6 > > on all three machines, all updated with freebsd-update, and all had > "service ntpd restart" done after the update. > >> There's a thread on freebsd-security@.... -- seems there's also a >> problem with the ntpq and ntpdc utilities. > > ntpq worked fine on all my machines, even before the reboots. > Another data point. On one of the machines I rebooted, ntpq -p was reporting slightly strange values so I tried using "service ntpd restart", and ntpd crashed immediately on restart with a SEGV. Only rebooting let it work again. There's definitely something dodgy with the latest version of ntpd, so I've used freebsd-update rollback to revert to the old one, which works fine. One strange thing after rollback was that a service restart spat out the PID twice as in root@fileserver:0# service ntpd restart Stopping ntpd. Waiting for PIDS: 670, 670. Starting ntpd. I'm fairly certain I'm not vulnerable to the problems in the Security Advisory, so I'll wait until the problem has been sorted to (re)upgrade. -- Moore's Law of Mad Science: Every eighteen months, the minimum IQ necessary to destroy the world drops by one point.