iotedge check error: config.yaml has correct URIs for daemon mgmt endpoint - Error

Expected Behavior

iotedge check should be passed

Current Behavior

config.yaml has correct URIs for daemon mgmt endpoint - Error

Steps to Reproduce

Provide a detailed set of steps to reproduce the bug. 1.updating iotedge daemon to 1.0.10 2.restart device 3.run iotedge check 4.

Context (Environment)

Output of `iotedge check`

Click here


config.yaml has correct URIs for daemon mgmt endpoint - Error
    Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.10' locally
    1.0.10: Pulling from azureiotedge-diagnostics
    b9e6fec25718: Already exists
    909c0cde5070: Already exists
    c96327c6c17f: Already exists
    bbd8c93a942a: Already exists
    9b87e22bb11a: Already exists
    4d7335a78b54: Already exists
    df7387814126: Pulling fs layer
    c9f46c2fce6c: Pulling fs layer
    076984b59710: Pulling fs layer
    8368ffadb3f2: Pulling fs layer
    076984b59710: Waiting
    8368ffadb3f2: Waiting
    c9f46c2fce6c: Verifying Checksum
    c9f46c2fce6c: Download complete
    df7387814126: Verifying Checksum
    df7387814126: Download complete
    df7387814126: Pull complete
    8368ffadb3f2: Verifying Checksum
    8368ffadb3f2: Download complete
    c9f46c2fce6c: Pull complete
    076984b59710: Verifying Checksum
    076984b59710: Download complete
    076984b59710: Pull complete
    8368ffadb3f2: Pull complete
    Digest: sha256:01d3348865716a28ef84b0ddc2f69e7560d3a6d5425db3740960222f96e381d6
    Status: Downloaded newer image for mcr.microsoft.com/azureiotedge-diagnostics:1.0.10
    One or more errors occurred. (Only 'http' and 'https' schemes are allowed. (Parameter 'requestUri'))

Device Information

Host OS [e.g. Ubuntu 16.04, Ubuntu 18.04, Windows IoT Core]: Windows LTSB 2019
Architecture [e.g. amd64, arm32, arm64]: arm64
Container OS [e.g. Linux containers, Windows containers]: Windows containers

Runtime Versions

iotedged [run iotedge version]: 1.0.10
Edge Agent [image tag (e.g. 1.0.0)]: 1.0.10
Edge Hub [image tag (e.g. 1.0.0)]: 1.0.10
Docker/Moby [run docker version]: 1.40

Issue Analytics

State:
Created 3 years ago
Comments:21 (8 by maintainers)

Top GitHub Comments

1reaction

wmk1commented, Jan 4, 2021

When I tried to stop these container, I had error that I have permission denied.

Yes, you were right. I have resolved a solution using docker forum.

For those people who might encounter following error: The issue is regarding docker daemon issue. I have resolved it using solution described here: https://forums.docker.com/t/can-not-stop-docker-container-permission-denied-error/41142/5

A solution: 
1. sudo aa-status
2. sudo systemctl disable apparmor.service --now
3. sudo service apparmor teardown
4. sudo aa-status

After these steps I restarted ```docker``` and ```iotedge``` daemons and restarted my RPI. After restarting I have everything working again. The issue happened when I tried to upgrade to newer version of IoT Edge and perhaps it was due to not fully removing some docker/iotedge stuff. Please be aware when performing such stuff.

0reactions

GertjanvanhetHofcommented, Jan 4, 2022

I’m running in the same issue. I try to setup my IoT Edge with DPS and certificates.

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 SocketError - SocketErrorCode (TimedOut) : Operation timed out One or more errors occurred. (Got bad response: )

In the logs I found:

Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 2022-01-04T13:23:11Z [INFO] - Starting service… Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 2022-01-04T13:23:11Z [INFO] - Version - 1.2.4 Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 2022-01-04T13:23:11Z [INFO] - Provisioning starting. Reason: Startup Jan 04 13:23:11 vm-iot-edge-dev aziot-certd[2616]: 2022-01-04T13:23:11Z [INFO] - <-- GET /certificates/device-id?api-version=2020-09-01 {“host”: “certd.sock”} Jan 04 13:23:11 vm-iot-edge-dev aziot-certd[2616]: 2022-01-04T13:23:11Z [INFO] - --> 200 {“content-type”: “application/json”} Jan 04 13:23:11 vm-iot-edge-dev aziot-keyd[2621]: 2022-01-04T13:23:11Z [INFO] - <-- GET /keypair/device-id?api-version=2020-09-01 {“host”: “keyd.sock”} Jan 04 13:23:11 vm-iot-edge-dev aziot-keyd[2621]: 2022-01-04T13:23:11Z [ERR!] - Permission denied (os error 13) Jan 04 13:23:11 vm-iot-edge-dev aziot-keyd[2621]: 2022-01-04T13:23:11Z [ERR!] - !!! internal error Jan 04 13:23:11 vm-iot-edge-dev aziot-keyd[2621]: 2022-01-04T13:23:11Z [ERR!] - !!! caused by: could not load key pair Jan 04 13:23:11 vm-iot-edge-dev aziot-keyd[2621]: 2022-01-04T13:23:11Z [ERR!] - !!! caused by: could not load key pair: AZIOT_KEYS_RC_ERR_EXTERNAL Jan 04 13:23:11 vm-iot-edge-dev aziot-keyd[2621]: 2022-01-04T13:23:11Z [INFO] - --> 500 {“content-type”: “application/json”} Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 2022-01-04T13:23:11Z [ERR!] - Failed to provision with IoT Hub, and no valid device backup was found: DPS client error Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 2022-01-04T13:23:11Z [ERR!] - service encountered an error Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 2022-01-04T13:23:11Z [ERR!] - caused by: DPS client error Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 2022-01-04T13:23:11Z [ERR!] - caused by: internal error Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 2022-01-04T13:23:11Z [ERR!] - 0: <unknown> Jan 04 13:23:11 vm-iot-edge-dev aziot-identityd[11371]: 1: <unknown> Jan 04 13:23:11 vm-iot-edge-dev systemd[1]: aziot-identityd.service: Main process exited, code=exited, status=1/FAILURE Jan 04 13:23:11 vm-iot-edge-dev systemd[1]: aziot-identityd.service: Failed with result ‘exit-code’.

Top Results From Across the Web

Getting error "configuration has correct URIs for daemon ...

hi I am facing below issue while installing IoT Edge . ... Getting error "configuration has correct URIs for daemon mgmt endpoint -...

docker - Configuration Error in Azure IoT Edge installation - ...

I had this error because my IOT Hub networks "Public network access" was set as "Disabled". You can correct this by going the...

Setup Azure IOT Edge Runtime on the Raspberry Pi

This appear after "sudo systemctl status iotedge" command. "sudo iotedge check" returned: "config.yaml has correct URIs for daemon mgmt endpoint ...

Configuration Error in Azure IoT Edge installation - &quot

Coding example for the question Configuration Error in Azure IoT Edge installation - "configuration has correct URIs for daemon mgmt endpoint - Error"...

Libnvds_azure_edge_proto.so VS libnvds_azure_proto.so

I made a copy of the aziot directory and named it iotedge but still getting the above error. IOTCHECK. Configuration checks (aziot-identity- ...