freebsd stable - Oct 2019 - python dameon coredumps when started from boot, but not by hand

> On 31 Oct 2019, at 10:09, Pete French <petefrench at ingresso.co.uk>
wrote:
> I opened an issue with Microsoft, including a gdb backtrace of the
> coredump agaist the python, but I feel this is probably something
> fairly straightforward which can be solved by some FreeBSD configuration
> that I am missing somehow.
> 
> github issue is here:
> 
> 	https://github.com/Azure/WALinuxAgent/issues/1687
> 
> but I would be intersted to know if anyone has any thoguhts or advice on
> this. Running FreeBSD in Azure is something which has worked well for me
> so far...
Does it crash if you run it from the command line with 'env -i' in
front?

That clears out the environment and will be a lot closer to the rc.d
environment.

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).

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum

> Does it crash if you run it from the command line with 'env -i' in
front?
>
> That clears out the environment and will be a lot closer to the rc.d
environment.
Interesting idea, but no, that works fine. Annoyingly!
> 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).
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.

-pete.