Skip to content
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

In an embedded linux environment and dns is invalid, after the bridge is configured, mosquitto distribute data is blocked from time to time. #3108

Open
sfwanglining opened this issue Sep 10, 2024 · 1 comment

Comments

@sfwanglining
Copy link

sfwanglining commented Sep 10, 2024

Linux version 4.9.84
mosquitto version: 2.0.18
Hi,
Using mosquitto in embedded scenarios, I found:
Mosquitto. conf in linux After Bridges is configured, if the network in linux is abnormal and dns is configured in /etc/resolv.conf (the dns does not take effect), data subscribed by the client is periodically blocked.

@sfwanglining sfwanglining reopened this Sep 10, 2024
@sfwanglining sfwanglining changed the title mosquitto distribution of client subscription data gets stuck from time to time In an embedded linux environment and dns is invalid, mosquitto distribution of client subscription data gets stuck from time to time. Sep 10, 2024
@sfwanglining sfwanglining changed the title In an embedded linux environment and dns is invalid, mosquitto distribution of client subscription data gets stuck from time to time. In an embedded linux environment and dns is invalid, after the bridge is configured, mosquitto distribute data is blocked from time to time. Sep 10, 2024
@sfwanglining
Copy link
Author

start_type [automatic | lazy | once], in addition to these three methods can be followed by a specified topic message or signal to control bridge reconnection when the bridge connection is disconnected (after receiving a signal or topic message, reconnection once)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant