New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EdgeHub - TimeoutException: Message completion response not received #7203
Comments
Do we have any details/log for the receiving module? @lfitchett (on-call) please help take a look |
Unfortunaetely the cloudToDeviceMessageReceiver_log.txt
moduleClientBridge_log.txt
Ill try and see tomorrow if I can dig up any log files, but generally the only things logged inside those are our own log statements and there are no warnings or exceptions logged as a result of unhandles exceptions etc that could explain this behaviour. From my understanding they are sent from the cloudToDeviceMessageReceiver module to the moduleClientBridge module via routes which uses the edgeHub module for that communication and they just get somewhere betwwen sending them from the cloudToDeviceMessageReceiver module and receiving them to the moduleClientBridge module. |
@furier any updates? How urgent is this? |
@jlian it is pretty urgent, we have been struggling with multiple problems with edge and eflow-vm since December and our customer (we are consultants) is starting to rattle the cage and ask if we need to drop azure iot edge and go for a different solution due to all the stability issues we are facing and this is just one of them. I tried to recover some logs from our custom modules, but not able to through the propper channels like the Diving into |
Hey @jilan, Not sure if you've had any breakthroughs, but from my side, the issue's been out of sight since we stopped the regular system reboots. However, I'm pretty sure it's not actually resolved, just not being provoked. We will reintroduce the frequent rebooting schedule to see if the issue becomes more prevalent again. Are there any updates or insights you've come across? If there’s anything specific you need from me to further the investigation, I’m available to help out. Just a heads up, accessing old logs might not be possible anymore. But I’m here to help with anything else you might find useful. |
Expected Behavior
EdgeHub should be able to send messages to other modules without timeout exceptions
Current Behavior
EdgeHub using
Microsoft.Azure.Devices.Edge.Hub.Core.Device.DeviceMessageHandler.SendMessageAsync
causesTimeoutException
when trying to send messages between modules.This causes incoming messages from the cloud to device to not be received by the consumer (end) module. Usually, a reboot of the edgeHub causes the pending messages to flow to the consumer module but shortly after the same exception occurs and we end up in the same error state where messages do not flow to it's final destination.
Context (Environment)
Output of
iotedge check
Click here
Device Information
Runtime Versions
1.4.20
mcr.microsoft.com/azureiotedge-agent:1.4
mcr.microsoft.com/azureiotedge-hub:1.4
20.10.25
Logs
aziot-edged logs
edge-agent logs
edge-hub logs
iotedge logs edgeHub --tail 500
PS: I had to manually try and delete stuff from the logs that was repetitive to make the post fit within 65k characters... and the bug may be related to this issue #7036 (comment)
The text was updated successfully, but these errors were encountered: