Recientemente intentamos instalar un plugin privado en nuestra instancia de Discourse. Al reiniciar Docker, el servicio no volvió a estar en línea. Después de múltiples intentos, vemos esto:
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
…otras cosas que intentamos para que la aplicación volviera a estar en línea:
- Reconstruir la aplicación
- Limpiar la caché de Docker usando:
./launcher cleanup
Si alguien ha experimentado esto o puede indicarnos la dirección correcta, se lo agradeceríamos.