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

Clients connection timeouts after less than 60 seconds #2996

Closed
reef-actor opened this issue Feb 6, 2024 · 1 comment
Closed

Clients connection timeouts after less than 60 seconds #2996

reef-actor opened this issue Feb 6, 2024 · 1 comment

Comments

@reef-actor
Copy link

I am running the latest docker image. I am seeing clients getting their connections kicked after about 50 seconds. Cients include other docker containers on the same server and wifi devices running tasmota.

In the log below there are 3 tasmota devices that get kicked and immediately reconnect. 48 seconds later the connections are dropped by timeout again.

13:58:09: Client DVES_43949C has exceeded timeout, disconnecting.
13:58:09: Client DVES_D36A02 has exceeded timeout, disconnecting.
13:58:09: Client DVES_3A499E has exceeded timeout, disconnecting.
13:58:09: New connection from 192.168.1.26:65384 on port 1883.
13:58:09: New client connected from 192.168.1.26:65384 as DVES_3A499E (p2, c1, k30, u'DVES_USER').
13:58:09: New connection from 192.168.1.186:58263 on port 1883.
13:58:09: New client connected from 192.168.1.186:58263 as DVES_43949C (p2, c1, k30, u'DVES_USER').
13:58:09: New connection from 192.168.1.44:49338 on port 1883.
13:58:09: New client connected from 192.168.1.44:49338 as DVES_D36A02 (p2, c1, k30, u'DVES_USER').
13:58:57: Client DVES_3A499E has exceeded timeout, disconnecting.
13:58:57: Client DVES_43949C has exceeded timeout, disconnecting.
13:58:57: Client DVES_D36A02 has exceeded timeout, disconnecting.

Shouldn't the broker have a 60 second timeout?

@reef-actor
Copy link
Author

For the last 3 hours it has been running without a single dropped connection. I did some updates (which included docker and the kernel) and everything got restarted. Going to close this as I am unable to reproduce whatever started this in the first place.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant