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: shutting down 2023-04-19 18:28:33.974 UTC [42] LOG: database system is shut down FAILED -------------------- Pups::ExecError: su postgres -c 'psql discourse -c "alter schema public owner to discourse;"' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn' exec failed with the params "su postgres -c 'psql $db_name -c \"alter schema public owner to $db_user;\"'" bootstrap failed with exit code 2 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. c13e1ba313de8fc84f6e2fb0f88197a908803c39791283effb8c82f55b56b6dc Command exited with non-zero status 1 1.85user 1.84system 3:21.56elapsed 1%CPU (0avgtext+0avgdata 36996maxresident)k 197608inputs+368outputs (1133major+96509minor)pagefaults 0swaps

[image] 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 the limit should be higher, if there are now many instances out there which are now vulnerable.

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

[image] 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 [image] Ed S: How many installations are now much bigger than was then normal? I don’t think that many on a standard install, as it’s been this way almost since the beginning. [image] Wingtip: It’s 105GB, on SSD, 16GB VM, and I gave postgres an 8GB buffer pool. Uh, yeah. That’s a big database. I suspect that few people have a database that big that’s not on RDS or at least a seperate container. You should probably consider switching to a 2-container install.

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

[image] 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?

[image] Wingtip: is the switching method documented? You can check out Move from standalone container to separate web and data containers [image] Wingtip: And are there any other advantages that increasing the 60s timer wouldn’t provide? You can build a new container while the old one continues to run. You don’t need to shut down the database to build a new container. [image] Wingtip: So any advantages for us at all? There is now a 10 minute window for shutting down postgres, which should solve your current problem. Once you do one more rebuild, you’ll have the 10 minutes instead of one.

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.

Problème de reconstruction à cause d'un arrêt lent de la base de données

Assistance produit Installation

pfaffman (Jay Pfaffman) Avril 25, 2023, 2:59 21

Vous voulez donc migrer rapidement vers des conteneurs web et de données séparés

Sujet		Réponses	Vues
Upgrade failed due to unclean database shutdown Self-hosting	20	4512	Décembre 30, 2016
Discourse update doesn't wait for Postgress DB to shut down Self-hosting	4	1263	Décembre 29, 2021
Database system was not properly shut down error when rebuilding Self-hosting	3	7101	Septembre 19, 2019
2.6.0 Beta4 update failed with what looks like db errors Self-hosting	6	829	Octobre 19, 2020
Bootstrap failed, please help :( Self-hosting	6	1108	Janvier 3, 2023

Problème de reconstruction à cause d'un arrêt lent de la base de données

Sujets connexes