A instalação de plugin privada faz com que o aplicativo não volte a ficar online

Recentemente, tentamos instalar um plugin privado em nossa instância do Discourse. Após reiniciar o Docker, o serviço não voltou a ficar online. Após várias tentativas, estamos vendo isto:

root@discourse:/var/discourse# docker container logs d6aa2ac484b9
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 Feb 4 07:23:08 PM UTC 2025] Domains not changed.
[Tue Feb 4 07:23:08 PM UTC 2025] Skip, Next renewal time is: 2025-03-17T17:22:01Z
[Tue Feb 4 07:23:08 PM UTC 2025] Add '--force' to force to renew.
[Tue Feb 4 07:23:09 PM UTC 2025] Installing key to: /shared/ssl/forum.get.it.key
[Tue Feb 4 07:23:09 PM UTC 2025] Installing full chain to: /shared/ssl/forum.get.it.cer
[Tue Feb 4 07:23:09 PM UTC 2025] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Tue Feb 4 07:23:09 PM UTC 2025] Reload error for :
[Tue Feb 4 07:23:10 PM UTC 2025] Domains not changed.
[Tue Feb 4 07:23:10 PM UTC 2025] Skip, Next renewal time is: 2025-03-17T17:22:09Z
[Tue Feb 4 07:23:10 PM UTC 2025] Add '--force' to force to renew.
[Tue Feb 4 07:23:11 PM UTC 2025] Installing key to: /shared/ssl/forum.get.it_ecc.key
[Tue Feb 4 07:23:11 PM UTC 2025] Installing full chain to: /shared/ssl/forum.get.it_ecc.cer
[Tue Feb 4 07:23:11 PM UTC 2025] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Tue Feb 4 07:23:12 PM UTC 2025] Reload error for :
Started runsvdir, PID is 534
ok: run: redis: (pid 548) 0s
ok: run: postgres: (pid 544) 0s
nginx: [warn] duplicate extension \"wasm\", content type: \"application/wasm\", previous content type: \"application/wasm\" in /etc/nginx/conf.d/discourse.conf:4
supervisor pid: 547 unicorn pid: 574

…outras coisas que tentamos para trazer o aplicativo de volta online:

  • Reconstruir o aplicativo
  • Limpar o cache do Docker usando: ./launcher cleanup

Se alguém já passou por isso ou puder nos indicar a direção certa, agradeceríamos.

Olá @Jacob_Peebles - a causa mais provável é Site offline after rebuild (4th Feb 2025) - #7 by david. Se você executar outra reconstrução, as coisas devem funcionar muito melhor. Desculpe pela interrupção!

3 curtidas

@david obrigado, vamos tentar e retornaremos.

Trabalhou @david!

1 curtida

Este tópico foi automaticamente fechado após 11 horas. Novas respostas não são mais permitidas.