Correct way to stop and start custom modules in Azure IoT

Satyam Chauhan 547

Hi,

I have created 2 Custom Modules, 1st module gets message from an API and sends it to the 2nd Module. 2nd Module does some processing and sends it to IoT Hub. I have followed steps from tutorial-csharp-module after I do build and publish and Create deployment for single device the Modules start running, and I have no idea how to stop and then start them again.

Please help, as I am very new to it.

Thanks and Regards,
Satyam

QuantumCache 20,271 Reputation points

2022-09-15T15:53:36.46+00:00

Hello @Satyam Chauhan ,

Once we deploy IoT Edge device, the basic deployment manifest of 'systemModules' contains 'edgeHub' and 'edgeAgent' modules and are in 'running' state by default.

IoT Edge modules do not cost money if they are not sending messages to IoT Hub.

If the intention is to stop IoT Edge runtime, then on device side there is the command
(on Windows for eg.): Powershell command

Stop-Service iotedge -NoWait

(on Linux for eg.): Single line bash command

sudo systemctl stop iotedge

For more info please see: Restart the IoT Edge security manager

You can always verify the IoT Edge status by using below commands

Powershell: iotedge list

bash: sudo iotedge list
Satyam Chauhan 547 Reputation points

2022-09-16T03:54:53.987+00:00

Hello @QuantumCache , thanks for the quick response.

I tried the Linux bash command as I am using RHEL 8, sudo systemctl stop iotedge, but its giving error - Failed to stop iotedge.service: Unit iotedge.service not loaded.

Please help!

Accepted answer

QuantumCache 20,271 Reputation points

2022-09-16T05:40:23.897+00:00
Hello @Satyam Chauhan ,

I have deployed an IoTEdge Device with RHEL8.1 for this scenario and tested quickly few module deployments and their status management..

Please follow the below instructions on how to properly manage the IoT Edge modules.

Starting and stopping of the modules depends on the IoT Edge deployment on the device, and is controlled by EdgeAgent by design.
If you want to stop the module, the way to do that is to create a new deployment with the module status as Stopped. You can also stop the entire IoT Edge runtime ($>sudo iotedge system stop), which will stop the modules as well.

Creating deployment from the portal: you have to choose the desired state of the Module and then submit the deployment for that device.

Once the Deployment is submitted from the Azure portal, i see the particular module is now stopped.

Run the below commands on the device.

sudo iotedge system stop

sudo iotedge system restart

If the response is helpful, please click "Accept Answer" and upvote it.

Happy to Help you! Please leave your comments in the below section for further help in this matter.
Please sign in to rate this answer.

2 people found this answer helpful.
QuantumCache 20,271 Reputation points

2022-09-22T18:08:01.37+00:00

Hello @Satyam Chauhan If the response is helpful, please click "Accept Answer" and upvote it.
So that we close this thread and is useful to the community.

FFTechDept 5 Reputation points

2024-08-03T11:25:37.1966667+00:00

Hi, thanks for your helpful info!

Just to better know, inside the device page at the modules panel I can see message 406 and this seems ok to me because the device is stopped; instead into the table at the bottom of the page the status runtime stated Error it is right when the device is stopped?

Also by using the command on the IoT device:

sudo iotedge list

the status of the SimulatedTemperatureSensor (I've followed the Quickstart tutorial Linux on Windows machine) is set to Failed (139) and not on stopped as requested through the Azure portal following the steps you detailed above.

Thanks and best regards.

F.F.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.