I have error when try to upgrade/rebuild my discourse

Product Support

AI-generated summary

cmdntd reported a failed ./launcher rebuild command, encountering a Pups::ExecError during the bundle install step. The error log indicated a Ruby version mismatch, stating, “Your Ruby version is 3.4.10, but your Gemfile specified ~> 4.0.0,” though this appeared to be a symptom rather than the primary cause. A subsequent sudo git pull failed with a fatal error: “Out of memory, malloc failed (tried to allocate 104857600000 bytes).” This suggests the process attempted to allocate approximately 100GB of memory. cmdntd clarified that system memory was normal and suspected a Docker or Git memory limit issue.

pfaffman confirmed that 100GB is an abnormal allocation size, indicating something is definitely wrong. They noted that ./launcher rebuild should handle the git pull automatically and questioned why a manual git pull would request such a large amount of memory. Jagster had initially asked if the system was actually out of memory, which cmdntd denied.

Ed_S requested more diagnostic information to determine if this was a standard installation. They asked for the current version of the installation (via view-source or dashboard), the version: line from the .yml configuration file (which defaults to tests-passed), and the last several hundred lines of the log file to identify the root cause. The thread remains open pending further details from the user.

1

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

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:

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`

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.
2

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

3

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

100Gb is like git-error memory?

4

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.

5

Is this a standard install? What version is the installation at according to a view-source, or the dashboard?

What does this bit of your *.yml file look like?

  ## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

Please post much more of your log file: the last several hundred lines should be enough.