-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
2.0.15 regression: bridge is not created, with "Expiring client local.xxx due to timeout" #2634
Comments
We also reverted to 2.0.14 to solve our problem. |
Same - had this issue and glad I saw this as I was pulling my hair out.
|
Having the same problem on Windows machine:
|
Same issue
|
I'm pretty sure I was seeing this as well today. That "expiring client local.blah due to timeout", and with zero extra info available. In my case I was only bridging to a same network, 192.168.blah, no encryption, and restarting fixed things, couldn't figure it out. I'll hopefully be able to collect more information though. |
In my case it happens every 2nd reboot, on the clock. |
How is this still not fixed? |
Can confirm with docker v2.0.15 on Debian 11 armv7l, revert to 2.0.14 fixes the problem |
Can report the same thing with: It was intermittent in my case. Not consistent when I could/couldn't not have the bridge running. |
We upgraded to 2.0.15 due to #2594 but now we have to downgrade due to this bug. This bug is severe, please look into this. |
Same issue with 2.0.15. It appears the issue has been known for some time; why in Jan 2023 it's still not fixed? Jan 15 13:12:51 micro mosquitto.mosquitto[1597]: 1673817171: Connecting bridge (step 2) 2cloudww (cloud.x.com:8883) |
@ralight ?? |
Hey. |
Same issue here right now trying to connect to HiveMQ, and it doesn't reconnect anymore as it says in the docs. |
Same issue here: mosquitto bridge 2.0.15 to mosquitto. I had to downgrade to 2.0.14 and now is working good |
same problem here, |
reboot does not solve this problem |
I create above issue, today found that root of cause is timeout to bridge broker. I'm wiaitng for fix but to workaround how to increase timeout for bridge and what value is default? |
Same problem here. I'm using version 2.0.15, and the issue occurs every second start of mosquitto. I'm using the following settings on bridge:
|
@ralight can you provide any insight/update on this issue? |
still there...
|
Signed-off-by: Jarek Świerczyński <swiergot@gmail.com>
Signed-off-by: Jarek Świerczyński <swiergot@gmail.com>
…ipse-mosquitto#2634. Signed-off-by: Jarek Świerczyński <swiergot@gmail.com>
…oses eclipse-mosquitto#2634. Signed-off-by: Jarek Świerczyński <swiergot@gmail.com>
I have submitted a PR. Please note that I had zero experience with mosquitto code prior to this so if you decide to use the fix before it is reviewed by maintainers, you risk running into potential side effects I have not foreseen. |
Nevermind, apparently the fix (6d240a9) has been on the fixes branch for over 3 months. There just hasn't been any new release since. |
I confirm this. But no need reboot. Just stop and start mosquitto |
Wondering if there is any progress on this since requires me a manual restart every day? |
Yes, it's fixed but not released. You can:
|
When is planned new release? |
Awesome! Thanks @ralight, almost thought Mosquitto was dead :) |
I guess it's on an annual release schedule now :)
|
After upgrading to 2.0.15, we observed that in about 50% of cases broker bridges are not created on start-up. The log shows the message
immediately on start-up (i.e. not after an actual conceivable timeout).
This was first reported in #1334 (comment) and subsequent comments in that thread (thanks @everactivetim, @vomov), though it's almost certainly a separate issue from #1334. It appears to have been an unintentional side effect of c99502a. Indeed, the issue does not seem to occur in 2.0.14.
In our specific case this is on Linux on ARM.
The text was updated successfully, but these errors were encountered: