Azure edgeAgent in N/A status on Azure portal for 4 out 20 devices

RJ 6

I deploy around 20 IoT Edge devices using automation script ARM/azure cli commands. These edge devices are nothing but VMs. I provision the edge Devices by specifying cloud-init config in VM ARM template. However out of 20, around 3-4 devices somehow have edge Agent in N/A state.

I checked the logs on the respective VMs, iotedge list shows edgeAgent is in running state. But I do see some errors in the edgeAgent logs. Attaching the screenshot.

Another thing I notice is, on the portal when I navigate to an edgeDevice whose status is N/A, and click on Troubleshoot->Restart Edge Agent , the edgeAgent comes to correct state. But I cannot do this manually for all offline devices. Can somebody help me with the root cause, as to why this is happening in few devices and few devices are all fine.

Edge runtime version I used is : 1.2.0

Sander van de Velde 28,236 Reputation points MVP

2021-06-13T22:24:49.567+00:00

Hello @RJ ,

I'm not sure if all devices have the same issue.

Regarding the state of your devices, this can take some time until this is represented in the right way in the IoT Hub.

You deploy the Azure IoT Edge runtime using a script.

Did you also assign (custom) modules in the deployment manifest already?

Does this give the same result?
RJ 6 Reputation points

2021-06-14T05:53:15.977+00:00

Hi @Sander van de Velde ,

No, all the devices does not show the same problem, a few among them does.

How much time is expected, because I have checked it for an hour or so, it never comes to correct state.

Yes, the IoT edge runtime is installed using cloud-init script, I do not assign any custom modules yet as I first expect the device to be in correct state which is : 417 -- The device's deployment configuration is not set

I also tired assigning the custom modules, but in that case also it has the same problem, device remains in N/A state and all modules including custom module also remain in N/A state.

As I said in my last post, if I do Troubleshoot->Restart Edge Agent , the device then comes to correct state. But since I need to deploy around say 50 devices, I cannot manually troubleshoot on the devices which has this problem.

Do you have any insight on the error "Updating reported properties failed with error The operation timed out"?
Sander van de Velde 28,236 Reputation points MVP

2021-06-14T07:04:15.153+00:00

Hello @RJ ,

thanks for the clarification.

No, this message does not sound familiar to me.

It seems to reach out to the IoTHub to update reported properties...

Can you double-check your edge devices are able to connect to the cloud (eg. ping 8.8.8.8 for HTTP)?

Depending on the protocol you use (AMQP, MQTT, over Websockets or not) are you sure there is no outbound limitation on any firewall?

If this all should work, please create an issue on the related Azure IoT Edge open source repo on .GitHub
RJ 6 Reputation points

2021-06-14T07:09:46.803+00:00

All the devices are deployed using the same ARM script and same configuration. A few of them is having the problem , rest are good. So, I do not suspect any firewall configuration issue here. However I can double check, and let you know if I see any problems.

Can this happen due to throttling? Is there a way I can handle it, by running some kind of post install script or something?

I will raise the issue to the Git repo you pointed to as well.

After I deploy my custom modules:
Sander van de Velde 28,236 Reputation points MVP

2021-06-14T21:19:51.447+00:00

Hello @RH-3404,

it's hard to make a solid statement about this behavior from here :-)

Please share any findings from the Github issue (number?) here, please.
RJ 6 Reputation points

2021-06-15T04:18:01.313+00:00

Hi @Sander van de Velde

Here is the github issue I created yesterday: https://github.com/Azure/iotedge/issues/5106

There it is suggested to create a support ticket.

Thanks,
RJ
AshokPeddakotla-MSFT 27,296 Reputation points

2021-06-15T14:14:44.407+00:00

@RH-3404, I see that you have created a support request. We hope you issue will be resolved by our support team. Once your issue is resolved, feel free to share the resolution.