vomov

I'm still having the issue on 2.0.14, where I've got three brokers. When restarting everything (docker compose), two brokers start up at nearly the same time, which means that one...

Just noticed something odd. I actually have a fourth broker, which I don't really use. This broker is also connected as a bridge, and this one DOES reconnect no matter...

@michaelfanta; the timeout should be caught by `keepalive_interval 60`, which you may need to reduce to 30 or something. However, the `restart_timeout 10 180` should make it reconnect as well.

Privileged containers is almost never a good idea, especially not when used to circumvent another bug. For system time in the container, you can best do this: ` volumes: -...

"Happily disconnected" does seem appropriate in this case, as the broker never appears to retry connecting. I'm starting to suspect there are multiple problems here: - It drops the connection,...

I've recently found this to be an issue with a friends' setup as well. He's also using a rPi Zero W which doesn't reconnect.

> Reading the mosquitto conf manual page [here](https://mosquitto.org/man/mosquitto-conf-5.html) I see with the restart_timeout setting the default is to initially retry after 5 seconds and then increase up to maximum retry...

This may be a different problem, just like the problem mentioned by @everactivetim , but they all appear related. What device/architecture are you using? I'm able to reproduce the problem...

2.0.18 appears to solve it for me as well.

Seeing the same. Can it have something to do with having a complex tf structure with external dependencies (other repos as modules)?