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"

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: It cannot be manipulated separately. In the Azure portal, you find the setting here: 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:

Change a module's runtime status from stopped to running

Accepted answer

Sander van de Velde | MVP 33,956 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:

It cannot be manipulated separately.

In the Azure portal, you find the setting here:

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:
Please sign in to rate this answer.
FFTechDept 5 Reputation points

2024-08-03T13:31:21.7766667+00:00

Thanks for the explanation, I've the trouble in stopping a running module, performing the steps through the portal I got an error exception into the device and the STATUS is set to Failed(139) instead stopped, instead if I put the state on running all goes fine.
Do you have some hint?

Thanks!!

F

Sander van de Velde | MVP 33,956 Reputation points MVP

2024-08-04T19:53:52.5866667+00:00

Hello @FFTechDept,

It seems your module runs into an error state (crashed?) while stopping.

Check your code for any errors while the module shits down (not so) gracefully.

FFTechDept 5 Reputation points

2024-08-05T07:55:28.1833333+00:00

Dear Sander thanks for your reply!
About the module I've just followed the tutorial "Quickstart: Deploy your first IoT Edge module to a Windows device" that is at this URL:

https://zcusa.951200.xyz/en-us/azure/iot-edge/quickstart?view=iotedge-1.5

all is working nice exactly as stated into the tutorial; the only problem is when I try to put the module into the stopped state because I got this error... do you have some idea?

Thanks and best regards.
F.

Sander van de Velde | MVP 33,956 Reputation points MVP

2024-08-05T18:33:28.81+00:00

Hello @FFTechDept ,

This seems to be the test module Microsoft normally uses:

mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:latest

You could try to check the log on the device itself:

sudo iotedge logs -f SimulatedTemperatureSensor

I normally use Linux as Host OS. I expect this also works for EFLOW.

FFTechDept 5 Reputation points

2024-08-06T07:54:37.5633333+00:00

Dear Sander, you're right this is the standard temperature sensor simulation model used into the Microsoft tutorial.
I've did the log after setting the module into the stop state from the Azure portal.
below the log related the execution of the command you suggest above before sending the command and after.
Before set the stop state (so the module is in running mode and we have no errors reported on the Azure portal), after doing the Connect-EflowVm command into a elevated powershell session I've the following log.

iotedge-user@WIN-11-EFLOW [ ~ ]$ sudo iotedge logs -f SimulatedTemperatureSensor [2024-08-05 16:54:12 : Starting Module SimulatedTemperatureSensor Main() started. Initializing simulated temperature sensor to send 500 messages, at an interval of 5 seconds. To change this, set the environment variable MessageCount to the number of messages that should be sent (set it to -1 to send unlimited messages). [Information]: Trying to initialize module client using transport type [Amqp_Tcp_Only]. [Information]: Successfully initialized module client of transport type [Amqp_Tcp_Only]. 08/05/2024 16:54:35> Sending message: 1, Body: [{"machine":{"temperature":21.284244890403656,"pressure":1.0323823292864924},"ambient":{"temperature":20.674505282854714,"humidity":24},"timeCreated":"2024-08-05T16:54:35.8457935Z"}] 08/05/2024 16:54:41> Sending message: 2, Body: [{"machine":{"temperature":22.299600446308304,"pressure":1.1480557470477815},"ambient":{"temperature":21.214386603905496,"humidity":25},"timeCreated":"2024-08-05T16:54:41.0656743Z"}] 08/05/2024 16:54:46> Sending message: 3, Body: [{"machine":{"temperature":22.25747457216312,"pressure":1.1432565968287096},"ambient":{"temperature":21.102622243322223,"humidity":24},"timeCreated":"2024-08-05T16:54:46.0808271Z"}] 08/05/2024 16:54:51> Sending message: 4, Body: [{"machine":{"temperature":22.241264669508144,"pressure":1.1414098990578898},"ambient":{"temperature":21.256542583169825,"humidity":24},"timeCreated":"2024-08-05T16:54:51.0944364Z"}]

it seems to me ok.

Now I'll stop the module from the Azure portal and here below the last logs rows using same commands.

08/06/2024 07:47:10> Sending message: 422, Body: [{"machine":{"temperature":106.80596127947508,"pressure":10.775362677408554},"ambient":{"temperature":20.79569570097135,"humidity":25},"timeCreated":"2024-08-06T07:47:10.6433541Z"}] Unhandled exception. System.AggregateException: One or more errors occurred. (A task was canceled.) ---> System.Threading.Tasks.TaskCanceledException: A task was canceled. at System.Threading.Tasks.Task.GetExceptions(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at SimulatedTemperatureSensor.Program.Main() in /mnt/vss/_work/1/s/edge-modules/SimulatedTemperatureSensor/src/Program.cs:line 48 --- End of stack trace from previous location --- --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at SimulatedTemperatureSensor.Program.Main() in /mnt/vss/_work/1/s/edge-modules/SimulatedTemperatureSensor/src/Program.cs:line 48 iotedge-user@WIN-11-EFLOW [ ~ ]$

the module crash, on the Azure portal I've the following situation.

Thanks for your help.

Best regards.

F.
Sign in to comment

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

Share via

Change a module's runtime status from stopped to running

0 additional answers

Your answer