Latest waagent coredumps python interpreter when started at boot on FreeBSD

'I am running the latest waagent on the 'develop branch. Operating system is FreeBSD 12.1 and I am using python3.6 which is the current default python in FreeBSD. Have removed all traces of older python 2.7.

When I run this using ‘service waagent start’ logged in as root then it runs fine.

If, however, I reboot the machine, and waagent is started on boot, then I find this repeated in dmesg:

2019/10/29 16:31:23.617805 INFO Daemon Agent WALinuxAgent-2.2.44 launched with command 'python3 -u /usr/local/sbin/waagent -run-exthandlers' is successfully running
2019/10/29 16:31:23.628337 INFO Daemon Installed Agent WALinuxAgent-2.2.44 is the most current agent
pid 4766 (python3.6), jid 0, uid 0: exited on signal 6 (core dumped)
2019/10/29 16:31:24.933556 INFO Daemon Agent WALinuxAgent-2.2.44 launched with command 'python3 -u /usr/local/sbin/waagent -run-exthandlers' is successfully running
2019/10/29 16:31:24.939914 INFO Daemon Installed Agent WALinuxAgent-2.2.44 is the most current agent
pid 4767 (python3.6), jid 0, uid 0: exited on signal 6 (core dumped)
2019/10/29 16:31:26.246526 INFO Daemon Agent WALinuxAgent-2.2.44 launched with command 'python3 -u /usr/local/sbin/waagent -run-exthandlers' is successfully running
2019/10/29 16:31:26.257418 INFO Daemon Installed Agent WALinuxAgent-2.2.44 is the most current agent
pid 4768 (python3.6), jid 0, uid 0: exited on signal 6 (core dumped)

It keeps trying to start it and then coredumping. If I run gdb against the coredump I see this:

Core was generated by `python3 -u /usr/local/sbin/waagent -run-exthandlers'.
Program terminated with signal SIGABRT, Aborted.
#0  thr_kill () at thr_kill.S:3
3	RSYSCALL(thr_kill)
(gdb) bt
#0  thr_kill () at thr_kill.S:3
#1  0x0000000800768b94 in __raise (s=6) at /usr/src/lib/libc/gen/raise.c:52
#2  0x00000008006dd229 in abort () at /usr/src/lib/libc/stdlib/abort.c:67
#3  0x000000080045e535 in Py_FatalError () from /usr/local/lib/libpython3.6m.so.1.0
#4  0x000000080045e2eb in _Py_InitializeEx_Private () from /usr/local/lib/libpython3.6m.so.1.0
#5  0x000000080047c914 in Py_Main () from /usr/local/lib/libpython3.6m.so.1.0
#6  0x000000000020144b in main ()
(gdb) 

[minusbat]

Its midnight ere, so am going to have to stop trying stuff, but I did try moving the startup to much later in the process, but with no effect. I always create new machines in Azure byu clonign old ones, so I don’t need any of the provisioning features. If it is possible to simply run without waagent then that would be a solution for me - but I would quite like to have this fixed, as would you I suspect!

I’ll do some more experiments tomorrow, and also maybe look into what the difference is between starring a script at boot compared to from a shell. Thanks.

[minusbat]

I can verify that its fixed for me, and works with the latest default python. Thank you - I never would have found this on my own given the nature of the bug!