Closed GrigoriOH closed 7 months ago
@GrigoriOH Thanks, I guess you have already found the issue (in the script). If you manage to fix this for you (and others), we'd be certainly thankful for a PR.
š Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq š Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.
Thanks for the quick response. I'll try to dig in to this and give a heads-up (or even PR). Not being a professional myself I'm looking forward for feedback or hints.
@GrigoriOH merged your patch, thanks for your contribution! :)
Hello there,
while fiddeling around with VerneMQ in a docker swarm environment, I noticed an odd behaviour utilizing multiple networks. Let's start with a working example of the docker-compose.yml:
As expected, this results in a healthy discovery node which supplies two healthy worker nodes.
When introducing another network (like the one I wanted to utilize for traefik as shown below), this changes drastically:
Taking a deeper look into the problem and what might cause it, I noticed that the error log shows the following:
Indicating that the name of the node was mangled to something that includes two IPs.
The root of this can be found in the vernemq.sh startup script at lines 55ff:
Here, hostname -i delivers multiple IPs in the case of multiple networks, rendering the script unfit for this case.
Maybe I am missing something here, but to me, multiple networks would be a necessity in a standard setup.
Please let me know if there are some thoughts mangled up in my mind and if I can do something to support troubleshooting.
Thanks for you help!