Space's room list don't display all available rooms

[Thatoo]

Description

Space's room list through federation don't display all available rooms

Steps to reproduce

• go to #monnaie-libre:matrix.org where it is supposed to have 16 rooms (an admin of the space told me that) but I can see only 4 of them from my account (from an other synapse server than matrix.org, my own yunohost synapse server).
• If I go to #community:matrix.org space, the list of room is very long but I can't be sure if all are listed.
• If I go to #monnaie-libre:matrix.org from a matrix.org account, it indeed shows me a list of 15 rooms (might mean that 1 of the room isn't public or that the admin of the space made a mistake)
• If I go to #monnaie-libre:matrix.org from a defis.info account, it shows me only 4 available room

Homeserver

leprette.fr, defis.info and matrix.org

Synapse Version

leprette.fr : 1.59, defis.info : 1.59.1

Installation Method

Debian packages from packages.matrix.org

Platform

leprette.fr : Yunohost package
defis.info : Debian packages in a proxmox container behind an nginx reverse proxy

Relevant log output

do not know

Anything else that would be useful to know?

No response

[DMRobertson]

There were a few spaces-related bugs fixed in 1.61 and 1.60. Matrix.org is currently running 1.62; can you see if the situation improves once leprette.fr and/or defis.info and update to 1.61 or newer?

[DMRobertson]

Please also note that cannot see a room in a space if:

• the room is invite-only and you're not invited
• joining the room is restricted and you don't have meet the requirements to join.

To debug this, we'd need a specific room ID that you can see via matrix.org but cannot see via your self-hosted server.

[Thatoo]

I can see #monnaielibre-basque:matrix.org with a matrix.org account but not with leprette.fr nor defis.info account.

However, I can see #G1MonedaLliure:matrix.org and #g1-suport-tecnic:matrix.org from all three accounts.

For what I have been said by their admins all three are public rooms.

[Thatoo]

I wanted to update from v 1.59.1 to 1.62 but synapse won't start anymore : #13193

[DMRobertson]

Which is your personal homeserver, leprette.fr or defis.info? Or a different homeserver altogether?

[Thatoo]

leprette.fr is my homeserver running thanks to yunohost so I can't update before yunohost package update.
defis.info is the server of an association. We'll try again later to update synapse when we have time.
I keep you updated here.

[reivilibre]

I just reproduced this problem on v1.60.0 but I upgraded to v1.62.0 and then it started working.

[DMRobertson]

I checked Matrix.org's database. I saw 22 child rooms of #monnaie-libre:matrix.org (this does not take into account rooms in subspaces). Of these, two were marked invite-only; the rest were public.

matrix->         space_room.room_version as space_room_version,
matrix->         space_state.state_key as room_id,
matrix->         to_timestamp(space_child_event.received_ts/1000) as ts,
matrix->         subroom.room_version,
matrix->         join_rules.json::jsonb->'content'->'join_rule' as join_rule,
matrix-> --        name.json::jsonb->'content'->'name' as name,
matrix-> --        subroom_aliases.room_alias
matrix-> from
matrix->         current_state_events as space_state
matrix->         join events as space_child_event on (space_child_event.event_id = space_state.event_id)
matrix->         join rooms as space_room on (space_room.room_id = space_state.room_id)
matrix->         join rooms as subroom on (subroom.room_id = space_state.state_key)
matrix->         join current_state_events as join_rules_state on (join_rules_state.room_id = space_state.state_key and join_rules_state.type='m.room.join_rules')
matrix->         join event_json as join_rules on (join_rules.event_id = join_rules_state.event_id)
matrix->         join current_state_events as name_state on (name_state.room_id = space_state.state_key and name_state.type='m.room.name')
matrix->         join event_json as name on (name.event_id = name_state.event_id)
matrix->         left join room_aliases as subroom_aliases on (subroom_aliases.room_id = subroom.room_id)
matrix-> where 
matrix->         space_state.type = 'm.space.child'
matrix->         and space_state.room_id = '!nsxQkuXAmwktOKyUNc:matrix.org'
matrix-> order by ts asc
matrix-> ;
 space_room_version │            room_id             │           ts           │ room_version │ join_rule 
════════════════════╪════════════════════════════════╪════════════════════════╪══════════════╪═══════════
 6                  │ !ualEMJKYcvRtyiWtBr:matrix.org │ 2021-08-13 17:12:11+01 │ 6            │ "invite"  
 6                  │ !RcHKSTMNEWOdVzGMbH:matrix.org │ 2022-07-04 09:22:29+01 │ 1            │ "public"  
 6                  │ !sLobaVOwbpusqGQKgw:matrix.org │ 2022-07-05 13:42:31+01 │ 9            │ "public"  
 6                  │ !AAjzOHNTtDmwlkHrVD:matrix.org │ 2022-07-05 14:22:08+01 │ 9            │ "public"  
 6                  │ !HliGkqkVySICwjOihN:matrix.org │ 2022-07-05 14:22:08+01 │ 9            │ "public"  
 6                  │ !LwbregvmrAiobWeSUZ:matrix.org │ 2022-07-05 14:22:09+01 │ 9            │ "public"  
 6                  │ !mFomkDgpgGJbbeFvzQ:matrix.org │ 2022-07-05 14:22:09+01 │ 9            │ "public"  
 6                  │ !YHwNsrHwRtvALhvTsG:matrix.org │ 2022-07-05 14:22:39+01 │ 6            │ "public"  
 6                  │ !sDsxMCaSAYTyBopueT:matrix.org │ 2022-07-05 14:22:39+01 │ 6            │ "public"  
 6                  │ !PAmyqkJZYTQJZaJyny:matrix.org │ 2022-07-05 14:22:52+01 │ 6            │ "public"  
 6                  │ !HyeIyLaeDoLQMZhaDq:matrix.org │ 2022-07-05 14:22:52+01 │ 9            │ "public"  
 6                  │ !LUPDIhkESRtkiHyeeM:matrix.org │ 2022-07-05 14:22:52+01 │ 6            │ "public"  
 6                  │ !rIVrFXddvnRVXRsFgW:matrix.org │ 2022-07-05 14:22:52+01 │ 9            │ "public"  
 6                  │ !uWZHngftIDCqGEGzzM:matrix.org │ 2022-07-05 14:22:53+01 │ 5            │ "public"  
 6                  │ !JzDdfCLVIhqIpKdFnQ:matrix.org │ 2022-07-05 14:22:53+01 │ 4            │ "public" 
 6                  │ !wwWcSTXhcYXHxoNLMp:matrix.org │ 2022-07-05 14:22:55+01 │ 5            │ "public" 
 6                  │ !eSZWsDoqgRnzJzoFtO:matrix.org │ 2022-07-05 14:23:10+01 │ 6            │ "public" 
 6                  │ !eEZrIcDuWYwIqeARBt:matrix.org │ 2022-07-05 14:23:10+01 │ 6            │ "public"  
 6                  │ !eiRZfcaCVpvMpVLfdz:matrix.org │ 2022-07-05 14:23:11+01 │ 6            │ "invite"  
 6                  │ !vxoNnTGabnmXNEJBLW:matrix.org │ 2022-07-05 14:23:11+01 │ 6            │ "public"  
 6                  │ !OgvEtWPQTiBNkjbRDz:matrix.org │ 2022-07-05 14:23:11+01 │ 6            │ "public"  
 6                  │ !WcILeUSHnikrDOJluU:matrix.org │ 2022-07-07 14:42:39+01 │ 9            │ "public"  
(22 rows)

Given @reivilibre's report (thanks Oliver) I think your best bet is to get your homeserver(s) upgraded to 1.62 and see if that fixes the problem. In particular I think you want to

• shut down synapse
• upgrade to 1.62
• run the command in Synapse won't start after upgrade attempt from 1.59.1 to 1.62: slow database migration means we get timed out by systemd #13193 (comment) to upgrade the database while synapse is not running
• restart synapse.

If you have problems with the upgrade, please re-open #13193.

If you still have problems with the space after the upgrade, please open this issue. Many thanks!

[Thatoo]

Hello,
I did exactly what you wrote @DMRobertson , synapse is now running version 1.63 and the database has been updated and migrated from SQLite to Postgres. It works but I face this issue now : #13426 . Once this issue solved, I'll be able to tell you if it had worked...