-
Notifications
You must be signed in to change notification settings - Fork 62
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
Connect failed, create socket failed. #304
Comments
It looks like the ipv6 connect is failing (immediately because it’s an invalid route, hence the reuse of the same fd), and it’s connecting on the ipv4 address. This is expected behavior. |
Ok. It is weird to have errors as expected behavior. Are you able to find out if device has ipv6 address before trying to use that? |
Well, we can change the log level, if that’s what’s concerning you. Since devices network configurations change (for example if a vpn tunnel is being used or if you change networks etc...) we’d rather not keep State that’s unnecessary about the network conditions: that’s just more opportunities for some rather nasty bugs. |
It is up to you. I would prefer to get rid of errors in working application (that is confusing for me at least). If i would write something like that, if i understand this use case correctly it would looks like:
|
Close the issue as we downgraded the log level for socket connection. #594 |
Hi,
i am trying to connect to aws iot cloud using aws-iot-device-sdk-python-v2. Everytime i am starting app, or when reconnecting i am getting these errors finished by Connected message and application is working well. But i am curios why these errors happening? Looks like they are related to this repository. Demo code example: aws/aws-iot-device-sdk-python-v2#90
[ERROR] [2020-07-25T12:30:01Z] [00007f5d7b0ac700] [socket] - id=0x7f5d6c004e90 fd=6: connect failed with error code 101.
[INFO ] [2020-07-25T12:30:01Z] [00007f5d7b0ac700] [dns] - id=0x1004a40: recording failure for record 2600:1f00:6000::385:ab7e for a1tuyp21t3nvof-ats.iot.us-east-2.amazonaws.com, moving to bad list
[ERROR] [2020-07-25T12:30:01Z] [00007f5d7b0ac700] [channel-bootstrap] - id=0x1032890: failed to create socket with error 1049
[INFO ] [2020-07-25T12:30:01Z] [00007f5d7b0ac700] [socket] - id=0x7f5d6c004e90 fd=6: connection success
[aws] Connected!
The text was updated successfully, but these errors were encountered: