Error starting edged

SB 56 Reputation points
2022-03-28T23:11:21.7+00:00

We are receiving this error:

Mar 28 18:56:56 FLASH001 systemd[1]: aziot-edged.service: Main process exited, code=exited, status=1/FAILURE
Mar 28 18:56:56 FLASH001 systemd[1]: aziot-edged.service: Failed with result 'exit-code'.
Mar 28 18:57:02 FLASH001 systemd[1]: aziot-edged.service: Scheduled restart job, restart counter is at 40.
Mar 28 18:57:02 FLASH001 systemd[1]: Stopped Azure IoT Edge daemon.
Mar 28 18:57:02 FLASH001 systemd[1]: Started Azure IoT Edge daemon.
Mar 28 18:57:02 FLASH001 aziot-edged[6178]: 2022-03-28T22:57:02Z [INFO] - Starting Azure IoT Edge Module Runtime
Mar 28 18:57:02 FLASH001 aziot-edged[6178]: 2022-03-28T22:57:02Z [INFO] - Version - 1.2.8
Mar 28 18:57:02 FLASH001 aziot-edged[6178]: 2022-03-28T22:57:02Z [ERR!] - The daemon could not start up successfully: Could not create cache directory
Mar 28 18:57:02 FLASH001 aziot-edged[6178]: 2022-03-28T22:57:02Z [ERR!] - caused by: Permission denied (os error 13)
Mar 28 18:57:02 FLASH001 systemd[1]: aziot-edged.service: Main process exited, code=exited, status=1/FAILURE
Mar 28 18:57:02 FLASH001 systemd[1]: aziot-edged.service: Failed with result 'exit-code'.
Mar 28 18:57:04 FLASH001 systemd[1]: aziot-edged.service: Failed to schedule restart job: Unit aziot-edged.service is masked.
Mar 28 18:57:04 FLASH001 systemd[1]: aziot-edged.service: Failed with result 'exit-code'.

And on Config apply:

*omnicell@FLASH001:~$ sudo iotedge config apply
Azure IoT Edge has been configured successfully!
Restarting service for configuration to take effect...
Stopping aziot-edged.service...Stopped!
Stopping aziot-identityd.service...Stopped!
Stopping aziot-keyd.service...Stopped!
Stopping aziot-certd.service...Stopped!
Stopping aziot-tpmd.service...Stopped!
systemctl exited with non-zero status code.

stdout:

stderr:

Starting aziot-edged.mgmt.socket...Failed to start aziot-edged.mgmt.socket: Unit aziot-edged.mgmt.socket is masked.
systemctl exited with non-zero status code.

stdout:

stderr:

Starting aziot-edged.workload.socket...Failed to start aziot-edged.workload.socket: Unit aziot-edged.workload.socket is masked.
systemctl exited with non-zero status code.

stdout:

stderr:

Starting aziot-identityd.socket...Failed to start aziot-identityd.socket: Unit aziot-identityd.socket is masked.
systemctl exited with non-zero status code.

stdout:

stderr:

Starting aziot-keyd.socket...Failed to start aziot-keyd.socket: Unit aziot-keyd.socket is masked.
systemctl exited with non-zero status code.

stdout:

stderr:

Starting aziot-certd.socket...Failed to start aziot-certd.socket: Unit aziot-certd.socket is masked.
systemctl exited with non-zero status code.

stdout:

stderr:

Starting aziot-tpmd.socket...Failed to start aziot-tpmd.socket: Unit aziot-tpmd.socket is masked.
systemctl exited with non-zero status code.

stdout:

stderr:

Starting aziot-edged.service...Failed to start aziot-edged.service: Unit aziot-edged.service is masked.*

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.
580 questions
{count} vote

1 answer

Sort by: Most helpful
  1. SB 56 Reputation points
    2022-03-29T16:51:40.907+00:00

    We've gotten the edged to start but keyd, identityd and certd are in error due to missing sock files:

    × keyd is running - Error
    Could not connect to keyd on unix:///run/aziot/keyd.sock
    × certd is running - Error
    Could not connect to certd on unix:///run/aziot/certd.sock
    × identityd is running - Error
    Could not connect to identityd on unix:///run/aziot/identityd.sock


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.