Running “./launcher rebuild app” fails on db:migrate. Note we are using PostgreSQL v12. This murdered our forum. The docker container came back up, but the forum didn’t. Luckily I took a VM snapshot before upgrading, restoring it now. Log: Tasks: TOP => db:migrate (See full trace by running task …

They aren’t separate and no external PG. The PG13 upgrade also fails (non-destructively, unlike today’s upgrade) and I didn’t get support on how to fix it in here, to be honest. I believe (can’t check obv) we only had one container showing up in docker ps. The standard install is 2 containers now?

[image] Wingtip: enable_extension("unaccent") This extension became available as a “trusted” extension on PostgreSQL 13+, where it can be enabled by any users. Since you are running an older PostgreSQL version, you will have to workaround this, by installing and enabling this extension for …

OK. So in summary, you are no longer supporting PG12. Suggest posting that to the PG13 upgrade thread somewhere, and probably in the 2.9.0b4 annoucements too.

If you’re worried about down time then one solution would be to is replicate the server to the new host. Something like community/archived/setting-up-postgres-hot-standby.md at master · GoogleCloudPlatform/community · GitHub . (You might be able to find more recent instructions or some that make mor…

That’s a neat idea, if it was mysql, ms-sql, or oracle I’d do that, but given my lack of experience with postgres I’d probably just eat the downtime.

So my restore finally finished, after over 4 hours. And Discourse was shooting 502 errors. This snapshot was taken before the upgrade, so this is super bizarre. Anyway looking at the nginx logs I found this error 2022/04/14 19:36:21 [error] 493#493: *350 connect() failed (111: Connection refused) …

[image] Wingtip: OK. So in summary, you are no longer supporting PG12 This :point_up: Now we are facing the whole “not enough space because the upgrade requires 300gb” all over again.

Good luck to you. As far as I can tell there is no real solution other than restoring a backup to a fresh host.

Thanks, but basically dead. Tried to do the “Restore to a Fresh Install”, but it doesn’t work, PG doesn’t cooperate. Tried to downgrade the discourse version and go back to PG12, but then it becomes a carnival of light with all the plugins.

Did you try to rebuild with this postgres template instead of the default one? discourse_docker/templates/postgres.12.template.yml at main · discourse/discourse_docker · GitHub

La reconstruction échoue sur db:migrate avec PG12

Soutien Installation

pfaffman (Jay Pfaffman) Mai 8, 2022, 4:38 25

Dans quel sens ? Y a-t-il une erreur ?

Sujet		Réponses	Vues
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2076	Février 15, 2021
Forum offline due to failed rebuilds on Tests-Pass Self-hosting	1	1053	Décembre 11, 2020
When rebuild, Discourse removes PostGreSQL 10 and reinstalls version 9.5 Self-hosting	6	1056	Mai 8, 2020
Forum crashes after upgrading from 2.4.0 Self-hosting	9	1409	Juillet 4, 2020
PostgreSQL Error While Rebuilding Self-hosting	10	1922	Juillet 15, 2020

La reconstruction échoue sur db:migrate avec PG12

Sujets connexes