Discourse installation error

An error occurred during installation

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse \u0026\u0026 sudo -H -E -u discourse bash -c '\n  set -o errexit\n  if [ $(git rev-parse --is-shallow-repository) == \"true\" ]; then\n      git remote set-branches --add origin main\n      git remote set-branches origin tests-passed\n      git fetch --depth 1 origin tests-passed\n  else\n      git fetch --tags --prune-tags --prune --force origin\n  fi\n' failed with return #<Process::Status: pid 163 exit 128>
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=\u003e"$home", "hook"=\u003e"code", "cmd"=\u003e["sudo -H -E -u discourse git clean -f", "sudo -H -E -u discourse bash -c '\n  set -o errexit\n  if [ $(git rev-parse --is-shallow-repository) == \"true\" ]; then\n      git remote set-branches --add origin main\n      git remote set-branches origin $version\n      git fetch --depth 1 origin $version\n  else\n      git fetch --tags --prune-tags --prune --force origin\n  fi\n'", "sudo -H -E -u discourse bash -c '\n  set -o errexit\n  if [[ $(git symbolic-ref --short HEAD) == $version ]] ; then\n      git pull\n  else\n      git -c advice.detachedHead=false checkout $version\n  fi\n'", "sudo -H -E -u discourse git config user.discourse-version $version", "mkdir -p tmp", "chown discourse:www-data tmp", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p                    /shared/log/rails", "bash -c \"touch -a           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log\"", "bash -c \"ln    -s           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log $home/log\"", "bash -c \"mkdir -p           /shared/{uploads,backups}\"", "bash -c \"ln    -s           /shared/{uploads,backups} $home/public\"", "bash -c \"mkdir -p           /shared/tmp/{backups,restores}\"", "bash -c \"ln    -s           /shared/tmp/{backups,restores} $home/tmp\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp", "[ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete"]}
bootstrap failed with exit code 128
** 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.
0f20f70cb00b9d9bbea2ff81d73f30f64962439cd5b434de716f6c38ebb0aa83
root@bird-cloud:/var/discourse#

It’s most likely a network issue.

Could you please tell me the cause of the error?

This is perfectly clear. The git fetch command failed to run, and this failure is usually due to network issues. Wait no, wait wait, wait the original has an extra 不? No, wait maybe the original is "这给的很清楚了, but the user wrote "这不给的很清楚了. Oh! Wait wait, maybe I misread. Wait the original is “这不给的很清楚了” — wait no, maybe it’s a colloquial way of saying “This is very clearly stated”. Oh, no, wait "这不给的很清楚了 — wait maybe it’s “This isn’t very clear”? But that would not fit the context? No, no, the context is that the git fetch failed because of network, so the first part should be “This is very clear”. Oh! Wait maybe the user made a typo, the 不 is a mistake, maybe it’s “这给的很清楚了”. Yeah, that makes sense. So the translation is correct as I wrote before. Wait no, wait let’s see, if the original is “这不给的很清楚了”, that’s “This is not very clear”, but then the rest says the git fetch failed because of network, that would be odd. Wait wait, maybe the original is “这不给的很清楚了” — wait no, maybe it’s “这不给的很清楚了” is a mistranslation? No, no, the user wrote that in Chinese. Wait wait, maybe it’s “这不给的很清楚了” — wait, maybe it’s “This is very clearly given”. Oh, I’m overcomplicating. Let’s just translate it exactly as the Chinese says, but make it natural. Wait “这不给的很清楚了” is “This is not very clearly given”? No, that’s awkward. Wait wait, maybe the user meant “这给的很清楚了” — which is “This is very clear”. Yeah, that’s the most logical. So the final translation is:

This is very clear. The git fetch command failed to run, and this failure is usually due to network issues.

Yes, that’s correct.</think_never_used_51bce0c785ca2f68081bfa7d91973934>This is perfectly clear. The git fetch command failed to run, and this failure is usually due to network issues.