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
All Modules Failing to GetTwinAsync #3382
Comments
I changed my system's name to a new name based on this thread and it looks to have resolved the issue: #1269 I previously already had the system name as all lowercase, but changing it again to a different all lowercase name seems to have fixed the issue. |
@ejectbutton Glad to hear you got past this issue. Would you mind sharing what your original hostname (the one that didn't work) was? |
@ejectbutton Would you mind sharing your original hostname? Thanks! |
The hostname was changed from 'intconnect' to 'edgedevice'. They were both 10 letters, all lowercase |
I ran into this exact same issue. Same versions of everything. I did not want to change the hostname of my pc so I dug into other possible things to change and I found something that got mine working: I hope that info helps. config.yaml section i changed:
|
Expected Behavior
When my modules attempt to get their DeviceTwin through GetTwinAsync, they're able to pull down their device twin successfully.
Current Behavior
All modules besides edgeAgent & edgeHub on my machine sit for 4-5 minutes until returning an IoTHubCommunicationException: Transient network error occurred, please retry. As well as SocketExpection (11001)L No such host is known.
Steps to Reproduce
Provide a detailed set of steps to reproduce the bug.
Context (Environment)
Output of
iotedge check
Click here
Device Information
Runtime Versions
iotedge version
]: 1.0.9.4docker version
]: 19.03.12Note: when using Windows containers on Windows, run
docker -H npipe:////./pipe/iotedge_moby_engine version
insteadLogs
iotedged logs
edge-agent logs
edge-hub logs
custom module logs
Additional Information
These modules all work perfectly fine in a simulator. From my perspective, the only problem occurs when trying to execute this code from within the edge runtime.
The timing of this issue starting is close to when I was trying to resolve some edgeHub storage binding warnings from the iotedge check command. Would be interested to know if this is an issue related to edgeHub 1.0.9.
Thank you.
The text was updated successfully, but these errors were encountered: