Server’s RAID died couple days back and we’re trying to bring back to life our Discourse instance from a filesystem backup. No luck so far. I get this error message from ./launcher rebuild app: FAILED -------------------- Pups::ExecError: /root/upgrade_postgres failed with return #<Process::Status…

Oh cool! So The source cluster was not shut down cleanly. You will need to follow this [Bild] PostgreSQL 13 update If you need to postpone the update during your next rebuild, you can swap the PostgreSQL template on your app.yml file by changing "templates/postgres.template.yml" to "templates…

[Bild] ulysses4ever: we’re trying to bring back to life our Discourse instance from a filesystem backup Why don’t you use our official backup features and restore a backup file to a new server? That is our supported recovery method and it’s documented at Create download and restore a backup …

This method assumes you have a backup prepared by a running discourse instance. I don’t have one (anymore) :cry:

Backups are enabled by default and saved on the host file system. If you have a file system backup you have the backup files in the backups folder…

The backup feature doesn’t seem to have been enabled: I’m seeing only a couple of backup tarballs with rather old modification dates…

I believe weekly backup is on by default in a normal Discourse install.

I may end up using one of those but still I need a running instance and I keep getting those errors when trying to run it.

It a lot easier to move the backup file to another server and follow Restore a backup from command line

How do you mean “another sever”: I only have a single server.

Okay, so let’s take a step back. When you issue a rebuild, you end up with a error. Can you paste more than just 4 lines of error so we know exactly what is failing?

You maybe missed it because I added the link to the full output only in an update to the top post: Full output of both commands available here .

Wiederherstellung aus Dateisystem-Backup: kann weder neu erstellen noch starten

Unterstützung Installation

Falco (Falco) 14. Februar 2021 um 02:26 12

Oh cool!

Also

Der Quellcluster wurde nicht ordnungsgemäß heruntergefahren.

Du musst wie folgt vorgehen

um die Datenbank zunächst ohne Upgrade zu starten und das Update anschließend durchzuführen.

Thema		Antworten	Aufrufe
Mistakes when upgrading docker image to 1.3.3 Support	12	2667	8. Juni 2024
Postgres Errors on Rebuild Self-hosting	3	1641	16. September 2015
Trying to recover an installation Self-hosting	8	1215	18. Mai 2023
Building bootstrap error Self-hosting	46	2125	20. Dezember 2022
Docker/Postgre problem, need help Marketplace delivered	4	1019	14. August 2020

Wiederherstellung aus Dateisystem-Backup: kann weder neu erstellen noch starten

Verwandte Themen