This recommended upgrade failed and didn’t get my forum back up after breaking. I’m running discourse-doctor now to try to fix it, and if that fails too, I took a VM snapshot. Output: 2023-04-19 18:28:31.298 UTC [42] LOG: received fast shutdown request 2023-04-19 18:28:33.651 UTC [65] LOG: shutt…

[afbeelding] Jay Pfaffman: How big is your database? Is it on ssd? How much ram do you have? When was 60s decided on for a safe shutdown? How many installations are now much bigger than was then normal? Ideally this 60s wait should be more of a closed-loop wait, with a limit. It sounds like …

It’s 105GB, on SSD, 16GB VM, and I gave postgres an 8GB buffer pool.

[afbeelding] Ed S: When was 60s decided on for a safe shutdown? I think I saw that it was at least as long ago as 2016. But things have changed. EDIT: Here’s a new commit. https://github.com/discourse/discourse_docker/commit/d54cc57f5fe7910db77cd92cfe40f2e011135bac [afbeelding] Ed S: H…

We’ll consider it, is the switching method documented? And are there any other advantages that increasing the 60s timer wouldn’t provide?

[afbeelding] Wingtip: that increasing the 60s timer wouldn’t provide? I increased it to 10 minutes yesterday

Oh great, I assumed he was posting the original commit back in 2016. So any advantages for us at all?

[afbeelding] Wingtip: is the switching method documented? You can check out Move from standalone container to separate web and data containers [afbeelding] Wingtip: And are there any other advantages that increasing the 60s timer wouldn’t provide? You can build a new container while t…

Oh that guy just built a completely new two container instance then restored from backup. We definitely aren’t doing that without a good reason, I just had to do it to avoid the PG13 upgrade disk space requirements like 2 months ago.

If you’re not on PG13 then you should fix that. I’d spin up a new server and move to it.

We are now, that one was ultimately unavoidable! Beyond the DB, we also needed to upgrade from the desupported 18.04LTS.

Probleem met opnieuw opbouwen vanwege trage database afsluiting

Ondersteuning Installatie

pfaffman (Jay Pfaffman) 25 april 2023 om 14:59 21

So you want to Migrate quickly to separate web and data containers

Topic		Antwoorden	Weergaven
Upgrade failed due to unclean database shutdown Self-hosting	20	4331	30 december 2016
Discourse update doesn't wait for Postgress DB to shut down Self-hosting	4	1092	29 december 2021
Database system was not properly shut down error when rebuilding Self-hosting	3	7017	19 september 2019
2.6.0 Beta4 update failed with what looks like db errors Self-hosting	6	736	19 oktober 2020
Bootstrap failed, please help :( Self-hosting	6	1017	3 januari 2023

Probleem met opnieuw opbouwen vanwege trage database afsluiting

Gerelateerde topics