Discourse 启动问题

刚注意到我应该进行一次 discourse 更新,于是顺利完成了更新。

仪表板通知我应禁用脚注插件并重建应用程序。完成此操作后,我看到一个无尽的启动屏幕(动画点)。

尝试了停止、启动、重建、重启……均无效。任何关于如何调试/修复的建议都将不胜感激。

更多信息…

sudo docker logs app
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/01-cleanup-web-pids
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
run-parts: executing /etc/runit/1.d/letsencrypt
[Tue 30 Jan 2024 12:27:24 AM UTC] Domains not changed.
[Tue 30 Jan 2024 12:27:24 AM UTC] Skip, Next renewal time is: 2024-03-13T00:35:08Z
[Tue 30 Jan 2024 12:27:24 AM UTC] Add '--force' to force to renew.
[Tue 30 Jan 2024 12:27:24 AM UTC] Installing key to: /shared/ssl/community.acescentral.com.key
[Tue 30 Jan 2024 12:27:24 AM UTC] Installing full chain to: /shared/ssl/community.acescentral.com.cer
[Tue 30 Jan 2024 12:27:24 AM UTC] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Tue 30 Jan 2024 12:27:25 AM UTC] Reload error for :
[Tue 30 Jan 2024 12:27:25 AM UTC] Domains not changed.
[Tue 30 Jan 2024 12:27:25 AM UTC] Skip, Next renewal time is: 2024-03-12T00:35:09Z
[Tue 30 Jan 2024 12:27:25 AM UTC] Add '--force' to force to renew.
[Tue 30 Jan 2024 12:27:25 AM UTC] Installing key to: /shared/ssl/community.acescentral.com_ecc.key
[Tue 30 Jan 2024 12:27:25 AM UTC] Installing full chain to: /shared/ssl/community.acescentral.com_ecc.cer
[Tue 30 Jan 2024 12:27:25 AM UTC] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Tue 30 Jan 2024 12:27:25 AM UTC] Reload error for :
Started runsvdir, PID is 537
ok: run: redis: (pid 549) 0s
ok: run: postgres: (pid 551) 0s
nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /etc/nginx/conf.d/discourse.conf:60
supervisor pid: 548 unicorn pid: 577
1 个赞

可以进入安全模式

我认为这与 pushover 插件有关

我认为这是问题所在?

我认为#bug现在应该已经修复了,所以我不认为会是那个问题。

你的/logs或浏览器控制台中可能还有更多细节可以确认,但如果你在不使用它的情况下进行重建,那也能回答这个问题。

以防万一不是,你还可以通过使用安全模式的不同选项来缩小范围,看看是否是主题/主题组件的问题。分享你的插件列表也很有用,以便任何人都能发现一个已知问题的插件。