From owner-freebsd-stable@freebsd.org Mon Nov 4 23:54:28 2019 Return-Path: Delivered-To: freebsd-stable@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 F110F1B42D4 for ; Mon, 4 Nov 2019 23:54:28 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [150.101.137.136]) by mx1.freebsd.org (Postfix) with ESMTP id 476V5H30TJz4WCD for ; Mon, 4 Nov 2019 23:54:26 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from unknown (HELO midget.dons.net.au) ([118.211.86.76]) by ipmail01.adl6.internode.on.net with ESMTP; 05 Nov 2019 10:24:20 +1030 Received: from midget.dons.net.au (localhost [127.0.0.1]) by midget.dons.net.au (8.15.2/8.15.2) with ESMTPS id xA4Nrs5V018118 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 5 Nov 2019 10:24:15 +1030 (ACDT) (envelope-from darius@dons.net.au) Received: (from mailnull@localhost) by midget.dons.net.au (8.15.2/8.15.2/Submit) id xA4NjI5x012166 for ; Tue, 5 Nov 2019 10:15:18 +1030 (ACDT) (envelope-from darius@dons.net.au) X-Authentication-Warning: midget.dons.net.au: mailnull set sender to using -f X-MIMEDefang-Relay-be813b1f1da6d6b27d681222cb70cc4f5b642383: 10.0.2.38 Received: from havok.dons.net.au ([10.0.2.38]) by ns.dons.net.au (envelope-sender ) (MIMEDefang) with ESMTP id xA4NjDb8012124; Tue, 05 Nov 2019 10:15:18 +1030 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: python dameon coredumps when started from boot, but not by hand From: "O'Connor, Daniel" In-Reply-To: <20191104151555.GB60435@neutralgood.org> Date: Tue, 5 Nov 2019 10:15:12 +1030 Cc: Pete French , freebsd-stable@freebsd.org, 000.fbsd@quip.cz Content-Transfer-Encoding: quoted-printable Message-Id: <4010794E-F6C7-47DB-9746-8A6F63C957F7@dons.net.au> References: <20191104151555.GB60435@neutralgood.org> To: "Kevin P. Neal" X-Mailer: Apple Mail (2.3445.104.11) X-Spam-Score: -1 () No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Scanned-By: MIMEDefang 2.83 on 10.0.2.1 X-Rspamd-Queue-Id: 476V5H30TJz4WCD X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of darius@dons.net.au has no SPF policy when checking 150.101.137.136) smtp.mailfrom=darius@dons.net.au X-Spamd-Result: default: False [4.47 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; HAS_XAW(0.00)[]; AUTH_NA(1.00)[]; DMARC_NA(0.00)[dons.net.au]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.57)[0.570,0]; NEURAL_SPAM_LONG(0.99)[0.988,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4739, ipnet:150.101.0.0/16, country:AU]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(1.51)[ip: (3.79), ipnet: 150.101.0.0/16(2.49), asn: 4739(1.27), country: AU(0.00)]; RCVD_IN_DNSWL_LOW(-0.10)[136.137.101.150.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2019 23:54:29 -0000 > On 5 Nov 2019, at 01:45, Kevin P. Neal wrote: >=20 > On Mon, Nov 04, 2019 at 02:50:14PM +0000, Pete French wrote: >> Soo, I tried this on my desktop machine, and it doesnt coredump, but >> nor does it try and lauch the second python process, so a bit of a = failed >> test there! >=20 > You can use ktrace to see what system calls it is doing. Sometimes it > is helpful to know that just before things went wrong a process tried > to open some particular file and failed, for example.=20 >=20 > Be sure to use the -i flag so children of the traced process also get > traced. I also suggest "-f " so the trace file doesn't end up > in some weird location. During boot I'd guess that the trace file = would > be in "/", but putting it elsewhere may be helpful. Just so long as = the > filesystem has already been mounted at that point in the boot. This would also capture the stderr output, and should be pretty easy to = shoe horn into the rc.d file. Nice thinking! -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum