-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Traceback in synapse.metrics.background_process_metrics #8318
Comments
I think this is a duplicate of #8220, which will be fixed in Synapse v1.20.0. |
Thanks a lot for pointing this out, that looked a lot like a duplicate, and it seems like this is fixed now that I use 1.20.0rc3. |
Thanks for confirming that it is fixed in the upcoming upgrade! 👍 |
Though I still do not federate with matrix.org 👀 The only noteworthy things in my logs are the following: Similar to #4727 :
Similar to #5604 and #8118 (I might have a slight case of the latter, as I had DNS lookup errors, which didn't subside when I added matrix-federation.matrix.org to /etc/hosts).
Interesting to me is that these errors started to happen on an otherwise long-running server (Synapse has been up for more than a year, not without some hiccups). I just happened to perform some postgresql DB maintenance lately, that's the only related thing I can see. I'll reboot the server just to see. Edit: solved by increasing timeout, filled #8338 |
Description
I am having issues federating with matrix.org. Inbound federation works, but matrix.org users can only receive my messages trough another server. My logs are spammed multiple times per second with the following traceback (I don't even have metrics enabled, as far as I can tell):
Roughly translating the last error, that gives:
Steps to reproduce
Unfortunately, I don't really know which specific configuration could help reproducing the issue. I can add more verbose logging to the python scripts if you tell me what is needed.
Version information
If not matrix.org:
Version: 1.18.0 (also reproduces on 1.19.0 and 1.19.1).
Install method: yunohost app
The text was updated successfully, but these errors were encountered: