-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Inbound federation fails, "synapse.federation.transport.server - 428 - ERROR - PUT-XXXXXX - on_incoming_transaction failed" #8832
Comments
Is it always failing on the same event, or different events each time? Is only one room affected? Also which workers are you currently using if any?
Given this, it looks like your server is unable to find the server ACL event for this room. Though I'm not sure whether this just happens to be the one event your server has lost, or it can't find a number of different events pointing to a larger problem. |
Using no workers at the moment. Outbound federation is always quick and responsive, but all inbound federation seems ends up being lagged for an hour or two before events arrive. I can DM you a copy of my Synapse logs if you wish. Edit: 2 days later and it's still repeatedly having the above error about that same event. :S |
Closing this since the lag seems to have vanished, yet Synapse is still screaming constantly about that event. :S Bless this mess. |
Synapse is likely wasting resources attempting to validate that event over and over. The event seems to exist in the current state of the room, but not in your database, which is either the symptom of a bug or some database surgery gone wibbly. To clear the error I'd suggest leaving the room, purging it from your database and then rejoining again. |
if the room in question was |
Description
Inbound federation to perthchat.org has been either very delayed or simply not working for over a month now. Outbound federation is responsive still.
Here is the synapse log error that seems to be related to it:
I tried rejoining the room with the matrix.org account, but that didn't change anything.
I'm happy to dig up more information if you need or try any fixes you can imagine. Unfortunately this is quite detrimental to our users experience. :(
Steps to reproduce
Version information
If not matrix.org:
Version:
"python_version": "3.8.6",
"server_version": "1.23.0"
Install method:
Spantaleevs deploy script.
Docker container on Debian 10.
The text was updated successfully, but these errors were encountered: