-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
synapse throw me out of #Matrix HQ because of an error resolving state for the room #7913
Comments
Looking through the logs, I see multiple instances of
and
A full trace would be:
I initially wondered if the remote servers associated with the errors in your logs ( Your server does seem to believe it's not in the room however, as evidenced by log lines like:
@richvdh @erikjohnston do you know if there is any manual cleanup required for homeservers to do if they were affected by #7742? |
I've got a horrible feeling that once your server has reached incorrect conclusions about room state as a result of #7742, those incorrect conclusions will tend to persist for the lifetime of the room. The only solution to that would be to leave the room, purge it from the database, and rejoin. However I haven't studied this in depth, and @erikjohnston is the authority here. It may be best to await his return. |
I own |
I also have a long list of rooms with this kind of error in my logs, i've just realized. Could this be related to unreferenced state groups? |
This will have been due to a state reset, the causes of which we've been slowly resolving |
Related: #8629 |
Please try to fix this soon, or I might just have to uninstall synapse and revert to email. I really like matrix but this bug is making it so hard to use. |
Today I was once again thrown out of Matrix HQ.
I wounder if this could be the same bug still lurking around or a new one?
My synapse log file: http://1bit.se/wp-content/uploads/simple-file-list/homeserver_log.1
(Loglevel set to INFO)
At 11:05:47 in the logfile I see an error resolving state for the room matrix hq.
After that time I also no longer got any new events in the room in my client. And after clear cache and reload it was revealed to me that I had been thrown out of the room.
I use synapse 1.17.0
The text was updated successfully, but these errors were encountered: