-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postgres 14 to 16 update fails. #3180
Comments
I've had a similar struggle, but think that my issue is related to not having enough drive space to store three versions of the database. Will keep an eye on this issue, whether it ends up being the same issue or a different one. |
I've justed tested this against a Debian 12 VM with a ---
matrix_domain: example.com
matrix_homeserver_implementation: synapse
matrix_homserver_federation_enabled: false
matrix_homeserver_generic_secret_key: 'test'
matrix_synapse_workers_enabled: true
matrix_playbook_reverse_proxy_type: playbook-managed-traefik
devture_traefik_config_entrypoint_web_secure_enabled: false
devture_traefik_config_certificatesResolvers_acme_email: ''
# We need this for Debian 12 due to a conflict with some `time-daemon` package
devture_timesync_installation_enabled: false
devture_postgres_connection_password: 'test'
# TODO - remove after the initial installation, so upgrading would be possible
devture_postgres_container_image_latest: "{{ devture_postgres_container_image_v14 }}" This makes a clean installation with Postgres pinned to v14. I've explicitly enabled Synapse workers to replicate your setup. After the initial installation, I created some Synapse users manually. I then removed the So, I'm not sure what's going on in your case and for others that have reported similar issues recently, but I can't reproduce the problem. |
if the issue rears its head next time i try a migration i will try to collect more logs that time to see if we can actually get some useful logs out of it. |
Describe the bug
Synapse refuses to work post Postgres 14 to 16 upgrade with 0 logs being able to be located that provide any information what so ever.
To Reproduce
My
vars.yml
file looks like this:Workers Enabled, Postgres password set and that should be it that touches Synapse and its postgres behavior.
As to how to reproduce it well try to upgrade from 14 to 16 with a database that has been used and Synapse seems to be unhappy.
Expected behavior
That it works ofc.
Matrix Server:
The text was updated successfully, but these errors were encountered: