From owner-freebsd-questions@freebsd.org Tue Oct 27 23:29:34 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 B3FDCA1F1D4 for ; Tue, 27 Oct 2015 23:29:34 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id 96DA010E1; Tue, 27 Oct 2015 23:29:34 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from [10.0.1.12] (static-71-177-216-148.lsanca.fios.verizon.net [71.177.216.148]) (authenticated bits=0) by zoom.lafn.org (8.14.7/8.14.9) with ESMTP id t9RNS2N0016629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Oct 2015 16:28:02 -0700 (PDT) (envelope-from bc979@lafn.org) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: ntpd crashing after update From: Doug Hardie In-Reply-To: <562F982E.1090007@qeng-ho.org> Date: Tue, 27 Oct 2015 16:28:01 -0700 Cc: Matthew Seaman , freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9BA003EB-815B-44C8-8DE7-554BD51D98AC@lafn.org> References: <562F38D5.40107@qeng-ho.org> <562F55AD.7020405@freebsd.org> <562F6CAB.8030205@qeng-ho.org> <562F982E.1090007@qeng-ho.org> To: Arthur Chance X-Mailer: Apple Mail (2.3096.5) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean 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 23:29:34 -0000 > On 27 October 2015, at 08:28, Arthur Chance = wrote: >=20 > 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? >>>=20 >>> Yes -- I've seen that on the one machine I've tried to update so = far. >>> ntpd crashes for me after freebsd-update(8). >>>=20 >>> 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. >>=20 >> 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. >>=20 >> For reference >>=20 >> freebsd-version -ku >> 10.2-RELEASE >> 10.2-RELEASE-p6 >>=20 >> on all three machines, all updated with freebsd-update, and all had >> "service ntpd restart" done after the update. >>=20 >>> There's a thread on freebsd-security@.... -- seems there's also a >>> problem with the ntpq and ntpdc utilities. >>=20 >> ntpq worked fine on all my machines, even before the reboots. >>=20 >=20 > 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. >=20 > 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 >=20 > root@fileserver:0# service ntpd restart > Stopping ntpd. > Waiting for PIDS: 670, 670. > Starting ntpd. >=20 >=20 > 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. >=20 I am running several 9.3 systems: FreeBSD mail 9.3-RELEASE-p24 FreeBSD 9.3-RELEASE-p24 #0: Sat Aug 22 = 01:54:44 UTC 2015 = root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 They were all rebooted after the last upgrade and ntpd seems to be = working fine. Nagios reports very low offsets. However ntpdc crashes = on all: mail# ntpdc = /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/net.c:221: = fatal error: RUNTIME_CHECK(((pthread_once((&once), (initialize_action)) = =3D=3D 0) ? 0 : 34) =3D=3D 0) failed Abort (core dumped) Rebooting doesn=E2=80=99t help with ntpdc. ntpq also crashes with the = same message: mail# ntpq = /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/net.c:221: = fatal error: RUNTIME_CHECK(((pthread_once((&once), (initialize_action)) = =3D=3D 0) ? 0 : 34) =3D=3D 0) failed Abort (core dumped)