Share via

aziot-edged is in a bad state. Unit aziot-edged.service entered failed state. aziot-edged.service failed.

Sabyasachi Mukherjee 0 Reputation points
2023-02-28T12:51:37.0566667+00:00

On running the - "sudo iotedge system status" I see the following message.

The system is running Linux and edge version is 1.4 

System services:
    aziot-edged             Down - activating
    aziot-identityd         Running
    aziot-keyd              Running
    aziot-certd             Running
    aziot-tpmd              Ready
aziot-edged is in a bad state because:
aziot-edged.service: Down - activating : Printing the last 10 log lines.
-- Logs begin at Mon 2023-02-27 20:57:20 CET, end at Tue 2023-02-28 13:30:16 CET. --
Feb 28 13:30:12 samhj1010 aziot-edged[215770]: 2023-02-28T12:30:12Z [DBUG] - [hyper::client::pool] pooling idle connection for ("http", keyd.sock)
Feb 28 13:30:12 samhj1010 aziot-edged[215770]: 2023-02-28T12:30:12Z [DBUG] - [hyper::proto::h1::io] flushed 86 bytes
Feb 28 13:30:12 samhj1010 aziot-edged[215770]: 2023-02-28T12:30:12Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:30:12 samhj1010 aziot-edged[215770]: 2023-02-28T12:30:12Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (1152 bytes)
Feb 28 13:30:12 samhj1010 aziot-edged[215770]: 2023-02-28T12:30:12Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:30:12 samhj1010 aziot-edged[215770]: 2023-02-28T12:30:12Z [DBUG] - [hyper::client::pool] pooling idle connection for ("http", certd.sock)
Feb 28 13:30:12 samhj1010 aziot-edged[215770]: 2023-02-28T12:30:12Z [INFO] - Using existing Edge CA certificate
Feb 28 13:30:12 samhj1010 systemd[1]: aziot-edged.service: main process exited, code=exited, status=1/FAILURE
Feb 28 13:30:12 samhj1010 systemd[1]: Unit aziot-edged.service entered failed state.
Feb 28 13:30:12 samhj1010 systemd[1]: aziot-edged.service failed.

The command "systemctl status iotedge" says

Unit iotedge.service could not be found.

sudo iotedge system logs -- -f logs is as follows:

sudo iotedge system logs -- -f

-- Logs begin at Mon 2023-02-27 20:57:20 CET. --
Feb 28 13:39:55 samhj1010 aziot-edged[222072]: 2023-02-28T12:39:55Z [INFO] - Stopping all modules...
Feb 28 13:39:55 samhj1010 aziot-edged[222072]: 2023-02-28T12:39:55Z [DBUG] - [edgelet_docker::runtime] Listing modules...
Feb 28 13:39:55 samhj1010 aziot-edged[222072]: 2023-02-28T12:39:55Z [DBUG] - [hyper::client::pool] reuse idle connection for ("unix", 25s66I72Af7Z756c2f646f636b657ZZc736f686b:0)
Feb 28 13:39:55 samhj1010 aziot-edged[222072]: 2023-02-28T12:39:55Z [DBUG] - [hyper::proto::h1::io] flushed 244 bytes
Feb 28 13:39:55 samhj1010 aziot-edged[222072]: 2023-02-28T12:39:55Z [DBUG] - [hyper::proto::h1::io] parsed 7 headers
Feb 28 13:39:55 samhj1010 aziot-edged[222072]: 2023-02-28T12:39:55Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (3 bytes)
Feb 28 13:39:55 samhj1010 aziot-edged[222072]: 2023-02-28T12:39:55Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:39:55 samhj1010 systemd[1]: aziot-edged.service: main process exited, code=exited, status=1/FAILURE
Feb 28 13:39:55 samhj1010 systemd[1]: Unit aziot-edged.service entered failed state.
Feb 28 13:39:55 samhj1010 systemd[1]: aziot-edged.service failed.
Feb 28 13:40:00 samhj1010 systemd[1]: aziot-edged.service holdoff time over, scheduling restart.
Feb 28 13:40:00 samhj1010 systemd[1]: Stopped Azure IoT Edge daemon.
Feb 28 13:40:00 samhj1010 systemd[1]: Started Azure IoT Edge daemon.
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [INFO] - Starting Azure IoT Edge Daemon
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [INFO] - Version - 1.4.0
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [INFO] - Obtaining Edge device provisioning data...
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (16 bytes)
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [INFO] - <-- POST /identities/device?api-version=2020-09-01 {"content-type": "application/json", "host": "identityd.sock", "content-length": "16"}
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 71 bytes
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 149 bytes
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (445 bytes)
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::client::pool] pooling idle connection for ("http", identityd.sock)
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [INFO] - Device is EdgeDeviceBKPPrd on mx-df-iwt-edge-hub-v3us-01-d.azure-devices.net
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [INFO] - Initializing module runtime...
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [INFO] - Using runtime network id azure-iot-edge
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 164 bytes
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (240 bytes)
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::client::pool] pooling idle connection for ("http", keyd.sock)
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 554 bytes
Feb 28 13:40:00 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 1 headers
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is empty
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [INFO] - <-- GET /key/device-id?api-version=2021-05-01 {"host": "keyd.sock"}
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 349 bytes
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 7 headers
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (445 bytes)
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::client::pool] pooling idle connection for ("unix", 25s66I72Af7Z756c2f646f636b657ZZc736f686b:0)
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [INFO] - Successfully initialized module runtime
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 179 bytes
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (61 bytes)
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [INFO] - <-- POST /keypair?api-version=2020-09-01 {"content-type": "application/json", "host": "keyd.sock", "content-length": "61"}
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 361 bytes
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (252 bytes)
Feb 28 13:40:00 samhj1010 aziot-edged[222101]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:00 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 1 headers
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is empty
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [INFO] - <-- GET /certificates/aziot-edged-ca?api-version=2020-09-01 {"host": "certd.sock"}
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 1262 bytes
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] parsed 1 headers
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] incoming body is empty
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [INFO] - <-- GET /certificates/aziot-edged-ca?api-version=2020-09-01 {"host": "certd.sock"}
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::io] flushed 1262 bytes
Feb 28 13:40:00 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:00Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:00 samhj1010 systemd[1]: aziot-edged.service: main process exited, code=exited, status=1/FAILURE
Feb 28 13:40:00 samhj1010 systemd[1]: Unit aziot-edged.service entered failed state.
Feb 28 13:40:00 samhj1010 systemd[1]: aziot-edged.service failed.
Feb 28 13:40:05 samhj1010 systemd[1]: aziot-edged.service holdoff time over, scheduling restart.
Feb 28 13:40:05 samhj1010 systemd[1]: Stopped Azure IoT Edge daemon.
Feb 28 13:40:05 samhj1010 systemd[1]: Started Azure IoT Edge daemon.
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [INFO] - Starting Azure IoT Edge Daemon
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [INFO] - Version - 1.4.0
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [INFO] - Obtaining Edge device provisioning data...
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 149 bytes
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (16 bytes)
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [INFO] - <-- POST /identities/device?api-version=2020-09-01 {"content-type": "application/json", "host": "identityd.sock", "content-length": "16"}
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 71 bytes
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (240 bytes)
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::client::pool] pooling idle connection for ("http", keyd.sock)
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 554 bytes
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 1 headers
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is empty
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [INFO] - <-- GET /key/device-id?api-version=2021-05-01 {"host": "keyd.sock"}
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 349 bytes
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (445 bytes)
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::client::pool] pooling idle connection for ("http", identityd.sock)
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [INFO] - Device is EdgeDeviceBKPPrd on mx-df-iwt-edge-hub-v3us-01-d.azure-devices.net
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [INFO] - Initializing module runtime...
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [INFO] - Using runtime network id azure-iot-edge
Feb 28 13:40:05 samhj1010 aziot-identityd[137650]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 164 bytes
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 7 headers
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (445 bytes)
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::client::pool] pooling idle connection for ("unix", 25s66I72Af7Z756c2f646f636b657ZZc736f686b:0)
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [INFO] - Successfully initialized module runtime
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 179 bytes
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (61 bytes)
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [INFO] - <-- POST /keypair?api-version=2020-09-01 {"content-type": "application/json", "host": "keyd.sock", "content-length": "61"}
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 361 bytes
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (252 bytes)
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::client::pool] pooling idle connection for ("http", keyd.sock)
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 86 bytes
Feb 28 13:40:05 samhj1010 aziot-keyd[137655]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 1 headers
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is empty
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [INFO] - <-- GET /certificates/aziot-edged-ca?api-version=2020-09-01 {"host": "certd.sock"}
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 1262 bytes
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 1 headers
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is empty
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [INFO] - <-- GET /certificates/aziot-edged-ca?api-version=2020-09-01 {"host": "certd.sock"}
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [INFO] - --> 200 {"content-type": "application/json"}
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 1262 bytes
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] parsed 3 headers
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body is content-length (1152 bytes)
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] incoming body completed
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::client::pool] pooling idle connection for ("http", certd.sock)
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [INFO] - Using existing Edge CA certificate
Feb 28 13:40:05 samhj1010 aziot-edged[222205]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::io] flushed 86 bytes
Feb 28 13:40:05 samhj1010 aziot-certd[137671]: 2023-02-28T12:40:05Z [DBUG] - [hyper::proto::h1::conn] read eof
Feb 28 13:40:05 samhj1010 systemd[1]: aziot-edged.service: main process exited, code=exited, status=1/FAILURE
Feb 28 13:40:05 samhj1010 systemd[1]: Unit aziot-edged.service entered failed state.
Feb 28 13:40:05 samhj1010 systemd[1]: aziot-edged.service failed.

I tried to reinstall IOTEdge, but that did not help. The config.toml also looks ok.

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.
561 questions