iotedge: HSM problems and IoT Hub connectivity test problems

Expected Behavior

No error logs in the security daemon and successful connection check in the edgeAgent module.

Current Behavior

Error log in the security daemon and problem during connection check in the edgeAgent module.

Steps to Reproduce

Provide a detailed set of steps to reproduce the bug.

Start iotedged
Everything works fine for a few days
Suddenly, the errors in the logs below occur.

Context (Environment)

Output of `iotedge check`

Click here

Configuration checks
--------------------
√ config.yaml is well-formed - OK
√ config.yaml has well-formed connection string - OK
√ container engine is installed and functional - OK
√ config.yaml has correct hostname - OK
√ config.yaml has correct URIs for daemon mgmt endpoint - OK
√ latest security daemon - OK
√ host time is close to real time - OK
√ container time is close to host time - OK
‼ DNS server - Warning
    Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
    Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
    You can ignore this warning if you are setting DNS server per module in the Edge deployment.
‼ production readiness: certificates - Warning
    The device CA cert will expire within the next 90 days, at 2021-12-17 02:34:00 UTC. Renew the certificate before this date to retain functionality.
    See https://aka.ms/iotedge-prod-checklist-certs for best practices.
√ production readiness: container engine - 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.
√ 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

Connectivity checks
-------------------
√ host can connect to and perform TLS handshake with DPS endpoint - OK
√ host can connect to and perform TLS handshake with IoT Hub AMQP port - OK
√ host can connect to and perform TLS handshake with IoT Hub HTTPS / WebSockets port - OK
√ host can connect to and perform TLS handshake with IoT Hub MQTT port - OK
√ container on the default network can connect to IoT Hub AMQP port - OK
√ container on the default network can connect to IoT Hub HTTPS / WebSockets port - OK
√ container on the default network can connect to IoT Hub MQTT port - OK
√ container on the IoT Edge module network can connect to IoT Hub AMQP port - OK
√ container on the IoT Edge module network can connect to IoT Hub HTTPS / WebSockets port - OK
√ container on the IoT Edge module network can connect to IoT Hub MQTT port - OK

21 check(s) succeeded.
3 check(s) raised warnings. Re-run with --verbose for more details.

Device Information

Host OS [e.g. Ubuntu 18.04, Windows Server IoT 2019]: CentOS Stream 8
Architecture [e.g. amd64, arm32, arm64]: amd64
Container OS [e.g. Linux containers, Windows containers]: Linux containers

Runtime Versions

aziot-edged [run iotedge version]: iotedge 1.1.8
Edge Agent [image tag (e.g. 1.0.0)]: 1.1 (resolved to 1.1.8)
Edge Hub [image tag (e.g. 1.0.0)]: 1.1 (resolved to 1.1.8)
Docker/Moby [run docker version]:

Client:
 Version:           3.0.8
 API version:       1.40
 Go version:        go1.12.10
 Git commit:        2355349d
 Built:             Wed Oct 23 17:47:59 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          3.0.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.10
  Git commit:       adfac69
  Built:            Wed Oct 23 17:54:47 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Note: when using Windows containers on Windows, run docker -H npipe:////./pipe/iotedge_moby_engine version instead

Logs

aziot-edged logs

Dec 06 09:40:59  iotedged[3139609]: 2021-12-06T09:40:59Z [INFO] - Checking edge runtime status
Dec 06 09:40:59  iotedged[3139609]: 2021-12-06T09:40:59Z [INFO] - Edge runtime is running.
Dec 06 09:41:00  iotedged[3139609]: 2021-12-06T09:41:00Z [INFO] - [mgmt] - - - [2021-12-06 09:41:00.172604555 UTC] "GET /modules?api-version=2020-07-07 HTTP/1.1" 200 OK 5044 "-" "-" auth_id(-)
Dec 06 09:41:05  iotedged[3139609]: 2021-12-06T09:41:05Z [INFO] - [mgmt] - - - [2021-12-06 09:41:05.209781196 UTC] "GET /modules?api-version=2020-07-07 HTTP/1.1" 200 OK 5044 "-" "-" auth_id(-)
Dec 06 09:41:10  iotedged[3139609]: 2021-12-06T09:41:10Z [INFO] - [mgmt] - - - [2021-12-06 09:41:10.250878261 UTC] "GET /modules?api-version=2020-07-07 HTTP/1.1" 200 OK 5044 "-" "-" auth_id(-)
Dec 06 09:41:14  iotedged[3139609]: 2021-12-06T09:41:14Z [INFO] - [work] - - - [2021-12-06 09:41:14.994130894 UTC] "POST /modules/%24edgeAgent/genid/637686149462566588/sign?api-version=2018-06-28 HTTP/1.1" 404 Not Found 188 "-" "-" auth_id(-)
Dec 06 09:41:15  iotedged[3139609]: 2021-12-06T09:41:15Z [INFO] - [mgmt] - - - [2021-12-06 09:41:15.293896478 UTC] "GET /modules?api-version=2020-07-07 HTTP/1.1" 200 OK 5044 "-" "-" auth_id(-)
Dec 06 09:41:15  iotedged[3139609]: 9:40:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_DispatchCmd Line:1102 Sending command to tpm -2144861951.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:40:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_GetTpmProperty Line:678 Get Capability failure
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:40:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_comm_linux.c Func:write_data_to_tpm Line:110 Failure writing data to tpm: 14:Bad address.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:40:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_comm_linux.c Func:tpm_comm_submit_command Line:390 Failure setting locality to TPM
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:40:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_SendCommand Line:1187 submitting command to TPM Communication.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:40:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_DispatchCmd Line:1102 Sending command to tpm -2144861951.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:40:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:SignData Line:377 Hashing token data failed TPM_RC_COMMAND_CODE
Dec 06 09:41:15  iotedged[3139609]: 2021-12-06T09:40:14Z [ERR!] (/project/edgelet/hsm-sys/azure-iot-hsm-c/src/hsm_client_tpm_device.c:hsm_client_tpm_sign_data:477) Failure signing data from hash
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_comm_linux.c Func:write_data_to_tpm Line:110 Failure writing data to tpm: 14:Bad address.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_comm_linux.c Func:tpm_comm_submit_command Line:390 Failure setting locality to TPM
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_SendCommand Line:1187 submitting command to TPM Communication.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_DispatchCmd Line:1102 Sending command to tpm -2144861951.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_GetTpmProperty Line:678 Get Capability failure
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_comm_linux.c Func:write_data_to_tpm Line:110 Failure writing data to tpm: 14:Bad address.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_comm_linux.c Func:tpm_comm_submit_command Line:390 Failure setting locality to TPM
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_SendCommand Line:1187 submitting command to TPM Communication.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_DispatchCmd Line:1102 Sending command to tpm -2144861951.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:14 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:SignData Line:377 Hashing token data failed TPM_RC_COMMAND_CODE
Dec 06 09:41:15  iotedged[3139609]: 2021-12-06T09:41:14Z [ERR!] (/project/edgelet/hsm-sys/azure-iot-hsm-c/src/hsm_client_tpm_device.c:hsm_client_tpm_sign_data:477) Failure signing data from hash
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:15 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_comm_linux.c Func:write_data_to_tpm Line:110 Failure writing data to tpm: 14:Bad address.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:15 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_comm_linux.c Func:tpm_comm_submit_command Line:390 Failure setting locality to TPM
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:15 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_SendCommand Line:1187 submitting command to TPM Communication.
Dec 06 09:41:15  iotedged[3139609]: Error: Time:Mon Dec  6 09:41:15 2021 File:/project/edgelet/hsm-sys/azure-iot-hsm-c/deps/utpm/src/tpm_codec.c Func:TSS_DispatchCmd Line:1102 Sending command to t<6>2021-12-06T09:41:15Z [INFO] - [work] - - - [2021-12-06 09:41:15.358>
Dec 06 09:41:20  iotedged[3139609]: 2021-12-06T09:41:20Z [INFO] - [mgmt] - - - [2021-12-06 09:41:20.334790396 UTC] "GET /modules?api-version=2020-07-07 HTTP/1.1" 200 OK 5044 "-" "-" auth_id(-)
Dec 06 09:41:25  iotedged[3139609]: 2021-12-06T09:41:25Z [INFO] - [mgmt] - - - [2021-12-06 09:41:25.381628205 UTC] "GET /modules?api-version=2020-07-07 HTTP/1.1" 200 OK 5044 "-" "-" auth_id(-)
Dec 06 09:41:30  iotedged[3139609]: 2021-12-06T09:41:30Z [INFO] - [mgmt] - - - [2021-12-06 09:41:30.418750067 UTC] "GET /modules?api-version=2020-07-07 HTTP/1.1" 200 OK 5044 "-" "-" auth_id(-)

edge-agent logs

Dec 06 09:42:37 2a087ef97ce6[32225]: <6> 2021-12-06 09:42:37.680 +00:00 [INF] - Cleaned up 0 messages from queue for endpoint bec0ddfe-9681-4151-ac51-3d623f5ea07a/DataAgent/command and 0 messages from message store.
Dec 06 09:42:42 2a087ef97ce6[32225]: <4> 2021-12-06 09:42:42.500 +00:00 [WRN] - Error calling IotHub for connectivity test
Dec 06 09:42:42 2a087ef97ce6[32225]: Microsoft.Azure.Devices.Edge.Util.Edged.WorkloadCommunicationException- Message:Error calling SignAsync: Module not found
Dec 06 09:42:42 2a087ef97ce6[32225]:         caused by: Signing error occurred.
Dec 06 09:42:42 2a087ef97ce6[32225]:         caused by: An error occurred in the key store.
Dec 06 09:42:42 2a087ef97ce6[32225]:         caused by: HSM failure
Dec 06 09:42:42 2a087ef97ce6[32225]:         caused by: HSM API failure occurred: 478, StatusCode:404, at:   at Microsoft.Azure.Devices.Edge.Util.Edged.Version_2019_01_30.WorkloadClient.HandleException(Exception ex, String operation) in /home/vsts/work/1/s/edge-uti>
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Util.Edged.WorkloadClientVersioned.Execute[T](Func`1 func, String operation) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/edged/WorkloadClientVersioned.cs:line 79
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Util.Edged.Version_2019_01_30.WorkloadClient.SignAsync(String keyId, String algorithm, String data) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/edged/version_2019_01_>
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Util.ClientTokenProvider.GetTokenAsync(Option`1 ttl) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/ClientTokenProvider.cs:line 62
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.AuthenticationWithTokenRefresh.GetTokenAsync(String iotHub)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.AmqpIoT.AmqpIoTCbsTokenProvider.GetTokenAsync(Uri namespaceAddress, String appliesTo, String[] requiredClaims)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Amqp.TaskHelpers.EndAsyncResult(IAsyncResult asyncResult)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Amqp.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
Dec 06 09:42:42 2a087ef97ce6[32225]: --- End of stack trace from previous location where exception was thrown ---
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Amqp.AsyncResult.End[TAsyncResult](IAsyncResult result)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Amqp.AmqpCbsLink.<>c__DisplayClass4_0.<SendTokenAsync>b__1(IAsyncResult a)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
Dec 06 09:42:42 2a087ef97ce6[32225]: --- End of stack trace from previous location where exception was thrown ---
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.AmqpIoT.AmqpIoTCbsLink.SendTokenAsync(ICbsTokenProvider tokenProvider, Uri namespaceAddress, String audience, String resource, String[] requiredClaims, TimeSpan timeout)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.Amqp.AmqpAuthenticationRefresher.InitLoopAsync(TimeSpan timeout)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.AmqpIoT.AmqpIoTConnection.CreateRefresherAsync(DeviceIdentity deviceIdentity, TimeSpan timeout)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.Amqp.AmqpConnectionHolder.CreateRefresherAsync(DeviceIdentity deviceIdentity, TimeSpan timeout)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.AmqpIoT.AmqpUnit.EnsureSessionAsync(TimeSpan timeout)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.AmqpIoT.AmqpUnit.OpenAsync(TimeSpan timeout)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.Amqp.AmqpTransportHandler.OpenAsync(CancellationToken cancellationToken)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.ProtocolRoutingDelegatingHandler.OpenAsync(CancellationToken cancellationToken)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.ErrorDelegatingHandler.<>c__DisplayClass23_0.<<ExecuteWithErrorHandlingAsync>b__0>d.MoveNext()
Dec 06 09:42:42 2a087ef97ce6[32225]: --- End of stack trace from previous location where exception was thrown ---
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.ErrorDelegatingHandler.ExecuteWithErrorHandlingAsync[T](Func`1 asyncOperation)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.RetryDelegatingHandler.<>c__DisplayClass33_0.<<OpenInternalAsync>b__0>d.MoveNext()
Dec 06 09:42:42 2a087ef97ce6[32225]: --- End of stack trace from previous location where exception was thrown ---
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.RetryDelegatingHandler.EnsureOpenedAsync(CancellationToken cancellationToken)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.RetryDelegatingHandler.<>c__DisplayClass25_0.<<SendTwinPatchAsync>b__0>d.MoveNext()
Dec 06 09:42:42 2a087ef97ce6[32225]: --- End of stack trace from previous location where exception was thrown ---
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.Transport.RetryDelegatingHandler.SendTwinPatchAsync(TwinCollection reportedProperties, CancellationToken cancellationToken)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Client.InternalClient.UpdateReportedPropertiesAsync(TwinCollection reportedProperties)
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.CloudProxy.ConnectivityAwareClient.<>c__DisplayClass30_0.<<InvokeFunc>b__0>d.MoveNext() in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.CloudProxy/ConnectivityAwareClie>
Dec 06 09:42:42 2a087ef97ce6[32225]: --- End of stack trace from previous location where exception was thrown ---
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.CloudProxy.ConnectivityAwareClient.InvokeFunc[T](Func`1 func, String operation, Boolean useForConnectivityCheck) in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.CloudPr>
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.CloudProxy.ConnectivityAwareClient.InvokeFunc[T](Func`1 func, String operation, Boolean useForConnectivityCheck) in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.CloudPr>
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.CloudProxy.CloudProxy.UpdateReportedPropertiesAsync(IMessage reportedPropertiesMessage) in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.CloudProxy/CloudProxy.cs:line 213
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.CloudProxy.CloudProxy.UpdateReportedPropertiesAsync(IMessage reportedPropertiesMessage) in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.CloudProxy/CloudProxy.cs:line 213
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.Core.Cloud.RetryingCloudProxy.<>c__DisplayClass22_0.<<ExecuteOperation>b__0>d.MoveNext() in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.Core/cloud/RetryingCloudProxy.c>
Dec 06 09:42:42 2a087ef97ce6[32225]: --- End of stack trace from previous location where exception was thrown ---
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.Core.Cloud.RetryingCloudProxy.ExecuteOperation[T](Func`2 func, String operation) in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.Core/cloud/RetryingCloudProxy.cs:line 72
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.CloudProxy.DeviceConnectivityManager.ConnectivityChecker.Check() in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.CloudProxy/DeviceConnectivityManager.cs:line 220
Dec 06 09:42:42 2a087ef97ce6[32225]:    at Microsoft.Azure.Devices.Edge.Hub.CloudProxy.DeviceConnectivityManager.CheckConnectivity() in /home/vsts/work/1/s/edge-hub/src/Microsoft.Azure.Devices.Edge.Hub.CloudProxy/DeviceConnectivityManager.cs:line 190
Dec 06 09:42:45 2a087ef97ce6[32225]: <6> 2021-12-06 09:42:45.180 +00:00 [INF] - Started task to cleanup processed and stale messages for endpoint bec0ddfe-9681-4151-ac51-3d623f5ea07a/ProtocolAbstraction/command
Dec 06 09:42:45 2a087ef97ce6[32225]: <6> 2021-12-06 09:42:45.182 +00:00 [INF] - Cleaned up 0 messages from queue for endpoint bec0ddfe-9681-4151-ac51-3d623f5ea07a/ProtocolAbstraction/command and 0 messages from message store.
Dec 06 09:42:45 2a087ef97ce6[32225]: <6> 2021-12-06 09:42:45.182 +00:00 [INF] - Started task to cleanup processed and stale messages for endpoint bec0ddfe-9681-4151-ac51-3d623f5ea07a/DataAgent/commandResponse
Dec 06 09:42:45 2a087ef97ce6[32225]: <6> 2021-12-06 09:42:45.182 +00:00 [INF] - Cleaned up 0 messages from queue for endpoint bec0ddfe-9681-4151-ac51-3d623f5ea07a/DataAgent/commandResponse and 0 messages from message store.

edge-hub logs

not relevant

Additional Information

Please provide any additional information that may be helpful in understanding the issue.

About this issue

Original URL
State: open
Created 3 years ago
Comments: 15 (7 by maintainers)

Most upvoted comments

It’ happens with every version of iotedged.

I’ve found a workaround for the problem. In the documentation it’s mentioned that also iotedge user must be owner of the /dev/tpmrm0 device. https://docs.microsoft.com/de-de/azure/iot-edge/how-to-provision-devices-at-scale-linux-tpm?view=iotedge-2018-06&preserve-view=true&tabs=physical-device#give-iot-edge-access-to-the-tpm

If I skip this, everything works as expected. I don’t know why the iotede user even needs access to the resource manager of the TPM module. Maybe the documentation is wrong with regards to CentOS.

Suizi11 on Jan 28, 2022