Hi All- First post here, thanks in advance for having me. Running a routine albeit overdue set of upgrades on our Discourse-powered forum ( https://forum.troygrady.com ), and we’ve hit a point where the upgrade fails after doing the command line “git pull” and “rebuild” steps as advised by the on-…

[afbeelding] troygrady: Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn’ hey, welcome to the discourse community. Where are you installing, what OS? You are following our official guide?

[afbeelding] troygrady: and look for earlier error messages I think you might have earlier error messages indeed, it looks like your database (server) might be inaccessible. [afbeelding] troygrady: given that this is a core component of our business Maybe you should consider managed h…

Hi Gavin! Thanks for the speedy response. We’re on a Droplet via Digital Ocean, and when I log in it looks like: Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-210-generic x86_64) As far as using your official guide, that I can’t say. This is an installation that we’ve been running for maybe 3-…

[afbeelding] troygrady: Ubuntu 16.04.6 LTS you would need to look at updating that. its old. very old. but lets 1st get you up and running. can you post the error log. need to see what the actual error is

Ok, grepping for warnings and errors in the rebuild output, here’s what I’ve got (below). – 227:initdb: warning: enabling “trust” authentication for local connections 294:update-alternatives: warning: forcing reinstallation of alternative /usr/share/postgresql/13/man/man1/psql.1.gz because link g…

Thanks again for taking a look at this Gavin, and sorry for the neglected OS upgrades. Above is just what I get when grepping for words “error” and “warning” in the script output, the entirety of which I have saved here. If there’s anything else I should be looking for in that output, just let me …

Ah, sorry, I realize that output is somewhat less than explanatory. Here’s the detail around the “StandardError” message. Looks like an INSERT query failed because of a duplicate key. Query guts redacted for readbility, I can include those if necessary. – I, [2021-08-29T20:23:37.257772 #1] INF…

[afbeelding] troygrady: duplicate key value violates unique constraint “data_explorer_queries_pkey” try this [afbeelding] Duplicate data explorer key blocking rebuild Support Hey all, Rare I ask for help, but I’m puzzled about how to resolve this.…

[afbeelding] troygrady: I have the entire terminal output of the rebuild saved to a file and can scan that. Yes, that works (as you have seen). [afbeelding] troygrady: So I’m not sure what would have changed to suddenly make the db inaccessible. Something went wrong during the upgrade…

[afbeelding] troygrady: so there’s not much twisting our arm to change it. But all you need to do is, once discourse is up and running again. backup discourse. download the backup update the droplet rebuild the app then you should be good to go for another few years

Discourse upgrade fout "FAILED TO BOOTSTRAP"

Ondersteuning

IAmGav (Gavin Perch) 29 augustus 2021 om 21:38 9

try this

Topic		Antwoorden	Weergaven
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2109	26 november 2021
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	396	10 juli 2025
Problem upgrading Discourse Self-hosting	4	1554	11 oktober 2019
Migration from discourse v2.8.13 (on Ubuntu 20.04.6 LTS) to latest Self-hosting	3	776	15 augustus 2023
Forum not working after update – what’s missing? Self-hosting	35	623	4 september 2025

Discourse upgrade fout "FAILED TO BOOTSTRAP"

Gerelateerde topics