Container missing shutdown signal

Hi. I gave this a look and would like you to try something quickly on your side. Can you open a host OS webterminal window, issue this command “systemctl restart systemd-logind” and then when this command returns try to press your press button and let us know if now your app receives SIGTERM as expected?

In fact, please share a device with us and I will do the changes on the machine. Something else I need to do also

For reference, this seems to have been the problem here: https://github.com/balena-os/meta-balena/pull/1847

Hi, let us know once you have sent the UUID

Hello,

I will set this up and provide you access tomorrow when I am in the office…

Sorry, I was out of the office today. I will setup it up, and provide access when I am in tomorrow. Due to the power requirements, and other safety reasons, I can’t leave the equipment on without being physically present.

thanks,

  • rusty

@Hedss despite this particular issue not have gone the way we’d like it to have, I still very much appreciate your efforts. I understand it is hard for anybody, on either side of the problem to attempt to reassemble a conversation from forum posts.

I also acknowledge that my side of communications was not totally clear nor complete. I had gotten to a point of being frustrated with this seeming endless typing spiral. …

I do appreciate your help and efforts @hedss. When I get back to the office, I’ll try your udev suggestion and see what the OS folks have to say…

  • rusty

btw - the last bit about monitoring the GPIO pin and a container crashing is pretty much my bosses opinion which I’d have to live with, if he is convinced of it :wink:

I have enabled support access for 1-day. The UUID is

uuid: e8f5596a4ef43cad28de82bfb1559b6f

It is currently running a single C program that SIGTERM signal and prints to STDOUT.

I can load an image with all of our software if you like.