Aggiornamento da 2.9.0 beta2 a beta4 fallito (il mio sito è inattivo)

Ciao, per favore aiutami a far rivivere il sito.

Log degli errori qui sotto. Ho provato a usare discourse-doctor ma non ha aiutato.

I, [2022-05-11T07:32:19.831848 #1]  INFO -- : cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
2022-05-11 07:32:24.341 UTC [2330] discourse@discourse ERROR:  permission denied to create extension "unaccent"
2022-05-11 07:32:24.341 UTC [2330] discourse@discourse HINT:  Must be superuser to create this extension.
2022-05-11 07:32:24.341 UTC [2330] discourse@discourse STATEMENT:  CREATE EXTENSION IF NOT EXISTS unaccent
rake aborted!
PG::InsufficientPrivilege: ERROR:  permission denied to create extension "unaccent"
HINT:  Must be superuser to create this extension.
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:110:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:110:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/mini_sql-1.4.0/lib/mini_sql/postgres/connection.rb:209:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/mini_sql-1.4.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `block in run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/mini_sql-1.4.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `block in with_lock'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/mini_sql-1.4.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `with_lock'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/mini_sql-1.4.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/mini_sql-1.4.0/lib/mini_sql/postgres/connection.rb:181:in `exec'
/var/www/discourse/lib/tasks/db.rake:218:in `block (3 levels) in <main>'
/var/www/discourse/lib/tasks/db.rake:218:in `each'
/var/www/discourse/lib/tasks/db.rake:218:in `block (2 levels) in <main>'
/var/www/discourse/lib/distributed_mutex.rb:33:in `block in synchronize'
/var/www/discourse/lib/distributed_mutex.rb:29:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:29:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:14:in `synchronize'
/var/www/discourse/lib/tasks/db.rake:210:in `block in <main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Tasks: TOP =&gt; db:migrate
(See full trace by running task with --trace)
I, [2022-05-11T07:32:24.370907 #1]  INFO -- :
I, [2022-05-11T07:32:24.371509 #1]  INFO -- : Terminating async processes
I, [2022-05-11T07:32:24.371622 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 1719
I, [2022-05-11T07:32:24.371705 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 1836
2022-05-11 07:32:24.371 UTC [1719] LOG:  received fast shutdown request
1836:signal-handler (1652254344) Received SIGTERM scheduling shutdown...
1836:M 11 May 2022 07:32:24.377 # User requested shutdown...
1836:M 11 May 2022 07:32:24.377 * Saving the final RDB snapshot before exiting.
2022-05-11 07:32:24.508 UTC [1719] LOG:  aborting any active transactions
2022-05-11 07:32:24.514 UTC [1719] LOG:  worker process: logical replication launcher (PID 1728) exited with exit code 1
2022-05-11 07:32:24.515 UTC [1723] LOG:  shutting down
2022-05-11 07:32:24.558 UTC [1719] LOG:  database system is shut down
1836:M 11 May 2022 07:32:30.043 * DB saved on disk
1836:M 11 May 2022 07:32:30.043 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse &amp;&amp; su discourse -c 'bundle exec rake db:migrate' failed with return #&lt;Process::Status: pid 2316 exit 1&gt;
Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
bootstrap failed with exit code 1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
8069e918f9bcb61fbf533bf8f8fd3247d5ba20f12e9a704344adf44453b73449
==================== END REBUILD LOG ====================
Failed to rebuild app.

Checking your domain name . . .

Connection to www.dastereo.ru succeeded.
You should probably remove any non-standard plugins and rebuild.
Attempting to restart existing container. . .
x86_64 arch detected.
WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml

starting up existing container
+ /usr/bin/docker start app
app
a35517feb14f        local_discourse/app   "/sbin/boot"        2 months ago        Up Less than a second   0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:2222->22/tcp   app
Restarted the container.


==================== PLUGINS ====================
          - git clone https://github.com/discourse/docker_manager.git
##        - git clone https://github.com/discourse/discourse-vk-auth.git
##        - git clone https://github.com/discourse/discourse-whos-online.git
##        - git clone https://github.com/discourse/discourse-reactions.git
##        - git clone https://github.com/discourse/discourse-categories-suppressed.git
##        - git clone https://github.com/jannolii/discourse-topic-trade-buttons.git
##        - git clone https://github.com/angusmcleod/discourse-topic-previews.git

WARNING:
You have what appear to be non-official plugins.
If you are having trouble, you should disable them and try rebuilding again.

See https://github.com/discourse/discourse/blob/main/lib/plugin/metadata.rb for the official list.

========================================
Discourse version at www.dastereo.ru: NOT FOUND
Discourse version at localhost: NOT FOUND


==================== MEMORY INFORMATION ====================
RAM (MB): 16434

              total       used       free     shared    buffers     cached
Mem:         16048      13261       2787          1       1256       7721
-/+ buffers/cache:       4283      11765
Swap:         2047         16       2031

==================== DISK SPACE CHECK ====================
---------- OS Disk Space ----------
Filesystem                 Size  Used Avail Use% Mounted on
/dev/disk/by-label/DOROOT  315G  225G   75G  76% /
/dev/disk/by-label/DOROOT  315G  225G   75G  76% /var/lib/docker/aufs
/dev/disk/by-label/DOROOT  315G  225G   75G  76% /
/dev/disk/by-label/DOROOT  315G  225G   75G  76% /var/lib/docker/plugins
/dev/disk/by-label/DOROOT  315G  225G   75G  76% /

==================== DISK INFORMATION ====================

WARNING: GPT (GUID Partition Table) detected on '/dev/vda'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sda doesn't contain a valid partition table

Disk /dev/vda: 343.6 GB, 343597383680 bytes
255 heads, 63 sectors/track, 41773 cylinders, total 671088640 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/vda1               1   671088639   335544319+  ee  GPT

Disk /dev/sda: 429.5 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders, total 838860800 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

==================== END DISK INFORMATION ====================

==================== MAIL TEST ====================
For a robust test, get an address from http://www.mail-tester.com/
Or just send a test message to yourself.
Email address for mail test? ('n' to skip) [dmitry.krasnoperov@gmail.com]: т
Sending mail to т. . .
unknown shorthand flag: 'w' in -w
See 'docker exec --help'.

Replacing: SMTP_PASSWORD
Replacing: LETSENCRYPT_ACCOUNT_EMAIL
Replacing: DEVELOPER_EMAILS
Replacing: DISCOURSE_DB_PASSWORD
Replacing: Sending mail to

==================== DONE! ====================
Would you like to serve a publicly available version of this file? (Y/n)n
Publicly available log not generated.

You can examine the output of this script with
LESS=-Ri less /tmp/discourse-debug.txt

BUT FIRST, make sure that you know the first three commands below!!!

Commands to know when viewing the file with the above command (called 'less'):
q              -- quit
/error&lt;ENTER&gt;  -- search for the word 'error'
n              -- search for the next occurrence
g              -- go to the beginning of the file
f              -- go forward a page
b              -- go back a page
G              -- go to the end of the file

Il tuo utente del database non dispone dei privilegi per installare estensioni.

Stai usando un postgres esterno? Potresti voler controllare i privilegi dell’utente del database.

Ciao,
Utilizzo PostgreSQL interno. Come posso verificare e correggere i privilegi dell’utente del database?

Hai apportato modifiche al tuo app.yml in passato per utilizzare una versione precedente di postgres?

Sì, non ho spazio libero per l’aggiornamento a PG12, quindi lo sostituisco con

templates:

  • “templates/postgres.10.template.yml”

Sì, è per questo che stai riscontrando problemi. Postgres 10 è troppo vecchio a questo punto.

Puoi avviare un nuovo server discourse e ripristinare un backup del tuo sito lì.

Se non hai rimosso l’immagine corrente. Il sito dovrebbe andare online con

./launcher start app

Non appena sarai in grado di accedere al sito, vorrai eseguire un backup completo e quindi ripristinarlo su un nuovo server che esegue l’ultima versione di discourse.

Dopo ./launcher start app

Ho ottenuto

Rilevata architettura x86_64.
ATTENZIONE: il file containers/app.yml è leggibile da chiunque. Puoi proteggere questo file eseguendo: chmod o-rwx containers/app.yml
a35517feb14f
Niente da fare, il tuo container è già stato avviato!

Ma il sito ora restituisce 502 Bad Gateway.

Ho il mio backup da-stereo-2022-05-10-090939-v20220215015538.sql (senza immagini) e ho il backup delle immagini separatamente. È sufficiente per avviare una nuova installazione?

Non è consigliato, ma potresti provarci.

OK, grazie!

Ma c’è un modo per correggere la mia installazione attuale?

A meno che tu non abbia abbastanza spazio sul server e sia disposto a dedicare del tempo a capire e aggiornare il server manualmente, non credo ci sia un modo per farlo.

Cosa intendi? Devo aggiornare a PG13? Ma il mio backup è di PG10.

Quanto spazio mi serve sul server?
E quale server devo aggiornare manualmente?

Non c’è un modo definito per farlo, dovrai agire in base ai problemi che riscontri durante l’aggiornamento.

Almeno 2 volte la dimensione dell’installazione corrente. Direi di avere almeno 3 volte lo spazio per assicurarti di non rimanere bloccato.

Dovrai iniziare con il processo standard di aggiornamento di postgres:

sostituisci il template di postgres 10 con il postgres.template.yml predefinito e poi prova a ricostruire. dato che hai abbastanza spazio sul tuo server, un aggiornamento del database dovrebbe essere eseguito automaticamente. segui le istruzioni sulla console.

Se l’aggiornamento fallisce, l’unica via d’uscita più semplice sarebbe ripristinare un backup di discourse su una nuova installazione.

Il processo generale è descritto in questo argomento: PostgreSQL 13 update

Puoi ripristinare un backup PG 10 su PG 13.

Hai bisogno di spazio sufficiente per ripristinare il tuo database? E poi dovrai usare rsync per trasferire i file manualmente, come descritto nel link “move to be server”.

Se per qualche motivo ami il vecchio server, potresti spostarlo sullo stesso server, dove faresti un’installazione pulita e poi ripristineresti il nuovo backup.

Per favore, prova a distribuire di nuovo il tuo sito. Dovrebbe funzionare correttamente. Ci scusiamo per l’inconveniente.

Il problema è che ci affidiamo ad alcune estensioni affinché alcune funzionalità funzionino e il tuo utente DB non dispone di privilegi sufficienti per abilitare le estensioni. Ho unito una correzione per mostrare un messaggio di errore quando ciò accade:

Grazie mille per l’aiuto!
Dopo aver ricostruito l’app, ho ottenuto gli stessi errori

stgresql.conf
I, [2022-05-11T14:06:36.779527 #1]  INFO -- : Sostituzione di (?-mix:#?log_min_duration_statement *=.*) con log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/10/main/postgresql.conf
I, [2022-05-11T14:06:36.779903 #1]  INFO -- : Sostituzione di (?-mix:^#local +replication +postgres +peer$) con local replication postgres  peer in /etc/postgresql/10/main/pg_hba.conf
I, [2022-05-11T14:06:36.780283 #1]  INFO -- : Sostituzione di (?-mix:^host.*all.*all.*127.*$) con host all all 0.0.0.0/0 md5 in /etc/postgresql/10/main/pg_hba.conf
I, [2022-05-11T14:06:36.780668 #1]  INFO -- : Sostituzione di (?-mix:^host.*all.*all.*::1\/128.*$) con host all all ::/0 md5 in /etc/postgresql/10/main/pg_hba.conf
I, [2022-05-11T14:06:36.781007 #1]  INFO -- : > HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main
I, [2022-05-11T14:06:36.783732 #1]  INFO -- : > sleep 5
2022-05-11 14:06:36.806 UTC [1711] LOG:  in ascolto sull'indirizzo IPv4 "0.0.0.0", porta 5432
2022-05-11 14:06:36.806 UTC [1711] LOG:  in ascolto sull'indirizzo IPv6 "::", porta 5432
2022-05-11 14:06:37.025 UTC [1711] LOG:  in ascolto sulla socket Unix "/var/run/postgresql/.s.PGSQL.5432"
2022-05-11 14:06:37.079 UTC [1714] LOG:  il sistema di database è stato arrestato il 2022-05-11 07:32:24 UTC
2022-05-11 14:06:37.088 UTC [1711] LOG:  il sistema di database è pronto ad accettare connessioni
I, [2022-05-11T14:06:41.787174 #1]  INFO -- :
I, [2022-05-11T14:06:41.788268 #1]  INFO -- : > su postgres -c 'createdb discourse' || true
2022-05-11 14:06:41.860 UTC [1724] postgres@postgres ERROR:  il database "discourse" esiste già
2022-05-11 14:06:41.860 UTC [1724] postgres@postgres STATEMENT:  CREATE DATABASE discourse;
createdb: creazione del database fallita: ERROR:  il database "discourse" esiste già
I, [2022-05-11T14:06:41.863507 #1]  INFO -- :
I, [2022-05-11T14:06:41.864434 #1]  INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
2022-05-11 14:06:41.942 UTC [1735] postgres@discourse ERROR:  il ruolo "discourse" esiste già
2022-05-11 14:06:41.942 UTC [1735] postgres@discourse STATEMENT:  create user discourse;
ERROR:  il ruolo "discourse" esiste già
I, [2022-05-11T14:06:41.944719 #1]  INFO -- :
I, [2022-05-11T14:06:41.945104 #1]  INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true
I, [2022-05-11T14:06:42.029108 #1]  INFO -- : GRANT

I, [2022-05-11T14:06:42.029645 #1]  INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"'
I, [2022-05-11T14:06:42.116003 #1]  INFO -- : ALTER SCHEMA

I, [2022-05-11T14:06:42.116626 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists hstore;"'
NOTICE:  l'estensione "hstore" esiste già, saltata
I, [2022-05-11T14:06:42.193405 #1]  INFO -- : CREATE EXTENSION

I, [2022-05-11T14:06:42.193820 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists pg_trgm;"'
NOTICE:  l'estensione "pg_trgm" esiste già, saltata
I, [2022-05-11T14:06:42.277646 #1]  INFO -- : CREATE EXTENSION

I, [2022-05-11T14:06:42.278076 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists hstore;"'
NOTICE:  l'estensione "hstore" esiste già, saltata
I, [2022-05-11T14:06:42.351783 #1]  INFO -- : CREATE EXTENSION

I, [2022-05-11T14:06:42.352644 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists pg_trgm;"'
NOTICE:  l'estensione "pg_trgm" esiste già, saltata
I, [2022-05-11T14:06:42.428638 #1]  INFO -- : CREATE EXTENSION

I, [2022-05-11T14:06:42.428966 #1]  INFO -- : > sudo -u postgres psql discourse
I, [2022-05-11T14:06:42.431512 #1]  INFO -- : update pg_database set encoding = pg_char_to_encoding('UTF8') where datname = 'discourse' AND encoding = pg_char_to_encoding('SQL_ASCII');

I, [2022-05-11T14:06:42.510669 #1]  INFO -- : File > /var/lib/postgresql/take-database-backup  chmod: +x  chown: postgres:postgres
I, [2022-05-11T14:06:42.515094 #1]  INFO -- : File > /var/spool/cron/crontabs/postgres  chmod:   chown:
I, [2022-05-11T14:06:42.515275 #1]  INFO -- : > echo postgres installed!
I, [2022-05-11T14:06:42.518311 #1]  INFO -- : postgres installed!

I, [2022-05-11T14:06:42.524709 #1]  INFO -- : File > /etc/service/redis/run  chmod: +x  chown:
I, [2022-05-11T14:06:42.532360 #1]  INFO -- : File > /etc/service/redis/log/run  chmod: +x  chown:
I, [2022-05-11T14:06:42.540851 #1]  INFO -- : File > /etc/runit/3.d/10-redis  chmod: +x  chown:
I, [2022-05-11T14:06:42.541113 #1]  INFO -- : Sostituzione di daemonize yes con  in /etc/redis/redis.conf
I, [2022-05-11T14:06:42.541730 #1]  INFO -- : Sostituzione di (?-mix:^pidfile.*$) con  in /etc/redis/redis.conf
I, [2022-05-11T14:06:42.543043 #1]  INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data
I, [2022-05-11T14:06:42.546574 #1]  INFO -- :
I, [2022-05-11T14:06:42.547153 #1]  INFO -- : Sostituzione di (?-mix:^logfile.*$) con logfile "" in /etc/redis/redis.conf
I, [2022-05-11T14:06:42.547651 #1]  INFO -- : Sostituzione di (?-mix:^bind .*$) con  in /etc/redis/redis.conf
I, [2022-05-11T14:06:42.548843 #1]  INFO -- : Sostituzione di (?-mix:^dir .*$) con dir /shared/redis_data in /etc/redis/redis.conf
I, [2022-05-11T14:06:42.549531 #1]  INFO -- : Sostituzione di (?-mix:^protected-mode yes) con protected-mode no in /etc/redis/redis.conf
I, [2022-05-11T14:06:42.550080 #1]  INFO -- : Sostituzione di # io-threads 4 con io-threads $redis_io_threads in /etc/redis/redis.conf
I, [2022-05-11T14:06:42.550748 #1]  INFO -- : > echo redis installed
I, [2022-05-11T14:06:42.554376 #1]  INFO -- : redis installed

I, [2022-05-11T14:06:42.554580 #1]  INFO -- : > cat /etc/redis/redis.conf | grep logfile
I, [2022-05-11T14:06:42.561563 #1]  INFO -- : logfile ""

I, [2022-05-11T14:06:42.562042 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2022-05-11T14:06:42.565971 #1]  INFO -- : > sleep 10
1828:C 11 Mag 2022 14:06:42.576 # oO0OoO0OoO0Oo Redis è in avvio oO0OoO0OoO0Oo
1828:C 11 Mag 2022 14:06:42.576 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=1828, appena avviato
1828:C 11 Mag 2022 14:06:42.576 # Configurazione caricata
1828:M 11 Mag 2022 14:06:42.577 * monotonic clock: POSIX clock_gettime
1828:M 11 Mag 2022 14:06:42.577 * Running mode=standalone, port=6379.
1828:M 11 Mag 2022 14:06:42.577 # WARNING: L'impostazione TCP backlog di 511 non può essere applicata perché /proc/sys/net/core/somaxconn è impostata sul valore inferiore di 128.
1828:M 11 Mag 2022 14:06:42.577 # Server inizializzato
1828:M 11 Mag 2022 14:06:42.577 # WARNING overcommit_memory è impostato a 0! Il salvataggio in background potrebbe fallire in condizioni di memoria bassa. Per risolvere questo problema aggiungi 'vm.overcommit_memory = 1' a /etc/sysctl.conf e poi riavvia o esegui il comando 'sysctl vm.overcommit_memory=1' affinché abbia effetto.
1828:M 11 Mag 2022 14:06:42.577 # WARNING hai il supporto Transparent Huge Pages (THP) abilitato nel tuo kernel. Questo creerà problemi di latenza e utilizzo della memoria con Redis. Per risolvere questo problema esegui il comando 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled' come root, e aggiungilo al tuo /etc/rc.local in modo da mantenere l'impostazione dopo un riavvio. Redis deve essere riavviato dopo che THP è disabilitato (impostato su 'madvise' o 'never').
1828:M 11 Mag 2022 14:06:42.578 * Caricamento RDB prodotto dalla versione 6.2.6
1828:M 11 Mag 2022 14:06:42.578 * RDB age 23658 seconds
1828:M 11 Mag 2022 14:06:42.578 * RDB memory usage when created 578.77 Mb
1828:M 11 Mag 2022 14:06:44.736 # Finito il caricamento RDB, chiavi caricate: 37302, chiavi scadute: 14975.
1828:M 11 Mag 2022 14:06:44.736 * DB caricato dal disco: 2.158 secondi
1828:M 11 Mag 2022 14:06:44.736 * Pronto ad accettare connessioni
I, [2022-05-11T14:06:52.570311 #1]  INFO -- :
I, [2022-05-11T14:06:52.571177 #1]  INFO -- : > thpoff echo "thpoff is installed!"
I, [2022-05-11T14:06:52.577565 #1]  INFO -- : thpoff is installed!

I, [2022-05-11T14:06:52.577800 #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, [2022-05-11T14:06:52.684259 #1]  INFO -- :
I, [2022-05-11T14:06:52.684959 #1]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_HOSTNAME"] == "discourse.example.com"; puts "Aborting! Domain is not configured!"; exit 1; end'
I, [2022-05-11T14:06:52.795343 #1]  INFO -- :
I, [2022-05-11T14:06:52.795716 #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, [2022-05-11T14:06:52.892589 #1]  INFO -- :
I, [2022-05-11T14:06:52.892891 #1]  INFO -- : > rm -f /etc/cron.d/anacron
I, [2022-05-11T14:06:52.896270 #1]  INFO -- :
I, [2022-05-11T14:06:52.899939 #1]  INFO -- : File > /etc/cron.d/anacron  chmod:   chown:
I, [2022-05-11T14:06:52.905986 #1]  INFO -- : File > /etc/runit/1.d/copy-env  chmod: +x  chown:
I, [2022-05-11T14:06:52.913249 #1]  INFO -- : File > /etc/service/unicorn/run  chmod: +x  chown:
I, [2022-05-11T14:06:52.921036 #1]  INFO -- : File > /etc/service/nginx/run  chmod: +x  chown:
I, [2022-05-11T14:06:52.928027 #1]  INFO -- : File > /etc/runit/3.d/01-nginx  chmod: +x  chown:
I, [2022-05-11T14:06:52.934267 #1]  INFO -- : File > /etc/runit/3.d/02-unicorn  chmod: +x  chown:
I, [2022-05-11T14:06:52.934455 #1]  INFO -- : Sostituzione di # postgres con sv start postgres || exit 1 in /etc/service/unicorn/run
I, [2022-05-11T14:06:52.934828 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2022-05-11T14:06:52.937774 #1]  INFO -- : > cd /var/www/discourse && git reset --hard
1855:C 11 Mag 2022 14:06:52.946 # oO0OoO0OoO0Oo Redis è in avvio oO0OoO0OoO0Oo
1855:C 11 Mag 2022 14:06:52.946 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=1855, appena avviato
1855:C 11 Mag 2022 14:06:52.946 # Configurazione caricata
1855:M 11 Mag 2022 14:06:52.947 * monotonic clock: POSIX clock_gettime
1855:M 11 Mag 2022 14:06:52.947 # Warning: Impossibile creare la socket di ascolto TCP del server *:6379: bind: Indirizzo già in uso
1855:M 11 Mag 2022 14:06:52.947 # Ascolto sulla porta 6379 (TCP) fallito, interruzione.
Aggiornamento file: 100% (31051/31051), fatto.
I, [2022-05-11T14:06:56.578349 #1]  INFO -- : HEAD is now at 6fc52d95 DEV: Remove scoped order warning in PostDestroyer.

I, [2022-05-11T14:06:56.578537 #1]  INFO -- : > cd /var/www/discourse && git clean -f
I, [2022-05-11T14:06:56.717688 #1]  INFO -- :
I, [2022-05-11T14:06:56.718416 #1]  INFO -- : > cd /var/www/discourse && git remote set-branches --add origin main
I, [2022-05-11T14:06:56.724007 #1]  INFO -- :
I, [2022-05-11T14:06:56.724135 #1]  INFO -- : > cd /var/www/discourse && git remote set-branches origin tests-passed
I, [2022-05-11T14:06:56.729607 #1]  INFO -- :
I, [2022-05-11T14:06:56.729884 #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, [2022-05-11T14:06:59.121360 #1]  INFO -- :
I, [2022-05-11T14:06:59.121488 #1]  INFO -- : > cd /var/www/discourse && git checkout tests-passed
Switched to a new branch 'tests-passed'
I, [2022-05-11T14:07:00.222763 #1]  INFO -- : Branch 'tests-passed' set up to track remote branch 'tests-passed' from 'origin'.

I, [2022-05-11T14:07:00.223001 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp
I, [2022-05-11T14:07:00.228175 #1]  INFO -- :
I, [2022-05-11T14:07:00.228495 #1]  INFO -- : > cd /var/www/discourse && chown discourse:www-data tmp
I, [2022-05-11T14:07:00.234500 #1]  INFO -- :
I, [2022-05-11T14:07:00.234701 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2022-05-11T14:07:00.239935 #1]  INFO -- :
I, [2022-05-11T14:07:00.240093 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2022-05-11T14:07:00.245991 #1]  INFO -- :
I, [2022-05-11T14:07:00.246163 #1]  INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2022-05-11T14:07:00.251235 #1]  INFO -- :
I, [2022-05-11T14:07:00.251454 #1]  INFO -- : > cd /var/www/discourse && mkdir -p                    /shared/log/rails
I, [2022-05-11T14:07:00.256407 #1]  INFO -- :
I, [2022-05-11T14:07:00.256646 #1]  INFO -- : > cd /var/www/discourse && bash -c "touch -a           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log"
I, [2022-05-11T14:07:00.264498 #1]  INFO -- :
I, [2022-05-11T14:07:00.264759 #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, [2022-05-11T14:07:00.273382 #1]  INFO -- :
I, [2022-05-11T14:07:00.273601 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/{uploads,backups}"
I, [2022-05-11T14:07:00.281529 #1]  INFO -- :
I, [2022-05-11T14:07:00.281737 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/{uploads,backups} /var/www/discourse/public"
I, [2022-05-11T14:07:00.288754 #1]  INFO -- :
I, [2022-05-11T14:07:00.288978 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/tmp/{backups,restores}"
I, [2022-05-11T14:07:00.295662 #1]  INFO -- :
I, [2022-05-11T14:07:00.295852 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/tmp/{backups,restores} /var/www/discourse/tmp"
I, [2022-05-11T14:07:00.302740 #1]  INFO -- :
I, [2022-05-11T14:07:00.302888 #1]  INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp
I, [2022-05-11T14:07:22.780286 #1]  INFO -- :
I, [2022-05-11T14:07:22.781068 #1]  INFO -- : > cd /var/www/discourse && find public/plugins/ -maxdepth 1 -xtype l -delete
I, [2022-05-11T14:07:22.787258 #1]  INFO -- :
I, [2022-05-11T14:07:22.787461 #1]  INFO -- : Sostituzione di # redis con sv start redis || exit 1 in /etc/service/unicorn/run
I, [2022-05-11T14:07:22.788102 #1]  INFO -- : > cd /var/www/discourse/plugins && mkdir -p plugins
I, [2022-05-11T14:07:22.792875 #1]  INFO -- :
I, [2022-05-11T14:07:22.792966 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2022-05-11T14:07:23.870152 #1]  INFO -- :
I, [2022-05-11T14:07:23.870649 #1]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2022-05-11T14:07:23.875467 #1]  INFO -- :
I, [2022-05-11T14:07:23.875624 #1]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2022-05-11T14:07:23.878764 #1]  INFO -- :
I, [2022-05-11T14:07:23.878898 #1]  INFO -- : > mkdir -p /var/nginx/cache
I, [2022-05-11T14:07:23.881881 #1]  INFO -- :
I, [2022-05-11T14:07:23.882219 #1]  INFO -- : Sostituzione di pid /run/nginx.pid; con daemon off; in /etc/nginx/nginx.conf
I, [2022-05-11T14:07:23.883093 #1]  INFO -- : Sostituzione di (?m-ix:upstream[^\}]+\}) con upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2022-05-11T14:07:23.883523 #1]  INFO -- : Sostituzione di (?-mix:server_name.+$) con server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2022-05-11T14:07:23.884020 #1]  INFO -- : Sostituzione di (?-mix:client_max_body_size.+$) con client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2022-05-11T14:07:23.884505 #1]  INFO -- : Sostituzione di (?-mix:worker_connections.+$) con worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2022-05-11T14:07:23.884965 #1]  INFO -- : > echo "done configuring web"
I, [2022-05-11T14:07:23.888448 #1]  INFO -- : done configuring web

I, [2022-05-11T14:07:23.888704 #1]  INFO -- : Sostituzione di (?-mix:sendfile.+on;) con server_names_hash_bucket_size 64;
sendfile on;
 in /etc/nginx/nginx.conf
I, [2022-05-11T14:07:23.893736 #1]  INFO -- : File > /etc/nginx/conf.d/discourse_redirect_1.conf  chmod:   chown:
I, [2022-05-11T14:07:23.894015 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
I, [2022-05-11T14:07:24.845234 #1]  INFO -- : Successfully installed bundler-2.3.13
1 gem installed

Si è verificato un errore nel mio aggiornamento

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

Per favore aiutami a correggerlo..
Installazione di excon 0.92.3
Installazione di regexp_parser 2.4.0
0: excon (0.92.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/excon-0.92.3.gemspec
Utilizzo di exifr 1.3.9
0: exifr (1.3.9) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/exifr-1.3.9.gemspec
Utilizzo di faraday-em_http 1.0.0
0: faraday-em_http (1.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-em_http-1.0.0.gemspec
Utilizzo di faraday-em_synchrony 1.0.0
0: faraday-em_synchrony (1.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-em_synchrony-1.0.0.gemspec
Utilizzo di faraday-excon 1.1.0
0: faraday-excon (1.1.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-excon-1.1.0.gemspec
Utilizzo di faraday-httpclient 1.0.1
0: faraday-httpclient (1.0.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-httpclient-1.0.1.gemspec
Utilizzo di multipart-post 2.1.1
0: multipart-post (2.1.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/multipart-post-2.1.1.gemspec
Utilizzo di faraday-net_http 1.0.1
0: faraday-net_http (1.0.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-net_http-1.0.1.gemspec
Utilizzo di faraday-net_http_persistent 1.2.0
0: faraday-net_http_persistent (1.2.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-net_http_persistent-1.2.0.gemspec
Utilizzo di faraday-patron 1.0.0
0: faraday-patron (1.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-patron-1.0.0.gemspec
Utilizzo di faraday-rack 1.0.0
0: faraday-rack (1.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-rack-1.0.0.gemspec
Utilizzo di faraday-retry 1.0.3
0: faraday-retry (1.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-retry-1.0.3.gemspec
Utilizzo di ruby2_keywords 0.0.5
0: ruby2_keywords (0.0.5) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/ruby2_keywords-0.0.5.gemspec
Utilizzo di fast_blank 1.0.1
0: fast_blank (1.0.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/fast_blank-1.0.1.gemspec
Utilizzo di fast_xs 0.8.0
0: fast_xs (0.8.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/fast_xs-0.8.0.gemspec
Utilizzo di fastimage 2.2.6
0: fastimage (2.2.6) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/fastimage-2.2.6.gemspec
Utilizzo di ffi 1.15.5
0: ffi (1.15.5) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/ffi-1.15.5.gemspec
Utilizzo di fspath 3.1.2
0: fspath (3.1.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/fspath-3.1.2.gemspec
Utilizzo di gc_tracer 1.5.1
0: gc_tracer (1.5.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/gc_tracer-1.5.1.gemspec
Utilizzo di guess_html_encoding 0.0.11
0: guess_html_encoding (0.0.11) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/guess_html_encoding-0.0.11.gemspec
Utilizzo di hana 1.3.7
0: hana (1.3.7) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/hana-1.3.7.gemspec
Utilizzo di hashie 5.0.0
0: hashie (5.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/hashie-5.0.0.gemspec
Utilizzo di highline 2.0.3
0: highline (2.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/highline-2.0.3.gemspec
Utilizzo di hkdf 0.3.0
0: hkdf (0.3.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/hkdf-0.3.0.gemspec
Utilizzo di htmlentities 4.3.4
0: htmlentities (4.3.4) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/htmlentities-4.3.4.gemspec
Utilizzo di http_accept_language 2.1.1
0: http_accept_language (2.1.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/http_accept_language-2.1.1.gemspec
Utilizzo di image_size 3.0.1
0: image_size (3.0.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/image_size-3.0.1.gemspec
Utilizzo di in_threads 1.6.0
0: in_threads (1.6.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/in_threads-1.6.0.gemspec
Utilizzo di progress 3.6.0
0: progress (3.6.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/progress-3.6.0.gemspec
Utilizzo di json 2.6.1
0: json (2.6.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/json-2.6.1.gemspec
Utilizzo di uri_template 0.7.0
0: uri_template (0.7.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/uri_template-0.7.0.gemspec
Utilizzo di jwt 2.3.0
0: jwt (2.3.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/jwt-2.3.0.gemspec
Utilizzo di kgio 2.11.4
0: kgio (2.11.4) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/kgio-2.11.4.gemspec
Utilizzo di libv8-node 16.10.0.0 (x86_64-linux)
0: libv8-node (16.10.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/libv8-node-16.10.0.0-x86_64-linux.gemspec
Utilizzo di logstash-event 1.2.02
0: logstash-event (1.2.02) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/logstash-event-1.2.02.gemspec
Recupero di logster 2.11.2
3: regexp_parser (2.4.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/regexp_parser-2.4.0.gemspec
Utilizzo di lru_redux 1.1.0
3: lru_redux (1.1.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/lru_redux-1.1.0.gemspec
Utilizzo di lz4-ruby 0.3.3
3: lz4-ruby (0.3.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/lz4-ruby-0.3.3.gemspec
Utilizzo di maxminddb 0.1.22
3: maxminddb (0.1.22) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/maxminddb-0.1.22.gemspec
Utilizzo di memory_profiler 1.0.0
3: memory_profiler (1.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/memory_profiler-1.0.0.gemspec
Utilizzo di redis 4.5.1
3: redis (4.5.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/redis-4.5.1.gemspec
Utilizzo di mini_sql 1.4.0
3: mini_sql (1.4.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/mini_sql-1.4.0.gemspec
Utilizzo di multi_json 1.15.0
3: multi_json (1.15.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/multi_json-1.15.0.gemspec
Utilizzo di multi_xml 0.6.0
3: multi_xml (0.6.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/multi_xml-0.6.0.gemspec
Utilizzo di mustache 1.1.1
3: mustache (1.1.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/mustache-1.1.1.gemspec
Recupero di uri 0.11.0
Installazione di uri 0.11.0
Installazione di logster 2.11.2
3: uri (0.11.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/uri-0.11.0.gemspec
Utilizzo di nio4r 2.5.8
3: nio4r (2.5.8) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/nio4r-2.5.8.gemspec
Recupero di oauth 0.5.10
Installazione di oauth 0.5.10
3: oauth (0.5.10) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/oauth-0.5.10.gemspec
Utilizzo di oj 3.13.11
3: oj (3.13.11) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/oj-3.13.11.gemspec
Utilizzo di optimist 3.0.1
3: optimist (3.0.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/optimist-3.0.1.gemspec
Utilizzo di pg 1.3.5
3: pg (1.3.5) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/pg-1.3.5.gemspec
Utilizzo di r2 0.2.7
3: r2 (0.2.7) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/r2-0.2.7.gemspec
Utilizzo di raindrops 0.20.0
3: raindrops (0.20.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/raindrops-0.20.0.gemspec
Utilizzo di rchardet 1.8.0
3: rchardet (1.8.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rchardet-1.8.0.gemspec
Utilizzo di rexml 3.2.5
3: rexml (3.2.5) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rexml-3.2.5.gemspec
Utilizzo di rinku 2.0.6
3: rinku (2.0.6) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rinku-2.0.6.gemspec
Utilizzo di rotp 6.2.0
3: rotp (6.2.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rotp-6.2.0.gemspec
Utilizzo di rqrcode_core 1.2.0
3: rqrcode_core (1.2.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rqrcode_core-1.2.0.gemspec
Utilizzo di rubyzip 2.3.2
3: rubyzip (2.3.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rubyzip-2.3.2.gemspec
Utilizzo di tilt 2.0.10
3: tilt (2.0.10) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/tilt-2.0.10.gemspec
Utilizzo di sshkey 2.0.0
3: sshkey (2.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/sshkey-2.0.0.gemspec
Utilizzo di stackprof 0.2.19
3: stackprof (0.2.19) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/stackprof-0.2.19.gemspec
Utilizzo di unf_ext 0.0.8.1
3: unf_ext (0.0.8.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/unf_ext-0.0.8.1.gemspec
Utilizzo di xorcist 1.1.2
3: xorcist (1.1.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/xorcist-1.1.2.gemspec
Utilizzo di i18n 1.10.0
3: i18n (1.10.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/i18n-1.10.0.gemspec
Utilizzo di tzinfo 2.0.4
3: tzinfo (2.0.4) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/tzinfo-2.0.4.gemspec
Recupero di nokogiri 1.13.6 (x86_64-linux)
0: logster (2.11.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/logster-2.11.2.gemspec
Utilizzo di rack-test 1.1.0
0: rack-test (1.1.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rack-test-1.1.0.gemspec
Utilizzo di sprockets 3.7.2
0: sprockets (3.7.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/sprockets-3.7.2.gemspec
Utilizzo di request_store 1.5.1
0: request_store (1.5.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/request_store-1.5.1.gemspec
Utilizzo di message_bus 4.2.0
0: message_bus (4.2.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/message_bus-4.2.0.gemspec
Utilizzo di rack-mini-profiler 3.0.0
0: rack-mini-profiler (3.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rack-mini-profiler-3.0.0.gemspec
Utilizzo di rack-protection 2.2.0
0: rack-protection (2.2.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rack-protection-2.2.0.gemspec
Utilizzo di addressable 2.8.0
0: addressable (2.8.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/addressable-2.8.0.gemspec
Recupero di aws-sigv4 1.5.0
Installazione di aws-sigv4 1.5.0
0: aws-sigv4 (1.5.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/aws-sigv4-1.5.0.gemspec
Recupero di net-protocol 0.1.3
Installazione di net-protocol 0.1.3
0: net-protocol (0.1.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/net-protocol-0.1.3.gemspec
Utilizzo di barber 0.12.2
0: barber (0.12.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/barber-0.12.2.gemspec
Utilizzo di bootsnap 1.11.1
0: bootsnap (1.11.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/bootsnap-1.11.1.gemspec
Utilizzo di ember-data-source 3.0.2
0: ember-data-source (3.0.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/ember-data-source-3.0.2.gemspec
Utilizzo di uglifier 4.2.0
0: uglifier (4.2.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/uglifier-4.2.0.gemspec
Utilizzo di openssl 2.2.1
0: openssl (2.2.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/openssl-2.2.1.gemspec
Utilizzo di pry 0.13.1
0: pry (0.13.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/pry-0.13.1.gemspec
Utilizzo di faraday-multipart 1.0.3
0: faraday-multipart (1.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-multipart-1.0.3.gemspec
Utilizzo di mini_suffix 0.3.3
0: mini_suffix (0.3.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/mini_suffix-0.3.3.gemspec
Utilizzo di sassc 2.0.1
0: sassc (2.0.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/sassc-2.0.1.gemspec
Utilizzo di omniauth 1.9.1
0: omniauth (1.9.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/omniauth-1.9.1.gemspec
Utilizzo di image_optim 0.31.1
0: image_optim (0.31.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/image_optim-0.31.1.gemspec
Utilizzo di logstash-logger 0.26.1
0: logstash-logger (0.26.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/logstash-logger-0.26.1.gemspec
Utilizzo di mini_racer 0.6.2
0: mini_racer (0.6.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/mini_racer-0.6.2.gemspec
Utilizzo di webpush 1.1.0
0: webpush (1.1.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/webpush-1.1.0.gemspec
Utilizzo di ecma-re-validator 0.4.0
0: ecma-re-validator (0.4.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/ecma-re-validator-0.4.0.gemspec
Recupero di sidekiq 6.4.2
Installazione di sidekiq 6.4.2
1: strscan (3.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/strscan-3.0.3.gemspec
Utilizzo di redis-namespace 1.8.2
1: redis-namespace (1.8.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/redis-namespace-1.8.2.gemspec
Recupero di net-http 0.2.2
Installazione di net-http 0.2.2
1: net-http (0.2.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/net-http-0.2.2.gemspec
Utilizzo di puma 5.6.4
1: puma (5.6.4) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/puma-5.6.4.gemspec
Utilizzo di rbtrace 0.4.14
1: rbtrace (0.4.14) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rbtrace-0.4.14.gemspec
Utilizzo di unicorn 6.1.0
1: unicorn (6.1.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/unicorn-6.1.0.gemspec
Utilizzo di rss 0.2.9
1: rss (0.2.9) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rss-0.2.9.gemspec
Utilizzo di rqrcode 2.1.1
1: rqrcode (2.1.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rqrcode-2.1.1.gemspec
Utilizzo di unf 0.1.4
1: unf (0.1.4) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/unf-0.1.4.gemspec
Recupero di activesupport 7.0.3
Installazione di activesupport 7.0.3
0: sidekiq (6.4.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/sidekiq-6.4.2.gemspec
Utilizzo di css_parser 1.11.0
0: css_parser (1.11.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/css_parser-1.11.0.gemspec
Installazione di nokogiri 1.13.6 (x86_64-linux)
Recupero di aws-sdk-core 3.130.2
Installazione di aws-sdk-core 3.130.2
1: activesupport (7.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/activesupport-7.0.3.gemspec
Utilizzo di ember-handlebars-template 0.8.0
1: ember-handlebars-template (0.8.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/ember-handlebars-template-0.8.0.gemspec
Utilizzo di openssl-signature_algorithm 1.1.1
1: openssl-signature_algorithm (1.1.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/openssl-signature_algorithm-1.1.1.gemspec
Utilizzo di pry-byebug 3.9.0
1: pry-byebug (3.9.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/pry-byebug-3.9.0.gemspec
Utilizzo di pry-rails 0.3.9
1: pry-rails (0.3.9) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/pry-rails-0.3.9.gemspec
Utilizzo di faraday 1.10.0
1: faraday (1.10.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/faraday-1.10.0.gemspec
Utilizzo di omniauth-oauth 1.2.0
1: omniauth-oauth (1.2.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/omniauth-oauth-1.2.0.gemspec
Recupero di json_schemer 0.2.21
0: aws-sdk-core (3.130.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/aws-sdk-core-3.130.2.gemspec
Utilizzo di mini_scheduler 0.13.0
0: mini_scheduler (0.13.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/mini_scheduler-0.13.0.gemspec
Utilizzo di globalid 1.0.0
0: globalid (1.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/globalid-1.0.0.gemspec
Recupero di activemodel 7.0.3
Installazione di json_schemer 0.2.21
Installazione di activemodel 7.0.3
1: json_schemer (0.2.21) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/json_schemer-0.2.21.gemspec
Utilizzo di cose 1.2.0
1: cose (1.2.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/cose-1.2.0.gemspec
Utilizzo di oauth2 1.4.7
1: oauth2 (1.4.7) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/oauth2-1.4.7.gemspec
Utilizzo di omniauth-twitter 1.4.0
1: omniauth-twitter (1.4.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/omniauth-twitter-1.4.0.gemspec
Recupero di aws-sdk-kms 1.56.0
Installazione di aws-sdk-kms 1.56.0
1: aws-sdk-kms (1.56.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/aws-sdk-kms-1.56.0.gemspec
Recupero di aws-sdk-sns 1.53.0
Installazione di aws-sdk-sns 1.53.0
0: activemodel (7.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/activemodel-7.0.3.gemspec
Recupero di activejob 7.0.3
Installazione di activejob 7.0.3
1: aws-sdk-sns (1.53.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/aws-sdk-sns-1.53.0.gemspec
Utilizzo di omniauth-oauth2 1.7.2
1: omniauth-oauth2 (1.7.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/omniauth-oauth2-1.7.2.gemspec
Recupero di aws-sdk-s3 1.114.0
0: activejob (7.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/activejob-7.0.3.gemspec
Utilizzo di active_model_serializers 0.8.4
0: active_model_serializers (0.8.4) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/active_model_serializers-0.8.4.gemspec
Recupero di activerecord 7.0.3
Installazione di aws-sdk-s3 1.114.0
Installazione di activerecord 7.0.3
1: aws-sdk-s3 (1.114.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/aws-sdk-s3-1.114.0.gemspec
Utilizzo di omniauth-facebook 9.0.0
1: omniauth-facebook (9.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/omniauth-facebook-9.0.0.gemspec
Utilizzo di omniauth-github 1.4.0
1: omniauth-github (1.4.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/omniauth-github-1.4.0.gemspec
Utilizzo di omniauth-google-oauth2 0.8.2
1: omniauth-google-oauth2 (0.8.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/omniauth-google-oauth2-0.8.2.gemspec
3: nokogiri (1.13.6) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/nokogiri-1.13.6-x86_64-linux.gemspec
Utilizzo di rails-dom-testing 2.0.3
1: rails-dom-testing (2.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rails-dom-testing-2.0.3.gemspec
Recupero di loofah 2.17.0
Utilizzo di ruby-readability 0.7.0
3: ruby-readability (0.7.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/ruby-readability-0.7.0.gemspec
Utilizzo di sanitize 6.0.0
3: sanitize (6.0.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/sanitize-6.0.0.gemspec
Installazione di loofah 2.17.0
1: loofah (2.17.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/loofah-2.17.0.gemspec
Utilizzo di rails-html-sanitizer 1.4.2
3: rails-html-sanitizer (1.4.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rails-html-sanitizer-1.4.2.gemspec
Recupero di actionview 7.0.3
Installazione di actionview 7.0.3
0: activerecord (7.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/activerecord-7.0.3.gemspec
Utilizzo di seed-fu 2.3.9
3: seed-fu (2.3.9) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/seed-fu-2.3.9.gemspec
1: actionview (7.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/actionview-7.0.3.gemspec
Recupero di actionpack 7.0.3
Utilizzo di actionview_precompiler 0.2.3
3: actionview_precompiler (0.2.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/actionview_precompiler-0.2.3.gemspec
Installazione di actionpack 7.0.3
0: actionpack (7.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/actionpack-7.0.3.gemspec
Utilizzo di sprockets-rails 3.4.2
Recupero di railties 7.0.3
3: sprockets-rails (3.4.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/sprockets-rails-3.4.2.gemspec
Installazione di railties 7.0.3
1: railties (7.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/railties-7.0.3.gemspec
Utilizzo di lograge 0.12.0
0: lograge (0.12.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/lograge-0.12.0.gemspec
Utilizzo di rails_failover 0.8.1
0: rails_failover (0.8.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rails_failover-0.8.1.gemspec
Utilizzo di rails_multisite 4.0.1
0: rails_multisite (4.0.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/rails_multisite-4.0.1.gemspec
Utilizzo di sassc-rails 2.1.2
0: sassc-rails (2.1.2) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/sassc-rails-2.1.2.gemspec
Utilizzo di jquery-rails 4.4.0
1: jquery-rails (4.4.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/jquery-rails-4.4.0.gemspec
Utilizzo di discourse-ember-rails 0.18.6
0: discourse-ember-rails (0.18.6) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/discourse-ember-rails-0.18.6.gemspec
2: digest (3.1.0) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/digest-3.1.0.gemspec
Recupero di net-pop 0.1.1
Recupero di net-smtp 0.3.1
Recupero di net-imap 0.2.3
Installazione di net-pop 0.1.1
Installazione di net-smtp 0.3.1
Installazione di net-imap 0.2.3
1: net-smtp (0.3.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/net-smtp-0.3.1.gemspec
3: net-pop (0.1.1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/net-pop-0.1.1.gemspec
0: net-imap (0.2.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/net-imap-0.2.3.gemspec
Recupero di mail 2.8.0.rc1
Installazione di mail 2.8.0.rc1
2: mail (2.8.0.rc1) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/mail-2.8.0.rc1.gemspec
Recupero di actionmailer 7.0.3
Installazione di actionmailer 7.0.3
1: actionmailer (7.0.3) da /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/actionmailer-7.0.3.gemspec
Bundle completo! 126 dipendenze del Gemfile, 184 gem installate.
Le gem nei gruppi ‘test’ e ‘development’ non sono state installate.
Le gem bundled sono installate in ./vendor/bundle

I, [2022-05-11T14:07:37.948353 #1] INFO – : > cd /var/www/discourse && [ ! -d ‘node_modules’ ] || su discourse -c ‘yarn install --production && yarn cache clean’
warning “eslint-config-discourse > eslint-plugin-lodash@7.1.0” ha una dipendenza peer non soddisfatta “lodash@>=4”.
warning " > @mixer/parallel-prettier@2.0.1" ha una dipendenza peer non soddisfatta “prettier@^2.0.0”.
I, [2022-05-11T14:08:46.198477 #1] INFO – : yarn install v1.22.18
[1/5] Validazione di package.json…
[2/5] Risoluzione dei pacchetti…
[3/5] Recupero dei pacchetti…
[4/5] Collegamento delle dipendenze…
[5/5] Costruzione dei pacchetti…
$ yarn --cwd app/assets/javascripts/discourse
yarn install v1.22.18
[1/4] Risoluzione dei pacchetti…
[2/4] Recupero dei pacchetti…
[3/4] Collegamento delle dipendenze…
[4/4] Costruzione dei pacchetti…
success File di blocco salvato.
Completato in 39.22s.
Completato in 62.80s.
yarn cache v1.22.18
success Cache cancellata.
Completato in 4.97s.

I, [2022-05-11T14:08:46.198919 #1] INFO – : > cd /var/www/discourse && su discourse -c ‘LOAD_PLUGINS=0 bundle exec rake plugin:pull_compatible_all’
I, [2022-05-11T14:08:49.426465 #1] INFO – : docker_manager è già alla versione compatibile più recente

I, [2022-05-11T14:08:49.426894 #1] INFO – : > cd /var/www/discourse && su discourse -c ‘bundle exec rake db:migrate’
2022-05-11 14:08:54.069 UTC [2322] discourse@discourse ERRORE: permesso negato per creare l’estensione “unaccent”
2022-05-11 14:08:54.069 UTC [2322] discourse@discourse SUGGERIMENTO: Deve essere superuser per creare questa estensione.
2022-05-11 14:08:54.069 UTC [2322] discourse@discourse ISTRUZIONE: CREATE EXTENSION IF NOT EXISTS unaccent
Impossibile abilitare l’estensione del database unaccent
ERRORE: permesso negato per creare l’estensione “unaccent”
SUGGERIMENTO: Deve essere superuser per creare questa estensione.
2022-05-11 14:08:54.170 UTC [2322] discourse@discourse ERRORE: permesso negato per creare l’estensione “unaccent”
2022-05-11 14:08:54.170 UTC [2322] discourse@discourse SUGGERIMENTO: Deve essere superuser per creare questa estensione.
2022-05-11 14:08:54.170 UTC [2322] discourse@discourse ISTRUZIONE: CREATE EXTENSION IF NOT EXISTS “unaccent”
rake interrotto!
StandardError: Si è verificato un errore, questa e tutte le migrazioni successive sono state annullate:

PG::InsufficientPrivilege: ERRORE: permesso negato per creare l’estensione “unaccent”
SUGGERIMENTO: Deve essere superuser per creare questa estensione.
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:69:in exec_params' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:69:in exec_params’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:768:in block (2 levels) in exec_no_cache' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/share_lock.rb:187:in yield_shares’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/dependencies/interlock.rb:41:in permit_concurrent_loads' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:767:in block in exec_no_cache’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in block in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract_adapter.rb:765:in block in log' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/notifications/instrumenter.rb:24:in instrument’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract_adapter.rb:756:in log' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:766:in exec_no_cache’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:745:in execute_and_clear' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:54:in exec_query’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:434:in enable_extension' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:932:in block in method_missing’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:900:in block in say_with_time' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:900:in say_with_time’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:921:in method_missing' /var/www/discourse/db/migrate/20220304162250_enable_unaccent_extension.rb:5:in change’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:870:in exec_migration' /var/www/discourse/lib/freedom_patches/schema_migration_details.rb:9:in block in exec_migration’
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in exec_migration' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:854:in block (2 levels) in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:853:in block in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in with_connection’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:852:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1046:in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1360:in block in execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/transaction.rb:319:in block in within_new_transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in block in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/transaction.rb:317:in within_new_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/database_statements.rb:316:in transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/transactions.rb:209:in transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1411:in ddl_transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1359:in execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1333:in each’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1333:in migrate_without_lock' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1282:in block in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1432:in block in with_advisory_lock' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in with_connection’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1447:in with_advisory_lock_connection' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1428:in with_advisory_lock’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1282:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1117:in up’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1092:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/tasks/database_tasks.rb:262:in migrate’
/var/www/discourse/lib/tasks/db.rake:227:in block (2 levels) in <main>' /var/www/discourse/lib/distributed_mutex.rb:33:in block in synchronize’
/var/www/discourse/lib/distributed_mutex.rb:29:in synchronize' /var/www/discourse/lib/distributed_mutex.rb:29:in synchronize’
/var/www/discourse/lib/distributed_mutex.rb:14:in synchronize' /var/www/discourse/lib/tasks/db.rake:210:in block in ’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in <top (required)>' /usr/local/bin/bundle:25:in load’
/usr/local/bin/bundle:25:in `’

Causato da:
ActiveRecord::StatementInvalid: PG::InsufficientPrivilege: ERROR: permission denied to create extension “unaccent”
HINT: Must be superuser to create this extension.
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:69:in exec_params' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:69:in exec_params’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:768:in block (2 levels) in exec_no_cache' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/share_lock.rb:187:in yield_shares’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/dependencies/interlock.rb:41:in permit_concurrent_loads' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:767:in block in exec_no_cache’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in block in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract_adapter.rb:765:in block in log' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/notifications/instrumenter.rb:24:in instrument’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract_adapter.rb:756:in log' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:766:in exec_no_cache’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:745:in execute_and_clear' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:54:in exec_query’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:434:in enable_extension' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:932:in block in method_missing’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:900:in block in say_with_time' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:900:in say_with_time’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:921:in method_missing' /var/www/discourse/db/migrate/20220304162250_enable_unaccent_extension.rb:5:in change’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:870:in exec_migration' /var/www/discourse/lib/freedom_patches/schema_migration_details.rb:9:in block in exec_migration’
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in exec_migration' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:854:in block (2 levels) in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:853:in block in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in with_connection’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:852:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1046:in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1360:in block in execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/transaction.rb:319:in block in within_new_transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in block in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/transaction.rb:317:in within_new_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/database_statements.rb:316:in transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/transactions.rb:209:in transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1411:in ddl_transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1359:in execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1333:in each’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1333:in migrate_without_lock' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1282:in block in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1432:in block in with_advisory_lock' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in with_connection’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1447:in with_advisory_lock_connection' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1428:in with_advisory_lock’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1282:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1117:in up’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1092:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/tasks/database_tasks.rb:262:in migrate’
/var/www/discourse/lib/tasks/db.rake:227:in block (2 levels) in <main>' /var/www/discourse/lib/distributed_mutex.rb:33:in block in synchronize’
/var/www/discourse/lib/distributed_mutex.rb:29:in synchronize' /var/www/discourse/lib/distributed_mutex.rb:29:in synchronize’
/var/www/discourse/lib/distributed_mutex.rb:14:in synchronize' /var/www/discourse/lib/tasks/db.rake:210:in block in ’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in <top (required)>' /usr/local/bin/bundle:25:in load’
/usr/local/bin/bundle:25:in `’

Causato da:
PG::InsufficientPrivilege: ERROR: permission denied to create extension “unaccent”
HINT: Must be superuser to create this extension.
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:69:in exec_params' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:69:in exec_params’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:768:in block (2 levels) in exec_no_cache' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/share_lock.rb:187:in yield_shares’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/dependencies/interlock.rb:41:in permit_concurrent_loads' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:767:in block in exec_no_cache’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in block in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract_adapter.rb:765:in block in log' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/notifications/instrumenter.rb:24:in instrument’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract_adapter.rb:756:in log' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:766:in exec_no_cache’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:745:in execute_and_clear' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:54:in exec_query’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:434:in enable_extension' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:932:in block in method_missing’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:900:in block in say_with_time' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:900:in say_with_time’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:921:in method_missing' /var/www/discourse/db/migrate/20220304162250_enable_unaccent_extension.rb:5:in change’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:870:in exec_migration' /var/www/discourse/lib/freedom_patches/schema_migration_details.rb:9:in block in exec_migration’
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in exec_migration' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:854:in block (2 levels) in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:853:in block in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in with_connection’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:852:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1046:in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1360:in block in execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/transaction.rb:319:in block in within_new_transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in block in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in handle_interrupt' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in synchronize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/transaction.rb:317:in within_new_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/database_statements.rb:316:in transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/transactions.rb:209:in transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1411:in ddl_transaction’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1359:in execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1333:in each’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1333:in migrate_without_lock' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1282:in block in migrate’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1432:in block in with_advisory_lock' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in with_connection’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1447:in with_advisory_lock_connection' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1428:in with_advisory_lock’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1282:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1117:in up’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/migration.rb:1092:in migrate' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3/lib/active_record/tasks/database_tasks.rb:262:in migrate’
/var/www/discourse/lib/tasks/db.rake:227:in block (2 levels) in <main>' /var/www/discourse/lib/distributed_mutex.rb:33:in block in synchronize’
/var/www/discourse/lib/distributed_mutex.rb:29:in synchronize' /var/www/discourse/lib/distributed_mutex.rb:29:in synchronize’
/var/www/discourse/lib/distributed_mutex.rb:14:in synchronize' /var/www/discourse/lib/tasks/db.rake:210:in block in ’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in <top (required)>' /usr/local/bin/bundle:25:in load’
/usr/local/bin/bundle:25:in `’
Tasks: TOP => db:migrate
(Vedi il tracciato completo eseguendo il task con --trace)
I, [2022-05-11T14:08:54.216922 #1] INFO – : == 20220304162250 EnableUnaccentExtension: migrating ==========================
– enable_extension(“unaccent”)

I, [2022-05-11T14:08:54.217782 #1] INFO – : Terminazione dei processi asincroni
I, [2022-05-11T14:08:54.218017 #1] INFO – : Invio di INT a HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 1711
I, [2022-05-11T14:08:54.218280 #1] INFO – : Invio di TERM a exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 1828
2022-05-11 14:08:54.218 UTC [1711] LOG: received fast shutdown request
1828:signal-handler (1652278134) Received SIGTERM scheduling shutdown…
2022-05-11 14:08:54.225 UTC [1711] LOG: aborting any active transactions
1828:M 11 May 2022 14:08:54.225 # User requested shutdown…
1828:M 11 May 2022 14:08:54.225 * Saving the final RDB snapshot before exiting.
2022-05-11 14:08:54.230 UTC [1711] LOG: worker process: logical replication launcher (PID 1720) exited with exit code 1
2022-05-11 14:08:54.230 UTC [1715] LOG: shutting down
2022-05-11 14:08:54.278 UTC [1711] LOG: database system is shut down
1828:M 11 May 2022 14:08:59.886 * DB saved on disk
1828:M 11 May 2022 14:08:59.886 # Redis is now ready to exit, bye bye…

NON RIUSCITO

Pups::ExecError: cd /var/www/discourse && su discourse -c ‘bundle exec rake db:migrate’ non è riuscito con return #<Process::Status: pid 2308 exit 1>
Posizione del fallimento: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn’
exec non è riuscito con i parametri {“cd”=>“$home”, “hook”=>“db_migrate”, “cmd”=>[“su discourse -c ‘bundle exec rake db:migrate’”]}
bootstrap non è riuscito con codice di uscita 1
** BOOTSTRAP NON RIUSCITO ** scorri verso l’alto e cerca messaggi di errore precedenti, potrebbero essercene più di uno.
./discourse-doctor può aiutare a diagnosticare il problema.
d7426e43b03ecac2ce69c47ac61a325e417e97501137e4e2b58a5bec76db34dd

Quell’errore proviene da una migrazione che è tecnicamente corretta. Probabilmente c’è qualcos’altro che non va nella tua configurazione.

Probabilmente puoi provare ad aggiungere questo alla tua configurazione (di solito app.yml) sotto hooks: (simile a come installeresti un plugin).

  after_postgres:
    - exec: su postgres -c 'psql discourse -c "create extension if not exists unaccent;"'

Questo creerà l’estensione di cui hai bisogno come superutente postgres.

Quindi PG10 è ancora supportato?

Non proprio, la soluzione di cui sopra è solo un rimedio temporaneo e stiamo concentrando i nostri sforzi di ottimizzazione solo sull’ultima versione di Postgres. Non è nemmeno garantito che funzioni e c’è la possibilità che futuri aggiornamenti rompano nuovamente il sito.

Ha senso continuare a offrire cerotti per PG10?

Crea solo un peso maggiore in seguito, in particolare se correzioni come quella sopra suggeriscono che è ancora supportabile in una certa misura.