Problemas ao construir um novo servidor

danielabc · Julho 18, 2023, 7:39am

Levei um tempo para encontrar um servidor barato, e quando o encontrei, ao tentar instalar, a instalação não conclui: demora muito e depois desconecta. Não entendo o porquê.

Configuration file at containers/app.yml updated successfully!

Updates successful. Rebuilding in 5 seconds.
Building app
x86_64 arch detected.
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
2.0.20230711-0100: Pulling from discourse/base
Digest: sha256:9c1157d9e106f7c891648fea201cb10ac40b374925bf6b26f5bfa549e2c10f4c
Status: Image is up to date for discourse/base:2.0.20230711-0100
docker.io/discourse/base:2.0.20230711-0100
/usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2023-07-18T07:20:31.767084 #1]  INFO -- : Reading from stdin
I, [2023-07-18T07:20:31.793958 #1]  INFO -- : > locale-gen $LANG && update-locale
I, [2023-07-18T07:20:32.019517 #1]  INFO -- : Generating locales (this might take a while)...
Generation complete.

I, [2023-07-18T07:20:32.020652 #1]  INFO -- : > mkdir -p /shared/postgres_run
I, [2023-07-18T07:20:32.030245 #1]  INFO -- :
I, [2023-07-18T07:20:32.031381 #1]  INFO -- : > chown postgres:postgres /shared/postgres_run
I, [2023-07-18T07:20:32.040590 #1]  INFO -- :
I, [2023-07-18T07:20:32.042002 #1]  INFO -- : > chmod 775 /shared/postgres_run
I, [2023-07-18T07:20:32.047709 #1]  INFO -- :
I, [2023-07-18T07:20:32.049046 #1]  INFO -- : > rm -fr /var/run/postgresql
I, [2023-07-18T07:20:32.065284 #1]  INFO -- :
I, [2023-07-18T07:20:32.067750 #1]  INFO -- : > ln -s /shared/postgres_run /var/run/postgresql
I, [2023-07-18T07:20:32.077791 #1]  INFO -- :
I, [2023-07-18T07:20:32.079627 #1]  INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
2023/07/18 07:20:32 socat[19] E connect(6, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): No such file or directory
I, [2023-07-18T07:20:32.106475 #1]  INFO -- :
I, [2023-07-18T07:20:32.107379 #1]  INFO -- : > rm -fr /shared/postgres_run/.s*
I, [2023-07-18T07:20:32.119624 #1]  INFO -- :
I, [2023-07-18T07:20:32.120153 #1]  INFO -- : > rm -fr /shared/postgres_run/*.pid
I, [2023-07-18T07:20:32.132718 #1]  INFO -- :
I, [2023-07-18T07:20:32.133565 #1]  INFO -- : > mkdir -p /shared/postgres_run/13-main.pg_stat_tmp
I, [2023-07-18T07:20:32.139615 #1]  INFO -- :
I, [2023-07-18T07:20:32.140993 #1]  INFO -- : > chown postgres:postgres /shared/postgres_run/13-main.pg_stat_tmp
I, [2023-07-18T07:20:32.151587 #1]  INFO -- :
I, [2023-07-18T07:20:32.168249 #1]  INFO -- : File > /etc/service/postgres/run  chmod: +x  chown:
I, [2023-07-18T07:20:32.181857 #1]  INFO -- : File > /etc/service/postgres/log/run  chmod: +x  chown:
I, [2023-07-18T07:20:32.195468 #1]  INFO -- : File > /etc/runit/3.d/99-postgres  chmod: +x  chown:
I, [2023-07-18T07:20:32.204314 #1]  INFO -- : File > /root/upgrade_postgres  chmod: +x  chown:
I, [2023-07-18T07:20:32.205247 #1]  INFO -- : > chown -R root /var/lib/postgresql/13/main
I, [2023-07-18T07:20:35.544754 #1]  INFO -- :
I, [2023-07-18T07:20:35.545754 #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-07-18T07:20:35.551542 #1]  INFO -- :
I, [2023-07-18T07:20:35.552298 #1]  INFO -- : > chown -R postgres:postgres /shared/postgres_data
I, [2023-07-18T07:20:35.644962 #1]  INFO -- :
I, [2023-07-18T07:20:35.646393 #1]  INFO -- : > chown -R postgres:postgres /var/run/postgresql
I, [2023-07-18T07:20:35.656200 #1]  INFO -- :
I, [2023-07-18T07:20:35.657734 #1]  INFO -- : > /root/upgrade_postgres
I, [2023-07-18T07:20:35.683335 #1]  INFO -- :
I, [2023-07-18T07:20:35.684776 #1]  INFO -- : > rm /root/upgrade_postgres
I, [2023-07-18T07:20:35.695826 #1]  INFO -- :
I, [2023-07-18T07:20:35.703076 #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-07-18T07:20:35.705066 #1]  INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-18T07:20:35.706158 #1]  INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-18T07:20:35.707013 #1]  INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-18T07:20:35.707926 #1]  INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-18T07:20:35.708906 #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-07-18T07:20:35.710022 #1]  INFO -- : > install -d -m 0755 -o postgres -g postgres /shared/postgres_backup
I, [2023-07-18T07:20:35.720021 #1]  INFO -- :
I, [2023-07-18T07:20:35.723036 #1]  INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-18T07:20:35.724284 #1]  INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-18T07:20:35.725498 #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-07-18T07:20:35.727899 #1]  INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres  peer in /etc/postgresql/13/main/pg_hba.conf
I, [2023-07-18T07:20:35.729886 #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-07-18T07:20:35.731825 #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-07-18T07:20:35.732577 #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-07-18T07:20:35.737408 #1]  INFO -- : > sleep 5
2023-07-18 07:20:35.956 UTC [42] LOG:  starting PostgreSQL 13.11 (Debian 13.11-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-18 07:20:35.959 UTC [42] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-18 07:20:35.959 UTC [42] LOG:  listening on IPv6 address "::", port 5432
2023-07-18 07:20:35.964 UTC [42] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-18 07:20:35.979 UTC [45] LOG:  database system was shut down at 2023-07-18 07:19:20 UTC
2023-07-18 07:20:35.990 UTC [42] LOG:  database system is ready to accept connections
I, [2023-07-18T07:20:40.747110 #1]  INFO -- :
I, [2023-07-18T07:20:40.747982 #1]  INFO -- : > su postgres -c 'createdb discourse' || true
2023-07-18 07:20:41.178 UTC [55] postgres@postgres ERROR:  database "discourse" already exists
2023-07-18 07:20:41.178 UTC [55] postgres@postgres STATEMENT:  CREATE DATABASE discourse;
createdb: error: database creation failed: ERROR:  database "discourse" already exists
I, [2023-07-18T07:20:41.183941 #1]  INFO -- :
I, [2023-07-18T07:20:41.184403 #1]  INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
2023-07-18 07:20:41.411 UTC [59] postgres@discourse ERROR:  role "discourse" already exists
2023-07-18 07:20:41.411 UTC [59] postgres@discourse STATEMENT:  create user discourse;
ERROR:  role "discourse" already exists
I, [2023-07-18T07:20:41.419164 #1]  INFO -- :
I, [2023-07-18T07:20:41.420200 #1]  INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true
I, [2023-07-18T07:20:41.515696 #1]  INFO -- : GRANT

I, [2023-07-18T07:20:41.516557 #1]  INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"'
I, [2023-07-18T07:20:41.691035 #1]  INFO -- : ALTER SCHEMA

I, [2023-07-18T07:20:41.691603 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2023-07-18T07:20:41.903095 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-18T07:20:41.904320 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists pg_trgm;"'
NOTICE:  extension "pg_trgm" already exists, skipping
I, [2023-07-18T07:20:42.063447 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-18T07:20:42.065027 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists vector;"'
NOTICE:  extension "vector" already exists, skipping
I, [2023-07-18T07:20:42.207308 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-18T07:20:42.209331 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2023-07-18T07:20:42.319538 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-18T07:20:42.321631 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists pg_trgm;"'
NOTICE:  extension "pg_trgm" already exists, skipping
I, [2023-07-18T07:20:42.455895 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-18T07:20:42.456795 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists vector;"'
NOTICE:  extension "vector" already exists, skipping
I, [2023-07-18T07:20:42.645308 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-18T07:20:42.646875 #1]  INFO -- : > sudo -u postgres psql discourse
I, [2023-07-18T07:20:42.653227 #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-07-18T07:20:42.967449 #1]  INFO -- : File > /var/lib/postgresql/take-database-backup  chmod: +x  chown: postgres:postgres
I, [2023-07-18T07:20:42.980161 #1]  INFO -- : File > /var/spool/cron/crontabs/postgres  chmod:   chown:
I, [2023-07-18T07:20:42.981146 #1]  INFO -- : > echo postgres installed!
I, [2023-07-18T07:20:42.992907 #1]  INFO -- : postgres installed!

I, [2023-07-18T07:20:43.015614 #1]  INFO -- : File > /etc/service/redis/run  chmod: +x  chown:
I, [2023-07-18T07:20:43.034164 #1]  INFO -- : File > /etc/service/redis/log/run  chmod: +x  chown:
I, [2023-07-18T07:20:43.053622 #1]  INFO -- : File > /etc/runit/3.d/10-redis  chmod: +x  chown:
I, [2023-07-18T07:20:43.055079 #1]  INFO -- : Replacing daemonize yes with  in /etc/redis/redis.conf
I, [2023-07-18T07:20:43.057030 #1]  INFO -- : Replacing (?-mix:^pidfile.*$) with  in /etc/redis/redis.conf
I, [2023-07-18T07:20:43.058579 #1]  INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data
I, [2023-07-18T07:20:43.065729 #1]  INFO -- :
I, [2023-07-18T07:20:43.066932 #1]  INFO -- : Replacing (?-mix:^logfile.*$) with logfile "" in /etc/redis/redis.conf
I, [2023-07-18T07:20:43.068198 #1]  INFO -- : Replacing (?-mix:^bind .*$) with  in /etc/redis/redis.conf
I, [2023-07-18T07:20:43.069206 #1]  INFO -- : Replacing (?-mix:^dir .*$) with dir /shared/redis_data in /etc/redis/redis.conf
I, [2023-07-18T07:20:43.070149 #1]  INFO -- : Replacing (?-mix:^protected-mode yes) with protected-mode no in /etc/redis/redis.conf
I, [2023-07-18T07:20:43.071046 #1]  INFO -- : Replacing # io-threads 4 with io-threads $redis_io_threads in /etc/redis/redis.conf
I, [2023-07-18T07:20:43.072023 #1]  INFO -- : > echo redis installed
I, [2023-07-18T07:20:43.076436 #1]  INFO -- : redis installed

I, [2023-07-18T07:20:43.077243 #1]  INFO -- : > cat /etc/redis/redis.conf | grep logfile
I, [2023-07-18T07:20:43.084825 #1]  INFO -- : logfile ""

I, [2023-07-18T07:20:43.085568 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-07-18T07:20:43.088373 #1]  INFO -- : > sleep 10
111:C 18 Jul 2023 07:20:43.106 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
111:C 18 Jul 2023 07:20:43.106 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=111, just started
111:C 18 Jul 2023 07:20:43.106 # Configuration loaded
111:M 18 Jul 2023 07:20:43.108 * monotonic clock: POSIX clock_gettime
111:M 18 Jul 2023 07:20:43.109 * Running mode=standalone, port=6379.
111:M 18 Jul 2023 07:20:43.109 # Server initialized
111:M 18 Jul 2023 07:20:43.110 # 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.
111:M 18 Jul 2023 07:20:43.110 * Loading RDB produced by version 7.0.7
111:M 18 Jul 2023 07:20:43.110 * RDB age 83 seconds
111:M 18 Jul 2023 07:20:43.111 * RDB memory usage when created 1.43 Mb
111:M 18 Jul 2023 07:20:43.112 * Done loading RDB, keys loaded: 32, keys expired: 0.
111:M 18 Jul 2023 07:20:43.112 * DB loaded from disk: 0.002 seconds
111:M 18 Jul 2023 07:20:43.112 * Ready to accept connections
I, [2023-07-18T07:20:53.097394 #1]  INFO -- :
I, [2023-07-18T07:20:53.098363 #1]  INFO -- : > thpoff echo "thpoff is installed!"
I, [2023-07-18T07:20:53.110927 #1]  INFO -- : thpoff is installed!

I, [2023-07-18T07:20:53.112864 #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-07-18T07:20:53.370880 #1]  INFO -- :
I, [2023-07-18T07:20:53.373398 #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-07-18T07:20:53.582231 #1]  INFO -- :
I, [2023-07-18T07:20:53.582730 #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-07-18T07:20:53.696659 #1]  INFO -- :
I, [2023-07-18T07:20:53.697305 #1]  INFO -- : > rm -f /etc/cron.d/anacron
I, [2023-07-18T07:20:53.703640 #1]  INFO -- :
I, [2023-07-18T07:20:53.708923 #1]  INFO -- : File > /etc/cron.d/anacron  chmod:   chown:
I, [2023-07-18T07:20:53.718910 #1]  INFO -- : File > /etc/runit/1.d/copy-env  chmod: +x  chown:
I, [2023-07-18T07:20:53.727068 #1]  INFO -- : File > /etc/service/unicorn/run  chmod: +x  chown:
I, [2023-07-18T07:20:53.734174 #1]  INFO -- : File > /etc/service/nginx/run  chmod: +x  chown:
I, [2023-07-18T07:20:53.747905 #1]  INFO -- : File > /etc/runit/3.d/01-nginx  chmod: +x  chown:
I, [2023-07-18T07:20:53.763210 #1]  INFO -- : File > /etc/runit/3.d/02-unicorn  chmod: +x  chown:
I, [2023-07-18T07:20:53.764279 #1]  INFO -- : Replacing # postgres with sv start postgres || exit 1 in /etc/service/unicorn/run
I, [2023-07-18T07:20:53.765392 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-07-18T07:20:53.779798 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git reset --hard
138:C 18 Jul 2023 07:20:53.810 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
138:C 18 Jul 2023 07:20:53.811 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=138, just started
138:C 18 Jul 2023 07:20:53.812 # Configuration loaded
138:M 18 Jul 2023 07:20:53.817 * monotonic clock: POSIX clock_gettime
138:M 18 Jul 2023 07:20:53.818 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
138:M 18 Jul 2023 07:20:53.820 # Failed listening on port 6379 (TCP), aborting.
Updating files: 100% (33425/33425), done.
I, [2023-07-18T07:21:07.274920 #1]  INFO -- : HEAD is now at 3140a4b2c DEV: invert pretty-text build logic (#22524)

I, [2023-07-18T07:21:07.275550 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git clean -f
I, [2023-07-18T07:21:07.628163 #1]  INFO -- :
I, [2023-07-18T07:21:07.628510 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse bash -c '
  set -o errexit
  if [ $(git rev-parse --is-shallow-repository) == "true" ]; then
      git remote set-branches --add origin main
      git remote set-branches origin tests-passed
      git fetch --depth 1 origin tests-passed
  else
      git fetch --tags --prune-tags --prune --force origin
  fi
'
From https://github.com/discourse/discourse
 - [deleted]             (none)     -> origin/avatar-utils
 - [deleted]             (none)     -> origin/capabilities-outside-service
 - [deleted]             (none)     -> origin/dependabot/npm_and_yarn/app/assets/javascripts/uppy/aws-s3-multipart-3.4.1
 - [deleted]             (none)     -> origin/dev/add-last-message-id-to-chat-channel-and-thread
 - [deleted]             (none)     -> origin/dev/make-sure-we-stream-data-to-csv-files-when-running-exports
 - [deleted]             (none)     -> origin/dev/make-sure-we-stream-data-to-csv-files-when-running-exports-2
 - [deleted]             (none)     -> origin/feature/status-on-mentions-on-updated-chat-messages
 - [deleted]             (none)     -> origin/feature/tracking-unread-thread-in-sidebar
 - [deleted]             (none)     -> origin/fix/hide-alternate-email-button
 - [deleted]             (none)     -> origin/update-history-modal
 - [deleted]             (none)     -> origin/upgrade-group-default-notifcations-modal
 - [deleted]             (none)     -> origin/ux_user_tips
   3140a4b2c..f76a9aab2  main                    -> origin/main
   a18f9e59c..a879fdf8a  0-bulk                  -> origin/0-bulk
 * [new branch]          0-fast-edit             -> origin/0-fast-edit
 * [new branch]          beta-version-bump       -> origin/beta-version-bump
 * [new branch]          dependabot/npm_and_yarn/app/assets/javascripts/uppy/aws-s3-multipart-3.5.0 -> origin/dependabot/npm_and_yarn/app/assets/javascripts/uppy/aws-s3-multipart-3.5.0
 * [new branch]          dependabot/npm_and_yarn/app/assets/javascripts/uppy/utils-5.4.1 -> origin/dependabot/npm_and_yarn/app/assets/javascripts/uppy/utils-5.4.1
 + d06ce80d6...c742e6722 dependabot/npm_and_yarn/app/assets/javascripts/uppy/xhr-upload-3.3.1 -> origin/dependabot/npm_and_yarn/app/assets/javascripts/uppy/xhr-upload-3.3.1  (forced update)
 * [new branch]          dev/add-chrome-options-system-specs -> origin/dev/add-chrome-options-system-specs
 * [new branch]          dev/generate-random-actions -> origin/dev/generate-random-actions
   6bb18917d..7b01b9b6b  dev/minio-s3-system-specs -> origin/dev/minio-s3-system-specs
 * [new branch]          dev/no-need-to-wrap-export-methods-into-enumerator-anymore -> origin/dev/no-need-to-wrap-export-methods-into-enumerator-anymore
   bc08b4040..e097c1ad7  dev/user-that-cant-chat-shouldnt-be-able-to-join-channel -> origin/dev/user-that-cant-chat-shouldnt-be-able-to-join-channel
 * [new branch]          dev/using-find-each-in-csv-exports -> origin/dev/using-find-each-in-csv-exports
 * [new branch]          discovery-named-outlets -> origin/discovery-named-outlets
 * [new branch]          edition-octane          -> origin/edition-octane
 * [new branch]          ember-5x-transition-to-route-on-controller -> origin/ember-5x-transition-to-route-on-controller
 * [new branch]          ember-5x-update-replace-with -> origin/ember-5x-update-replace-with
 * [new branch]          ember-5x-update-transition-to -> origin/ember-5x-update-transition-to
 * [new branch]          ember-5x-upgrade-replace-route-on-controller -> origin/ember-5x-upgrade-replace-route-on-controller
 + e0d06354e...190f80e7c feature/resolve-outdated-translation -> origin/feature/resolve-outdated-translation  (forced update)
   2be34487f..f16c32353  feature/show-status-on-mentions-when-user-havent-used-autocomplete -> origin/feature/show-status-on-mentions-when-user-havent-used-autocomplete
   d9a139fe0..af4da6e18  glimmer-lightbox        -> origin/glimmer-lightbox
 * [new branch]          issue/bookmark-no-method-disabled-error -> origin/issue/bookmark-no-method-disabled-error
 * [new branch]          issue/double-ups-thread-list -> origin/issue/double-ups-thread-list
 + 6c044ab81...414ae2fdc loic-migrate-chat-message-creator-to-a-service -> origin/loic-migrate-chat-message-creator-to-a-service  (forced update)
 * [new branch]          onebox-srcset           -> origin/onebox-srcset
 * [new branch]          pr-to-discourse-4115    -> origin/pr-to-discourse-4115
 * [new branch]          pr/22593                -> origin/pr/22593
   cec7c05da..461966e02  stable                  -> origin/stable
   3140a4b2c..f76a9aab2  tests-passed            -> origin/tests-passed
 * [new branch]          unsilence-modal-deprecation -> origin/unsilence-modal-deprecation
 * [new branch]          upgrade-create-invite-bulk-modal -> origin/upgrade-create-invite-bulk-modal
 t [tag update]          beta                    -> beta
 t [tag update]          latest-release          -> latest-release
 * [new tag]             v3.0.5                  -> v3.0.5
 * [new tag]             v3.1.0.beta6            -> v3.1.0.beta6
I, [2023-07-18T07:21:09.606648 #1]  INFO -- :
I, [2023-07-18T07:21:09.606965 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse bash -c '
  set -o errexit
  if [[ $(git symbolic-ref --short HEAD) == tests-passed ]] ; then
      git pull
  else
      git -c advice.detachedHead=false checkout tests-passed
  fi
'
Switched to a new branch 'tests-passed'
I, [2023-07-18T07:21:16.184613 #1]  INFO -- : Branch 'tests-passed' set up to track remote branch 'tests-passed' from 'origin'.

I, [2023-07-18T07:21:16.187511 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git config user.discourse-version tests-passed
I, [2023-07-18T07:21:16.212351 #1]  INFO -- :
I, [2023-07-18T07:21:16.213268 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp
I, [2023-07-18T07:21:16.222197 #1]  INFO -- :
I, [2023-07-18T07:21:16.223313 #1]  INFO -- : > cd /var/www/discourse && chown discourse:www-data tmp
I, [2023-07-18T07:21:16.233253 #1]  INFO -- :
I, [2023-07-18T07:21:16.233945 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2023-07-18T07:21:16.242401 #1]  INFO -- :
I, [2023-07-18T07:21:16.243169 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2023-07-18T07:21:16.249820 #1]  INFO -- :
I, [2023-07-18T07:21:16.250358 #1]  INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2023-07-18T07:21:16.258656 #1]  INFO -- :
I, [2023-07-18T07:21:16.259512 #1]  INFO -- : > cd /var/www/discourse && mkdir -p                    /shared/log/rails
I, [2023-07-18T07:21:16.268451 #1]  INFO -- :
I, [2023-07-18T07:21:16.269195 #1]  INFO -- : > cd /var/www/discourse && bash -c "touch -a           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log"
I, [2023-07-18T07:21:16.281321 #1]  INFO -- :
I, [2023-07-18T07:21:16.281832 #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-07-18T07:21:16.297333 #1]  INFO -- :
I, [2023-07-18T07:21:16.298037 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/{uploads,backups}"
I, [2023-07-18T07:21:16.307057 #1]  INFO -- :
I, [2023-07-18T07:21:16.307285 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/{uploads,backups} /var/www/discourse/public"
I, [2023-07-18T07:21:16.314905 #1]  INFO -- :
I, [2023-07-18T07:21:16.315207 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/tmp/{backups,restores}"
I, [2023-07-18T07:21:16.327453 #1]  INFO -- :
I, [2023-07-18T07:21:16.327923 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/tmp/{backups,restores} /var/www/discourse/tmp"
I, [2023-07-18T07:21:16.337563 #1]  INFO -- :
I, [2023-07-18T07:21:16.338041 #1]  INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp
I, [2023-07-18T07:21:16.361820 #1]  INFO -- :
I, [2023-07-18T07:21:16.362419 #1]  INFO -- : > cd /var/www/discourse && [ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete
I, [2023-07-18T07:21:16.368095 #1]  INFO -- :
I, [2023-07-18T07:21:16.385351 #1]  INFO -- : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run
I, [2023-07-18T07:21:16.386357 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2023-07-18T07:21:17.897337 #1]  INFO -- :
I, [2023-07-18T07:21:17.898152 #1]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2023-07-18T07:21:17.912590 #1]  INFO -- :
I, [2023-07-18T07:21:17.919972 #1]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2023-07-18T07:21:17.936043 #1]  INFO -- :
I, [2023-07-18T07:21:17.936400 #1]  INFO -- : > mkdir -p /var/nginx/cache
I, [2023-07-18T07:21:17.944092 #1]  INFO -- :
I, [2023-07-18T07:21:17.945746 #1]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2023-07-18T07:21:17.947171 #1]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2023-07-18T07:21:17.948443 #1]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2023-07-18T07:21:17.949618 #1]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2023-07-18T07:21:17.950700 #1]  INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2023-07-18T07:21:17.951540 #1]  INFO -- : > echo "done configuring web"
I, [2023-07-18T07:21:17.957300 #1]  INFO -- : done configuring web

I, [2023-07-18T07:21:17.958285 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
I, [2023-07-18T07:21:20.144662 #1]  INFO -- : Successfully installed bundler-2.4.13
1 gem installed

I, [2023-07-18T07:21:20.144850 #1]  INFO -- : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+
I, [2023-07-18T07:21:39.950404 #1]  INFO -- :
I, [2023-07-18T07:21:39.951223 #1]  INFO -- : > cd /var/www/discourse && if [ "tests-passed" != "tests-passed" ]; then
  rm -rf app/assets/javascripts/node_modules
fi
I, [2023-07-18T07:21:39.957453 #1]  INFO -- :
I, [2023-07-18T07:21:39.957605 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
warning " > @mixer/parallel-prettier@2.0.3" has unmet peer dependency "prettier@^2.0.0".
warning Resolution field "babel-plugin-ember-template-compilation@2.0.0" is incompatible with requested version "babel-plugin-ember-template-compilation@^2.0.1"
warning Resolution field "unset-value@2.0.1" is incompatible with requested version "unset-value@^1.0.0"
2023-07-18 07:24:36.093 UTC [42] LOG:  lock file "postmaster.pid" contains wrong PID: 2953 instead of 42
2023-07-18 07:24:36.093 UTC [42] LOG:  performing immediate shutdown because data directory lock file is invalid
2023-07-18 07:24:36.093 UTC [42] LOG:  received immediate shutdown request
2023-07-18 07:24:36.156 UTC [49] WARNING:  terminating connection because of crash of another server process
2023-07-18 07:24:36.156 UTC [49] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2023-07-18 07:24:36.156 UTC [49] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2023-07-18 07:24:36.160 UTC [369] WARNING:  terminating connection because of crash of another server process
2023-07-18 07:24:36.160 UTC [369] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2023-07-18 07:24:36.160 UTC [369] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2023-07-18 07:24:36.187 UTC [42] LOG:  database system is shut down
warning " > babel-plugin-debug-macros@0.4.0-pre1" has unmet peer dependency "@babel/core@^7.0.0".
warning "workspace-aggregator-1d4e40b4-d39e-4d17-9c25-b2c1596e5705 > discourse > @uppy/aws-s3@3.0.6" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-1d4e40b4-d39e-4d17-9c25-b2c1596e5705 > discourse > @uppy/aws-s3-multipart@3.1.3" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-1d4e40b4-d39e-4d17-9c25-b2c1596e5705 > discourse > @uppy/xhr-upload@3.1.1" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-1d4e40b4-d39e-4d17-9c25-b2c1596e5705 > discourse > @uppy/aws-s3 > @uppy/xhr-upload@3.3.0" has incorrect peer dependency "@uppy/core@^3.2.1".
I, [2023-07-18T07:26:44.621322 #1]  INFO -- : yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
$ yarn --cwd app/assets/javascripts $(node -e 'if(JSON.parse(process.env.npm_config_argv).original.includes(`--frozen-lockfile`)){console.log(`--frozen-lockfile`)}')
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
$ patch-package
patch-package 7.0.2
Applying patches...
@ember/jquery@2.0.0 ✔
ember-source@3.28.12 ✔
virtual-dom@2.1.1 ✔
Done in 122.73s.
Done in 265.36s.
yarn cache v1.22.19
success Cleared cache.
Done in 37.30s.

I, [2023-07-18T07:26:44.629706 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle config --local deployment true'
I, [2023-07-18T07:26:45.991719 #1]  INFO -- :
I, [2023-07-18T07:26:45.992992 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle config --local without "development test"'
I, [2023-07-18T07:26:46.363234 #1]  INFO -- : You are replacing the current local value of without, which is currently "test:development"

Houve um erro na minha atualização

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

Por favor, me ajude a corrigi-lo.

piffy · Julho 18, 2023, 7:48am

A mensagem de erro é “client_loop: send disconnect: Connection reset”. Esta é uma mensagem de erro do SSH, indicando que sua máquina perdeu a conexão com o servidor.

As causas mais prováveis são a queda da sua conexão com a internet ou o servidor estar ficando sem recursos (RAM ou espaço em disco) e encerrando a conexão.

Canapin · Julho 18, 2023, 7:51am

Você pode compartilhar as especificações do seu servidor (cpu, ram, tamanho do disco)?

danielabc · Julho 18, 2023, 11:00am

Olá, essa configuração

Meu Deus, mas meu servidor tem isso

Ed_S · Julho 18, 2023, 11:08am

Você precisa de pelo menos 1G de espaço de troca - você o tem?

free

irá lhe dizer.

Editar: Recomendo que você leia
Opinião de MKJ sobre Configuração de Implantação do Discourse
também. Você tem este aviso que não é bom em um sistema com pouca memória

Veja a seção Configuração do Kernel - você precisa desses efeitos, embora se são exatamente esses comandos pode depender de qual distribuição você está executando:

Michael K Johnson:

Configuração do Kernel

O Redis (um dos principais componentes em que o Discourse é construído) recomenda fortemente desabilitar páginas grandes transparentes, e eu também permito o overcommit de memória.
echo 'sys.kernel.mm.transparent_hugepage.enabled=never' > /etc/sysctl.d/10-huge-pages.conf
echo 'vm.overcommit_memory=1' > /etc/sysctl.d/90-vm_overcommit_memory.conf
sysctl --system

Editar: você pode verificar essas duas configurações importantes em seu servidor em execução assim

# cat /proc/sys/vm/overcommit_memory
1
# cat /sys/kernel/mm/transparent_hugepage/enabled
always madvise [never]

danielabc · Julho 18, 2023, 3:55pm

Desculpe, estou usando o Google Tradutor, não entendi direito, o que seria o espaço de troca (swap space)? Meu servidor não tem esse espaço de troca?

Ed_S · Julho 18, 2023, 4:23pm

Ok, tente o comando free na linha de comando e poste a saída.

danielabc · Julho 21, 2023, 5:19am

Acabei comprando outro servidor, mais robusto e potente, 4 Cores vCPU. 8 GB RAM, 50 GB NVMe, acontece que quando vou instalar o discourse nele, todas as etapas funcionam bem, não ocorrem erros, mas quando vou acessar o endereço do meu site aparece a seguinte mensagem “ERR_CONNECTION_TIMED_OUT” quando digito o comando discourse doctor ele sempre trava nessa tela e nunca sai dela.

Já reinstalei o servidor, já reinstalei o discourse, fiz todos os passos novamente, mas isso sempre acontece, não sei mais o que fazer.

danielabc · Julho 21, 2023, 2:02pm

a seguinte mensagem aparece

Ed_S · Julho 21, 2023, 2:06pm

Obrigado. Então, de fato, você não tem swap, e esse pode ser o motivo pelo qual as coisas continuam falhando. (Mas, hmm, você tem 8G de RAM, o que normalmente seria suficiente.)

Estes são os passos que o script oficial de instalação fará, quando decidir criar swap:

      ##
      ## derivado de https://meta.discourse.org/t/13880
      ##
      install -o root -g root -m 0600 /dev/null /swapfile
      fallocate -l 2G /swapfile
      mkswap /swapfile
      swapon /swapfile
      echo "/swapfile       swap    swap    auto      0       0" | tee -a /etc/fstab
      sysctl -w vm.swappiness=10
      echo 'vm.swappiness = 10' > /etc/sysctl.d/30-discourse-swap.conf

Sugiro que você, cuidadosamente, um por um, cole esses comandos. Em seguida, poste a transcrição de todos os comandos e toda a saída.

E então tente free novamente.

Ed_S · Julho 21, 2023, 2:07pm

Por favor, consulte os comandos que postei anteriormente e publique os resultados:

danielabc · Julho 21, 2023, 2:40pm

É assim que você coloca os códigos?

Mas então, eu troquei de servidor, comprei um mais robusto, faço a instalação normalmente, não vejo nenhum erro, mas quando acesso o site aparece “ERR_CONNECTION_TIMED_OUT” e o discourse doctor trava nessa tela.

danielabc · Julho 21, 2023, 2:40pm

Ed_S · Julho 21, 2023, 4:15pm

Talvez você não tenha atualizado seu DNS para apontar para seu novo servidor?

Nesse ponto, o médico está tentando acessar a página ‘privacy’ em seu fórum. Se o médico parar sem progresso, acho que é porque ele não consegue se conectar. (Embora deva haver um tempo limite de 3 segundos, então talvez este não seja o problema.)

Tente isto

wget -q --no-check-certificate --timeout=3 https://localhost/privacy  -O - |egrep generator

e nos diga o que você vê.

Existe um limite de taxa para renovar certificados com letsencrypt - é possível que você o tenha atingido, caso em que você precisa esperar uma semana.

Quando você fez a instalação mais recente, você viu isso novamente, o mesmo que relatou em sua primeira postagem?

client_loop: send disconnect: Connection reset

danielabc · Julho 21, 2023, 5:52pm

Quando tento o comando, nada acontece

Não me lembro se apareceu novamente, então terei que esperar 1 semana? Não há outra maneira de evitar que isso aconteça?

client_loop: send disconnect: Connection reset

Ed_S · Julho 21, 2023, 6:10pm

Não tenho certeza do que sugerir - as instruções para uma instalação padrão devem ser sempre bem-sucedidas. Em algum lugar, algo deu errado, e você não viu, ou não compartilhou. É muito difícil ajudar quando não podemos ver.

Notei que você alterou o comando wget - você não colou o comando exato. Portanto, não acho que possamos aprender algo com isso. Talvez você devesse tentar novamente.

Você não respondeu à pergunta sobre o DNS. Você deve tentar pingar seu nome de domínio totalmente qualificado

ping -c2 your.full.domain.name.com

mas é claro, usando seu próprio nome de domínio. Você deve verificar se o endereço IP que é relatado é exatamente o mesmo que o endereço IP do seu servidor.

Seria útil compartilhar a saída completa da sessão - é claro, remova quaisquer detalhes privados primeiro.

pfaffman · Julho 21, 2023, 7:10pm

Você executou o discourse-setup? Ele verificará se o seu DNS aponta para o seu servidor.

Se o seu DNS estiver correto e apontar para o seu servidor, então o seu problema provavelmente é que você tentou várias vezes quando o DNS não estava funcionando e atingiu os limites de taxa do Let’s Encrypt. As soluções fáceis são esperar uma semana ou usar um subdomínio diferente. Uma solução mais difícil é solicitar um novo certificado com vários domínios em Set up Let’s Encrypt with multiple domains / redirects, mas como você já está tendo problemas, recomendo que você use apenas um subdomínio diferente até resolver as coisas.

danielabc · Julho 21, 2023, 7:14pm

Desculpe, estou usando o Google Tradutor e muitas coisas para mim têm uma tradução estranha, não consigo entender, mas fiz o comando que você pediu e isso apareceu, estou escondendo meu IP


root@vmi1371983:~# ping -c2 dex-forum.com
PING dex-forum.com 56(84) bytes of data.
64 bytes from vmi1371983.contaboserver.net : icmp_seq=1 ttl=64 time=0.464 ms
64 bytes from vmi1371983.contaboserver.net : icmp_seq=2 ttl=64 time=0.066 ms

--- dex-forum.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1021ms
rtt min/avg/max/mdev = 0.066/0.265/0.464/0.199 ms
root@vmi1371983:~#

pfaffman · Julho 21, 2023, 7:17pm

O comando ssh dex-forum.com te conecta ao mesmo servidor que você está usando agora? Se sim, tente criar um novo registro A para www.dex-forum.com ou forum.dex-forum.com e usá-lo em vez disso. Eu recomendo usar www.dex-forum.com e forcewww.com para redirecionar seu domínio apex em vez de usar dex-forum.com de qualquer maneira.

danielabc · Julho 21, 2023, 9:28pm

Que estranho, quando uso o comando ssh root@myip consigo acessar meu servidor normalmente, mas quando uso o comando ssh dex-forum.com e digito a senha, ele diz “Permissão negada, tente novamente.” Não é a mesma senha?

Tópico		Respostas	Visualizações
Moving to New Server woes Support	16	474	10 de Março de 2025
Cloud installation is not working Self-hosting	11	1429	19 de Junho de 2024
Discourse Installation Failure on Fresh Server: FAILED TO BOOTSTRAP Self-hosting	11	1124	7 de Maio de 2023
Unable to boostrap Discourse since last upgrade Self-hosting	4	780	22 de Janeiro de 2023
Discourse stopped working all of a sudden Self-hosting	8	422	6 de Julho de 2024

Problemas ao construir um novo servidor

Tópicos relacionados