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/discourse && su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development' failed with return # Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test developm ent'"]} bootstrap failed with exit code 137 I’ve been getting this error when rebuilding, I have no idea what to do.

I think we may have a How-To for that: [image] 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 do not set up swapfiles as part of their server provisioning. In particular, upgrading Discourse produces a lot of memory pressure. With a swap file, rather than randomly terminating processes with an out of memory error, things will slow down instead. Having a swap file is a cheap insurance policy that protects you from many other lo…

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: This is from a different-but-similar topic, and has the text from the log in: [image]3G RAM + 1G Partition Swap - is it enough? WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.

Pups ExecError while rebuilding

Product Support Self-hosting

OverseersMight (OverseersMight) June 9, 2022, 6:01pm 3

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

Topic		Replies	Views
Rebuild failed, look for help Self-hosting	2	313	April 30, 2024
Rebuild Failed: bootstrap failed with exit code 137 Self-hosting	5	290	July 31, 2024
Failed to boostrap (exit code 137) Self-hosting server-resources	7	1272	June 13, 2022
Error on launcher rebuild app Self-hosting	2	697	April 5, 2023
Error rebuilding, bundler exits with code 137 Self-hosting server-resources	12	5773	June 26, 2016

Pups ExecError while rebuilding

Related topics