Closed ciacco85 closed 7 months ago
@ciacco85 at least from the above it appears you probably did some deployment and there was an issue trying to stop glema-badger
module. It then looks like a bit later the deployment succeeded. It is a little hard to say exactly what happened, but it could be the case that the module glema-badger
was gone and the deployment step to stop it failed, but then a little later it was present and it worked. Do you know what the state of your module was when the deployment occurred?
@ciacco85 any updates?
Sorry for the delay. Honestly I haven't done any deployment, that's why I've opened the issue and, form the log, it seems that the IoT hub has fired this "restart". It hasn't happend anymore since the issue was opened. I think we can close if you haven't other suggestion why this event has happend
Closing issue, if this reoccurs please reopen :)
I'm closo to release in production and I've exprerienced a restart in my custom module and I've digged inside $edgeagent log. Since I haven't found anything inside the docs, I want to understand if it's something expected or not. I'm running latest version of every tool and module