Date: Thu, 31 Oct 2019 22:02:41 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: Pete French <petefrench@ingresso.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: python dameon coredumps when started from boot, but not by hand Message-ID: <28335B0B-43D8-4E78-8112-334D7153AFE3@dons.net.au> In-Reply-To: <E1iQ7YF-0004bX-K1@dilbert.ingresso.co.uk> References: <E1iQ7YF-0004bX-K1@dilbert.ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 31 Oct 2019, at 20:49, Pete French <petefrench@ingresso.co.uk> = wrote: >=20 >> Does it crash if you run it from the command line with 'env -i' in = front? >>=20 >> That clears out the environment and will be a lot closer to the rc.d = environment. >=20 > Interesting idea, but no, that works fine. Annoyingly! Hmm very odd.. Does the tool depend on something else running? >> If that doesn't show anything then you will have to try capturing = stderr >> from the rc.d run as that will hopefully have the reason why Python = is >> aborting (ie what Py_FatalError is complaining about). >=20 > So, I naiively tried to do this by simply sticking a '2> = /tmp/waagent.stderr' > on the end of the rc.d command arguments, but it didnt produce = anything (i.e. > an empty file was created). Will try some other ways though, as you = are > right that getting the output from that is how to find the issue. What does the rc.d file for it look like? -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28335B0B-43D8-4E78-8112-334D7153AFE3>