Open zombielinux opened 4 years ago
The kicking of connections will not likely be due to IP addresses, but to _clientID_s. Do you have clients connecting simultaneously with the same ID? That's a reason for Mosquitto to kick a client.
I don't think so.
Most of my devices are running the tasmota firmware (8.5.1 to be specific). I'm pretty sure they default to DVES_$macAddress and I haven't changed them.
I do have one bit of JS that just subscribes.
And there is homeassistant as well. Overall, not much on the broker at all.
You might get more information with debug
logging, or if you're willing to try the develop
branch then you get a wider variety of disconnection messages.
To do that:
git clone https://github.com/eclipse/mosquitto
cd mosquitto
git checkout develop
make localdocker
At the end of the process you will have an eclipse-mosquitto:local
image.
I have the latest docker image pulled from here: https://hub.docker.com/_/eclipse-mosquitto
I have a docker swarm set up, and the container defined with docker-compose (see attached)
I have my swarm fronted by HAProxy to load balance between my ingress nodes.
I have many devices pointing to the HAProxy address (dockercluster.fqdn.org), and the data mostly seems to get there.
I get frequent disconnects claiming socket error. A snippit of my log is attached.
I do not have authentication turned on.
It appears multiple devices are trying to use the same IP address to connect from and its kicking a previous connection off (maybe?)
I'm trying to wrap my head around what could be going on here so I can get some stability in my devices.
mosquitto_sub -h dockercluster.fqdn.org -t '#'
doesn't seem to show anything odd either.