You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
upgrading from before 1.3.0 to 1.10.0 destroys all your rooms #6923
the delete_old_current_state_events background update clears current_state_events of any rooms with no rows where membership='join'. But membership is only populated by the current_state_events_membership update, so this goes badly.
Because the FreeBSD port is still on 1.10.0, I ran into this when I upgraded. Is there a way to recover from this? I'm the only user of my homeserver, there are not a lot of rooms to restore
delete the entries in current_state_events for rooms I could not manage to join
re-join those rooms
Right now I'm figuring out other conflicts in the database, mainly in *_historical tables
curl -X GET 'https://HS/_matrix/client/r0/joined_rooms' | jq -r '.joined_rooms[]' | while read r
do
curl -X POST "https://HS/_matrix/client/r0/join/$r"
done
Activity
richvdh commentedon Feb 17, 2020
fixed by #6924
sandhose commentedon Feb 19, 2020
Because the FreeBSD port is still on 1.10.0, I ran into this when I upgraded. Is there a way to recover from this? I'm the only user of my homeserver, there are not a lot of rooms to restore
sandhose commentedon Feb 19, 2020
I kinda got my HS running again. What I did is:
1when the field was NULL to get past this errorcurrent_state_eventsfor rooms I could not manage to joinRight now I'm figuring out other conflicts in the database, mainly in *_historical tables
Footnotes
basically something like this: ↩