Errore aggiornamento Discourse

ankur1857 · 28 Gennaio 2023, 5:13pm

Sto riscontrando il seguente errore durante l’aggiornamento di discourse.
Per favore, aiutami a risolverlo.

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock) failed with return #<Process::Status: pid 319 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,\\\"\\\"); print $0 }' Gemfile.lock)", "find $home ! -user discourse -exec chown discourse {} \\+"]}
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.
536bd1f80226f1b8a1d434d4283f549ca181601d79ea9a786d2932047ad93a25

Canapin · 28 Gennaio 2023, 5:16pm

Bentornato Ankur

Hai scrollato in alto e cercato i messaggi di errore? Non ci sono molte informazioni nel tuo estratto e potrebbe derivare da molte cose.

Direi che un problema comune è che un plugin è rotto. Quali plugin usi?

ankur1857 · 28 Gennaio 2023, 5:19pm

Ecco alcuni altri errori e plugin

I, [2023-01-28T17:07:54.332031 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2023-01-28T17:07:55.445163 #1]  INFO -- :
I, [2023-01-28T17:07:55.445837 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-topic-group-button.git
Cloning into 'discourse-topic-group-button'...
I, [2023-01-28T17:07:55.838969 #1]  INFO -- :
I, [2023-01-28T17:07:55.839826 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-solved.git
Cloning into 'discourse-solved'...
I, [2023-01-28T17:07:56.278121 #1]  INFO -- :
I, [2023-01-28T17:07:56.278906 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-cakeday.git
Cloning into 'discourse-cakeday'...
I, [2023-01-28T17:07:56.738730 #1]  INFO -- :
I, [2023-01-28T17:07:56.739331 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-push-notifications.git
Cloning into 'discourse-push-notifications'...
I, [2023-01-28T17:07:57.116334 #1]  INFO -- :
I, [2023-01-28T17:07:57.117037 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-assign.git
Cloning into 'discourse-assign'...
I, [2023-01-28T17:07:57.689670 #1]  INFO -- :
I, [2023-01-28T17:07:57.690584 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-plugin-linkedin-auth.git
Cloning into 'discourse-plugin-linkedin-auth'...
I, [2023-01-28T17:07:58.053126 #1]  INFO -- :
I, [2023-01-28T17:07:58.053926 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-adplugin.git
Cloning into 'discourse-adplugin'...
I, [2023-01-28T17:07:58.585148 #1]  INFO -- :
I, [2023-01-28T17:07:58.585851 #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-28T17:07:59.075614 #1]  INFO -- :
I, [2023-01-28T17:07:59.076234 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-whos-online.git
Cloning into 'discourse-whos-online'...
I, [2023-01-28T17:07:59.513322 #1]  INFO -- :
I, [2023-01-28T17:07:59.514042 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-chat-integration.git
Cloning into 'discourse-chat-integration'...
I, [2023-01-28T17:08:00.109836 #1]  INFO -- :
I, [2023-01-28T17:08:00.110558 #1]  INFO -- : cd /var/www/discourse/plugins & git clone https://github.com/discourse/discourse-translator.git
Cloning into 'discourse-translator'...
I, [2023-01-28T17:08:00.646294 #1]  INFO -- :
I, [2023-01-28T17:08:00.647373 #1]  INFO -- : cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2023-01-28T17:08:00.652443 #1]  INFO -- :
I, [2023-01-28T17:08:00.653331 #1]  INFO -- : rm /etc/nginx/sites-enabled/default
I, [2023-01-28T17:08:00.657454 #1]  INFO -- :
I, [2023-01-28T17:08:00.658241 #1]  INFO -- : mkdir -p /var/nginx/cache
I, [2023-01-28T17:08:00.664696 #1]  INFO -- :
I, [2023-01-28T17:08:00.665699 #1]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2023-01-28T17:08:00.666603 #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-28T17:08:00.667332 #1]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2023-01-28T17:08:00.668172 #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-28T17:08:00.668809 #1]  INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2023-01-28T17:08:00.669244 #1]  INFO -- : cd /var/www/discourse & echo "done configuring web"
I, [2023-01-28T17:08:00.672417 #1]  INFO -- : done configuring web

I, [2023-01-28T17:08:00.673256 #1]  INFO -- : cd /var/www/discourse & gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
ERROR:  Loading command: install (RuntimeError)
        failed to get urandom
        /usr/local/lib/ruby/3.1.0/securerandom.rb:75:in `urandom'
        /usr/local/lib/ruby/3.1.0/securerandom.rb:75:in `singleton class'
        /usr/local/lib/ruby/3.1.0/securerandom.rb:42:in `<module:SecureRandom>'
        /usr/local/lib/ruby/3.1.0/securerandom.rb:41:in `<top (required)>'
        in /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in `require'
        in /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in `require'
        /usr/local/lib/ruby/3.1.0/resolv.rb:8:in `<top (required)>'
        in /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in `require'
        in /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in `require'
        /usr/local/lib/ruby/3.1.0/net/http.rb:25:in `<top (required)>'
        in /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in `require'
        in /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in `require'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/request.rb:2:in `<top (required)>'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/remote_fetcher.rb:3:in `require_relative'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/remote_fetcher.rb:3:in `<top (required)>'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/spec_fetcher.rb:2:in `require_relative'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/spec_fetcher.rb:2:in `<top (required)>'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/dependency_installer.rb:6:in `require_relative'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/dependency_installer.rb:6:in `<top (required)>'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/commands/install_command.rb:4:in `require_relative'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/commands/install_command.rb:4:in `<top (required)>'
        in /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in `require'
        in /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in `require'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:234:in `load_and_instantiate'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:135:in `[]'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:207:in `find_command'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:249:in `invoke_command'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:191:in `process_args'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:149:in `run'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/gem_runner.rb:51:in `run'
        /usr/local/bin/gem:10:in `<main>'
ERROR:  While executing gem ... (NoMethodError)
    undefined method `deprecated?' for nil:NilClass

    cmd.deprecation_warning if cmd.deprecated?
                                  ^^^^^^^^^^^
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:250:in `invoke_command'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:191:in `process_args'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:149:in `run'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/gem_runner.rb:51:in `run'
        /usr/local/bin/gem:10:in `<main>'
I, [2023-01-28T17:08:01.021683 #1]  INFO -- :
I, [2023-01-28T17:08:01.022468 #1]  INFO -- : Terminating async processes
I, [2023-01-28T17:08:01.022673 #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/13/bin/postmaster -D /etc/postgresql/13/main pid: 41
2023-01-28 17:08:01.022 UTC [41] LOG:  received fast shutdown request
I, [2023-01-28T17:08:01.023063 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 102
102:signal-handler (1674925681) Received SIGTERM scheduling shutdown...
2023-01-28 17:08:01.032 UTC [41] LOG:  aborting any active transactions
2023-01-28 17:08:01.046 UTC [41] LOG:  background worker "logical replication launcher" (PID 50) exited with exit code 1
2023-01-28 17:08:01.048 UTC [45] LOG:  shutting down
2023-01-28 17:08:01.106 UTC [41] LOG:  database system is shut down
102:M 28 Jan 2023 17:08:01.117 # User requested shutdown...
102:M 28 Jan 2023 17:08:01.117 * Saving the final RDB snapshot before exiting.
102:M 28 Jan 2023 17:08:01.904 * DB saved on disk
102:M 28 Jan 2023 17:08:01.905 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse & gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock) failed with return #<Process::Status: pid 319 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,\\\"\\\"); print $0 }' Gemfile.lock)", "find $home ! -user discourse -exec chown discourse {} \\+"]}
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.
536bd1f80226f1b8a1d434d4283f549ca181601d79ea9a786d2932047ad93a25

Canapin · 28 Gennaio 2023, 5:23pm

Puoi copiare e incollare anche il contenuto del comando ./discourse-doctor?

Il tuo problema mi ricorda " undefined method `deprecated?' for nil:NilClass" on rebuild che contiene anche failed to get urandom.

ankur1857 · 28 Gennaio 2023, 5:31pm

root@abc:/var/discourse# ./discourse-doctor
DISCOURSE DOCTOR Sat Jan 28 12:24:22 EST 2023
OS: Linux ask 3.13.0-79-generic #123-Ubuntu SMP Fri Feb 19 14:27:58 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


Found containers/app.yml

==================== YML SETTINGS ====================
DISCOURSE_HOSTNAME=ask.******.com
SMTP_ADDRESS=email-smtp.us-east-1.amazonaws.com # obbligatorio
DEVELOPER_EMAILS=info@*****.com
SMTP_PASSWORD=**************# obbligatorio, ATTENZIONE il carattere '#' nella password può causare problemi!
SMTP_PORT=587 # (opzionale, predefinito 587)
SMTP_USER_NAME=******* # obbligatorio
LETSENCRYPT_ACCOUNT_EMAIL=info@********.com

==================== DOCKER INFO ====================
DOCKER VERSION: Docker version 18.06.1-ce, build e68fc7a

DOCKER PROCESSES (docker ps -a)

CONTAINER ID        IMAGE                 COMMAND             CREATED             STATUS                      PORTS               NAMES
d8f0766fe33d        local_discourse/app   "/sbin/boot"        5 months ago        Exited (5) 17 minutes ago                       app

==================== SERIOUS PROBLEM!!!! ====================
app not running!
Attempting to rebuild
==================== REBUILD LOG ====================
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
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 60 app
app
2.0.20230116-0051: Pulling from discourse/base
Digest: sha256:9e75876adb52427902a6d76dab731c4888af811d7e5ad9ee6efcec4ce6db986f
Status: Image is up to date for 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-28T17:24:35.345781 #1]  INFO -- : Reading from stdin
I, [2023-01-28T17:24:35.355727 #1]  INFO -- : > locale-gen $LANG && update-locale
I, [2023-01-28T17:24:35.397593 #1]  INFO -- : Generating locales (this might take a while)...
Generation complete.

I, [2023-01-28T17:24:35.398311 #1]  INFO -- : > mkdir -p /shared/postgres_run
I, [2023-01-28T17:24:35.402142 #1]  INFO -- :
I, [2023-01-28T17:24:35.403164 #1]  INFO -- : > chown postgres:postgres /shared/postgres_run
I, [2023-01-28T17:24:35.407165 #1]  INFO -- :
I, [2023-01-28T17:24:35.408165 #1]  INFO -- : > chmod 775 /shared/postgres_run
I, [2023-01-28T17:24:35.411476 #1]  INFO -- :
I, [2023-01-28T17:24:35.412337 #1]  INFO -- : > rm -fr /var/run/postgresql
I, [2023-01-28T17:24:35.415841 #1]  INFO -- :
I, [2023-01-28T17:24:35.416665 #1]  INFO -- : > ln -s /shared/postgres_run /var/run/postgresql
I, [2023-01-28T17:24:35.420726 #1]  INFO -- :
I, [2023-01-28T17:24:35.421537 #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/28 17:24:35 socat[18] E connect(6, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): No such file or directory
I, [2023-01-28T17:24:35.429613 #1]  INFO -- :
I, [2023-01-28T17:24:35.430171 #1]  INFO -- : > rm -fr /shared/postgres_run/.s*
I, [2023-01-28T17:24:35.434488 #1]  INFO -- :
I, [2023-01-28T17:24:35.435257 #1]  INFO -- : > rm -fr /shared/postgres_run/*.pid
I, [2023-01-28T17:24:35.439463 #1]  INFO -- :
I, [2023-01-28T17:24:35.440194 #1]  INFO -- : > mkdir -p /shared/postgres_run/13-main.pg_stat_tmp
I, [2023-01-28T17:24:35.443956 #1]  INFO -- :
I, [2023-01-28T17:24:35.444889 #1]  INFO -- : > chown postgres:postgres /shared/postgres_run/13-main.pg_stat_tmp
I, [2023-01-28T17:24:35.448569 #1]  INFO -- :
I, [2023-01-28T17:24:35.457179 #1]  INFO -- : File > /etc/service/postgres/run  chmod: +x  chown:
I, [2023-01-28T17:24:35.464977 #1]  INFO -- : File > /etc/service/postgres/log/run  chmod: +x  chown:
I, [2023-01-28T17:24:35.472916 #1]  INFO -- : File > /etc/runit/3.d/99-postgres  chmod: +x  chown:
I, [2023-01-28T17:24:35.480519 #1]  INFO -- : File > /root/upgrade_postgres  chmod: +x  chown:
I, [2023-01-28T17:24:35.481419 #1]  INFO -- : > chown -R root /var/lib/postgresql/13/main
I, [2023-01-28T17:24:35.581500 #1]  INFO -- :
I, [2023-01-28T17:24:35.581872 #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-28T17:24:35.585172 #1]  INFO -- :
I, [2023-01-28T17:24:35.585860 #1]  INFO -- : > chown -R postgres:postgres /shared/postgres_data
I, [2023-01-28T17:24:35.611351 #1]  INFO -- :
I, [2023-01-28T17:24:35.612223 #1]  INFO -- : > chown -R postgres:postgres /var/run/postgresql
I, [2023-01-28T17:24:35.616135 #1]  INFO -- :
I, [2023-01-28T17:24:35.616968 #1]  INFO -- : > /root/upgrade_postgres
I, [2023-01-28T17:24:35.624309 #1]  INFO -- :
I, [2023-01-28T17:24:35.625026 #1]  INFO -- : > rm /root/upgrade_postgres
I, [2023-01-28T17:24:35.628933 #1]  INFO -- :
I, [2023-01-28T17:24:35.629978 #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-28T17:24:35.631633 #1]  INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-28T17:24:35.633128 #1]  INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-28T17:24:35.634082 #1]  INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-28T17:24:35.634930 #1]  INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-28T17:24:35.636238 #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-28T17:24:35.636994 #1]  INFO -- : > install -d -m 0755 -o postgres -g postgres /shared/postgres_backup
I, [2023-01-28T17:24:35.642054 #1]  INFO -- :
I, [2023-01-28T17:24:35.643184 #1]  INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-28T17:24:35.644230 #1]  INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/13/main/postgresql.conf
I, [2023-01-28T17:24:35.645413 #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-28T17:24:35.646268 #1]  INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres  peer in /etc/postgresql/13/main/pg_hba.conf
I, [2023-01-28T17:24:35.646902 #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-28T17:24:35.647840 #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-28T17:24:35.648418 #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-28T17:24:35.651069 #1]  INFO -- : > sleep 5
2023-01-28 17:24:35.700 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-28 17:24:35.700 UTC [41] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-01-28 17:24:35.701 UTC [41] LOG:  listening on IPv6 address "::", port 5432
2023-01-28 17:24:35.705 UTC [41] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-01-28 17:24:35.715 UTC [44] LOG:  database system was shut down at 2023-01-28 17:08:01 UTC
2023-01-28 17:24:35.725 UTC [41] LOG:  database system is ready to accept connections
I, [2023-01-28T17:24:40.660617 #1]  INFO -- :
I, [2023-01-28T17:24:40.660886 #1]  INFO -- : > su postgres -c 'createdb discourse' || true
2023-01-28 17:24:40.739 UTC [54] postgres@postgres ERROR:  database "discourse" already exists
2023-01-28 17:24:40.739 UTC [54] postgres@postgres STATEMENT:  CREATE DATABASE discourse;
createdb: error: database creation failed: ERROR:  database "discourse" already exists
I, [2023-01-28T17:24:40.742750 #1]  INFO -- :
I, [2023-01-28T17:24:40.743445 #1]  INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
2023-01-28 17:24:40.822 UTC [58] postgres@discourse ERROR:  role "discourse" already exists
2023-01-28 17:24:40.822 UTC [58] postgres@discourse STATEMENT:  create user discourse;
ERROR:  role "discourse" already exists
I, [2023-01-28T17:24:40.824865 #1]  INFO -- :
I, [2023-01-28T17:24:40.825464 #1]  INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true
I, [2023-01-28T17:24:40.900992 #1]  INFO -- : GRANT

I, [2023-01-28T17:24:40.901596 #1]  INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"'
I, [2023-01-28T17:24:40.974358 #1]  INFO -- : ALTER SCHEMA

I, [2023-01-28T17:24:40.975028 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2023-01-28T17:24:41.053082 #1]  INFO -- : CREATE EXTENSION

I, [2023-01-28T17:24:41.053858 #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-28T17:24:41.133447 #1]  INFO -- : CREATE EXTENSION

I, [2023-01-28T17:24:41.134284 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2023-01-28T17:24:41.209305 #1]  INFO -- : CREATE EXTENSION

I, [2023-01-28T17:24:41.210115 #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-28T17:24:41.285522 #1]  INFO -- : CREATE EXTENSION

I, [2023-01-28T17:24:41.286519 #1]  INFO -- : > sudo -u postgres psql discourse
I, [2023-01-28T17:24:41.290834 #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-28T17:24:41.379816 #1]  INFO -- : File > /var/lib/postgresql/take-database-backup  chmod: +x  chown: postgres:postgres
I, [2023-01-28T17:24:41.384917 #1]  INFO -- : File > /var/spool/cron/crontabs/postgres  chmod:   chown:
I, [2023-01-28T17:24:41.385734 #1]  INFO -- : > echo postgres installed!
I, [2023-01-28T17:24:41.388975 #1]  INFO -- : postgres installed!

I, [2023-01-28T17:24:41.397154 #1]  INFO -- : File > /etc/service/redis/run  chmod: +x  chown:
I, [2023-01-28T17:24:41.405146 #1]  INFO -- : File > /etc/service/redis/log/run  chmod: +x  chown:
I, [2023-01-28T17:24:41.413150 #1]  INFO -- : File > /etc/runit/3.d/10-redis  chmod: +x  chown:
I, [2023-01-28T17:24:41.413918 #1]  INFO -- : Replacing daemonize yes with  in /etc/redis/redis.conf
I, [2023-01-28T17:24:41.414930 #1]  INFO -- : Replacing (?-mix:^pidfile.*$) with  in /etc/redis/redis.conf
I, [2023-01-28T17:24:41.417192 #1]  INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data
I, [2023-01-28T17:24:41.422129 #1]  INFO -- :
I, [2023-01-28T17:24:41.423161 #1]  INFO -- : Replacing (?-mix:^logfile.*$) with logfile "" in /etc/redis/redis.conf
I, [2023-01-28T17:24:41.424914 #1]  INFO -- : Replacing (?-mix:^bind .*$) with  in /etc/redis/redis.conf
I, [2023-01-28T17:24:41.425942 #1]  INFO -- : Replacing (?-mix:^dir .*$) with dir /shared/redis_data in /etc/redis/redis.conf
I, [2023-01-28T17:24:41.427672 #1]  INFO -- : Replacing (?-mix:^protected-mode yes) with protected-mode no in /etc/redis/redis.conf
I, [2023-01-28T17:24:41.428956 #1]  INFO -- : Replacing # io-threads 4 with io-threads $redis_io_threads in /etc/redis/redis.conf
I, [2023-01-28T17:24:41.430435 #1]  INFO -- : > echo redis installed
I, [2023-01-28T17:24:41.434645 #1]  INFO -- : redis installed

I, [2023-01-28T17:24:41.435606 #1]  INFO -- : > cat /etc/redis/redis.conf | grep logfile
I, [2023-01-28T17:24:41.442127 #1]  INFO -- : logfile ""

I, [2023-01-28T17:24:41.442883 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-01-28T17:24:41.445375 #1]  INFO -- : > sleep 10
102:C 28 Jan 2023 17:24:41.460 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
102:C 28 Jan 2023 17:24:41.460 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=102, just started
102:C 28 Jan 2023 17:24:41.461 # Configuration loaded
102:M 28 Jan 2023 17:24:41.461 * monotonic clock: POSIX clock_gettime
102:M 28 Jan 2023 17:24:41.462 * Running mode=standalone, port=6379.
102:M 28 Jan 2023 17:24:41.463 # 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 28 Jan 2023 17:24:41.463 # Server initialized
102:M 28 Jan 2023 17:24:41.463 # 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 28 Jan 2023 17:24:41.463 # WARNING You have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled (set to 'madvise' or 'never').
102:M 28 Jan 2023 17:24:41.464 * Loading RDB produced by version 7.0.7
102:M 28 Jan 2023 17:24:41.464 * RDB age 1000 seconds
102:M 28 Jan 2023 17:24:41.464 * RDB memory usage when created 94.37 Mb
102:M 28 Jan 2023 17:24:41.915 * Done loading RDB, keys loaded: 24491, keys expired: 86.
102:M 28 Jan 2023 17:24:41.915 * DB loaded from disk: 0.452 seconds
102:M 28 Jan 2023 17:24:41.916 * Ready to accept connections
I, [2023-01-28T17:24:51.453948 #1]  INFO -- :
I, [2023-01-28T17:24:51.454921 #1]  INFO -- : > thpoff echo "thpoff is installed!"
I, [2023-01-28T17:24:51.461076 #1]  INFO -- : thpoff is installed!

I, [2023-01-28T17:24:51.461859 #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-28T17:24:51.603109 #1]  INFO -- :
I, [2023-01-28T17:24:51.604021 #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-28T17:24:51.735700 #1]  INFO -- :
I, [2023-01-28T17:24:51.736589 #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-28T17:24:51.876732 #1]  INFO -- :
I, [2023-01-28T17:24:51.877519 #1]  INFO -- : > rm -f /etc/cron.d/anacron
I, [2023-01-28T17:24:51.881595 #1]  INFO -- :
I, [2023-01-28T17:24:51.886941 #1]  INFO -- : File > /etc/cron.d/anacron  chmod:   chown:
I, [2023-01-28T17:24:51.895950 #1]  INFO -- : File > /etc/runit/1.d/copy-env  chmod: +x  chown:
I, [2023-01-28T17:24:51.904187 #1]  INFO -- : File > /etc/service/unicorn/run  chmod: +x  chown:
I, [2023-01-28T17:24:51.912562 #1]  INFO -- : File > /etc/service/nginx/run  chmod: +x  chown:
I, [2023-01-28T17:24:51.921491 #1]  INFO -- : File > /etc/runit/3.d/01-nginx  chmod: +x  chown:
I, [2023-01-28T17:24:51.930695 #1]  INFO -- : File > /etc/runit/3.d/02-unicorn  chmod: +x  chown:
I, [2023-01-28T17:24:51.931461 #1]  INFO -- : Replacing # postgres with sv start postgres || exit 1 in /etc/service/unicorn/run
I, [2023-01-28T17:24:51.932184 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-01-28T17:24:51.936273 #1]  INFO -- : > cd /var/www/discourse && git reset --hard
129:C 28 Jan 2023 17:24:51.960 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
129:C 28 Jan 2023 17:24:51.961 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=129, just started
129:C 28 Jan 2023 17:24:51.961 # Configuration loaded
129:M 28 Jan 2023 17:24:51.962 * monotonic clock: POSIX clock_gettime
129:M 28 Jan 2023 17:24:51.962 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
129:M 28 Jan 2023 17:24:51.962 # Failed listening on port 6379 (TCP), aborting.
Updating files: 100% (32677/32677), done.
I, [2023-01-28T17:24:55.920809 #1]  INFO -- : HEAD is now at 2eb0a300 FIX: Use hashtags in channel archive PMs if available (#19859)

I, [2023-01-28T17:24:55.921441 #1]  INFO -- : > cd /var/www/discourse && git clean -f
I, [2023-01-28T17:24:56.139104 #1]  INFO -- :
I, [2023-01-28T17:24:56.139983 #1]  INFO -- : > cd /var/www/discourse && git remote set-branches --add origin main
I, [2023-01-28T17:24:56.145859 #1]  INFO -- :
I, [2023-01-28T17:24:56.146541 #1]  INFO -- : > cd /var/www/discourse && git remote set-branches origin tests-passed
I, [2023-01-28T17:24:56.153237 #1]  INFO -- :
I, [2023-01-28T17:24:56.153924 #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-28T17:24:58.758598 #1]  INFO -- :
I, [2023-01-28T17:24:58.759305 #1]  INFO -- : > cd /var/www/discourse && git checkout tests-passed
Switched to a new branch 'tests-passed'
I, [2023-01-28T17:25:00.174821 #1]  INFO -- : Branch 'tests-passed' set up to track remote branch 'tests-passed' from 'origin'.

I, [2023-01-28T17:25:00.175827 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp
I, [2023-01-28T17:25:00.182996 #1]  INFO -- :
I, [2023-01-28T17:25:00.184342 #1]  INFO -- : > cd /var/www/discourse && chown discourse:www-data tmp
I, [2023-01-28T17:25:00.193079 #1]  INFO -- :
I, [2023-01-28T17:25:00.193892 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2023-01-28T17:25:00.203623 #1]  INFO -- :
I, [2023-01-28T17:25:00.204341 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2023-01-28T17:25:00.209799 #1]  INFO -- :
I, [2023-01-28T17:25:00.210501 #1]  INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2023-01-28T17:25:00.215415 #1]  INFO -- :
I, [2023-01-28T17:25:00.216074 #1]  INFO -- : > cd /var/www/discourse && mkdir -p                    /shared/log/rails
I, [2023-01-28T17:25:00.221152 #1]  INFO -- :
I, [2023-01-28T17:25:00.221800 #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-28T17:25:00.230317 #1]  INFO -- :
I, [2023-01-28T17:25:00.230965 #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-28T17:25:00.238111 #1]  INFO -- :
I, [2023-01-28T17:25:00.238844 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/{uploads,backups}"
I, [2023-01-28T17:25:00.246812 #1]  INFO -- :
I, [2023-01-28T17:25:00.247554 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/{uploads,backups} /var/www/discourse/public"
I, [2023-01-28T17:25:00.254589 #1]  INFO -- :
I, [2023-01-28T17:25:00.255261 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/tmp/{backups,restores}"
I, [2023-01-28T17:25:00.262612 #1]  INFO -- :
I, [2023-01-28T17:25:00.263279 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/tmp/{backups,restores} /var/www/discourse/tmp"
I, [2023-01-28T17:25:00.270186 #1]  INFO -- :
I, [2023-01-28T17:25:00.270829 #1]  INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp
I, [2023-01-28T17:25:01.349652 #1]  INFO -- :
I, [2023-01-28T17:25:01.350476 #1]  INFO -- : > cd /var/www/discourse && [ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete
I, [2023-01-28T17:25:01.356166 #1]  INFO -- :
I, [2023-01-28T17:25:01.357019 #1]  INFO -- : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run
I, [2023-01-28T17:25:01.358568 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2023-01-28T17:25:08.154799 #1]  INFO -- :
I, [2023-01-28T17:25:08.155492 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-topic-group-button.git
Cloning into 'discourse-topic-group-button'...
I, [2023-01-28T17:25:09.109635 #1]  INFO -- :
I, [2023-01-28T17:25:09.110378 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-solved.git
Cloning into 'discourse-solved'...
I, [2023-01-28T17:25:10.077193 #1]  INFO -- :
I, [2023-01-28T17:25:10.078107 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-cakeday.git
Cloning into 'discourse-cakeday'...
I, [2023-01-28T17:25:10.619083 #1]  INFO -- :
I, [2023-01-28T17:25:10.620389 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-push-notifications.git
Cloning into 'discourse-push-notifications'...
I, [2023-01-28T17:25:11.341592 #1]  INFO -- :
I, [2023-01-28T17:25:11.342323 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-assign.git
Cloning into 'discourse-assign'...
I, [2023-01-28T17:25:12.380392 #1]  INFO -- :
I, [2023-01-28T17:25:12.381078 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-plugin-linkedin-auth.git
Cloning into 'discourse-plugin-linkedin-auth'...
I, [2023-01-28T17:25:12.737567 #1]  INFO -- :
I, [2023-01-28T17:25:12.738337 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-adplugin.git
Cloning into 'discourse-adplugin'...
I, [2023-01-28T17:25:13.389728 #1]  INFO -- :
I, [2023-01-28T17:25:13.390496 #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-28T17:25:13.977333 #1]  INFO -- :
I, [2023-01-28T17:25:13.978025 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-whos-online.git
Cloning into 'discourse-whos-online'...
I, [2023-01-28T17:25:14.453814 #1]  INFO -- :
I, [2023-01-28T17:25:14.454499 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-chat-integration.git
Cloning into 'discourse-chat-integration'...
I, [2023-01-28T17:25:15.076264 #1]  INFO -- :
I, [2023-01-28T17:25:15.076917 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-translator.git
Cloning into 'discourse-translator'...
I, [2023-01-28T17:25:15.628454 #1]  INFO -- :
I, [2023-01-28T17:25:15.629521 #1]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2023-01-28T17:25:15.634617 #1]  INFO -- :
I, [2023-01-28T17:25:15.635642 #1]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2023-01-28T17:25:15.640854 #1]  INFO -- :
I, [2023-01-28T17:25:15.641650 #1]  INFO -- : > mkdir -p /var/nginx/cache
I, [2023-01-28T17:25:15.645714 #1]  INFO -- :
I, [2023-01-28T17:25:15.646666 #1]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2023-01-28T17:25:15.647760 #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-28T17:25:15.648992 #1]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2023-01-28T17:25:15.649851 #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-28T17:25:15.650419 #1]  INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2023-01-28T17:25:15.650869 #1]  INFO -- : > echo "done configuring web"
I, [2023-01-28T17:25:15.653996 #1]  INFO -- : done configuring web

I, [2023-01-28T17:25:15.654779 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
ERROR:  Loading command: install (RuntimeError)
        failed to get urandom
        /usr/local/lib/ruby/3.1.0/securerandom.rb:75:in `urandom'
        /usr/local/lib/ruby/3.1.0/securerandom.rb:75:in `singleton class'
        /usr/local/lib/ruby/3.1.0/securerandom.rb:42:in `<module:SecureRandom>'
        /usr/local/lib/ruby/3.1.0/securerandom.rb:41:in `<top (required)>'
        <internal:/usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        <internal:/usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        /usr/local/lib/ruby/3.1.0/resolv.rb:8:in `<top (required)>'
        <internal:/usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        <internal:/usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        /usr/local/lib/ruby/3.1.0/net/http.rb:25:in `<top (required)>'
        <internal:/usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        <internal:/usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/request.rb:2:in `<top (required)>'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/remote_fetcher.rb:3:in `require_relative'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/remote_fetcher.rb:3:in `<top (required)>'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/spec_fetcher.rb:2:in `require_relative'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/spec_fetcher.rb:2:in `<top (required)>'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/dependency_installer.rb:6:in `require_relative'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/dependency_installer.rb:6:in `<top (required)>'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/commands/install_command.rb:4:in `require_relative'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/commands/install_command.rb:4:in `<top (required)>'
        <internal:/usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        <internal:/usr/local/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:234:in `load_and_instantiate'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:135:in `[]'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:207:in `find_command'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:249:in `invoke_command'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:191:in `process_args'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:149:in `run'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/gem_runner.rb:51:in `run'
        /usr/local/bin/gem:10:in `<main>'
ERROR:  Durante l'esecuzione di gem ... (NoMethodError)
    metodo `deprecated?' non definito per nil:NilClass

    cmd.deprecation_warning if cmd.deprecated?
                                  ^^^^^^^^^^^^
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:250:in `invoke_command'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:191:in `process_args'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/command_manager.rb:149:in `run'
        /usr/local/lib/ruby/site_ruby/3.1.0/rubygems/gem_runner.rb:51:in `run'
        /usr/local/bin/gem:10:in `<main>'
I, [2023-01-28T17:25:16.033091 #1]  INFO -- :
I, [2023-01-28T17:25:16.033997 #1]  INFO -- : Terminazione dei processi asincroni
I, [2023-01-28T17:25:16.034360 #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/13/bin/postmaster -D /etc/postgresql/13/main pid: 41
2023-01-28 17:25:16.034 UTC [41] LOG:  ricevuta richiesta di arresto rapido
I, [2023-01-28T17:25:16.034914 #1]  INFO -- : Invio di TERM a exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 102
102:signal-handler (1674926716) Ricevuto SIGTERM, pianificazione dell'arresto...
2023-01-28 17:25:16.041 UTC [41] LOG:  interruzione di eventuali transazioni attive
2023-01-28 17:25:16.050 UTC [41] LOG:  worker di background "logical replication launcher" (PID 50) terminato con codice di uscita 1
2023-01-28 17:25:16.051 UTC [45] LOG:  arresto in corso
102:M 28 Jan 2023 17:25:16.059 # Arresto richiesto dall'utente...
102:M 28 Jan 2023 17:25:16.059 * Salvataggio dello snapshot RDB finale prima dell'uscita.
2023-01-28 17:25:16.122 UTC [41] LOG:  sistema di database arrestato
102:M 28 Jan 2023 17:25:16.825 * DB salvato su disco
102:M 28 Jan 2023 17:25:16.825 # Redis è ora pronto per uscire, arrivederci...


FALLITO
--------------------
Pups::ExecError: cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock) fallito con ritorno #<Process::Status: pid 319 exit 1>
Posizione del fallimento: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec fallito con i parametri {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,\"\"); print $0 }' Gemfile.lock)", "find $home ! -user discourse -exec chown discourse {} \\+"]}
bootstrap fallito con codice di uscita 1
** BOOTSTRAP FALLITO ** scorri verso l'alto e cerca i messaggi di errore precedenti, potrebbero essercene più di uno.
./discourse-doctor potrebbe aiutare a diagnosticare il problema.
ac268b32eab07a975103e7695259026306aec05d05d9804d92c2a76744a15930
==================== FINE LOG RICOSTRUZIONE ====================
Ricostruzione app fallita.

Controllo del nome del dominio . . .

Connessione a ask.pharmaguideline.com riuscita.
Probabilmente dovresti rimuovere eventuali plugin non standard e ricostruire.
Tentativo di riavvio del contenitore esistente. . .
Architettura x86_64 rilevata.
ATTENZIONE: il file containers/app.yml è leggibile da tutti. Puoi proteggere questo file eseguendo: chmod o-rwx containers/app.yml

avvio del contenitore esistente
+ /usr/bin/docker start app
app
d8f0766fe33d        local_discourse/app   "/sbin/boot"        5 mesi fa        In esecuzione da meno di un secondo   0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   app
Contenitore riavviato.


==================== PLUGIN ====================
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-topic-group-button.git
          - git clone https://github.com/discourse/discourse-solved.git
          - git clone https://github.com/discourse/discourse-cakeday.git
          - git clone https://github.com/discourse/discourse-push-notifications.git
          - git clone https://github.com/discourse/discourse-assign.git
          - git clone https://github.com/discourse/discourse-plugin-linkedin-auth.git
          - git clone https://github.com/discourse/discourse-adplugin.git
          - git clone https://github.com/discourse/discourse-data-explorer.git
          - git clone https://github.com/discourse/discourse-whos-online.git
          - git clone https://github.com/discourse/discourse-chat-integration.git
          - git clone https://github.com/discourse/discourse-translator.git

Nessun plugin non ufficiale rilevato.

Vedi https://github.com/discourse/discourse/blob/main/lib/plugin/metadata.rb per l'elenco ufficiale.

========================================
Versione Discourse su ask.*******.com: NON TROVATA
Versione Discourse su localhost: NON TROVATA


==================== INFORMAZIONI MEMORIA ====================
RAM (MB): 2050

              totale        usata        libera      condivisa  buff/cache   disponibile
Mem:           2001         143         759          24        1098        1644
Swap:          2047           0        2047

==================== CONTROLLO SPAZIO DISCO ====================
---------- Spazio Disco OS ----------
Filesystem                 Dimensione  Usato Disponibile Uso% Montato su
/dev/disk/by-label/DOROOT   50G   21G   27G  44% /

==================== INFORMAZIONI DISCO ====================
Disco /dev/vda: 50 GiB, 53687091200 byte, 104857600 settori
Unità: settori di 1 * 512 = 512 byte
Dimensione settore (logico/fisico): 512 byte / 512 byte
Dimensione I/O (minima/ottimale): 512 byte / 512 byte
Tipo etichetta disco: gpt
Identificatore disco: 29B528BA-16C4-402E-BEE9-53555C8B6F10

Dispositivo     Inizio       Fine   Settori Dimensione Tipo
/dev/vda1   2048 104855551 104853504  50G File system Linux

==================== FINE INFORMAZIONI DISCO ====================

==================== TEST MAIL ====================
Per un test robusto, ottieni un indirizzo da http://www.mail-tester.com/
Oppure invia semplicemente un messaggio di test a te stesso.
Indirizzo email per il test mail? ('n' per saltare) : n
Test mail saltato.
Sostituzione: SMTP_PASSWORD
Sostituzione: LETSENCRYPT_ACCOUNT_EMAIL
Sostituzione: DEVELOPER_EMAILS
Sostituzione: DISCOURSE_DB_PASSWORD
Sostituzione: Invio mail a

==================== Fatto! ====================
Vuoi servire una versione pubblicamente disponibile di questo file? (S/n)n
Log pubblicamente disponibile non generato.

Puoi esaminare l'output di questo script con
LESS=-Ri less /tmp/discourse-debug.txt

MA PRIMA, assicurati di conoscere i primi tre comandi qui sotto!!!

Comandi da conoscere quando si visualizza il file con il comando sopra (chiamato 'less'):
q              -- esci
/error<INVIO>  -- cerca la parola 'error'
n              -- cerca la prossima occorrenza
g              -- vai all'inizio del file
f              -- vai avanti di una pagina
b              -- vai indietro di una pagina
G              -- vai alla fine del file

ankur1857 · 28 Gennaio 2023, 7:04pm

Qualcuno può aiutarmi a risolvere il problema?

Canapin · 28 Gennaio 2023, 9:20pm

La mia ipotesi è che il problema sia in qualche modo correlato al tuo sistema. Si tratta di un’installazione standard? Quale versione di Linux?

Puoi attendere la risposta di qualcuno con conoscenze più approfondite, oppure provare a reinstallare Discourse su un sistema pulito e ripristinare un backup recente.
Se il tuo forum è attualmente online e funzionante, ti suggerirei di provare prima su un server temporaneo.

Falco · 28 Gennaio 2023, 10:27pm

Questo kernel è troppo vecchio, devi aggiornarlo.

ankur1857 · 29 Gennaio 2023, 2:25am

Come posso aggiornare il kernel?

darkpixlz · 29 Gennaio 2023, 3:58am

Puoi eseguire sudo apt update && sudo apt upgrade, supponendo che tu sia su Ubuntu.

ankur1857 · 29 Gennaio 2023, 4:24am

Questo comando non ha fatto nulla
la versione del kernel è ancora la stessa

root@ask:/var/discourse# uname -ir
3.13.0-79-generic x86_64
root@ask:/var/discourse# sudo apt update && sudo apt upgrade
Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:2 http://mirrors.digitalocean.com/ubuntu xenial InRelease
Hit:3 http://mirrors.digitalocean.com/ubuntu xenial-updates InRelease
Hit:4 http://mirrors.digitalocean.com/ubuntu xenial-backports InRelease
Get:5 https://download.docker.com/linux/ubuntu xenial InRelease [66.2 kB]
Hit:6 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease
Fetched 66.2 kB in 1s (37.8 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-201 linux-headers-4.4.0-201-generic
  linux-headers-4.4.0-203 linux-headers-4.4.0-203-generic
  linux-headers-4.4.0-204 linux-headers-4.4.0-204-generic
  linux-headers-4.4.0-206 linux-headers-4.4.0-206-generic
  linux-headers-4.4.0-208 linux-headers-4.4.0-208-generic
  linux-image-4.4.0-201-generic linux-image-4.4.0-203-generic
  linux-image-4.4.0-204-generic linux-image-4.4.0-206-generic
  linux-image-4.4.0-208-generic linux-modules-4.4.0-201-generic
  linux-modules-4.4.0-203-generic linux-modules-4.4.0-204-generic
  linux-modules-4.4.0-206-generic linux-modules-4.4.0-208-generic
  linux-modules-extra-4.4.0-201-generic linux-modules-extra-4.4.0-203-generic
  linux-modules-extra-4.4.0-204-generic linux-modules-extra-4.4.0-206-generic
  linux-modules-extra-4.4.0-208-generic
Use 'sudo apt autoremove' to remove them.
The following security updates require Ubuntu Pro with 'esm-infra' enabled:
  libpam0g libgssapi3-heimdal libxdmcp6 perl-base libpolkit-gobject-1-0
  libdns-export162 fuse libcomerr2 libkrb5-3 libgssapi-krb5-2
  python-twisted-core libisccfg140 intel-microcode libdbus-1-3
  libwind0-heimdal uuid-runtime linux-headers-generic libfdisk1
  libsasl2-modules-db vim-common libcurl3 libldap-2.4-2 libpam-modules openssl
  byobu libgnutls-openssl27 ntfs-3g git-man libsystemd0 linux-image-generic
  libheimntlm0-heimdal cpp-5 python-twisted-bin dbus python2.7-minimal
  libmount1 tcpdump libsqlite3-0 libicu55 bind9-host e2fsprogs zlib1g dnsutils
  libgmp10 perl-modules-5.22 sudo libpython2.7 libncurses5 python2.7
  libheimbase1-heimdal libc6 util-linux libpython3.5 python3.5 git
  openssh-sftp-server python3.5-minimal libsepol1 libpolkit-agent-1-0
  libk5crypto3 libisc160 udev locales passwd libsasl2-2 libklibc
  libpam-runtime e2fslibs isc-dhcp-common gcc-6-base python-lxml libncursesw5
  libx11-6 libexpat1 libudev1 rsyslog krb5-locales libgcc1 libss2 mount
  libperl5.22 gcc-5-base apport gdisk libblkid1 dpkg libisc-export160
  busybox-static libc-bin man-db libsasl2-modules libtinfo5 python3-apport
  libkrb5support0 libpcre3 libfuse2 tar systemd-sysv libuuid1 libgcrypt20
  liblwres141 libhcrypto4-heimdal python-pkg-resources vim-runtime liblz4-1
  gpgv vim libpam-systemd distro-info-data xz-utils ncurses-term
  python3-pkg-resources systemd libsmartcols1 login libpolkit-backend-1-0
  ncurses-bin libpam-modules-bin openssh-server libx11-data openssh-client
  bsdutils libdns162 libglib2.0-data ncurses-base bash policykit-1 libxml2
  libpython2.7-minimal multiarch-support cpio libgnutls30 libroken18-heimdal
  libfreetype6 ca-certificates perl rsync vim-tiny libasn1-8-heimdal libzstd1
  libisccc140 libkrb5-26-heimdal cron libpython3.5-stdlib libbind9-140 gzip
  python3-jinja2 libtasn1-6 gnupg libpam-cracklib libpython2.7-stdlib liblzma5
  libpython3.5-minimal libstdc++6 curl libhx509-5-heimdal isc-dhcp-client
  klibc-utils linux-generic python3-problem-report libpng12-0 libglib2.0-0
  libcurl3-gnutls libxslt1.1 libssl1.0.0 tzdata busybox-initramfs
Learn more about Ubuntu Pro for 16.04 at https://ubuntu.com/16-04
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@ask:/var/discourse# uname -ir
3.13.0-79-generic x86_64
root@ask:/var/discourse#

ufukayyildiz · 29 Gennaio 2023, 4:29am

cerca do-release-upgrade

ankur1857 · 29 Gennaio 2023, 5:23am

esegui il comando do-release-upgrade ma la versione è ancora 3.13.0-79-generic

Benjamin_D · 29 Gennaio 2023, 7:50am

È necessario sottoscrivere Ubuntu Pro (gratuito per uso personale fino a 5 macchine)

Oppure creare una nuova droplet e caricare un backup

ankur1857 · 29 Gennaio 2023, 9:11am

dopo aver eseguito il comando do-release-update, non è accessibile tramite ssh

ankur1857 · 29 Gennaio 2023, 11:29am

come eseguire l’app, come mostrato nel log degli errori l’app non è in esecuzione.

jo-andre · 29 Gennaio 2023, 12:17pm

cd /var/discourse
./launcher start app

ankur1857 · 29 Gennaio 2023, 12:37pm

Si è verificato un nuovo errore
Versione di Discourse su ask.pharmaguideline.com: NON TROVATO

root@ask:/var/discourse# ./discourse-doctor
DISCOURSE DOCTOR Dom 29 Gen 2023 07:24:05 EST
OS: Linux ask 3.13.0-79-generic #123-Ubuntu SMP Ven 19 Feb 2016 14:27:58 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


Trovato containers/app.yml

==================== IMPOSTAZIONI YML ====================
DISCOURSE_HOSTNAME=******************
SMTP_ADDRESS=************
DEVELOPER_EMAILS=************
SMTP_PASSWORD=************** # richiesto, ATTENZIONE il carattere '#' nella password può causare problemi!
SMTP_PORT=587 # (opzionale, predefinito 587)
SMTP_USER_NAME=****************** # richiesto
LETSENCRYPT_ACCOUNT_EMAIL=*****************

==================== INFORMAZIONI DOCKER ====================
VERSIONE DOCKER: Docker version 19.03.13, build 4484c46d9d

PROCESSI DOCKER (docker ps -a)

CONTAINER ID        IMMAGINE              COMANDO             CREATO              STATO               PORTE                                      NOMI
d8f0766fe33d        local_discourse/app   \"/sbin/boot\"        5 mesi fa           Attivo da 9 secondi   0.0.0.0:80-\u003e80/tcp, 0.0.0.0:443-\u003e443/tcp   app

d8f0766fe33d        local_discourse/app   \"/sbin/boot\"        5 mesi fa           Attivo da 9 secondi   0.0.0.0:80-\u003e80/tcp, 0.0.0.0:443-\u003e443/tcp   app

Il container dell'app Discourse è in esecuzione


==================== PLUGIN ===================
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-topic-group-button.git
          - git clone https://github.com/discourse/discourse-solved.git
          - git clone https://github.com/discourse/discourse-cakeday.git
          - git clone https://github.com/discourse/discourse-push-notifications.git
          - git clone https://github.com/discourse/discourse-assign.git
          - git clone https://github.com/discourse/discourse-plugin-linkedin-auth.git
          - git clone https://github.com/discourse/discourse-adplugin.git
          - git clone https://github.com/discourse/discourse-data-explorer.git
          - git clone https://github.com/discourse/discourse-whos-online.git
          - git clone https://github.com/discourse/discourse-chat-integration.git
          - git clone https://github.com/discourse/discourse-translator.git

Nessun plugin non ufficiale rilevato.

Vedi https://github.com/discourse/discourse/blob/main/lib/plugin/metadata.rb per l'elenco ufficiale.

========================================
Versione di Discourse su ask.pharmaguideline.com: NON TROVATO

rahim123 · 29 Gennaio 2023, 1:18pm

Ciao, ho lo stesso problema su un’installazione di test nuovissima. Ho anche abilitato mysql-dep-template.yml perché è per l’importazione di un forum di test. Questo processo ha funzionato costantemente per me molte volte negli ultimi mesi. Ma ora fallisce con ./launcher bootstrap app. Guardando l’output di bootstrap, mi chiedo se il repository aggiuntivo https://dl.yarnpkg.com/debian per l’immagine Docker di base Debian che Discourse utilizza abbia cambiato la sua chiave di repository e stia impedendo l’installazione di alcuni pacchetti nel container?

2:  actionmailer (7.0.4.1) from /var/www/discourse/vendor/bundle/ruby/3.1.0/specifications/actionmailer-7.0.4.1.gemspec
Bundle complete! 135 dipendenze Gemfile, 172 gemme ora installate.
Gemme nei gruppi 'test' e 'development' non sono state installate.
Gemme pacchettizzate sono installate in './vendor/bundle'

I, [2023-01-29T13:08:02.394673 #1]  INFO -- : > cd /var/www/discourse & echo "gem 'mysql2'" >> Gemfile
I, [2023-01-29T13:08:02.396956 #1]  INFO -- : 
I, [2023-01-29T13:08:02.397059 #1]  INFO -- : > cd /var/www/discourse & apt-get update & DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev
W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: Le seguenti firme non sono valide: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
E: Il repository 'https://dl.yarnpkg.com/debian stable InRelease' non è firmato.
I, [2023-01-29T13:08:04.131013 #1]  INFO -- : Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:4 http://deb.debian.org/debian bullseye-backports InRelease [49.0 kB]
Get:5 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
Get:6 http://deb.debian.org/debian bullseye/main amd64 Packages [8,183 kB]
Get:7 https://deb.nodesource.com/node_18.x bullseye InRelease [4,586 B]
Get:8 http://apt.postgresql.org/pub/repos/apt bullseye-pgdg InRelease [91.7 kB]
Get:9 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [216 kB]
Get:10 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [14.6 kB]
Get:11 http://deb.debian.org/debian bullseye-backports/main amd64 Packages [384 kB]
Err:5 https://dl.yarnpkg.com/debian stable InRelease
  Le seguenti firme non sono valide: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
Get:12 https://deb.nodesource.com/node_18.x bullseye/main amd64 Packages [774 B]
Get:13 http://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 Packages [268 kB]
Lettura degli elenchi dei pacchetti...

I, [2023-01-29T13:08:04.131367 #1]  INFO -- : Terminating async processes
I, [2023-01-29T13:08:04.131403 #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/13/bin/postmaster -D /etc/postgresql/13/main pid: 42
I, [2023-01-29T13:08:04.131434 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
103:signal-handler (1674997684) Received SIGTERM scheduling shutdown...
2023-01-29 13:08:04.131 UTC [42] LOG:  received fast shutdown request
2023-01-29 13:08:04.133 UTC [42] LOG:  aborting any active transactions
2023-01-29 13:08:04.134 UTC [42] LOG:  background worker "logical replication launcher" (PID 51) exited with exit code 1
2023-01-29 13:08:04.134 UTC [46] LOG:  shutting down
2023-01-29 13:08:04.154 UTC [42] LOG:  database system is shut down
103:M 29 Jan 2023 13:08:04.205 # User requested shutdown...
103:M 29 Jan 2023 13:08:04.205 * Saving the final RDB snapshot before exiting.
103:M 29 Jan 2023 13:08:04.207 * DB saved on disk
103:M 29 Jan 2023 13:08:04.207 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse & apt-get update & DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev failed with return #<Process::Status: pid 451 exit 100>
Location of failure: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"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 failed with exit code 100
** 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.

rahim123 · 29 Gennaio 2023, 1:51pm

A un’ispezione più attenta sembra che questo sia un errore diverso.

Argomento		Risposte	Visualizzazioni
Unable to boostrap Discourse since last upgrade Self-hosting	4	776	Gennaio 22, 2023
Latest site upgrade not working Self-hosting	10	1855	Febbraio 22, 2022
" undefined method `deprecated?' for nil:NilClass" on rebuild Self-hosting	22	2531	Gennaio 23, 2023
Update Not Completed and Discourse not opening Self-hosting	16	650	Giugno 17, 2024
Bootstrap failure during most recent upgrade Self-hosting	6	646	Febbraio 3, 2023

Errore aggiornamento Discourse

Argomenti correlati