-
Notifications
You must be signed in to change notification settings - Fork 224
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
retry device resync doesn't follow exponentially back off algorithm #9603
Labels
Comments
matrixbot
changed the title
Dummy issue
retry device resync doesn't follow exponentially back off algorithm
Dec 21, 2023
My logfiles are filled with messages like
It starts every 20 to 30 seconds. Version: matrix-synapse-py3 1.114.0+bookworm1 |
As an admin is there anything I can do manually to make Synapse forget these and stop trying? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue has been migrated from #9603.
Description
As far as I'm aware matrix-synapse should stop syncing to dead servers using an exponential back off algorithm.
Reference:
matrix-org/synapse#4979
matrix-org/synapse#5113
This actually doesn't happen if the error is "No Content-Type header received from remote server". Most likely the server owner disabled the server and left the reverse proxy online or the domain got resold and now there is another HTTP/HTTPS service on that domain.
In my case my server tries to contact it almost twice a minute and is spamming my logs. The exponential back off algorithm does not work in that case.
Logs in my case:
Steps to reproduce
Version information
Version: 1.29.0+buster1
Install method: Debian Package Manager
The text was updated successfully, but these errors were encountered: