You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EdgeAgent 1.4 should connect to IoT Hub and pull all others modules
Current Behavior
Only edgeAgent is up and got error message "Empty edge agent config was received. Attempting to read config from backup (/tmp/edgeAgent/backup.json) instead" - "Connection status changed to Disconnected with reason Retry_Expired"
Otherwise, aziot-keyd also failed:
`
Nov 28 13:55:22 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T13:55:22Z [ERR!] - !!! internal error
Nov 28 13:55:22 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T13:55:22Z [ERR!] - !!! caused by: could not load key pair
Nov 28 13:55:22 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T13:55:22Z [ERR!] - !!! caused by: could not load key pair: AZIOT_KEYS_RC_ERR_EXTERNAL
Nov 28 13:55:22 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T13:55:22Z [INFO] - --> 500 {"content-type": "application/json"}
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [INFO] - <-- GET /keypair/device-id?api-version=2021-05-01 {"host": "keyd.sock"}
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [ERR!] - error:1E08010C:DECODER routines:OSSL_DECODER_from_bio:unsupported:../crypto/encode_decode/decoder_lib.c:101:No supported dat>
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [ERR!] - !!! internal error
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [ERR!] - !!! caused by: could not load key pair
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [ERR!] - !!! caused by: could not load key pair: AZIOT_KEYS_RC_ERR_EXTERNAL
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [INFO] - --> 500 {"content-type": "application/json"}
`
Steps to Reproduce
Provide a detailed set of steps to reproduce the bug.
Install IoTedge by default
Context (Environment)
Output of iotedge check
Click here
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 - Warning
Installed aziot-identity-service package has version 1.4.4 but 1.4.9 is the latest stable version available.
Please see https://aka.ms/aziot-update-runtime for update instructions.
caused by: Installed aziot-identity-service package has version 1.4.4 but 1.4.9 is the latest stable version available.
Please see https://aka.ms/aziot-update-runtime for update instructions.
‼ host time is close to reference time - Warning
Could not query NTP server
caused by: Could not query NTP server
caused by: could not receive NTP server response: Resource temporarily unavailable (os error 11)
caused by: Resource temporarily unavailable (os error 11)
√ 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 - Error
Error while fetching latest versions of edge components: could not send HTTP request
caused by: Error while fetching latest versions of edge components: could not send HTTP request
caused by: error trying to connect: Connection reset by peer (os error 104)
caused by: Connection reset by peer (os error 104)
caused by: Connection reset by peer (os error 104)
caused by: Connection reset by peer (os error 104)
√ container time is close to host time - OK
√ DNS server - OK
‼ production readiness: logs policy - Warning
Container engine is not configured to rotate module logs which may cause it run out of disk space.
Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
You can ignore this warning if you are setting log policy per module in the Edge deployment.
caused by: Container engine is not configured to rotate module logs which may cause it run out of disk space.
Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
You can ignore this warning if you are setting log policy per module in the Edge deployment.
‼ production readiness: Edge Agent's storage directory is persisted on the host filesystem - Warning
The edgeAgent module is not configured to persist its /tmp/edgeAgent directory on the host filesystem.
Data might be lost if the module is deleted or updated.
Please see https://aka.ms/iotedge-storage-host for best practices.
caused by: The edgeAgent module is not configured to persist its /tmp/edgeAgent directory on the host filesystem.
Data might be lost if the module is deleted or updated.
Please see https://aka.ms/iotedge-storage-host for best practices.
× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
Could not check current state of edgeHub container
caused by: Could not check current state of edgeHub container
caused by: docker returned exit status: 1, stderr = Error: No such object: edgeHub
√ 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 - Error
Container on the default network could not connect to xxx.azure-devices.net:443
caused by: Container on the default network could not connect to xxx.azure-devices.net:443
caused by: docker returned exit status: 1, stderr = One or more errors occurred. (The SSL connection could not be established, see inner exception.)
√ container on the default network can connect to upstream MQTT port - OK
√ 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 - Error
Container on the azure-iot-edge network could not connect to xxx.azure-devices.net:443
caused by: Container on the azure-iot-edge network could not connect toxxx.azure-devices.net:443
caused by: docker returned exit status: 1, stderr = One or more errors occurred. (The SSL connection could not be established, see inner exception.)
√ container on the IoT Edge module network can connect to upstream MQTT port - OK
29 check(s) succeeded.
4 check(s) raised warnings.
4 check(s) raised errors.
Device Information
Host OS : Ubuntu 22.04.3 LTS
Architecture [e.g. amd64, arm32, arm64]: arm64
Container OS [e.g. Linux containers, Windows containers]: Linux containers
Expected Behavior
EdgeAgent 1.4 should connect to IoT Hub and pull all others modules
Current Behavior
Only edgeAgent is up and got error message "Empty edge agent config was received. Attempting to read config from backup (/tmp/edgeAgent/backup.json) instead" - "Connection status changed to Disconnected with reason Retry_Expired"
Otherwise, aziot-keyd also failed:
`
Nov 28 13:55:22 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T13:55:22Z [ERR!] - !!! internal error
Nov 28 13:55:22 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T13:55:22Z [ERR!] - !!! caused by: could not load key pair
Nov 28 13:55:22 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T13:55:22Z [ERR!] - !!! caused by: could not load key pair: AZIOT_KEYS_RC_ERR_EXTERNAL
Nov 28 13:55:22 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T13:55:22Z [INFO] - --> 500 {"content-type": "application/json"}
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [INFO] - <-- GET /keypair/device-id?api-version=2021-05-01 {"host": "keyd.sock"}
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [ERR!] - error:1E08010C:DECODER routines:OSSL_DECODER_from_bio:unsupported:../crypto/encode_decode/decoder_lib.c:101:No supported dat>
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [ERR!] - !!! internal error
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [ERR!] - !!! caused by: could not load key pair
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [ERR!] - !!! caused by: could not load key pair: AZIOT_KEYS_RC_ERR_EXTERNAL
Nov 28 14:04:31 iotwuxiubuntu02 aziot-keyd[59647]: 2024-11-28T14:04:31Z [INFO] - --> 500 {"content-type": "application/json"}
`
Steps to Reproduce
Provide a detailed set of steps to reproduce the bug.
Install IoTedge by default
Context (Environment)
Output of
iotedge checkClick here
Device Information
Runtime Versions
iotedge version]: 1.4.10docker version]: 20.10.25+azure-2Note: when using Windows containers on Windows, run
docker -H npipe:////./pipe/iotedge_moby_engine versioninsteadLogs
aziot-edged logs
edge-agent logs
edge-hub logs
Additional Information
Please provide any additional information that may be helpful in understanding the issue.
The text was updated successfully, but these errors were encountered: