Open timvlaer opened 7 hours ago
When I restart greengrass via systemctl (systemctl restart greengrass
), the system works as expected. My component gets a SIGTERM and properly terminates (exit code 0
).
(I get exit code 137
when the component is killed.)
Right now, I cannot quickly bump the aws.greengrass.Nucleus
component to the latest 2.13.0
because it's incompatible with aws.greengrass.ShadowManager 2.3.6
which I also use.
I'd like to avoid bumping all my dependencies without good reason, so let me know if you think it's worth the effort.
Describe the bug When I deploy a new version of my component, the currently running version of my component is not nicely shutdown but immediately killed.
To Reproduce
Expected behavior I expected to get a SIGTERM signal first and then after a while a hard SIGKILL.
Actual behavior The application is immediately killed. The logs say they send a sigterm (force=false) and then a sigkill (force=true) but I don't see the SIGTERM. It doesn't look like a get a SIGTERM or I don't have the time to react to it.
Environment
Additional context In the debug logs, a couple of things seems weird to me:
force is false
andforce is true
is a couple of milliseconds. The code suggests it should be 5 seconds.bluetoothctl power on\npython3 -u
) but if I dops -ef
on the machine, it only shows a processpython3...
. I guess the string logged is taken from the config and not the real situation.