-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
strange issues because of #matrix:matrix.org #1899
Comments
i experience a similar issue with my hs i get bombarded with log warning like this:
when the "DOS" starts my server becomes unresponsive and crashes after some minutes. EDIT: this happened after i tried to join some rooms on matrix.org EDIT2: it seems that my hs is initiating all these requests, because when i blocked connections from matrix.org to my federation port the warnings still came. i blocked connections in both directions for now. EDIT3: now i get errors because my server still tries to connect to matrix.org |
few days later, after reporting the issue, I left #matrix:matrix:org and everything stayed stable. after upgrading to 0.19.3 same symptoms returned. so I joined #matrix:matrix.org again and things are calm for now. at least joining was pretty fast this time - less than a minute. |
my hs started to consume lots of cpu and ram few weeks ago. can't pinpoint exact time, but around same time when federation meltdown happened. usual symptoms were very high message latency and lots of
Rejecting
messages in log (only messages I could connect with high loads without going too deep). restarting once per day helped, and after a while once every few hours. so basically it got worse.after upgrading 0.19.1 and still experiencing the issue, I dug into logs:
grep Rejecting /var/log/matrix-synapse/* | sed -nr 's/.+in room (.+)\.$/\1/p' | sort | uniq
only result was
!cURbafjkfsMDVwdRDQ:matrix.org
(#matrix:matrix.org).important part here is that I and nobody else in my hs wasn't in that room. I once was, but parted. after rejoining room (
"event_id": "$14867256702sJbsx:XXXX.XX"
, it took many minutes and multiple tries) and very high load for a few minutes after rejoin (log raced like madman), everything calmed down and things have been stable since then ("event_id": "$148672624215JsZFh:XXXX.XX"
).not sure what to think about it. somekind of splitbrain state where my hs knows that i'm not in the room anymore, but other hs thinks otherwise? :-(
The text was updated successfully, but these errors were encountered: