Bridge dropping connection

[Rod-O]

on RPi client it restores if I restart the service, but after 7 hours I have in the logs:
Client local.XXXXXX closed its connection.
Connecting bridge XXXXX (XX.XX.XX:XXX)

on Server:
Bad socket read/write on client

[Rod-O]

I noticed this happens only with the bridge from RPi to a x64 server, I have other x64 bridges working without issues.

[ralight]

It's a bit difficult to say anything meaningful without more details I'm afraid. Could it have been a temporary network problem? Does it happen repeatedly? Always after 7 hours? :)

[Rod-O]

I know.
I've been trying to catch the error, and just yesterday I was able to reproduce,
the main server went offline because it restarted,
so the instance that bridges to this main server, wasn't able to recover because of this socket error.

[Rod-O]

Happened again, seems that the bridge is not able to recover specially when SSL is involved

[ralight]

That's useful information, thank you.

I have fixed a bridge connection related problem in 2.0.9 which could be related. Which version are you using? The packages for 2.0.9 are available as of right now if you'd like to try them. I'll try with my Pi to see if I can reproduce it.

[Rod-O]

I'm on fixes branch,
I just updated yesterday, I'll keep you posted if I see this happening again.

[Rod-O]

It happened again, after connection is lost, the bridge is unable to recover.

[ralight]

I haven't been able to reproduce this yet on my pi4 - I've been trying to simulate the connection closing to no avail. Are there any configuration / compile time options that you used that you could share?

[rgaufman]

Bridge connection is being lost for us on 2.0.9 on Raspberry Pi and X86_64 units, especially after reboot it fails to establish the connection for some reason.

It seems manually restarting Mosquitto helps, but the permanent solution for us was to downgrade to 2.0.5 which fixed the problem.

[Rod-O]

If I restart the Pi, I get the issue, if I restart the service, it connects fine.

[fti7]

Same here, Raspberry Pi Zero with Bridge Config -> X86_64 Broker
Mosquitto 2.0.5 fixes this issue

[Rod-O]

then let's close this

[fti7]

@Rod-O Im sorry for my word choice. Its not really fixed. 2.0.5 is an downgrade, where the bug doesnt occur. Please Reopen :D

[cameo69]

Hi all, is there any progress on this? I have a similar issue, albeit no RaspberryPi is involved. The bridge in question is from one docker to another, both running on X86_64.

Mosquitto A <-- Mosquitto B

Config on A is like this:

connection bridge-KS-broker1
address 192.168.3.103:1883
topic # in 0 ks/ ""
cleansession false
remote_username bridge
remote_password ***
start_type automatic
restart_timeout 5 30

Restarting A is not a problem, but if for whatever reason B went down or even if the container B is restarted due to an update, bridging is dead.
Restarting A re-establishes the bridge.

[rgaufman]

Unfortunately this happens for me on 2.0.15 but 2.0.14 works correctly. Have you tried 2.0.14?