Discourse para de carregar na caixa de diálogo de login quando visualizado com qualquer navegador

Suporte Instalação
1

Algumas atualizações atrás, notei que não conseguia mais acessar meu fórum discourse www.nzarchitecture.net.nz, de nenhum dos meus smartphones Android 10, ou do meu Chromebook ou de qualquer PC com Windows (exceto em um onde eu já estava logado)

O site para de carregar ao tentar invocar a caixa de diálogo de login, exibindo o gráfico de pontos coloridos ‘loading’ infinitamente.

download|0x0

Testei em três telefones Samsung Galaxy S9+ diferentes (todos na minha família têm o mesmo telefone) usando Brave, Chrome, Edge e o navegador pré-instalado da Samsung.

Nenhuma alteração via janela de navegação anônima (modo de segurança).

Infelizmente, não sei exatamente qual atualização do Discourse pode ter causado o problema, pois raramente saio deliberadamente, e minha máquina Windows principal está permanentemente logada, então ignora a caixa de diálogo de login quando normalmente acesso o site.

Este é um problema conhecido e existe uma solução?

Talvez algo relacionado a pop-ups do navegador?

2

Obrigado pelo relatório! Você poderia nos informar qual versão do navegador está usando? Assumo que você esteja usando o Chrome no Android?

Se não tiver certeza, tente visitar https://www.whatsmybrowser.org/ e procure o número da versão do Chrome no topo.

3

Na verdade, não consigo carregar http://www.nzarchitecture.net.nz/ também (último Chrome, macOS), então não acho que seja um problema específico do navegador. O console do navegador mostra um erro com discourse-merge-users. Esse plugin está obsoleto, então o administrador do seu fórum precisa desinstalá-lo.

4

Confirme que o site não carrega no Ubuntu, Win10 e Android 10 (Firefox).

5

Olá, um exemplo onde a caixa de diálogo de login não abre é no Chrome 109 What browser am I using?

Mas, como observado acima, o problema também afeta o Edge e o Brave no Windows 11 e Android 10, e o próprio navegador da Samsung no Android 10.

Acabei de testar e também afeta o navegador Tor (12.0.1) no Windows 11.

Anteriormente, tentei regenerar o site usando

cd /var/discourse
git pull; ./launcher rebuild app
./launcher cleanup

mas novamente nenhuma mudança - então assumi que minha instalação não está corrompida.
Dado que os sites do Discourse de outras pessoas ainda parecem funcionar, isso sugere que deve haver alguma configuração nova incompatível associada a uma atualização recente?

6

Alguém mais teve esse problema com Merge Users recentemente também:

7

Isso vai ser um problema - eu já tentei desinstalar esse plugin há cerca de um ano e quebrei o site como resultado, sendo forçado a restaurar a partir de um backup.

E, claro, agora que saí após todos os meus testes, não consigo mais fazer login para tentar desativar o plugin novamente.

8

Desativar um plugin via admin não o desativa totalmente.

Você precisará removê-lo do seu arquivo yml e reconstruir via terminal.

O plugin Merge users está obsoleto agora, o recurso é nativo do discourse desde a versão 2.5.

9

Este link deve ajudar a fazer login: https://nzarchitecture.net.nz/login?safe_mode=no_plugins

(você pode adicionar ?safe_mode=no_plugins a qualquer URL)

Mas, como @Stephen disse, a única maneira de remover um plugin com certeza é removê-lo da configuração YML e reconstruir.

10

Hmm - meu arquivo app.yml parece diferente e não tem referências a plugins que eu possa ver.

Sessão do console Putty abaixo, caso ajude


root@nz:~# cd /var/discourse
root@nz:/var/discourse# nano containers/app.yml
  GNU nano 2.9.3                         containers/app.yml

## este é o template do container Docker Discourse tudo-em-um e autônomo
##
## Após fazer alterações neste arquivo, você DEVE reconstruir
## /var/discourse/launcher rebuild app
##
## TENHA *MUITO* CUIDADO AO EDITAR!
## ARQUIVOS YAML SÃO SUPER SUPER SENSÍVEIS A ERROS DE ESPAÇAMENTO OU ALINHAMENTO!
## visite http://www.yamllint.com/ para validar este arquivo conforme necessário

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
## Descomente estas duas linhas se desejar adicionar Lets Encrypt (https)
  - "templates/web.ssl.template.yml"
  - "templates/web.letsencrypt.ssl.template.yml"
  - "templates/import/mysql-dep.template.yml"

## quais portas TCP/IP este container deve expor?
## Se você quiser que o Discourse compartilhe uma porta com outro servidor web como Apache ou nginx,
## veja https://meta.discourse.org/t/17247 para detalhes
expose:
  - "80:80"   # http
  - "443:443" # https

params:
  db_default_text_search_config: "pg_catalog.english"

  ## Defina db_shared_buffers para um máximo de 25% da memória total.
  ## será definido automaticamente pelo bootstrap com base na RAM detectada, ou você pode substituir
  db_shared_buffers: "128MB"

  ## pode melhorar o desempenho da ordenação, mas adiciona uso de memória por conexão
  #db_work_mem: "40MB"

  ## Qual revisão Git este container deve usar? (padrão: tests-passed)
  #version: tests-passed
11

Como esta instância foi instalada? Você está usando dois contêineres?

12

Olá, apenas um contêiner (pelo menos que eu saiba)

Para ser justo, não sei e não entendo nada sobre Linux…
Sei que tenho uma única instância Digital Ocean - isso é o mesmo que um ‘contêiner’?

13

Há bastante mais nesse arquivo, role para baixo.

Os plugins estão na seção hooks: por volta da linha 94.

Se você estiver no nano, use Ctrl+_ para pular para um número de linha ou nano +94 app.yml

14

Ah, obrigado! - parece ser um problema com o aplicativo Putty - de acordo com a posição da barra de rolagem no aplicativo, o que colei acima representa tudo, e não é possível rolar mais pela barra de rolagem.

No entanto, posso rolar mais usando as teclas de seta.

15

Sim, isso ocorre porque as barras de rolagem do PuTTY são baseadas em informações já transmitidas para o seu terminal local, enquanto as teclas de rolagem instruem a sessão remota a mostrar mais.

16

Infelizmente, parece que um resultado semelhante ao que aconteceu na primeira vez que tentei remover esse plugin no ano passado está ocorrendo agora.

Durante a reconstrução, recebo o seguinte (acabei de tentar duas vezes):

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev falhou com retorno #<Process::Status: pid 488 exit 100>
Localização da falha: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec falhou com os parâmetros {"cd"=>"$home", "cmd"=>["echo \"gem 'mysql2'\" >> Gemfile", "apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev", "su discourse -c 'bundle config unset deployment'", "su discourse -c 'bundle install --no-deployment --path vendor/bundle --jobs 4 --without test development'"]}
bootstrap falhou com código de saída 100
** FALHA AO INICIAR ** por favor, role para cima e procure por mensagens de erro anteriores, pode haver mais de uma.
./discourse-doctor pode ajudar a diagnosticar o problema.
b40e566c2a5dd29d8d7253ab893b7bef0c937020615f7e0a24bd57e5b2ec99d3
root@nz:/var/discourse#

