Change a module's runtime status from stopped to running

Omar Navarro 331 Reputation points
2022-04-12T15:32:26.81+00:00

The initial deployment manifest is applied with a bash script. One module initiates in the "stopped" state.

az iot edge set-modules --hub-name "$IOT_HUB_NAME" --device-id "$DEVICE_ID" --content "$MANIFEST_FILE_PATH" --only-show-error -o table  

What's the best way to update the module's status to "running"

192329-stopped.png

Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
663 questions
Azure IoT Central
Azure IoT Central
An Azure hosted internet of things (IoT) application platform.
357 questions
Azure IoT Hub
Azure IoT Hub
An Azure service that enables bidirectional communication between internet of things (IoT) devices and applications.
1,146 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sander van de Velde | MVP 30,551 Reputation points MVP
    2022-04-12T18:27:16.83+00:00

    Hello @Omar Navarro ,

    you deployed an Azure IoT Edge module which is now marked as stopped.

    In general, the desired status of a module is configured in the Deployment manifest:

    192425-image.png

    It cannot be manipulated separately.

    In the Azure portal, you find the setting here:

    192453-image.png

    So, you need to deploy the manifest again. The EdgeAgent will pick it up and check for the differences.

    What I expect is that the module 'crashed'. Please check the logging of the individual module for clues why the module stopped.

    On the device, you can access the log using the command line:

    sudo iotedge logs -f [modulename]

    Or, use the troubleshoot option in the Azure portal:

    192454-image.png

    0 comments No comments

0 additional answers

Sort by: Most helpful