While trying to restore/rebuild discouse It always end with database migration error current version:20220818171849 restored version:20150822141540 . . . relation "digest_unsubscribe_keys_pkey" already exists in schema "public" (PG::DuplicateTable) CONTEXT: SQL statement "ALTER TABLE backup.un…

Thanks! That’s very helpful. Looks like an old DB migration fails when the site setting value is an empty string. Here’s a fix: FIX: DB migration fails if old site setting has empty value main ← fix-old-migration …

[imagen] Marcello Coutinho: relation "digest_unsubscribe_keys_pkey" already exists in schema "public" (PG::DuplicateTable) Try dropping the PK before the restore. [imagen] Marcello Coutinho: restored version:2015 :scream: damn that is impressively old, hope it works!

[imagen] Marcello Coutinho: restored version:20150822141540 That’s Discourse v1.4.0.beta10. In theory restoring that backup on latest should work. I’ve successfully tested it with every major version since v1.1. Are you trying to restore that backup on a standard install ? Can you post the fu…

Yes, I’ve tried a lot of combinations, including clean install. On this error I’m copying /var/discourse from old server to the new one, executing the rebuild app, then trying restore from console/ssh. I’ll get the full logs

[imagen] Marcello Coutinho: relation "digest_unsubscribe_keys_pkey" already exists in schema "public" (PG::DuplicateTable) ALTER TABLE backup.unsubscribe_keys SET SCHEMA public; Hmm that brings back old (and not so good) memories… There is actually a topic for this Backup Restore Error - #9 …

Hmm, since you are upgrading from such an old version it might be wise to start from scratch on the new server instead of copying over the /var/discourse directory. Do a standard install on the new server Manually tweak the app.yml if needed Create a full backup on the old server and restore it on…

This is the log starting on Migrating the database… Migrating the database... EXCEPTION: /var/www/discourse/lib/discourse.rb:121:in `exec': Failed to migrate database. rake aborted! StandardError: An error has occurred, this and all later migrations canceled: PG::InvalidTextRepresentation: ERROR: …

Migration log before “migrating database” [STARTED] 'system' has started the restore! Marking restore as running... Making sure /var/www/discourse/tmp/restores/default/2022-09-20-162103 exists... Copying archive to tmp directory... Unzipping archive, this may take a while... Validating metadata... …

Hi, thanks for the updated and time spend on this version upgrade. I’ve tried from a clean install and activation + add extra admin from console and then tried a restore but without success again. [STARTED] 'system' has started the restore! Marking restore as running... Making sure /var/www/discou…

The PR has not been merged yet so won’t have gone into effect: [Untitled]

The PR has been merged. You can give it another try.

Problemas de base de datos al migrar de la versión antigua 20150822141540

Soporte Instalación

RGJ (Richard - Communiteq) 19 Septiembre, 2022 17:35 5

Hmm, eso trae viejos (y no tan buenos) recuerdos…
En realidad hay un tema para esto Backup Restore Error - #9 by tgxworld

Tema		Respuestas	Vistas
Problem with restore Discourse from backup (3.4, quite large DB) Support	18	296	14 Enero 2025
Error when restore DB backup Self-hosting	26	1851	27 Agosto 2018
Error Restoring Backup on Migration Bug	41	4670	14 Enero 2020
Restore problem: relation "theme_fields" does not exist Self-hosting	10	2803	5 Junio 2020
Failed To Bootstrap Pups::ExecError 'bundle exec rake db:migrate' failed with return exec failed with the params 2.9.0.beta4 to 2.9.0.beta5 Self-hosting	7	1476	20 Junio 2022

Problemas de base de datos al migrar de la versión antigua 20150822141540

Temas relacionados