Meu arquivo app.yml foi editado, tenho certeza que corretamente, com apenas a linha referente ao plugin ‘merge users’ sendo excluída e nenhuma outra alteração.

17

O erro real está acima da seção que você colou, precisamos ver mais.

18

Aqui está a sessão completa

root@nz:/var/discourse# git pull; ./launcher rebuild app
Already up to date.
x86_64 arch detected.

WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient

2.0.20230116-0051: Pulling from discourse/base
8740c948ffd4: Pull complete
219274ac76f4: Pull complete
8c33c4f7b2b0: Pull complete
Digest: sha256:9e75876adb52427902a6d76dab731c4888af811d7e5ad9ee6efcec4ce6db986f
Status: Downloaded newer image for discourse/base:2.0.20230116-0051
docker.io/discourse/base:2.0.20230116-0051
WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
2.0.20230116-0051: Pulling from discourse/base
Digest: sha256:9e75876adb52427902a6d76dab731c4888af811d7e5ad9ee6efcec4ce6db986f
Status: Image is up to date for discourse/base:2.0.20230116-0051
docker.io/discourse/base:2.0.20230116-0051
/usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2023-01-26T14:16:42.982925 #1]  INFO -- : Reading from stdin
I, [2023-01-26T14:16:42.989944 #1]  INFO -- : > locale-gen $LANG && update-locale
I, [2023-01-26T14:16:43.061977 #1]  INFO -- : Generating locales (this might take a while)...
Generation complete.

I, [2023-01-26T14:16:43.062708 #1]  INFO -- : > mkdir -p /shared/postgres_run
I, [2023-01-26T14:16:43.071852 #1]  INFO -- :
I, [2023-01-26T14:16:43.073682 #1]  INFO -- : > chown postgres:postgres /shared/postgres_run
I, [2023-01-26T14:16:43.079338 #1]  INFO -- :
I, [2023-01-26T14:16:43.080200 #1]  INFO -- : > chmod 775 /shared/postgres_run
I, [2023-01-26T14:16:43.084938 #1]  INFO -- :
I, [2023-01-26T14:16:43.085649 #1]  INFO -- : > rm -fr /var/run/postgresql
I, [2023-01-26T14:16:43.088679 #1]  INFO -- :
I, [2023-01-26T14:16:43.089260 #1]  INFO -- : > ln -s /shared/postgres_run /var/run/postgresql
I, [2023-01-26T14:16:43.093417 #1]  INFO -- :
I, [2023-01-26T14:16:43.093998 #1]  INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
2023/01/26 14:16:43 socat[18] E connect(6, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): No such file or directory
I, [2023-01-26T14:16:43.132885 #1]  INFO -- :
I, [2023-01-26T14:16:43.133578 #1]  INFO -- : > rm -fr /shared/postgres_run/.s*
I, [2023-01-26T14:16:43.137967 #1]  INFO -- :
I, [2023-01-26T14:16:43.138440 #1]  INFO -- : > rm -fr /shared/postgres_run/*.pid
I, [2023-01-26T14:16:43.141928 #1]  INFO -- :
I, [2023-01-26T14:16:43.142341 #1]  INFO -- : > mkdir -p /shared/postgres_run/13-main.pg_stat_tmp
I, [2023-01-26T14:16:43.145367 #1]  INFO -- :
I, [2023-01-26T14:16:43.146041 #1]  INFO -- : > chown postgres:postgres /shared/postgres_run/13-main.pg_stat_tmp
I, [2023-01-26T14:16:43.148783 #1]  INFO -- :
I, [2023-01-26T14:16:43.154701 #1]  INFO -- : File > /etc/service/postgres/run  chmod: +x  chown:
I, [2023-01-26T14:16:43.160967 #1]  INFO -- : File > /etc/service/postgres/log/run  chmod: +x  chown:
I, [2023-01-26T14:16:43.166831 #1]  INFO -- : File > /etc/runit/3.d/99-postgres  chmod: +x  chown:
I, [2023-01-26T14:16:43.172547 #1]  INFO -- : File > /root/upgrade_postgres  chmod: +x  chown:
I, [2023-01-26T14:16:43.173176 #1]  INFO -- : > chown -R root /var/lib/postgresql/13/main
I, [2023-01-26T14:16:45.254384 #1]  INFO -- :
I, [2023-01-26T14:16:45.255332 #1]  INFO -- : > [ ! -e /shared/postgres_data ] && install -d -m 0755 -o postgres -g postgres /shared/postgres_data && sudo -E -u postgres /usr/lib/postgresql/13/bin/initdb -D /shared/postgres_data || exit 0
I, [2023-01-26T14:16:45.258797 #1]  INFO -- :
I, [2023-01-26T14:16:45.259262 #1]  INFO -- : > chown -R postgres:postgres /shared/postgres_data
I, [2023-01-26T14:16:45.343383 #1]  INFO -- :
I, [2023-01-26T14:16:45.344327 #1]  INFO -- : > chown -R postgres:postgres /var/run/postgresql
I, [2023-01-26T14:16:45.348139 #1]  INFO -- :
I, [2023-01-26T14:16:45.348746 #1]  INFO -- : > /root/upgrade_postgres
I, [2023-01-26T14:16:45.360582 #1]  INFO -- :
I, [2023-01-26T14:16:45.361157 #1]  INFO -- : > rm /root/upgrade_postgres
I, [2023-01-26T14:16:45.363919 #1]  INFO -- :
I, [2023-01-26T14:16:45.365619 #1]  INFO -- : Replacing data_directory = '/var/lib/postgresql/13/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.366828 #1]  INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.367748 #1]  INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.368827 #1]  INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.369798 #1]  INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.370814 #1]  INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.371443 #1]  INFO -- : > install -d -m 0755 -o postgres -g postgres /shared/postgres_backup
I, [2023-01-26T14:16:45.378215 #1]  INFO -- :
I, [2023-01-26T14:16:45.378959 #1]  INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.379628 #1]  INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.380253 #1]  INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-26T14:16:45.381456 #1]  INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres  peer in /etc/postgresql/13/main/pg_hba.conf
I, [2023-01-26T14:16:45.382114 #1]  INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/13/main/pg_hba.conf
I, [2023-01-26T14:16:45.382760 #1]  INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/13/main/pg_hba.conf
I, [2023-01-26T14:16:45.383330 #1]  INFO -- : > HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main
I, [2023-01-26T14:16:45.385445 #1]  INFO -- : > sleep 5
2023-01-26 14:16:45.563 UTC [41] LOG:  starting PostgreSQL 13.9 (Debian 13.9-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-01-26 14:16:45.563 UTC [41] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-01-26 14:16:45.563 UTC [41] LOG:  listening on IPv6 address "::", port 5432
2023-01-26 14:16:45.565 UTC [41] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-01-26 14:16:45.571 UTC [44] LOG:  database system was shut down at 2023-01-26 14:06:07 UTC
2023-01-26 14:16:45.587 UTC [41] LOG:  database system is ready to accept connections
I, [2023-01-26T14:16:50.393555 #1]  INFO -- :
I, [2023-01-26T14:16:50.394596 #1]  INFO -- : > su postgres -c 'createdb discourse' || true
2023-01-26 14:16:50.508 UTC [54] postgres@postgres ERROR:  database "discourse" already exists
2023-01-26 14:16:50.508 UTC [54] postgres@postgres STATEMENT:  CREATE DATABASE discourse;
createdb: error: database creation failed: ERROR:  database "discourse" already exists
I, [2023-01-26T14:16:50.512245 #1]  INFO -- :
I, [2023-01-26T14:16:50.512797 #1]  INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
2023-01-26 14:16:50.602 UTC [58] postgres@discourse ERROR:  role "discourse" already exists
2023-01-26 14:16:50.602 UTC [58] postgres@discourse STATEMENT:  create user discourse;
ERROR:  role "discourse" already exists
I, [2023-01-26T14:16:50.605342 #1]  INFO -- :
I, [2023-01-26T14:16:50.605962 #1]  INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true
I, [2023-01-26T14:16:50.670186 #1]  INFO -- : GRANT

I, [2023-01-26T14:16:50.670972 #1]  INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"'
I, [2023-01-26T14:16:50.734661 #1]  INFO -- : ALTER SCHEMA

I, [2023-01-26T14:16:50.735409 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2023-01-26T14:16:50.812257 #1]  INFO -- : CREATE EXTENSION

I, [2023-01-26T14:16:50.812793 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists pg_trgm;"'
NOTICE:  extension "pg_trgm" already exists, skipping
I, [2023-01-26T14:16:50.877976 #1]  INFO -- : CREATE EXTENSION

I, [2023-01-26T14:16:50.878554 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2023-01-26T14:16:50.941782 #1]  INFO -- : CREATE EXTENSION

I, [2023-01-26T14:16:50.942340 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists pg_trgm;"'
NOTICE:  extension "pg_trgm" already exists, skipping
I, [2023-01-26T14:16:51.005198 #1]  INFO -- : CREATE EXTENSION

I, [2023-01-26T14:16:51.005792 #1]  INFO -- : > sudo -u postgres psql discourse
I, [2023-01-26T14:16:51.011746 #1]  INFO -- : update pg_database set encoding = pg_char_to_encoding('UTF8') where datname = 'discourse' AND encoding = pg_char_to_encoding('SQL_ASCII');

I, [2023-01-26T14:16:51.109604 #1]  INFO -- : File > /var/lib/postgresql/take-database-backup  chmod: +x  chown: postgres:postgres
I, [2023-01-26T14:16:51.113750 #1]  INFO -- : File > /var/spool/cron/crontabs/postgres  chmod:   chown:
I, [2023-01-26T14:16:51.114275 #1]  INFO -- : > echo postgres installed!
I, [2023-01-26T14:16:51.117142 #1]  INFO -- : postgres installed!

I, [2023-01-26T14:16:51.123996 #1]  INFO -- : File > /etc/service/redis/run  chmod: +x  chown:
I, [2023-01-26T14:16:51.130514 #1]  INFO -- : File > /etc/service/redis/log/run  chmod: +x  chown:
I, [2023-01-26T14:16:51.136804 #1]  INFO -- : File > /etc/runit/3.d/10-redis  chmod: +x  chown:
I, [2023-01-26T14:16:51.138417 #1]  INFO -- : Replacing daemonize yes with  in /etc/redis/redis.conf
I, [2023-01-26T14:16:51.139445 #1]  INFO -- : Replacing (?-mix:^pidfile.*$) with  in /etc/redis/redis.conf
I, [2023-01-26T14:16:51.140250 #1]  INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data
I, [2023-01-26T14:16:51.143826 #1]  INFO -- :
I, [2023-01-26T14:16:51.144887 #1]  INFO -- : Replacing (?-mix:^logfile.*$) with logfile "" in /etc/redis/redis.conf
I, [2023-01-26T14:16:51.145784 #1]  INFO -- : Replacing (?-mix:^bind .*$) with  in /etc/redis/redis.conf
I, [2023-01-26T14:16:51.146637 #1]  INFO -- : Replacing (?-mix:^dir .*$) with dir /shared/redis_data in /etc/redis/redis.conf
I, [2023-01-26T14:16:51.147505 #1]  INFO -- : Replacing (?-mix:^protected-mode yes) with protected-mode no in /etc/redis/redis.conf
I, [2023-01-26T14:16:51.148380 #1]  INFO -- : Replacing # io-threads 4 with io-threads $redis_io_threads in /etc/redis/redis.conf
I, [2023-01-26T14:16:51.149227 #1]  INFO -- : > echo redis installed
I, [2023-01-26T14:16:51.152638 #1]  INFO -- : redis installed

I, [2023-01-26T14:16:51.153323 #1]  INFO -- : > cat /etc/redis/redis.conf | grep logfile
I, [2023-01-26T14:16:51.160679 #1]  INFO -- : logfile ""

I, [2023-01-26T14:16:51.161294 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-01-26T14:16:51.163540 #1]  INFO -- : > sleep 10
102:C 26 Jan 2023 14:16:51.201 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
102:C 26 Jan 2023 14:16:51.202 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=102, just started
102:C 26 Jan 2023 14:16:51.202 # Configuration loaded
102:M 26 Jan 2023 14:16:51.203 * monotonic clock: POSIX clock_gettime
102:M 26 Jan 2023 14:16:51.206 * Running mode=standalone, port=6379.
102:M 26 Jan 2023 14:16:51.206 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
102:M 26 Jan 2023 14:16:51.206 # Server initialized
102:M 26 Jan 2023 14:16:51.207 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
102:M 26 Jan 2023 14:16:51.208 * Loading RDB produced by version 7.0.7
102:M 26 Jan 2023 14:16:51.209 * RDB age 644 seconds
102:M 26 Jan 2023 14:16:51.209 * RDB memory usage when created 12.19 Mb
102:M 26 Jan 2023 14:16:51.245 * Done loading RDB, keys loaded: 3408, keys expired: 0.
102:M 26 Jan 2023 14:16:51.246 * DB loaded from disk: 0.038 seconds
102:M 26 Jan 2023 14:16:51.246 * Ready to accept connections
I, [2023-01-26T14:17:01.170067 #1]  INFO -- :
I, [2023-01-26T14:17:01.170872 #1]  INFO -- : > thpoff echo "thpoff is installed!"
I, [2023-01-26T14:17:01.176533 #1]  INFO -- : thpoff is installed!

I, [2023-01-26T14:17:01.177175 #1]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_SMTP_ADDRESS"] == "smtp.example.com"; puts "Aborting! Mail is not configured!"; exit 1; end'
I, [2023-01-26T14:17:01.277567 #1]  INFO -- :
I, [2023-01-26T14:17:01.278425 #1]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_HOSTNAME"] == "discourse.example.com"; puts "Aborting! Domain is not configured!"; exit 1; end'
I, [2023-01-26T14:17:01.382541 #1]  INFO -- :
I, [2023-01-26T14:17:01.383358 #1]  INFO -- : > /usr/local/bin/ruby -e 'if (ENV["DISCOURSE_CDN_URL"] || "")[0..1] == "//"; puts "Aborting! CDN must have a protocol specified. Once fixed you should rebake your posts now to correct all posts."; exit 1; end'
I, [2023-01-26T14:17:01.483297 #1]  INFO -- :
I, [2023-01-26T14:17:01.484111 #1]  INFO -- : > rm -f /etc/cron.d/anacron
I, [2023-01-26T14:17:01.488073 #1]  INFO -- :
I, [2023-01-26T14:17:01.491949 #1]  INFO -- : File > /etc/cron.d/anacron  chmod:   chown:
I, [2023-01-26T14:17:01.498386 #1]  INFO -- : File > /etc/runit/1.d/copy-env  chmod: +x  chown:
I, [2023-01-26T14:17:01.504731 #1]  INFO -- : File > /etc/service/unicorn/run  chmod: +x  chown:
I, [2023-01-26T14:17:01.512218 #1]  INFO -- : File > /etc/service/nginx/run  chmod: +x  chown:
I, [2023-01-26T14:17:01.519133 #1]  INFO -- : File > /etc/runit/3.d/01-nginx  chmod: +x  chown:
I, [2023-01-26T14:17:01.526329 #1]  INFO -- : File > /etc/runit/3.d/02-unicorn  chmod: +x  chown:
I, [2023-01-26T14:17:01.526989 #1]  INFO -- : Replacing # postgres with sv start postgres || exit 1 in /etc/service/unicorn/run
I, [2023-01-26T14:17:01.527634 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-01-26T14:17:01.531006 #1]  INFO -- : > cd /var/www/discourse && git reset --hard
129:C 26 Jan 2023 14:17:01.543 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
129:C 26 Jan 2023 14:17:01.543 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=129, just started
129:C 26 Jan 2023 14:17:01.544 # Configuration loaded
129:M 26 Jan 2023 14:17:01.545 * monotonic clock: POSIX clock_gettime
129:M 26 Jan 2023 14:17:01.546 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
129:M 26 Jan 2023 14:17:01.546 # Failed listening on port 6379 (TCP), aborting.
Updating files: 100% (32677/32677), done.
I, [2023-01-26T14:17:05.780430 #1]  INFO -- : HEAD is now at 2eb0a300 FIX: Use hashtags in channel archive PMs if available (#19859)

I, [2023-01-26T14:17:05.781165 #1]  INFO -- : > cd /var/www/discourse && git clean -f
I, [2023-01-26T14:17:05.942875 #1]  INFO -- :
I, [2023-01-26T14:17:05.943538 #1]  INFO -- : > cd /var/www/discourse && git remote set-branches --add origin main
I, [2023-01-26T14:17:05.948859 #1]  INFO -- :
I, [2023-01-26T14:17:05.949320 #1]  INFO -- : > cd /var/www/discourse && git remote set-branches origin tests-passed
I, [2023-01-26T14:17:05.953818 #1]  INFO -- :
I, [2023-01-26T14:17:05.954262 #1]  INFO -- : > cd /var/www/discourse && git fetch --depth 1 origin tests-passed
From https://github.com/discourse/discourse
 * branch              tests-passed -> FETCH_HEAD
 * [new branch]        tests-passed -> origin/tests-passed
I, [2023-01-26T14:17:09.308486 #1]  INFO -- :
I, [2023-01-26T14:17:09.309026 #1]  INFO -- : > cd /var/www/discourse && git checkout tests-passed
Switched to a new branch 'tests-passed'
I, [2023-01-26T14:17:10.275650 #1]  INFO -- : Branch 'tests-passed' set up to track remote branch 'tests-passed' from 'origin'.

I, [2023-01-26T14:17:10.276151 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp
I, [2023-01-26T14:17:10.285317 #1]  INFO -- :
I, [2023-01-26T14:17:10.285801 #1]  INFO -- : > cd /var/www/discourse && chown discourse:www-data tmp
I, [2023-01-26T14:17:10.289734 #1]  INFO -- :
I, [2023-01-26T14:17:10.290191 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2023-01-26T14:17:10.294127 #1]  INFO -- :
I, [2023-01-26T14:17:10.294540 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2023-01-26T14:17:10.298287 #1]  INFO -- :
I, [2023-01-26T14:17:10.298686 #1]  INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2023-01-26T14:17:10.304050 #1]  INFO -- :
I, [2023-01-26T14:17:10.304469 #1]  INFO -- : > cd /var/www/discourse && mkdir -p                    /shared/log/rails
I, [2023-01-26T14:17:10.308280 #1]  INFO -- :
I, [2023-01-26T14:17:10.308667 #1]  INFO -- : > cd /var/www/discourse && bash -c "touch -a           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log"
I, [2023-01-26T14:17:10.315784 #1]  INFO -- :
I, [2023-01-26T14:17:10.316235 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log /var/www/discourse/log"
I, [2023-01-26T14:17:10.322160 #1]  INFO -- :
I, [2023-01-26T14:17:10.322614 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/{uploads,backups}"
I, [2023-01-26T14:17:10.328696 #1]  INFO -- :
I, [2023-01-26T14:17:10.329194 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/{uploads,backups} /var/www/discourse/public"
I, [2023-01-26T14:17:10.334736 #1]  INFO -- :
I, [2023-01-26T14:17:10.335218 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/tmp/{backups,restores}"
I, [2023-01-26T14:17:10.341853 #1]  INFO -- :
I, [2023-01-26T14:17:10.342296 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/tmp/{backups,restores} /var/www/discourse/tmp"
I, [2023-01-26T14:17:10.347822 #1]  INFO -- :
I, [2023-01-26T14:17:10.348217 #1]  INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp
I, [2023-01-26T14:17:10.506857 #1]  INFO -- :
I, [2023-01-26T14:17:10.507552 #1]  INFO -- : > cd /var/www/discourse && [ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete
I, [2023-01-26T14:17:10.515484 #1]  INFO -- :
I, [2023-01-26T14:17:10.516048 #1]  INFO -- : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run
I, [2023-01-26T14:17:10.517020 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2023-01-26T14:17:12.849641 #1]  INFO -- :
I, [2023-01-26T14:17:12.850307 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/procourse/discourse-multiselect-user-field.git
Cloning into 'discourse-multiselect-user-field'...
I, [2023-01-26T14:17:13.757414 #1]  INFO -- :
I, [2023-01-26T14:17:13.758052 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-data-explorer.git
Cloning into 'discourse-data-explorer'...
I, [2023-01-26T14:17:15.303902 #1]  INFO -- :
I, [2023-01-26T14:17:15.304622 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-bbcode.git
Cloning into 'discourse-bbcode'...
I, [2023-01-26T14:17:16.240885 #1]  INFO -- :
I, [2023-01-26T14:17:16.241615 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-adplugin.git
Cloning into 'discourse-adplugin'...
I, [2023-01-26T14:17:17.381679 #1]  INFO -- :
I, [2023-01-26T14:17:17.382323 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/pmusaraj/discourse-jitsi.git
Cloning into 'discourse-jitsi'...
I, [2023-01-26T14:17:18.544561 #1]  INFO -- :
I, [2023-01-26T14:17:18.545254 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/rimian/discourse-subscriptions.git
Cloning into 'discourse-subscriptions'...
I, [2023-01-26T14:17:19.802643 #1]  INFO -- :
I, [2023-01-26T14:17:19.803401 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/Discourse-nav-links-component.git
Cloning into 'Discourse-nav-links-component'...
I, [2023-01-26T14:17:20.738239 #1]  INFO -- :
I, [2023-01-26T14:17:20.738889 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/procourse/procourse-static-pages.git
Cloning into 'procourse-static-pages'...
I, [2023-01-26T14:17:21.673095 #1]  INFO -- :
I, [2023-01-26T14:17:21.673965 #1]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2023-01-26T14:17:21.684929 #1]  INFO -- :
I, [2023-01-26T14:17:21.686516 #1]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2023-01-26T14:17:21.689612 #1]  INFO -- :
I, [2023-01-26T14:17:21.690150 #1]  INFO -- : > mkdir -p /var/nginx/cache
I, [2023-01-26T14:17:21.693449 #1]  INFO -- :
I, [2023-01-26T14:17:21.694459 #1]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2023-01-26T14:17:21.695165 #1]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2023-01-26T14:17:21.695758 #1]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2023-01-26T14:17:21.696412 #1]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2023-01-26T14:17:21.697058 #1]  INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2023-01-26T14:17:21.697582 #1]  INFO -- : > echo "done configuring web"
I, [2023-01-26T14:17:21.700406 #1]  INFO -- : done configuring web

I, [2023-01-26T14:17:21.701140 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
I, [2023-01-26T14:17:22.828640 #1]  INFO -- : Successfully installed bundler-2.4.1
1 gem installed

I, [2023-01-26T14:17:22.829302 #1]  INFO -- : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+
I, [2023-01-26T14:17:26.445446 #1]  INFO -- :
I, [2023-01-26T14:17:26.446315 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --production --frozen-lockfile && yarn cache clean'
warning " > @mixer/parallel-prettier@2.0.3" has unmet peer dependency "prettier@^2.0.0".
warning "eslint-config-discourse > eslint-plugin-lodash@7.1.0" has unmet peer dependency "lodash@>=4".
I, [2023-01-26T14:19:08.637257 #1]  INFO -- : yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
$ yarn --cwd app/assets/javascripts/discourse $(node -e 'if(JSON.parse(process.env.npm_config_argv).original.includes(`--frozen-lockfile`)){console.log(`--frozen-lockfile`)}')
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 58.21s.
Done in 91.62s.
yarn cache v1.22.19
success Cleared cache.
Done in 9.77s.

Ocorreu um erro na minha atualização

```ruby
api_key = "a quick brown fox"
fetch("https://api.example.com/data", headers: { 'Authorization' => api_key })

Por favor, me ajude a corrigi-lo..
Instalando erubi 1.12.0
Instalando rack 2.2.6.2
3: erubi (1.12.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/erubi-1.12.0.gemspec
Usando timeout 0.3.1
3: timeout (0.3.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/timeout-0.3.1.gemspec
Usando public_suffix 5.0.1
3: public_suffix (5.0.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/public_suffix-5.0.1.gemspec
Usando aws-eventstream 1.2.0
3: aws-eventstream (1.2.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/aws-eventstream-1.2.0.gemspec
Usando aws-partitions 1.583.0
3: aws-partitions (1.583.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/aws-partitions-1.583.0.gemspec
Usando jmespath 1.6.2
3: jmespath (1.6.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/jmespath-1.6.2.gemspec
Usando msgpack 1.6.0
3: msgpack (1.6.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/msgpack-1.6.0.gemspec
Usando bundler 2.4.1
3: bundler (2.4.1) de /usr/local/lib/ruby/gems/3.1.0/specifications/bundler-2.4.1.gemspec
Usando byebug 11.1.3
3: byebug (11.1.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/byebug-11.1.3.gemspec
Usando cbor 0.5.9.6
3: cbor (0.5.9.6) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/cbor-0.5.9.6.gemspec
Usando cgi 0.3.6
3: cgi (0.3.6) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/cgi-0.3.6.gemspec
Usando chunky_png 1.4.0
3: chunky_png (1.4.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/chunky_png-1.4.0.gemspec
Usando coderay 1.1.3
3: coderay (1.1.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/coderay-1.1.3.gemspec
Usando colored2 3.1.2
3: colored2 (3.1.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/colored2-3.1.2.gemspec
Usando connection_pool 2.3.0
3: connection_pool (2.3.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/connection_pool-2.3.0.gemspec
Usando openssl 3.0.2
3: openssl (3.0.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/openssl-3.0.2.gemspec
Usando cppjieba_rb 0.4.2
3: cppjieba_rb (0.4.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/cppjieba_rb-0.4.2.gemspec
Usando diffy 3.4.2
3: diffy (3.4.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/diffy-3.4.2.gemspec
Usando digest 3.1.1
3: digest (3.1.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/digest-3.1.1.gemspec
Usando discourse-fonts 0.0.9
3: discourse-fonts (0.0.9) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/discourse-fonts-0.0.9.gemspec
Buscando regexp_parser 2.6.2
Instalando regexp_parser 2.6.2
2: rack (2.2.6.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rack-2.2.6.2.gemspec
Usando email_reply_trimmer 0.1.13
2: email_reply_trimmer (0.1.13) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/email_reply_trimmer-0.1.13.gemspec
Buscando excon 0.97.2
3: regexp_parser (2.6.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/regexp_parser-2.6.2.gemspec
Usando execjs 2.8.1
3: execjs (2.8.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/execjs-2.8.1.gemspec
Usando exifr 1.3.10
3: exifr (1.3.10) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/exifr-1.3.10.gemspec
Usando faraday-net_http 3.0.2
3: faraday-net_http (3.0.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/faraday-net_http-3.0.2.gemspec
Usando ruby2_keywords 0.0.5
3: ruby2_keywords (0.0.5) de /usr/local/lib/ruby/gems/3.1.0/specifications/default/ruby2_keywords-0.0.5.gemspec
Usando fast_blank 1.0.1
3: fast_blank (1.0.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/fast_blank-1.0.1.gemspec
Usando fast_xs 0.8.0
3: fast_xs (0.8.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/fast_xs-0.8.0.gemspec
Usando fastimage 2.2.6
3: fastimage (2.2.6) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/fastimage-2.2.6.gemspec
Usando ffi 1.15.5
3: ffi (1.15.5) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/ffi-1.15.5.gemspec
Usando fspath 3.1.2
3: fspath (3.1.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/fspath-3.1.2.gemspec
Usando gc_tracer 1.5.1
3: gc_tracer (1.5.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/gc_tracer-1.5.1.gemspec
Usando guess_html_encoding 0.0.11
3: guess_html_encoding (0.0.11) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/guess_html_encoding-0.0.11.gemspec
Usando hana 1.3.7
3: hana (1.3.7) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/hana-1.3.7.gemspec
Usando hashie 5.0.0
3: hashie (5.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/hashie-5.0.0.gemspec
Usando highline 2.1.0
3: highline (2.1.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/highline-2.1.0.gemspec
Usando hkdf 1.0.0
3: hkdf (1.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/hkdf-1.0.0.gemspec
Usando htmlentities 4.3.4
3: htmlentities (4.3.4) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/htmlentities-4.3.4.gemspec
Usando http_accept_language 2.1.1
3: http_accept_language (2.1.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/http_accept_language-2.1.1.gemspec
Usando image_size 3.2.0
3: image_size (3.2.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/image_size-3.2.0.gemspec
Usando in_threads 1.6.0
3: in_threads (1.6.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/in_threads-1.6.0.gemspec
Usando progress 3.6.0
3: progress (3.6.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/progress-3.6.0.gemspec
Usando json 2.6.3
3: json (2.6.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/json-2.6.3.gemspec
Usando uri_template 0.7.0
3: uri_template (0.7.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/uri_template-0.7.0.gemspec
Usando jwt 2.6.0
3: jwt (2.6.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/jwt-2.6.0.gemspec
Usando kgio 2.11.4
3: kgio (2.11.4) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/kgio-2.11.4.gemspec
Usando libv8-node 16.10.0.0 (x86_64-linux)
3: libv8-node (16.10.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/libv8-node-16.10.0.0-x86_64-linux.gemspec
Usando method_source 1.0.0
3: method_source (1.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/method_source-1.0.0.gemspec
Usando thor 1.2.1
3: thor (1.2.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/thor-1.2.1.gemspec
Usando zeitwerk 2.6.6
3: zeitwerk (2.6.6) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/zeitwerk-2.6.6.gemspec
Usando logstash-event 1.2.02
3: logstash-event (1.2.02) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/logstash-event-1.2.02.gemspec
Usando logster 2.11.3
3: logster (2.11.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/logster-2.11.3.gemspec
Usando lru_redux 1.1.0
3: lru_redux (1.1.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/lru_redux-1.1.0.gemspec
Usando lz4-ruby 0.3.3
3: lz4-ruby (0.3.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/lz4-ruby-0.3.3.gemspec
Usando maxminddb 0.1.22
3: maxminddb (0.1.22) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/maxminddb-0.1.22.gemspec
Usando memory_profiler 1.0.1
3: memory_profiler (1.0.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/memory_profiler-1.0.1.gemspec
Usando redis 4.8.0
3: redis (4.8.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/redis-4.8.0.gemspec
Usando mini_sql 1.4.0
3: mini_sql (1.4.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/mini_sql-1.4.0.gemspec
Usando multi_json 1.15.0
3: multi_json (1.15.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/multi_json-1.15.0.gemspec
Usando multi_xml 0.6.0
3: multi_xml (0.6.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/multi_xml-0.6.0.gemspec
Usando mustache 1.1.1
3: mustache (1.1.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/mustache-1.1.1.gemspec
Usando uri 0.12.0
3: uri (0.12.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/uri-0.12.0.gemspec
Usando nio4r 2.5.8
3: nio4r (2.5.8) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/nio4r-2.5.8.gemspec
Usando version_gem 1.1.1
3: version_gem (1.1.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/version_gem-1.1.1.gemspec
Usando oj 3.13.14
3: oj (3.13.14) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/oj-3.13.14.gemspec
Usando optimist 3.0.1
3: optimist (3.0.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/optimist-3.0.1.gemspec
Usando pg 1.4.5
3: pg (1.4.5) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/pg-1.4.5.gemspec
Usando r2 0.2.7
0: concurrent-ruby (1.2.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/concurrent-ruby-1.2.0.gemspec
3: r2 (0.2.7) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/r2-0.2.7.gemspec
Usando raindrops 0.20.0
3: raindrops (0.20.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/raindrops-0.20.0.gemspec
Usando rchardet 1.8.0
3: rchardet (1.8.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rchardet-1.8.0.gemspec
Usando rexml 3.2.5
3: rexml (3.2.5) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rexml-3.2.5.gemspec
Usando rinku 2.0.6
3: rinku (2.0.6) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rinku-2.0.6.gemspec
Usando rotp 6.2.2
3: rotp (6.2.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rotp-6.2.2.gemspec
Usando rqrcode_core 1.2.0
3: rqrcode_core (1.2.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rqrcode_core-1.2.0.gemspec
Usando rubyzip 2.3.2
3: rubyzip (2.3.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rubyzip-2.3.2.gemspec
Usando tilt 2.0.11
3: tilt (2.0.11) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/tilt-2.0.11.gemspec
Usando sshkey 2.0.0
3: sshkey (2.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/sshkey-2.0.0.gemspec
Usando stackprof 0.2.23
3: stackprof (0.2.23) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/stackprof-0.2.23.gemspec
Usando unf_ext 0.0.8.2
3: unf_ext (0.0.8.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/unf_ext-0.0.8.2.gemspec
Usando webrick 1.7.0
3: webrick (1.7.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/webrick-1.7.0.gemspec
Usando xorcist 1.1.3
3: xorcist (1.1.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/xorcist-1.1.3.gemspec
Usando nokogiri 1.14.0 (x86_64-linux)
3: nokogiri (1.14.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/nokogiri-1.14.0-x86_64-linux.gemspec
Usando net-protocol 0.2.1
0: net-protocol (0.2.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/net-protocol-0.2.1.gemspec
Usando addressable 2.8.1
0: addressable (2.8.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/addressable-2.8.1.gemspec
Usando aws-sigv4 1.5.0
0: aws-sigv4 (1.5.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/aws-sigv4-1.5.0.gemspec
Usando bootsnap 1.15.0
0: bootsnap (1.15.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/bootsnap-1.15.0.gemspec
Usando openssl-signature_algorithm 1.2.1
0: openssl-signature_algorithm (1.2.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/openssl-signature_algorithm-1.2.1.gemspec
Usando rack-test 2.0.2
0: rack-test (2.0.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rack-test-2.0.2.gemspec
Usando request_store 1.5.1
0: request_store (1.5.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/request_store-1.5.1.gemspec
Usando message_bus 4.3.2
0: message_bus (4.3.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/message_bus-4.3.2.gemspec
Usando rack-mini-profiler 3.0.0
0: rack-mini-profiler (3.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rack-mini-profiler-3.0.0.gemspec
Usando rack-protection 3.0.5
0: rack-protection (3.0.5) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rack-protection-3.0.5.gemspec
Usando ecma-re-validator 0.4.0
0: ecma-re-validator (0.4.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/ecma-re-validator-0.4.0.gemspec
Buscando faraday 2.7.4
Instalando excon 0.97.2
Instalando faraday 2.7.4
Usando mail 2.8.0.edge de GitHub - discourse/mail: A Really Ruby Mail Library · GitHub (em main@5b700fc)
3: mail (2.8.0.edge) de /var/www/discourse/vendor/bundle/ruby/3.1.0/bundler/gems/mail-5b700fc95ee6/mail.gemspec
Usando mini_suffix 0.3.3
3: mini_suffix (0.3.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/mini_suffix-0.3.3.gemspec
Usando sassc 2.0.1
3: sassc (2.0.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/sassc-2.0.1.gemspec
Usando uglifier 4.2.0
3: uglifier (4.2.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/uglifier-4.2.0.gemspec
Usando image_optim 0.31.2
3: image_optim (0.31.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/image_optim-0.31.2.gemspec
Usando logstash-logger 0.26.1
3: logstash-logger (0.26.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/logstash-logger-0.26.1.gemspec
Usando mini_racer 0.6.3
3: mini_racer (0.6.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/mini_racer-0.6.3.gemspec
Usando omniauth 1.9.2
3: omniauth (1.9.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/omniauth-1.9.2.gemspec
Usando pry 0.14.2
3: pry (0.14.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/pry-0.14.2.gemspec
Usando web-push 3.0.0
3: web-push (3.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/web-push-3.0.0.gemspec
Usando sidekiq 6.5.8
3: sidekiq (6.5.8) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/sidekiq-6.5.8.gemspec
Usando net-http 0.3.2
3: net-http (0.3.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/net-http-0.3.2.gemspec
Usando oauth-tty 1.0.5
3: oauth-tty (1.0.5) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/oauth-tty-1.0.5.gemspec
Usando snaky_hash 2.0.1
3: snaky_hash (2.0.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/snaky_hash-2.0.1.gemspec
Usando puma 6.0.2
3: puma (6.0.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/puma-6.0.2.gemspec
Usando rbtrace 0.4.14
3: rbtrace (0.4.14) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rbtrace-0.4.14.gemspec
Buscando redis-namespace 1.10.0
2: excon (0.97.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/excon-0.97.2.gemspec
Usando unicorn 6.1.0
2: unicorn (6.1.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/unicorn-6.1.0.gemspec
Usando i18n 1.12.0
2: i18n (1.12.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/i18n-1.12.0.gemspec
Usando tzinfo 2.0.5
2: tzinfo (2.0.5) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/tzinfo-2.0.5.gemspec
Usando loofah 2.19.1
2: loofah (2.19.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/loofah-2.19.1.gemspec
Usando net-pop 0.1.2
2: net-pop (0.1.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/net-pop-0.1.2.gemspec
Usando net-smtp 0.3.3
2: net-smtp (0.3.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/net-smtp-0.3.3.gemspec
Usando aws-sdk-core 3.130.2
2: aws-sdk-core (3.130.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/aws-sdk-core-3.130.2.gemspec
Usando cose 1.3.0
2: cose (1.3.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/cose-1.3.0.gemspec
Buscando css_parser 1.14.0
Instalando redis-namespace 1.10.0
3: redis-namespace (1.10.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/redis-namespace-1.10.0.gemspec
Instalando css_parser 1.14.0
Usando json_schemer 0.2.23
3: json_schemer (0.2.23) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/json_schemer-0.2.23.gemspec
Usando rqrcode 2.1.2
3: rqrcode (2.1.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rqrcode-2.1.2.gemspec
Usando rss 0.2.9
3: rss (0.2.9) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rss-0.2.9.gemspec
Usando ruby-readability 0.7.0
3: ruby-readability (0.7.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/ruby-readability-0.7.0.gemspec
Usando sanitize 6.0.0
3: sanitize (6.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/sanitize-6.0.0.gemspec
Usando sprockets 3.7.2 de GitHub - rails/sprockets: Rack-based asset packaging system · GitHub (em 3.x@f4d3dae)
0: faraday (2.7.4) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/faraday-2.7.4.gemspec
3: sprockets (3.7.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/bundler/gems/sprockets-f4d3dae71ef2/sprockets.gemspec
Usando unf 0.1.4
3: unf (0.1.4) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/unf-0.1.4.gemspec
Usando mini_scheduler 0.15.0
3: mini_scheduler (0.15.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/mini_scheduler-0.15.0.gemspec
Usando oauth 1.1.0
3: oauth (1.1.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/oauth-1.1.0.gemspec
Usando pry-byebug 3.10.1
3: pry-byebug (3.10.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/pry-byebug-3.10.1.gemspec
Usando pry-rails 0.3.9
3: pry-rails (0.3.9) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/pry-rails-0.3.9.gemspec
Buscando activesupport 7.0.4.1
Buscando rails-html-sanitizer 1.5.0
2: css_parser (1.14.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/css_parser-1.14.0.gemspec
Usando aws-sdk-kms 1.56.0
2: aws-sdk-kms (1.56.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/aws-sdk-kms-1.56.0.gemspec
Usando aws-sdk-sns 1.53.0
2: aws-sdk-sns (1.53.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/aws-sdk-sns-1.53.0.gemspec
Usando aws-sdk-s3 1.114.0
2: aws-sdk-s3 (1.114.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/aws-sdk-s3-1.114.0.gemspec
Usando faraday-retry 2.0.0
2: faraday-retry (2.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/faraday-retry-2.0.0.gemspec
Usando oauth2 1.4.11
2: oauth2 (1.4.11) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/oauth2-1.4.11.gemspec
Usando omniauth-oauth 1.2.0
2: omniauth-oauth (1.2.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/omniauth-oauth-1.2.0.gemspec
Usando omniauth-oauth2 1.7.3
2: omniauth-oauth2 (1.7.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/omniauth-oauth2-1.7.3.gemspec
Usando omniauth-twitter 1.4.0
2: omniauth-twitter (1.4.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/omniauth-twitter-1.4.0.gemspec
Usando omniauth-facebook 9.0.0
2: omniauth-facebook (9.0.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/omniauth-facebook-9.0.0.gemspec
Usando omniauth-github 1.4.0
2: omniauth-github (1.4.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/omniauth-github-1.4.0.gemspec
Usando omniauth-google-oauth2 0.8.2
2: omniauth-google-oauth2 (0.8.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/omniauth-google-oauth2-0.8.2.gemspec
Instalando rails-html-sanitizer 1.5.0
0: rails-html-sanitizer (1.5.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rails-html-sanitizer-1.5.0.gemspec
Instalando activesupport 7.0.4.1
3: activesupport (7.0.4.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/activesupport-7.0.4.1.gemspec
Usando rails-dom-testing 2.0.3
2: rails-dom-testing (2.0.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rails-dom-testing-2.0.3.gemspec
Buscando globalid 1.0.1
Buscando activemodel 7.0.4.1
Buscando actionview 7.0.4.1
Instalando globalid 1.0.1
Instalando activemodel 7.0.4.1
2: globalid (1.0.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/globalid-1.0.1.gemspec
Buscando activejob 7.0.4.1
Instalando actionview 7.0.4.1
Instalando activejob 7.0.4.1
0: activemodel (7.0.4.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/activemodel-7.0.4.1.gemspec
Usando active_model_serializers 0.8.4
0: active_model_serializers (0.8.4) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/active_model_serializers-0.8.4.gemspec
Buscando activerecord 7.0.4.1
2: activejob (7.0.4.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/activejob-7.0.4.1.gemspec
3: actionview (7.0.4.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/actionview-7.0.4.1.gemspec
Buscando actionpack 7.0.4.1
Usando actionview_precompiler 0.2.3
3: actionview_precompiler (0.2.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/actionview_precompiler-0.2.3.gemspec
Instalando activerecord 7.0.4.1
Instalando actionpack 7.0.4.1
2: actionpack (7.0.4.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/actionpack-7.0.4.1.gemspec
Buscando railties 7.0.4.1
Usando sprockets-rails 3.4.2
2: sprockets-rails (3.4.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/sprockets-rails-3.4.2.gemspec
Instalando railties 7.0.4.1
0: activerecord (7.0.4.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/activerecord-7.0.4.1.gemspec
Usando discourse-seed-fu 2.3.12
2: discourse-seed-fu (2.3.12) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/discourse-seed-fu-2.3.12.gemspec
3: railties (7.0.4.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/railties-7.0.4.1.gemspec
Usando lograge 0.12.0
0: lograge (0.12.0) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/lograge-0.12.0.gemspec
Usando rails_failover 0.8.1
0: rails_failover (0.8.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rails_failover-0.8.1.gemspec
Usando rails_multisite 4.0.1
0: rails_multisite (4.0.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/rails_multisite-4.0.1.gemspec
Usando sassc-rails 2.1.2
0: sassc-rails (2.1.2) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/sassc-rails-2.1.2.gemspec
1: date (3.3.3) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/date-3.3.3.gemspec
Buscando net-imap 0.3.4
Instalando net-imap 0.3.4
0: net-imap (0.3.4) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/net-imap-0.3.4.gemspec
Buscando actionmailer 7.0.4.1
Instalando actionmailer 7.0.4.1
2: actionmailer (7.0.4.1) de /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/actionmailer-7.0.4.1.gemspec
Bundle concluído! 135 dependências do Gemfile, 172 gems instaladas agora.
Gems nos grupos ‘test’ e ‘development’ não foram instaladas.
Gems em bundle são instaladas em ./vendor/bundle

I, [2023-01-26T14:19:26.723212 #1] INFO – : > cd /var/www/discourse && echo “gem ‘mysql2’” >> Gemfile
I, [2023-01-26T14:19:26.726719 #1] INFO – :
I, [2023-01-26T14:19:26.727030 #1] INFO – : > cd /var/www/discourse && apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev
W: Erro GPG: https://dl.yarnpkg.com/debian stable InRelease: As seguintes assinaturas eram inválidas: EXPKEYSIG 23E7166788B63E1E Yarn Packaging yarn@dan.cx
E: O repositório ‘https://dl.yarnpkg.com/debian stable InRelease’ não está assinado.
I, [2023-01-26T14:19:31.052733 #1] INFO – : Get:1 Index of /debian bullseye InRelease [116 kB]
Get:2 Index of /debian-security bullseye-security InRelease [48.4 kB]
Get:3 Index of /debian bullseye-updates InRelease [44.1 kB]
Get:4 Index of /debian bullseye-backports InRelease [49.0 kB]
Get:5 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
Get:6 Index of /debian bullseye/main amd64 Packages [8,183 kB]
Get:7 Index of /debian-security bullseye-security/main amd64 Packages [216 kB]
Get:8 Index of /pub/repos/apt/ bullseye-pgdg InRelease [91.7 kB]
Get:9 https://deb.nodesource.com/node_18.x bullseye InRelease [4,586 B]
Get:10 Index of /debian bullseye-updates/main amd64 Packages [14.6 kB]
Get:11 Index of /debian bullseye-backports/main amd64 Packages [384 kB]
Err:5 https://dl.yarnpkg.com/debian stable InRelease
As seguintes assinaturas eram inválidas: EXPKEYSIG 23E7166788B63E1E Yarn Packaging yarn@dan.cx
Get:12 Index of /pub/repos/apt/ bullseye-pgdg/main amd64 Packages [268 kB]
Get:13 https://deb.nodesource.com/node_18.x bullseye/main amd64 Packages [774 B]
Lendo lista de pacotes…

I, [2023-01-26T14:19:31.053724 #1] INFO – : Terminando processos assíncronos
I, [2023-01-26T14:19:31.054076 #1] INFO – : Enviando INT para HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 41
I, [2023-01-26T14:19:31.054459 #1] INFO – : Enviando TERM para exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 102
2023-01-26 14:19:31.054 UTC [41] LOG: recebido pedido de desligamento rápido
102:signal-handler (1674742771) Recebido SIGTERM agendando desligamento…
2023-01-26 14:19:31.059 UTC [41] LOG: abortando transações ativas
2023-01-26 14:19:31.066 UTC [41] LOG: trabalhador em segundo plano “logical replication launcher” (PID 50) saiu com código de saída 1
2023-01-26 14:19:31.067 UTC [45] LOG: desligando
2023-01-26 14:19:31.093 UTC [41] LOG: sistema de banco de dados desligado
102:M 26 Jan 2023 14:19:31.152 # Usuário solicitou desligamento…
102:M 26 Jan 2023 14:19:31.153 * Salvando o snapshot RDB final antes de sair.
102:M 26 Jan 2023 14:19:31.215 * Banco de dados salvo em disco
102:M 26 Jan 2023 14:19:31.215 # Redis está pronto para sair, tchau…

FALHOU

Pups::ExecError: cd /var/www/discourse && apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev falhou com retorno #<Process::Status: pid 488 exit 100>
Localização da falha: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn’
exec falhou com os parâmetros {“cd”=>“$home”, “cmd”=>[“echo "gem ‘mysql2’" >> Gemfile”, “apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev”, “su discourse -c ‘bundle config unset deployment’”, “su discourse -c ‘bundle install --no-deployment --path vendor/bundle --jobs 4 --without test development’”]}
bootstrap falhou com código de saída 100
** FALHA AO FAZER BOOTSTRAP ** por favor, role para cima e procure por mensagens de erro anteriores, pode haver mais de uma.
./discourse-doctor pode ajudar a diagnosticar o problema.
b40e566c2a5dd29d8d7253ab893b7bef0c937020615f7e0a24bd57e5b2ec99d3
root@nz:/var/discourse# ^C
root@nz:/var/discourse#

19

apt-get install -y libmariadb-dev

Isso parece ter sobrado de um modelo de importação. Eu tentaria remover esta linha do topo de app.yml

  - "templates/import/mysql-dep.template.yml"
20

Obrigado!

A reconstrução desta vez foi concluída sem erros, e agora consigo fazer login e logout perfeitamente!

Muito obrigado a todos - ajuda fantástica, muito apreciada!