stuck on this for like 6 mins now while rebuilding [SCR-20240508-oc9]

See Error during the update ESOCKETTIMEDOUT registry.yarnpkg.com

im really confuse, my line 159 as stated in the topic you posted is different.. [image] but I searched for “yarn” and found this [image]

Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 600 app app 2.0.20240502-0021: Pulling from discourse/base Digest: sha256:ca10543693caa0b52f7318105dea1d47a84991e7927330db1010e13e39777ba7 Status: Image is up to date for discourse/base:2.0.20240502-0021 docker.io/discourse/base:2.0.20240502-0021 /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups.rb /usr/local/bin/pups --stdin I, [2024-05-09T03:58:42.050521 #1] INFO -- : Reading from stdin I, [2024-05-09T03:58:42.077104 #1] INFO -- : File > /etc/service/postgres/run chmod: +x chown: I, [2024-05-09T03:58:42.095108 #1] INFO -- : File > /etc/service/postgres/log/run chmod: +x chown: I, [2024-05-09T03:58:42.108229 #1] INFO -- : File > /etc/runit/3.d/99-postgres chmod: +x chown: I, [2024-05-09T03:58:42.126445 #1] INFO -- : File > /root/install_postgres chmod: +x chown: I, [2024-05-09T03:58:42.145105 #1] INFO -- : File > /root/upgrade_postgres chmod: +x chown: I, [2024-05-09T03:58:42.145716 #1] INFO -- : Replacing data_directory = '/var/lib/postgresql/13/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.147110 #1] INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.150337 #1] INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.180094 #1] INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.181568 #1] INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.182124 #1] INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.183465 #1] INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.184221 #1] INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.198484 #1] INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/13/main/postgresql.conf I, [2024-05-09T03:58:42.209671 #1] INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres peer in /etc/postgresql/13/main/pg_hba.conf I, [2024-05-09T03:58:42.213239 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/13/main/pg_hba.conf I, [2024-05-09T03:58:42.218935 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/13/main/pg_hba.conf I, [2024-05-09T03:58:42.221346 #1] INFO -- : > [ -f /root/install_postgres ] && /root/install_postgres && rm -f /root/install_postgres I, [2024-05-09T03:58:42.404926 #1] INFO -- : Generating locales (this might take a while)... Generation complete. postgres already running stop container FAILED -------------------- Pups::ExecError: [ -f /root/install_postgres ] && /root/install_postgres && rm -f /root/install_postgres failed with return # Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn' exec failed with the params {"tag"=>"db", "cmd"=>"[ -f /root/install_postgres ] && /root/install_postgres && rm -f /root/install_postgres"} bootstrap failed with exit code 1 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. 902db7e2e5295f896eb00f8379d8507209ddc1844e335ecb403f0cd900502448```

please I need some help, I can’t even have rebuild, I just want the changes in my app.yml to change on the site, its not even using the full amount of ram it can use, I made some changes to the shared buffers and I want it to go live. now I can’t even rebuild, to get site back online I used discourse doctor or just restart the old app

[image] Genisis: postgres already running stop container Is there some other instance of postgres running (on the main host?) that is somehow communicating with the container as it’s trying to build?

no idea and id not think so, as I set it up on a fresh server. should I somehow stop. I googled how to check if postgres is running and I ran this command, ‘service postgresql status’, returned Unit postgresql.service could not be found. I even rebooted server, still didn’t work. full console log before it sticks https://pastebin.com/Nz4ux9qs

thats where it sticks, if I let it stay too long then it says this as I shown in my earlier messages. Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn' exec failed with the params {"tag"=>"db", "cmd"=>"[ -f /root/install_postgres ] && /root/install_postgres && rm -f /root/install_postgres"} bootstrap failed with exit code 1 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. 902db7e2e5295f896eb00f8379d8507209ddc1844e335ecb403f0cd900502448 I wanted to avoid long downtime so I stopped it and started back the app, also thank you for your response, idk what to do, I need to rebuild app

How much RAM + Swap do you have? Might not be enough for it to build.

Is that identical to the new errors? The new logs seems to crash after those commands have already been run.

Yarn error

Product Support Self-hosting

Genisis May 9, 2024, 5:00pm 16

more than enough, 40GB ram, 400GB storage

its not even using much ram, I made changes to app.yml to take more from ram and added 25 UNICORN_WORKERS (12 core cpu)

Topic		Replies	Views
Continuous Issues when Rebuilding Discourse Self-hosting	5	789	March 19, 2024
Down after upgrade: yarn: not found Self-hosting	2	839	April 15, 2022
Can't install reaction plugin Self-hosting reactions	20	1132	June 11, 2024
Discourse Installation Failure on Fresh Server: FAILED TO BOOTSTRAP Self-hosting	11	1230	May 7, 2023
Error during rebuild: registry.yarnpkg.com ESOCKETTIMEDOUT Self-hosting	4	664	August 2, 2024

Yarn error

Related topics