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: [이미지] 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 …

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.

Pups 재빌드 중 ExecError 발생

제품 지원 자체 호스팅

JammyDodger 6월 9, 2022, 6:06오후 4

이 내용에 대한 안내(How-To)가 있을 것 같습니다:

글		댓글	조회수
Rebuild failed, look for help Self-hosting	2	304	4월 30, 2024
Rebuild Failed: bootstrap failed with exit code 137 Self-hosting	5	256	7월 31, 2024
Failed to boostrap (exit code 137) Self-hosting server-resources	7	1226	6월 13, 2022
Error on launcher rebuild app Self-hosting	2	674	4월 5, 2023
Error rebuilding, bundler exits with code 137 Self-hosting server-resources	12	5750	6월 26, 2016

Pups 재빌드 중 ExecError 발생

Related topics