You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.
I'm using a docker image of synapse (matrix.mydomain) and dimension (dimension.mydomain) behind a reverse proxy which handles encryption. From time to time, the reverse proxy crashes. Dimension is therefore unable to access matrix.mydomain.
Then dimension:
Queries the DNS for matrix.mydomain
Tries to connect to matrix.mydomain
Gets ECONNREFUSED
Immediately starts from 1 again
Last time the proxy was down for 5min. Meanwhile dimension sent 70.000 DNS queries which is more than 200 queries per second.
The CPU usage also goes up to 100%. This looks like an infinite loop to me.
It would be good to add a delay before retrying the failed connection.
The logs show this message for every connection attempt:
Looks like this is an issue in matrix-bot-sdk which has been solved already in release v0.6.0-beta.1 by this Pull Request. However dimension still requires v0.5.19. I guess a version bump would be sufficient.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using a docker image of synapse (matrix.mydomain) and dimension (dimension.mydomain) behind a reverse proxy which handles encryption. From time to time, the reverse proxy crashes. Dimension is therefore unable to access matrix.mydomain.
Then dimension:
Last time the proxy was down for 5min. Meanwhile dimension sent 70.000 DNS queries which is more than 200 queries per second.
The CPU usage also goes up to 100%. This looks like an infinite loop to me.
It would be good to add a delay before retrying the failed connection.
The logs show this message for every connection attempt:
The text was updated successfully, but these errors were encountered: