I upgrade regularly (every month or so), and haven’t had an issue like this that prevented building. My server is currently inaccessible. I would say I have a pretty standard install. There is ample free disk space. discourse-doctor didn’t produce any errors or things that looked suspicious. Nothing about the system has changed. A git pull was performed before attempting launcher rebuild app. If more info is needed for a proper diagnosis, let me know. I’m not quite sure from the log what the issue is. If someone more familiar with this software can take a look, I’d appreciate it. Here are the plugins I’m using: - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/discourse/discourse-akismet.git - git clone https://github.com/discourse/discourse-spoiler-alert.git - git clone https://github.com/discourse/discourse-yearly-review.git - git clone https://github.com/discourse/discourse-patreon - git clone https://github.com/discourse/discourse-solved - git clone https://github.com/discourse/discourse-github - git clone https://github.com/discourse/discourse-checklist - git clone https://github.com/discourse/discourse-tooltips.git - git clone https://github.com/discourse/discourse-docs - git clone https://github.com/discourse/discourse-user-notes - git clone https://github.com/discourse/discourse-math - git clone https://github.com/discourse/discourse-chat-integration - git clone https://github.com/discourse/discourse-encrypt.git - git clone https://github.com/discourse/discourse-footnote - git clone https://github.com/discourse/discourse-follow - git clone https://github.com/discourse/discourse-push-notifications Here is the end of my build log: I, [2022-10-12T15:47:04.673293 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'LOAD_PLUGINS=0 bundle exec rake plugin:pull_compatible_all' I, [2022-10-12T15:47:09.943126 #1] INFO -- : discourse-math is already at latest compatible version discourse-chat-integration is already at latest compatible version discourse-spoiler-alert is already at latest compatible version discourse-encrypt is already at latest compatible version discourse-tooltips is already at latest compatible version discourse-follow is already at latest compatible version docker_manager is already at latest compatible version discourse-github is already at latest compatible version discourse-push-notifications is already at latest compatible version discourse-solved is already at latest compatible version discourse-akismet is already at latest compatible version discourse-footnote is already at latest compatible version discourse-yearly-review is already at latest compatible version discourse-checklist is already at latest compatible version discourse-patreon is already at latest compatible version discourse-docs is already at latest compatible version discourse-user-notes is already at latest compatible version I, [2022-10-12T15:47:09.944907 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' I, [2022-10-12T15:47:23.023114 #1] INFO -- : gem install sawyer -v 0.9.2 -i /var/www/discourse/plugins/discourse-github/gems/2.7.6 --no-document --ignore-dependencies --no-user-install Successfully installed sawyer-0.9.2 1 gem installed gem install octokit -v 5.6.1 -i /var/www/discourse/plugins/discourse-github/gems/2.7.6 --no-document --ignore-dependencies --no-user-install Successfully installed octokit-5.6.1 1 gem installed I, [2022-10-12T15:47:23.024237 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' 103:M 12 Oct 2022 15:47:34.098 * 100 changes in 300 seconds. Saving... 103:M 12 Oct 2022 15:47:34.102 * Background saving started by pid 1695 1695:C 12 Oct 2022 15:47:34.384 * DB saved on disk 1695:C 12 Oct 2022 15:47:34.386 * RDB: 0 MB of memory used by copy-on-write 103:M 12 Oct 2022 15:47:34.407 * Background saving terminated with success - Building - Building - building... Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-property-in-object since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties. The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding ["@babel/plugin-proposal-private-property-in-object", { "loose": true }] to the "plugins" section of your Babel config. Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-private-property-in-object. The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding ["@babel/plugin-proposal-private-methods", { "loose": true }] to the "plugins" section of your Babel config. [WARN] (broccoli-terser-sourcemap) Minifying "assets/discourse.js" took: 26102ms (more than 20,000ms) Killed error Command failed with exit code 137. I, [2022-10-12T15:51:18.234000 #1] INFO -- : Checking 'discourse-homepage-feature-component' for 'default'... up to date Checking 'Versatile Banner' for 'default'... up to date Checking 'Custom Header Links' for 'default'... yarn run v1.22.19 $ /var/www/discourse/app/assets/javascripts/node_modules/.bin/ember build -prod Environment: production info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. I, [2022-10-12T15:51:18.245871 #1] INFO -- : Terminating async processes I, [2022-10-12T15:51:18.246532 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42 I, [2022-10-12T15:51:18.247499 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103 103:signal-handler (1665589878) Received SIGTERM scheduling shutdown... 2022-10-12 15:51:18.249 UTC [42] LOG: received fast shutdown request 103:M 12 Oct 2022 15:51:18.327 # User requested shutdown... 103:M 12 Oct 2022 15:51:18.327 * Saving the final RDB snapshot before exiting. 2022-10-12 15:51:19.052 UTC [42] LOG: aborting any active transactions 2022-10-12 15:51:19.100 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1 2022-10-12 15:51:19.102 UTC [46] LOG: shutting down 2022-10-12 15:51:19.188 UTC [42] LOG: database system is shut down 103:M 12 Oct 2022 15:51:20.072 * DB saved on disk 103:M 12 Oct 2022 15:51:20.073 # Redis is now ready to exit, bye bye... FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' 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"=>"assets_precompile", "cmd"=>["su discourse -c 'bundle exec rake themes:update assets:precompile'"]} bootstrap failed with exit code 137 ** 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. 5354ffedbf56742079333cb69face684193aaa0afa7f1ff492666e17a2e1f51d

I think error 137 is not enough memory. Did you do a standard install and let it add some swap when it gave you the option? There’s a pretty informative discussion about a similar error in this topic, if it sounds like it could be the case: [image] Failed to upgrade discourse instance to Feb 15 2022 Self-hosting Upgrading from Commits · discourse/discourse · GitHub to the latest has caused the site to go down, here is notable segments of the logs: I, [2022-02-15T05:27:48.995821 #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, [2022-02-15T05:27:48.997476 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/13/main/pg_hba.conf I, [2022-02-15T05:27:48.998553 #1] INFO --…

[image] JammyDodger: Did you do a standard install and let it add some swap when it gave you the option? I don’t recall, but it’s a VSP with 2 GB mem and 2 GB swap. $ free -h total used free shared buff/cache available Mem: 1.9Gi 688Mi 64Mi 33Mi 1.2Gi 1.1Gi Swap: 2.0Gi 1.0Gi 1.0Gi

Heya! :wave: Could you do free -h, and share the output? :slight_smile:

[image] maiki: Could you do free -h, and share the output? I edited my last post. [image] JammyDodger: I think error 137 is not enough memory. This seems the likely culprit. I’ve been clearing disk space and upgrading via apt, and after a reboot, I built again and it actually completed. Although there were package changes, I think the reboot restored just enough ram/swap to let the build finish. Interestingly, I’ve had to stop upgrading via the UI because of low memory (I exclusively do it from the command line), but I’ve never had a build fail at the command line. I’ll see about increasing my swap another 1 GB to prevent this in the future and see if I can restore my ability to upgrade via the UI.

Just one more update. I’ve had to wait since I upgraded to have a new upgrade to test with. Previously, upgrading via the UI was not possible, as it would also crash mid-upgrade, due to low RAM. I was able to just successfully upgrade via the UI after fixing this command line build issue by increasing the swapfile size. Thanks for the help.

Upgrade failed, "FAILED TO BOOTSTRAP", error 137

Product Support Self-hosting

maiki (maiki) October 12, 2022, 6:08pm 4

Heya!

Could you do free -h, and share the output?

Topic		Replies	Views
Error while updating through launcher rebuild Self-hosting	2	681	April 16, 2024
Problem with Upgrade [error 137] Self-hosting server-resources	31	2039	February 11, 2024
Failed to boostrap (exit code 137) Self-hosting server-resources	7	1270	June 13, 2022
Failed to upgrade discourse instance to Feb 15 2022 Self-hosting server-resources	29	3375	February 16, 2022
3.1.x to 3.2.0 upgrade hangs/fails on 1GB instance Self-hosting	34	2218	February 23, 2024

Upgrade failed, "FAILED TO BOOTSTRAP", error 137

Related topics