Hi @diegosucaria, how exactly have you killed the main process? Web terminal and kill a PID? Or some other way? Just so we can try to troubleshoot what’s going on (and you are using a dev image, so there could be a lot that you could have done)
The problem re appeared, I had a device online for a week and today I found the screen off, the app container is not running and it didn’t start again.
If you want to take a look to the logs I will send you the device url. I left it as is.
Hi Diego,
I’ve just taken a look at that device and restarted the device, not just the container. Things seem to have come back up okay. I notice in the logs that your container code exits occasionally, most recent example being 19.05.17 03:13:42 (+0000)
Anyways, yes, I knew a reboot will fix the issue, it happened before, (when I wrote the first post) but it seems a bug in the supervisor perhaps?
The fact is, a container restart from inside my app made the supervisor hang. it doesn’t happen always, and I have not experienced it on 1.x OS.
this time was particularly dangerous, because it could have been a production device (this is a dev one sitting on my desk) working good for days, and suddenly, hanged up without warning.
Hey, are you still using pkill to restart the container? Does the supervisor hang also happen when you use the API (either though the dashboard restart button, or the supervisor directly (supervisor restart call)? Just trying to get to the bottom of why it might hang, and the more info you can give on what are you doing exactly, the more likely it is that we can replicate it. Thanks!