I am creating a new discourse instance from scratch for development purposes and see this bootstrap error again: FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 1002 exit 1> Location of fai…

problem solved. CREATE EXTENSION hstore; CREATE EXTENSION pg_trgm; was missing on the new database. Therefore the initial creation of the database on the external server failed. Thanks @Falco

Any recent errors in the output of dmesg which might be relevant?

[imagen] Ed_S: Best guess would be that you don’t have enough memory That’s a weird guess, we don’t usually see OoM causing migration errors in Discourses.

x86_64 arch detected. Ensuring launcher is up to date Launcher is up-to-date 2.0.20250226-0128: Pulling from discourse/base Digest: sha256:6f18aa2cd22bba0deb91d69194e577d4f96130ad555ae8ec646a8792cbfe37db Status: Image is up to date for discourse/base:2.0.20250226-0128 docker.io/discourse/base:2.0.20…

If this is a web_only container, why does it have redis on it? Can you share your yml container definitions? And why are you even running a two container install?

Hey Falco you are right and I am stupid :wink: I will correct that …

OK, I fixed the separation of web_only and redis. Error msg now is FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 981 e xit 1> Location of failure: /usr/local/lib/ruby/gems/3.3.0/ge…

Thanks for the diagram. That’s quite a sophisticated setup - you’d do that if you had a good reason and knew the territory. If you’re still seeing the following, I think that’s the indication of what’s wrong. Redis can’t open the port it needs to be listening on. [imagen] Thomas_Rother: 999:C …

Hi @Ed_S thanks for the hint about the missing port. I first want to wait for the reply from Falco concerning my questions about the general setup of discourse with an external postgres database. Yes, the setup is a bit sophisticated compared to the standard with just one app container. I run ever…

You still need to share the full logs, including the part where the migration failed. My guess (and it’s a guess since you haven’t shared the error) is that you’re using the AI plugin and your database doesn’t have the add-on that is required.

Cómo resolver errores de Pups exec durante el bootstrap de Discourse

Soporte

Falco (Falco) 22 Abril, 2025 16:52 18

El instalador creará automáticamente todo lo que sea necesario siempre que se le proporcionen credenciales válidas y pueda acceder a la base de datos. Esto está documentado en Configurar Discourse para usar un servidor PostgreSQL separado

Tema		Respuestas	Vistas
Discourse Rebuild Failed to Bootstrap Self-hosting	6	600	31 Agosto 2023
Troubleshooting bootstrap failures in Discourse Self-hosting	14	214	28 Julio 2025
Upgrade from 2.8.0.beta10 to 3.1.0.beta1 failed on Ubuntu 16.04 Self-hosting	3	704	26 Enero 2023
Building bootstrap error Self-hosting	46	2122	20 Diciembre 2022
Unable to create web_only image for a fresh install Self-hosting two-container	10	870	25 Febrero 2021

Cómo resolver errores de Pups exec durante el bootstrap de Discourse

Temas relacionados