2022-06-09 15:54:49.619 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1 2022-06-09 15:54:49.620 UTC [46] LOG: shutting down 2022-06-09 15:54:49.671 UTC [42] LOG: database system is shut down FAILED -------------------- Pups::ExecError: cd /var/www…

I think we may have a How-To for that: [imagen] Create a swapfile for your Linux server Self-Hosting bulb For servers with <= 4GB of RAM, running ./discourse-setup will prompt for and automatically create a 2GB swapfile. Most cloud virtual machine providers …

I think error code 137 is not enough memory. Do you have a swap file set up? You can check by running free on the command line. Alternatively, you could upgrade and add more RAM? One I haven’t tried yet but have read a few times on here is adding vm.overcommit_memory = 1 to /etc/sysctl.conf Edit…

I do not have a swap file setup, I’ll check on how to do it and get back to you.

Error de ejecución de Pups al reconstruir

Soporte Instalación

JammyDodger 9 Junio, 2022 18:06 4

Creo que podemos tener un tutorial para eso:

Tema		Respuestas	Vistas
Rebuild failed, look for help Self-hosting	2	265	30 Abril 2024
Rebuild Failed: bootstrap failed with exit code 137 Self-hosting	5	194	31 Julio 2024
Failed to boostrap (exit code 137) Self-hosting server-resources	7	977	13 Junio 2022
Error on launcher rebuild app Self-hosting	2	623	5 Abril 2023
Error rebuilding, bundler exits with code 137 Self-hosting server-resources	12	5624	26 Junio 2016

Error de ejecución de Pups al reconstruir

Temas relacionados