# I have error when try to upgrade/rebuild my discourse

**URL:** <https://meta.discourse.org/t/i-have-error-when-try-to-upgrade-rebuild-my-discourse/417211>\
**Category:** Product Support\
**Created:** [November 12, 2026, 2:12pm UTC](https://meta.discourse.org/t/i-have-error-when-try-to-upgrade-rebuild-my-discourse/417211 "2026-11-12T14:12:19Z")\
**Posts on this page:** 4\
**Page:** 1

## AI-generated summary

[cmdntd](/t/-/417211/1) reports a failure when rebuilding Discourse. The `pups` build process aborts with exit code 18 during `bundle install`, accompanied by a `SIGTERM` signal. A critical error message reveals a version mismatch: "Your Ruby version is 3.4.10, but your Gemfile specified ~> 4.0.0". Additionally, cmdntd encounters a separate fatal error when manually running `sudo git pull`, where Git fails with an "Out of memory" error after attempting to allocate 104,857,600,000 bytes (100GB).

[Jagster](/t/-/417211/2) asks if the system was truly out of memory. [cmdntd](/t/-/417211/3) responds that system memory is normal, suspecting a Docker image or Git memory limit, and questions if the 100GB allocation attempt is a Git error.

[pfaffman](/t/-/417211/4) confirms that attempting to allocate 100GB indicates something is definitely wrong. They advise that the `/var/discourse` directory might be outdated and note that a standard `./launcher rebuild` should automatically pull changes. While pfaffman suggests this automated pull is the correct method, they state they cannot explain why a manual `git pull` would demand such an excessive amount of memory.

<div class="post-metadata">

**Author:** ![cmdntd](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmdntd/32/192008_2.png) [@cmdntd](https://meta.discourse.org/u/cmdntd)\
**Post date:** [November 12, 2026, 2:12pm UTC](https://meta.discourse.org/t/i-have-error-when-try-to-upgrade-rebuild-my-discourse/417211/1 "2026-11-12T14:12:19Z")

</div>

I have error when try to upgrade/rebuild my discourse:

```plaintext
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --jobs $(nproc --ignore=1) --retry 3' failed with return #<Process::Status: pid 1868 exit 18>
Location of failure: /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/exec_command.rb:138:in 'Pups::ExecCommand#spawn'
exec failed with the params {"cd" => "$home", "tag" => "build", "hook" => "bundle_exec", "cmd" => ["su discourse -c 'bundle install --jobs $(nproc --ignore=1) --retry 3'", "su discourse -c 'bundle clean'", "su discourse -c 'find /var/www/discourse/vendor/bundle -name cache -not -path \"*/gems/*\" -type d -exec rm -rf {} +'", "su discourse -c 'find /var/www/discourse/vendor/bundle -name tmp -type d -exec rm -rf {} +'"]}
bootstrap failed with exit code 18
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one.

```

I see this above:

```plaintext
Fetching gem metadata from https://rubygems.org/.
Fetching bundler 4.0.23
Installing bundler 4.0.23
Your Ruby version is 3.4.10, but your Gemfile specified ~> 4.0.0
128:signal-handler (1794492346) Received SIGTERM scheduling shutdown...

```

I have an error when run `sudo git pull`

```plaintext
sudo git pull

fatal: Out of memory, malloc failed (tried to allocate 104857600000 bytes)
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

```

---

<div class="post-metadata">

**Author:** ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)\
**Post date:** [November 12, 2026, 3:32pm UTC](https://meta.discourse.org/t/i-have-error-when-try-to-upgrade-rebuild-my-discourse/417211/2 "2026-11-12T15:32:13Z")

</div>

I don’t know, but did you were out of memory?

---

<div class="post-metadata">

**Author:** ![cmdntd](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmdntd/32/192008_2.png) [@cmdntd](https://meta.discourse.org/u/cmdntd)\
**Post date:** [November 12, 2026, 3:37pm UTC](https://meta.discourse.org/t/i-have-error-when-try-to-upgrade-rebuild-my-discourse/417211/3 "2026-11-12T15:37:52Z")

</div>

My memory is normal. I think this is something from docker-image/git memory limit.

100Gb is like git-error memory?

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [November 12, 2026, 3:46pm UTC](https://meta.discourse.org/t/i-have-error-when-try-to-upgrade-rebuild-my-discourse/417211/4 "2026-11-12T15:46:27Z")

</div>

> [@cmdntd](#):
>
> `104857600000`

Yeah. That’s 100GB. So something is definitely wrong.

So it looks like you have an old `/var/discourse`–it should do a pull automatically if you do a `./launcher rebuild`.

Why a `git pull` wants 100GB I can’t explain.