@tgxworld , I think this is in your wheelhouse. Trying to restore a backup from Discourse 2.1.0.beta5 - https://github.com/discourse/discourse version 8da2d8df3d5f7196f1c267b8a664597a725241ac or "Discourse 2.1.0.beta5 - https://github.com/discourse/discourse version bed34b52b51ab903bcb7854cc1efb2bf4…

Going to have to ship this into the Support category, there could be some sort of bug here, but we need a proper repro that works consistently. Can you consistently make this fail?

Me too got this issue now. What I did: I did a backup with discourse 2.5.0.beta4. as root git clone https://github.com/discourse/discourse_docker.git /var/discourse cd /var/discourse cp /var/production-backup/var/discourse/containers/app.yml /var/discourse/containers/ mkdir -p /var/discourse/…

Can you restore it via the UI ?

No. > [2020-05-22 12:11:36] 'Patrick' has started the restore! > [2020-05-22 12:11:36] Marking restore as running... > [2020-05-22 12:11:36] Making sure /var/www/discourse/tmp/restores/default/2020-05-22-121136 exists... > [2020-05-22 12:11:36] Copying archive to tmp directory... > [2020-05-22 12:1…

Something is not right about your backup. Can you extract it on local and load it into a PG database? The gzip contains 2 files … 1 backups of PG and 1 uploads directory.

Thank you for help! I’ve created a new backup from the still fully functional old production server. Purged both docker and discourse from newer stage server. Re-installed both docker and discourse according official instructions. Then went with command line restoration instructions. The backup w…

[image] adrelanos: Is it a legitimate approach to backup an outdated docker/postgres version and try to restore on an up to date docker/discourse installation? Yes, this is supported. [image] adrelanos: ERROR: could not create unique index "index_incoming_referers_on_path_and_incoming_d…

I am getting the same error as the OP regarding “theme_fields” even on a brand new Discourse installation. E, [2020-06-04T16:32:44.492756 #2024] ERROR -- : PG::UndefinedTable: ERROR: relation "theme_fields" does not exist LINE 8: WHERE a.attrelid = '"theme_fields"'::regclass …

Are you running the latest version of Discourse? Is this an upgrade from an ancient version of Discourse?

This is a brand new fresh install of Discourse 2.4, no previous anything. I also tried upgrading to Postgres 12. Error still appears in my logs.

Restore problem: relation "theme_fields" does not exist

Support Self-hosting

riking (Kane York) May 25, 2020, 5:08pm 8

Yes, this is supported.

→ Corrupt indexes in PG12, how do I fix?

Topic		Replies	Views
Error when restore DB backup Self-hosting	25	1886	August 23, 2018
Database issues migrating form old version 20150822141540 Self-hosting	13	1064	September 22, 2022
Problem with restore Discourse from backup (3.4, quite large DB) Support	17	339	January 14, 2025
Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes) Self-hosting	12	4770	January 6, 2020
Restore failing- possible Data Explorer issue Self-hosting	21	2377	December 9, 2019

Restore problem: relation "theme_fields" does not exist

Related topics