-
-
Notifications
You must be signed in to change notification settings - Fork 230
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
Connection issues after host system reboot #333
Comments
@teemupiiroinenwirepas hm... 👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq |
|
@ioolkos Do you need more debugging information from us? |
@teemupiiroinenwirepas no need for more debugging info (no free bandwidth to undertake an investigation) but let's focus on why a delay in the Docker daemon start fixes this. What can be possibly concluded from it? would the volume mounts for the VerneMQ data dir not be available or something like that? 👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq |
I doubt that it is about file system mounting as we mount directly the root directory. We run Postgres and Influx also in the vm and we haven't see any issues with them. Volumes are in the default directory /var/lib/docker/volumes.
|
Ok, thanks. Please keep us posted on your findings. 👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq |
When the host system is rebooted with "sudo reboot" command, some connections change from clean_session true to false. Also some old connection names can be seen after the restart. We were not able to reproduce this with native Vernemq installation, but only happens when using Vernemq Docker image. The issue can be seen from Python, JavaScript and C/C++ language connections, so it doesn't seem to be client library issue.
Issue can be "fixed" by adding extra sleep before Docker daemon start, by running "sudo systemctl edit docker.service" and adding these lines:
[Service]
ExecStartPre=/bin/sleep 10
Host: Ubuntu 20.04.4 LTS running in AWS EC2
Docker version: 20.10.21 (issue is also seen with older version)
Vernemq docker version: latest (issues is also seen with older versions)
Before host restart:
After host restart:
The text was updated successfully, but these errors were encountered: