This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
[V2] Problems connecting and sending data #545
Labels
Comments
|
Hi @termocontrole , From your logs looks like you are having problems on modbus module. It's getting connected to edge hub, but I can see that it's keeping having TLS Handshake failures. Also, there was a time that you went Out of memory, which can be a problem that you are not able to send message to IoT Hub. So, here is what I recommend: So, uninstall everything, make sure you have enough memory on your device (cleaning up logs) and do a deployment turning Debug logs and changing the route to the above. 3rd - Make sure you are using the latest version of both Device SDK and edge hub. Let us know how it goes, Thanks, Angelo Ribeiro. |
|
Hi @aribeironovaes, I followed your instructions and reinstalled everything, but this time with the debug logs on. First, the debug logs helps a lot to understand what is going on with Second, things are working, the data is send from So, thank you very much for that. But there is still somethings that I want to understand better: edgeHub logs: If you look at my edgeHub logs, you are going to see that the modbus token is renewed every one hour, because the token is set to expire every one hour, is this default? Can I change the validity of this token somewhere? Another question is that sometimes appers Thank you very much. |
|
Hi @termocontrole , Great that it's working. I'm not sure about the TLS handshake, it can be just a side effect of the token expiring. Hope this helps, and let us know if there is anything else on this github issue that we can help. Thanks, Angelo Ribeiro. |
|
Hi @aribeironovaes, Cool, I understand better now, I'm going to see with the modbus team. Thank you. |
|
Hi, As far as I know, there is no place to explicitly configure the token expiration time in current C# Microsoft.Azure.Devices.Client SDK. Modbus module is written based on the sample TempSensor module as a template. So I checked the sample tempSensor module log that I collected a couple weeks ago and found tempSensor module also renew its token every one hour. So I think it might worth checking with the Microsoft.Azure.Devices.Client SDK team if this is a expected behavior. Thanks, |
|
Hi, Thank you @606simps. So seems that this token expiration time is default and maybe it's not configurable. If that's true, it's ok for me, but I'm still thinking if it's this that is causing the I don't know what is the Microsoft.Azure.Devices.Client SDK team repo to open an issue referring to this, I found two that could be: Azure SDK for NET or Azure IoT SDK C. I think is the second one, but I'm not sure. So, does anyone know where or with whom I can get this information? Thank you very much. |
|
Hi,
The github is: https://github.com/Azure/azure-iot-sdk-csharp (for modules
they have a modules_preview branch).
Thanks,
Angelo Ribeiro
…On Fri, Mar 30, 2018 at 9:48 AM, termocontrole ***@***.***> wrote:
Hi,
Thank you @606simps <https://github.com/606simps>.
So seems that this *token expiration time* is default and maybe it's not
configurable. If that's true, it's ok for me, but I'm still thinking if
it's this that is causing the TLS handshake failure and if there is any
consequence of that happening or if this is the expected behavior as
pointed by @606simps <https://github.com/606simps>.
I don't know what is the *Microsoft.Azure.Devices.Client SDK team repo*
to open an issue referring to this, I found two that could be: *Azure SDK
for NET <https://github.com/Azure/azure-sdk-for-net>* or *Azure IoT SDK C
<https://github.com/Azure/azure-iot-sdk-c>*. I think is the second one,
but I'm not sure.
So, does anyone know where or with whom I can get this information?
Thank you very much.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#545 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AI75b3yIU5YgkGZkX-TCLtrn45MiROUVks5tjmHsgaJpZM4SsI9c>
.
--
---
Angelo Ribeiro
Msc - Federal University of Pernambuco
Team in Training Alumni Triple Crowned! :)
|
|
Thank you @aribeironovaes, I opened an issue there. |
|
Closing as this issue seems to be resolved. Please reopen if you continue to run into it. Thanks! |
|
Hi @myagley, Unfortunately the problem wasn't solved, it is still happening, mainly the Please, can you help there? (issue) Well, it seems I can't reopen the issue :( Thank you very much. |
|
The The exceptions seen on platforms at the low end of our HW requirements (like Pi) are being tracked in #475. |
|
Thanks @damonbarry for the clarifications, I will follow that issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I´m using a Raspberry Pi with Azure IoT Edge V2 and the modbus module, in the beginning the modbus module had some issues, but we were abble to track and solve it.
Now the messages are not correctly sent to IoT Hub, a lot of messages seems to be missed: some times it connects and send data to Hub, other times doesn´t connect and there are times that seems to be connected but doesn´t send any data to the endpoint.
I don´t know how to debug the IoT Edge V2 or turn the debug flags on to better understand whats heppening.
Here is my logs from 13-03 to 15-03:
13-03 - IoT Edge connected in portal but sending no data.
14-03 - IoT Edge connected in portal but sending no data.
15-03 - Warning: Your device is disconnected from this IoT Hub. The information displayed below is not up to date. You can go to the device twin to see the last update time. If you have not set up your IoT Edge device, please follow IoT Edge QuickStart instructions. If you have already set up your device, please check device connectivity.
edgeAgent:
edgeHub:
Can someone help me?
Thank you
The text was updated successfully, but these errors were encountered: