Getting error "configuration has correct URIs for daemon mgmt endpoint - Error" & "production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error" while installing IoT edge on ubuntu

Somiya 246 Reputation points
2021-05-31T08:04:05.603+00:00

hi I am facing below issue while installing IoT Edge . Here are the details

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 - Error 
    One or more errors occurred. (Connection refused /var/run/iotedge/mgmt.sock) 
        caused by: docker returned exit code: 1, stderr = One or more errors occurred. (Connection refused /var/run/iotedge/mgmt.sock)** 
√ aziot-edge package is up-to-date - 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: 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 - 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. 
**× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error 
    Could not check current state of edgeHub container 
        caused by: docker returned exit code: 1, stderr = Error: No such object: edgeHub** 
√ Agent image is valid and can be pulled from upstream - 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 
√ 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 
31 check(s) succeeded. 
3 check(s) raised warnings. 
2 check(s) raised errors. 

IoT Edge container logs

6> 2021-05-31 07:51:52.424 +00:00 [INF] - Experimental features configuration: {"Enabled":false,"DisableCloudSubscriptions":false} 
<3> 2021-05-31 07:51:52.461 +00:00 [ERR] - Shutting down because no response from unix:///var/run/iotedge/workload.sock for TrustBundleAsync 
System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (111): Connection refused /var/run/iotedge/workload.sock 
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) 
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) 
   at System.Net.Sockets.Socket.UnsafeBeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state, Boolean flowContext) 
   at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state) 
   at System.Net.Sockets.Socket.ConnectAsync(EndPoint remoteEP) 
   at System.Net.Sockets.SocketTaskExtensions.ConnectAsync(Socket socket, EndPoint remoteEP) 
   at Microsoft.Azure.Devices.Edge.Util.Uds.HttpUdsMessageHandler.GetConnectedSocketAsync() in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpUdsMessageHandler.cs:line 47 
   at Microsoft.Azure.Devices.Edge.Util.Uds.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/uds/HttpUdsMessageHandler.cs:line 23 
   at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) 
   at Microsoft.Azure.Devices.Edge.Util.Edged.Version_2019_01_30.GeneratedCode.HttpWorkloadClient.TrustBundleAsync(String api_version, CancellationToken cancellationToken) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/edged/version_2019_01_30/generatedCode/HttpWorkloadClient.cs:line 700 
   at Microsoft.Azure.Devices.Edge.Util.TaskEx.TimeoutAfter[T](Task`1 task, TimeSpan timeout) in /home/vsts/work/1/s/edge-util/src/Microsoft.Azure.Devices.Edge.Util/TaskEx.cs:line 126 
   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 59 
2021-05-31 07:52:52  Starting Edge Agent 
2021-05-31 07:52:52  Changing ownership of storage folder: /tmp/edgeAgent to 1000 
2021-05-31 07:52:52  Changing ownership of management socket: /var/run/iotedge/mgmt.sock 
2021-05-31 07:52:52.144 +00:00 Edge Agent Main() 
<6> 2021-05-31 07:52:52.289 +00:00 [INF] - Initializing Edge Agent. 
<6> 2021-05-31 07:52:52.380 +00:00 [INF] - Version - 1.2.0.41251928 (27661e55482c30597850f5e7af345814f3e26864) 

docker version : Docker version 20.10.6+azure, build 370c28948e3c12dce3d1df60b6f184990618553f
IoT Edge vision: iotedge 1.2.0

Azure IoT Edge
Azure IoT Edge
An Azure service that is used to deploy cloud workloads to run on internet of things (IoT) edge devices via standard containers.
573 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sander van de Velde | MVP 32,726 Reputation points MVP
    2021-06-02T23:00:52.037+00:00

    Hello @Somiya ,

    it seems to complain the edgeHub module is missing.

    Is this the 'vanilla' Azure IoT Edge installation? And you have not deployed any modules on it?

    In that case, only the edgeAgent module is rolled out.

    The edgeHub will be deployed the first time together with any custom module.

    Please do the same check AFTER a module (like this simple heartbeat module) is deployed.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.