-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
room $ROOM for event $EVENT is unknown #7615
Comments
I confirm that I've the same issue with version |
@Josue-T I can confirm that deleting the events associated with this broken room stopped the errors and allowed events to flow to appservice services, thereby allowing my bridge bot to join rooms and function again. Here's the code where this error is being thrown: synapse/synapse/storage/data_stores/main/events_worker.py Lines 626 to 632 in e5c67d0
I connected to the Synapse postgres db and verified that the room mentioned in the error message was not present in the
I also verified that none of the entries in the
then I went ahead and deleted the offending events:
Restarted I do NOT recommend cavalier database edits. You'll probably want to wait for an official response and fix, but I thought I'd post what I've found here in case it's useful to someone else. |
@brandoncurtis I don't suppose you have a copy of the event in question? I'm wondering if we've somehow managed to store an |
My bad, I have destroyed the events. Perhaps @Josue-T can help? This homeserver has been updated through many years and many event bugs, so I would not be surprised if this was a side-effect of previous database surgery. This
|
Ah, never mind. Could you check for the room in (I'm not sure whether to be happy or sad that an event can leave its mark on so many tables...) |
Hello, I've theses event type in the
In the table The content of some part of
The content of some part of
The content of some part of
The content of some part of
Hope that It will help to find the bug. |
Oh, that's very interesting. So this is an entirely local room? Could you check what the |
On riot the room version is 5. I did some more investigation and as I see the problematic event are not linked to the problematic room but to an other room
I can find the problematic event int the This is my synapse log:
|
@brandoncurtis I've a very big number of event in this table linked to this problematic room. |
So this is why you're seeing the error, the problem is that we really should have it in there. Have you upgraded synapse since the room was created? |
Now I found which room is: Some part of
|
The room |
Sorry, that was badly phrased, I guess I have you upgraded since the first time that room ID appeared on your server (i.e. since you first joined/were invited)? Basically, not too long ago we added some background updates to populate a new |
Yes Is it a solution to just add this room in the |
Yeah, that should fix |
This sounds similar to #6902 |
@brandoncurtis I've tried to fix the issue as described here #7615 (comment) . I've no more warning but the bot still broken. Any idea ? |
@Josue-T Sorry for dropping the ball on this a bit. Did you add the room to the |
Hello, it's quite old so I don't really remember what I finally did. As I remember I dropped all problematic event as @brandoncurtis described and if fixed the issue. |
Thanks! Sorry again for the delay. I'm going to close this for now then, we've fixed some bugs in this area around not correctly populating the rooms table recently. Please shout if it happens again though! |
I have an instance of this problem right now:
There are 3 events in the
I cannot really afford to wait to delete these events, but if the problem reoccurs, is there anything we can contribute or try? |
Removing the I've added the room to the |
I am also failing to get an appservice ( |
@madduck You should NOT manually make edits to the Synapse database at all. Doing so without knowing what you're doing is highly unsafe and we cannot support anyone who has done so without our guidance. Your best bet is to use the Delete room admin API with |
@DMRobertson Thanks for that, that seems to have solved the problem (though the appservice still doesn't get sent any events). And yeah, I am aware that messing with the database is bad. Mind you, I did so only on a copy, would never do it on a live system. |
Description
Synapse log is full of these warnings:
I suspect that this may be causing problems with Synapse reporting events to a self-hosted bridge; that may be a separate issue, this issue is just about dealing with this warning.
Speculatively related:
Steps to reproduce
Version information
If not matrix.org:
pipenv
The text was updated successfully, but these errors were encountered: