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
Bridge connection fails with multiple addresses #481
Comments
There were some bridge related fixes in version 1.4.11 and 1.4.12, could you please try updating? |
Hi, thank you for a quick reply. just tried to update. still the same issue |
Which version did you end up with? |
Ok, I'll have to take a proper look later. |
I've reproduced it and fixed part of the problem, but still have to track down the bit which means the reconnection fails. |
@ralight Hi, do you have any update regarding this issue? |
It is proving difficult to deal with for non blocking sockets and so will require a bit of a think to see whether it can be done without a lot of code change. The problem is that connect() with a non blocking socket doesn't allow you to distinguish between a potentially successful connection and the situation where the connection is definitely refused. You have to wait for that to resolve, and the code isn't set up for that type of check at the moment. |
hi, meet this same problem with the version 1.4.14 addresses server1:8883 server2:8883 @ralight is there any update for this issue? thanks |
is there any update for this issue? thanks . |
I believe this should now be fixed. |
Initial tests with 1.5.3 tag indicate that the problem is not fixed. If the first broker is not up, both connections still fail. changing round_robin to true results in a successful connection. |
We have bridge configured with multiple addresses. when the primary(first) address goes down(manually or due to some issue) mosquitto trying to connect to the second address specified in bridge configuration but all time gets error:
if to place this address on a first position in configuration, connection is created.
i found that this issue was already mentioned in #31 as possible bug in a fix
if set
round_robin true
issue disappearsThe text was updated successfully, but these errors were encountered: