edgeHub module won't start after certificate renewal #7397
Comments
|
EdgeHub shouldn't need to be manually restarted for certificate renewal @vadim-kovalyov (on-call) can you help take a look? Might be related to #7321 |
|
I would check two things, that "restartPolicy": "always" for edgeHub container in the deployment manifest, and also that if the device was offline at the time the cert renewed then it indeed might be related to #7321. Although from the log snippet of EdgeAgent this doesn't look like offline case. Also, just a not that 1.4 LTS version support ended this month, we have a bunch of fixes in 1.5 version, so I would try to upgrade to see if that helps. |
|
Thank you for your responses. I've checked the restart policy, and it is set to "always" (which I am quite sure is the default). |
|
Maybe you can provide more details on the device setup and share your config.toml file (please redact all sensitive info) so we can check that configuration is ok. For example, if using EST, the cert renewal only works with DPS CA-based provisioning and is not supported for any other types of provisioning. It looks like your setup is simpler, but wanted to double check. |
|
I'm using symmetrical key and my connection string is established as part of my initialization of the device.
The problem i have is that when i issue a sudo reboot command, the edgeHub does not gracefully shut down the device. It just does not go down all the way, and hence does not reboot.
My work around is to issue a
Iotedge system stop first, then issue the sudo shutdown. This works perfectly everytime.
From my review, the broadcast issued via the reboot is not working correctly, but the shutdown request using iotedge is.
My custom module, I feel is working correct, as it gracefully shutdown using either method.
Hth,
R
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Vadim Kovalyov ***@***.***>
Sent: Monday, December 2, 2024 11:52:07 AM
To: Azure/iotedge ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [Azure/iotedge] edgeHub module won't start after certificate renewal (Issue #7397)
Maybe you can provide more details on the device setup and share your config.toml file (please redact all sensitive info) so we can check that configuration is ok. For example, if using EST, the cert renewal only works with DPS CA-based provisioning and is not supported for any other types of provisioning. It looks like your setup is simpler, but wanted to double check.
—
Reply to this email directly, view it on GitHub<#7397 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEVJVPQXTE4A7L22CGSJGD2DS26PAVCNFSM6AAAAABSOBKLZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJSGYZDSNZTGE>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Expected Behavior
edgeHub module restart successfuly after cert renewal
Current Behavior
edgeHub shuts down and stay in this state until manual restart
Steps to Reproduce
Just running iotEdge on a device. No perticular scenario
Context (Environment)
PROD
Output of
iotedge checkClick here
Device Information
Runtime Versions
Logs
aziot-edged logs
edge-agent logs
edge-hub logs
Additional Information
Please provide any additional information that may be helpful in understanding the issue.
The text was updated successfully, but these errors were encountered: