-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Error when loading particular communities: Failed handle request via 'GroupRoomServlet' #4891
Comments
@benparsons I got same problem, described in #5824, did your group recovers, or still shows the error? Can you lookup content of |
I cleared out |
I have the same issue here. |
Same issue on synapse 1.11.0: https://gist.github.com/fridtjof/884e6cb2bdbc5b78188a4164a60ad74f |
Seeing the 500 error in the browser network inspector for the |
Any idea how to clean it up manually? |
Due to the (inter)national state of affairs a lot of people started to use matrix. Communities would be the way to separate rooms into local communities, local languages. Please, shed some light on what's broken and how to hack it to work, or how to periodically fix it. We desperately need communities working now, not 6 months in the future when room communities will be implemented. Please? Thanks! |
looks like someone has figured it out in #7097:
|
(I understand your frustration, but sorry: communities aren't our top priority as a team right now, compared to more pressing concerns like performance. In the meantime, the joy of open-source is that solutions don't have to come from the core dev team. Thanks to @airblag for taking the time to investigate and propose a workaround!) |
#7070 should fix missing room_version values in the rooms table.
(On a side note, how do I find out more about a room just with its ID? I have no idea what these two rooms were, there aren't even any aliases in room_aliases for those IDs...) |
In my case the room looked perfectly valid, had a version, but trying to join it resulted various errors on synapse side (for reasons not relevant here). This resulted retrieving the room list fail with a server error which resulted room list not returned which in turn results infinite wait on the client side. Removing the bad room from |
i have fixed here manualy..
after this step i have used my Riot-Client to add my rooms to the community group. |
For me, on synapse:v1.12.0, running I identified the remaining bad rooms in those 2 using @grinapo's clue above ("trying to join it resulted in errors"), using "/join !..." in Riot-web, and those attempts resulted the logs described in #7108 (matching this regex: Running I suspect those rooms are obsolete in some way, but have not found more info about them except their room_versions (which are 4 and 5). |
I am running a Synapse server on which I am the only user. I have found that when I leave a channel that was in a community, this breaks the community until I remove the relevant room ID from the database table group_rooms. It seems that communities break when they refer to a room that has no local participants. |
This query fixed the two broken communities on my unfederated server: DELETE FROM group_rooms WHERE room_id IN ( select group_rooms.room_id from group_rooms left join room_stats_current on group_rooms.room_id = room_stats_current.room_id where joined_members = 0 ); |
I'm facing this issue as well. Existing Riot clients / sessions are working properly but when I create a new login the Riot lists only bunch of unnamed rooms and they won't ever be synchronized correctly. Sometimes if I open an empty room it gets the correct room name but it's unable to fetch the messages or user list. And if I close the Riot client the room is named "unnamed room" again. It's very same kind of situation than here: #5824 (comment) |
I can confirm this. We are running 2 distinct servers on domain A and domain B, the room list for a community on server A would not load for a user on server A as long as there was a room in the community no local user was in, the room list for the same community would load fine for a user on server B though as server B has at least one user in each of the community's rooms. Rejoining the rooms no-one from server A was in with a user from server A also restored the room list to working condition on server A. |
A user was able to reproduce this in #7462 by adding a room to a community, then removing all users from that room. Whenever the community room list is queried, Synapse returns a 500 with OP's traceback. |
For me, the issue is not caused by a room in the community which does not have any members.
So It seems the changes in the pull request do not fix this completly, since the issue can be caused by something else as well. I could solve the issues by removing a single room from a community. Here are the room stats:
Removing 'roomid5:example.com' solved the issue. Here is the error in the matrix log:
If you you need any more information about this, to figure out what caused this,I'll happily provide it. |
Communities/groups are being removed, see #11584. |
Description
Whenever I try to load any group/community, I see the following in logs:
Version information
0.99.2, matrix.bpulse.org
Possibly duplicates #4786, but more detail here
The text was updated successfully, but these errors were encountered: