search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.28k stars 21.46k forks source link

Errors after configuring ioedge in stm32mp1 device #81428

Closed EnricoBeltramo closed 3 years ago

EnricoBeltramo commented 3 years ago

I'm configuring IOEdge on a stm32m1 device (Openstlinux os), I configured the device as suggested in: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge?view=iotedge-2018-06&preserve-view=true It looks to work fine, but when I run: iotedge check it say some errors. In particular way, I dont understand why it say that:

config.yaml has hostname stm32m1 but device reports hostname stm32mp1.

the complete host name in azure connection string is: stm32m1board.azure-devices.net

in configuration file I set actually: hostname: "stm32m1"

I tried different variants like: hostname: "stm32m1board.azure-devices.net" hostname: "stm32m1board"

but I have always an check error.

I have other ambigous messages, like: × container time is close to host time - Error (is an error?) × production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error (is an error?)

There is a way to fix them?

I attach below the complete error log:

× config.yaml has correct hostname - Error config.yaml has hostname stm32m1 but device reports hostname stm32mp1. Hostname in config.yaml must either be identical to the device hostname or be a fully-qualified domain name that has the device hostname as the first component. √ config.yaml has correct URIs for daemon mgmt endpoint - OK ‼ latest security daemon - Warning Installed IoT Edge daemon has version 1.0.9.4 but 1.1.6 is the latest stable version available. Please see https://aka.ms/iotedge-update-runtime for update instructions. √ host time is close to real time - OK × container time is close to host time - Error Detected time drift between host and container ‼ DNS server - Warning Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub. Please see https://aka.ms/iotedge-prod-checklist-dns for best practices. You can ignore this warning if you are setting DNS server per module in the Edge deployment. ‼ production readiness: certificates - Warning The Edge device is using self-signed automatically-generated development certificates. They will expire in 89 days (at 2021-12-21 12:29:46 UTC) causing module-to-module and downstream device communication to fail on an active deployment. After the certs have expired, restarting the IoT Edge daemon will trigger it to generate new development certs. Please consider using production certificates instead. See https://aka.ms/iotedge-prod-checklist-certs for best practices. ‼ production readiness: container engine - Warning Device is not using a production-supported container engine (moby-engine). Please see https://aka.ms/iotedge-prod-checklist-moby for details. ‼ production readiness: logs policy - Warning Container engine is not configured to rotate module logs which may cause it run out of disk space. Please see https://aka.ms/iotedge-prod-checklist-logs for best practices. You can ignore this warning if you are setting log policy per module in the Edge deployment. ‼ production readiness: Edge Agent's storage directory is persisted on the host filesystem - Warning The edgeAgent module is not configured to persist its /tmp/edgeAgent directory on the host filesystem. Data might be lost if the module is deleted or updated. Please see https://aka.ms/iotedge-storage-host for best practices. × production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error Could not check current state of edgeHub container

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

asergaz commented 3 years ago

@EnricoBeltramo Thanks for the feedback! We are currently investigating and will update you shortly.

asergaz commented 3 years ago

@EnricoBeltramo did you consider using the latest version of IoTEdge 1.2?

See also Azure IoT Edge supported systems. Please note that Openstlinux is not listed as a supported OS.

Thanks

EnricoBeltramo commented 3 years ago

In ST official site there is a tutorial how integrate Azure IO edge on stm32m1 on openstlinux, so I supposed was compatible: https://wiki.st.com/stm32mpu/wiki/How_to_integrate_Azure_IoT_Edge_on_OpenSTLinux

unfortunately the release provided looks to be only IoTEdge 1.1.

Despite the errors and the warning, the image distibution works well, I'm only worried about possible production issues. That errors are know issues?

asergaz commented 3 years ago

Hello @EnricoBeltramo, since this doc is targeting specifically Ubuntu Server 18.04 and Raspberry Pi OS Stretch steps I am closing the issue to maintain the focus on the other related issue you opened: https://github.com/Azure/meta-iotedge/issues/72

I would suggest that you also open an issue in https://github.com/Azure/iotedge/issues and make sure you cross-reference them if you are not having good traction in the meta-iotedge repo.

Despite the errors and the warning, the image distibution works well, I'm only worried about possible production issues. That errors are know issues?

Thank you so much!

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.