edgeHub crashes on reboot, device goes into zombie state #7398
Assignees
Comments
|
@vadim-kovalyov please take a look |
|
Any progress? We are holding production units to hopefully understand why units are requiring a complete powercycle to restart. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Raspberry PI running iotedge, does not hang when device is asked to reboot
Current Behavior
issuing an "sudo reboot" command causes the edgeHub module to throw an exception on shutdown. This causes the device to hang, and requires a power cycle to clear. Power Cycling my devices in Africa is not cool.
Steps to Reproduce
Provide a detailed set of steps to reproduce the bug.
Context (Environment)
Raspberry zero 2 (x64) for both os and iotEdge
##workaround
'sudo iotedge system stop' before issuing the 'sudo reboot' command
Output of
iotedge checkGFSAdmin001@GFS0000000315:~ $ sudo iotedge check --verbose
Configuration checks (aziot-identity-service)
√ keyd configuration is well-formed - OK
√ certd configuration is well-formed - OK
√ tpmd configuration is well-formed - OK
√ identityd configuration is well-formed - OK
√ daemon configurations up-to-date with config.toml - OK
√ identityd config toml file specifies a valid hostname - OK
√ aziot-identity-service package is up-to-date - OK
√ host time is close to reference time - OK
√ preloaded certificates are valid - OK
√ keyd is running - OK
√ certd is running - OK
√ identityd is running - OK
√ read all preloaded certificates from the Certificates Service - OK
√ read all preloaded key pairs from the Keys Service - OK
√ check all EST server URLs utilize HTTPS - OK
√ ensure all preloaded certificates match preloaded private keys with the same ID - OK
Connectivity checks (aziot-identity-service)
√ host can connect to and perform TLS handshake with iothub AMQP port - OK
√ host can connect to and perform TLS handshake with iothub HTTPS / WebSockets port - OK
√ host can connect to and perform TLS handshake with iothub MQTT port - OK
Configuration checks
√ aziot-edged configuration is well-formed - OK
√ configuration up-to-date with config.toml - OK
√ container engine is installed and functional - OK
√ configuration has correct URIs for daemon mgmt endpoint - OK
√ aziot-edge package is up-to-date - OK
× container time is close to host time - Error
Detected time drift between host and container
caused by: Detected time drift between host and container (NOTE: this happens only occasionally and is corrected when sync occurs)support_bundle_2024_11_25_18_34_29_UTC.zip
√ DNS server - OK
√ production readiness: logs policy - OK
√ production readiness: Edge Agent's storage directory is persisted on the host filesystem - OK
√ production readiness: Edge Hub's storage directory is persisted on the host filesystem - OK
√ Agent image is valid and can be pulled from upstream - OK
√ proxy settings are consistent in aziot-edged, aziot-identityd, moby daemon and config.toml - OK
Connectivity checks
√ container on the default network can connect to upstream AMQP port - OK
√ container on the default network can connect to upstream HTTPS / WebSockets port - OK
√ container on the default network can connect to upstream MQTT port - OK
skipping because of not required in this configuration
√ container on the IoT Edge module network can connect to upstream AMQP port - OK
√ container on the IoT Edge module network can connect to upstream HTTPS / WebSockets port - OK
√ container on the IoT Edge module network can connect to upstream MQTT port - OK
skipping because of not required in this configuration
34 check(s) succeeded.
1 check(s) raised errors.
2 check(s) were skipped due to errors from other checks. (NOTE: can't seem to remove this error)
Click here
Device Information
Runtime Versions
Note: when using Windows containers on Windows, run
docker -H npipe:////./pipe/iotedge_moby_engine versioninsteadLogs
Attached the support bundel
Additional Information
This issue, for me, caused damaged with a client, as all devices zombied just after 24 hours (new update)
The text was updated successfully, but these errors were encountered: