IoTEdge daemon/edgeAgent hit issues from bootup (an error occurred trying to connect: Permission denied (os error 13))

[Devinwong]

We are working on enabling IoTEdge on Embedded Linux with Ambarella Computer Vision chipset.
Now Moby and IoTEdge daemon are installed But it seems daemon/edgeAgent hit some issues.
Could you help to take a look?

1. IoTEdgeD brought up by OS service from bootup
   Hit this error.
   an error occurred trying to connect: Permission denied (os error 13)
   Please see attached journallog.iotedge

2. Iotedge check.
   Everything looks good except EdgeHub.
   Please see iotedge.check.log

3. Manually run iotedged -c /etc/iotedge/config.yaml.
   Saw this as info. <6>2019-12-23T03:45:58Z [INFO] - Edge runtime status is failed, starting module now...
   Please see iotedged.log.

logs with IoTEdge_1.0.8-1.zip

We are using the following packages.
https://github.com/Azure/azure-iotedge/releases/download/1.0.8/libiothsm-std_1.0.8-2_arm64.deb
https://github.com/Azure/azure-iotedge/releases/download/1.0.8/iotedge_1.0.8-1_arm64.deb
It doesn’t have any package management tool on that embedded linux distribution.
So we put the files to corresponding locations manually.

[darobs]

Hello @Devinwong,

This is the most likely problem:

× config.yaml has correct URIs for daemon mgmt endpoint - Error
Error: could not execute list-modules request: an error occurred trying to connect: Connection refused (os error 111)
caused by: docker returned exit code: 1, stderr = Error: could not execute list-modules request: an error occurred trying to connect: Connection refused (os error 111)

The first thing to check would be check if the iotedged daemon is running as a specific user (typically iotedge), and make sure that user has access to Docker. We do that in the Debian package by adding iotedge to the docker group.

Some of the additional work that the packaging does is here: edgelet/contrib/debian/preinst

[Devinwong]

Thanks David. will try it out and get back to you.

[Devinwong]

Reviewed the iotedge user/group permission but still saw the error.
Finally changing the permission of config.yaml to 777 did the trick.
Thanks.