-
Notifications
You must be signed in to change notification settings - Fork 462
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
Temporary name resolution on module with network host #6374
Comments
Hello, Anyone could help me please? I'm blocked rigth now. |
@amunozh - 'Temporary failure in name resolution' is a DNS issue, not specific to Edge Hub. For one, try restarting docker. But more importantly, you are on very old versions of EdgeAgent and EdgeHub. Your iotedge daemon is 1.1.13, but EA and EH are 1.0.0 -- please update them to 1.1.13 and try again. Please do not continue to use 1.0.0 |
@amunozh it is not clear from the logs what name you use to connect to edgeHub. But just in case, you can't use |
Please reopen if you have further questions |
Hello, I'm reopening because I did not solve the problem. I just updated all the runtime environment:
I'm not directly connecting to the edgeHub with any addess because I'm using the Python SDK, therefore to create the client connection with the edgeHub I'm using the following code:
When creating from edge environment it crashes. |
@amunozh the code you provided should work as is. There is something going on with the networking on you system. Check UPD: is there are reason you use |
Hello @vadim-kovalyov. Thanks for your replies. I don't know why that module is not taking into consideration the environment variable Logs of the module Click here
Environmental variables Click here
Configuration of the module in the deployment
PD: I set |
UPDATE: I tried the commands you said before @vadim-kovalyov :
|
About websocket - the main use case is for isolated environments, where firewall rules don't allow MQTT or AMQP ports, but only HTTPS (433), and/or if you use HTTP proxy to connect to the outside world. Unless you have a good reason, I would not use WebSocket for module2module communication, it adds overhead with no apparent benefits. Just use MQTT. You must not set Also, make sure that |
Since we haven't heard back, presumably, the enquiry has been addressed. Please reopen if there are further questions. |
Expected Behavior
I'm developing a module that needs to access to the bluetooth stack. Therefore, I configured it with network host. I expected that having the edgeHub ports exposed the module connects without any problem.
Current Behavior
When the module tries to connect to the edge hub environment it crashes because a failure on name resolution. Thus, I think it does not find the ip of the edge hub.
Steps to Reproduce
Provide a detailed set of steps to reproduce the bug.
Output of
iotedge check
Click here
Device Information
Runtime Versions
iotedge version
]: iotedge 1.1.13docker version
]: 3.0.13+azureLogs
aziot-edged logs
edge-agent logs
My module logs
Deployment Template
deployment.template.json
The text was updated successfully, but these errors were encountered: