From owner-freebsd-current@freebsd.org Thu Sep 5 13:07:26 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DC853E6E4A for ; Thu, 5 Sep 2019 13:07:26 +0000 (UTC) (envelope-from cy@freebsd.org) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PLZQ3GBfz3DWB for ; Thu, 5 Sep 2019 13:07:26 +0000 (UTC) (envelope-from cy@freebsd.org) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id 5rTvi2Zu5sAGk5rTwiCEPz; Thu, 05 Sep 2019 07:07:24 -0600 X-Authority-Analysis: v=2.3 cv=WeVylHpX c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=J70Eh1EUuV4A:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=LowuVhTJSFmqWrArY1IA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id CF60812B; Thu, 5 Sep 2019 06:07:22 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id x85D7Mlv034062; Thu, 5 Sep 2019 06:07:22 -0700 (PDT) (envelope-from cy@freebsd.org) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id x85D7MGs034053; Thu, 5 Sep 2019 06:07:22 -0700 (PDT) (envelope-from cy@freebsd.org) Message-Id: <201909051307.x85D7MGs034053@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Vladimir Zakharov cc: freebsd-current@freebsd.org Subject: Re: ntpd segfaults on start In-reply-to: <20190905063354.qxecqjkafikdtdyq@vzakharov> References: <20190905061251.rrip6635ebbfimsv@vzakharov> <20190905063354.qxecqjkafikdtdyq@vzakharov> Comments: In-reply-to Vladimir Zakharov message dated "Thu, 05 Sep 2019 09:33:54 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Sep 2019 06:07:22 -0700 X-CMAE-Envelope: MS4wfHIgI/rkbFXSjmXCvnhw0kDiQulZe3z7/kHFvk1OsVYZsmmIjRzmRndlKfh8LzDojZhQfEXQLnZCwqQaSLupxR54vJv8OZ9kT8yZuRA6IFnjoR3eqvVc oEmPj6mnHcjUq9OzLOu33SwdtquxaM/20k94YhhaVmVW/1pSqJjnvLs4pJFKSrtX/xZms7rXU70n4w== X-Rspamd-Queue-Id: 46PLZQ3GBfz3DWB X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Sep 2019 13:07:26 -0000 In message <20190905063354.qxecqjkafikdtdyq@vzakharov>, Vladimir Zakharov write s: > > --ply3axd74k44nuk3 > Content-Type: text/plain; charset=utf-8 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Thu, Sep 05, 2019, Vladimir Zakharov wrote: > > Hello! > >=20 > > Accidentally it turned out that the ntpd does not start on boot. > > Logs show that it core dumps: > > 2019-09-05T08:38:43.588563+03:00 vzakharov ntpd 34934 - - ntpd 4.2.8p12-a= > (1): Starting > > 2019-09-05T08:38:43.588717+03:00 vzakharov kernel - - - Security policy l= > oaded: MAC/ntpd (mac_ntpd) > > 2019-09-05T08:38:43.718356+03:00 vzakharov kernel - - - pid 35074 (ntpd),= > jid 0, uid 123: exited on signal 11 > >=20 > > Not sure how long does it happen. ktrace and gdb points to `setrlimit` > > call. Clean rebuild has no effect. Does anyone have any idea what the > > problem could be? > > Accidental insight after sending initial mail: I've disabled > ASLR related sysctls, and now ntpd starts and runs again. > # grep aslr /boot/loader.conf > kern.elf32.aslr.enable=3D0 > kern.elf64.aslr.enable=3D0 > # service ntpd status > ntpd is running as pid 30528. I'll take a look at this. When you get a chance can you open a PR for this and assign the ticket to me, please. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.