Discourse 更新时卡住

安装
1

您好，

我负责管理我们组织的一个 Discourse 论坛。它运行在 AWS 的 Ubuntu 18.04 服务器上。我对 Ubuntu 有些了解，但对 Discourse 了解不多。

我尝试升级到最新版本时卡住了。这是我尝试过的：

# 应用安全更新
apt-get update
apt-get dist-upgrade

# 更新软件包
apt-get update
apt-get upgrade

# 更新 Docker
wget -qO- https://get.docker.com/ | sh

# 再次尝试更新 Discourse
cd /var/discourse
./launcher rebuild app

当我进行到以下步骤时，更新就卡住了：


I, [2023-09-28T21:24:31.330675 #1]  INFO -- : > cd /var/www/discourse && gem install bundl
er --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lo
ck)
I, [2023-09-28T21:24:32.423727 #1]  INFO -- : Successfully installed bundler-2.4.13
1 gem installed

I, [2023-09-28T21:24:32.424286 #1]  INFO -- : > cd /var/www/discourse && find /var/www/dis
course ! -user discourse -exec chown discourse {} \+
I, [2023-09-28T21:26:48.768332 #1]  INFO -- : 
I, [2023-09-28T21:26:48.769200 #1]  INFO -- : > cd /var/www/discourse && if [ "tests-passe
d" != "tests-passed" ]; then
  rm -rf app/assets/javascripts/node_modules
fi
I, [2023-09-28T21:26:48.771875 #1]  INFO -- : 
I, [2023-09-28T21:26:48.772302 #1]  INFO -- : > cd /var/www/discourse && su discourse -c '
yarn install --frozen-lockfile && yarn cache clean'
warning " > @glint/environment-ember-loose@1.1.0" has unmet peer dependency "@glimmer/comp
onent@^1.1.2".
warning " > @glint/environment-ember-template-imports@1.1.0" has unmet peer dependency "em
ber-template-imports@^3.0.0".
warning " > @mixer/parallel-prettier@2.0.3" has unmet peer dependency "prettier@^2.0.0".

htop 显示有几个 yarn.js 进程似乎卡住了：

13727 ubuntu     20   0  911M  160M 29000 S  2.7 16.5  0:54.90 node /usr/share/yarn/bin/yarn.js install --frozen-lockfile
13747 ubuntu     20   0  911M  160M 29000 D  0.7 16.5  0:04.90 node /usr/share/yarn/bin/yarn.js install --frozen-lockfile

有什么可以尝试的吗？

提前感谢。

2 个赞
2

如果相关的话，您是从哪个版本的 Discourse 升级的？

看起来问题就出在这里。这可能是一个很小的几率，但可能与此有关：https://meta.discourse.org/t/stuck-on-yarn-install-time-out/227738。

或许值得确认您的服务器是否满足此处显示的软件要求：https://github.com/discourse/discourse/blob/main/docs/INSTALL.md。

3 个赞
3

Well you were right about this one. I’ve followed the same procedure and the update went through instead of timing out. It took a long time to run (~20 hours) because the machine was overloaded, but that’s another story.

Thanks for helping out.

1 个赞
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.