我的论坛更新软件时崩溃了，现在已经完全消失了。我收到了以下错误消息……
“哎呀
为这个讨论论坛提供支持的软件遇到了意外问题。我们对造成的不便深表歉意。
有关错误的详细信息已记录下来，并生成了自动通知。我们会对其进行查看。
无需进一步操作。但是，如果错误状况持续存在，您可以通过在该站点的反馈类别中发布讨论主题来提供更多详细信息，包括重现错误的步骤。”
我运行的论坛地址是 > https://forum.testpressing.org/
任何帮助都将不胜感激。
我也刚升级，我的容器无法构建然后崩溃。这非常不幸。
当它卡住时，不要重新启动它进行重建，因为我这样做时它会使整个东西崩溃……
这里也有同样的行为。我之前看到工作进程出现错误，重启了它……崩溃了……尝试重建。现在一直崩溃
/var/discourse# ./launcher rebuild app
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
2.0.20240825-0027: Pulling from discourse/base
Digest: sha256:6de68cb49198b5281f79ed9401b3fe818c854d220dcf0238549fe2f2adb19146
Status: Image is up to date for discourse/base:2.0.20240825-0027
/usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2024-08-27T21:43:42.091270 #1] INFO -- : Reading from stdin
I, [2024-08-27T21:43:42.110405 #1] INFO -- : File > /etc/service/postgres/run chmod: +x chown:
I, [2024-08-27T21:43:42.117678 #1] INFO -- : File > /etc/service/postgres/log/run chmod: +x chown:
I, [2024-08-27T21:43:42.125472 #1] INFO -- : File > /etc/runit/3.d/99-postgres chmod: +x chown:
I, [2024-08-27T21:43:42.132700 #1] INFO -- : File > /root/install_postgres chmod: +x chown:
I, [2024-08-27T21:43:42.139622 #1] INFO -- : File > /root/upgrade_postgres chmod: +x chown:
I, [2024-08-27T21:43:42.140454 #1] INFO -- : Replacing data_directory = '/var/lib/postgresql/13/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/13/main/postgresql.conf
I, [2024-08-27T21:43:42.141762 #1] INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/13/main/postgresql.conf
I, [2024-08-27T21:43:42.142675 #1] INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/13/main/postgresql.conf
I, [2024-08-27T21:43:42.143534 #1] INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/13/main/postgresql.conf
I, [2024-08-27T21:43:42.144382 #1] INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/13/main/postgresql.conf
I, [2024-08-27T21:43:42.144912 #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, [2024-08-27T21:43:42.145541 #1] INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/13/main/postgresql.conf
I, [2024-08-27T21:43:42.146355 #1] INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/13/main/postgresql.conf
I, [2024-08-27T21:43:42.146979 #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, [2024-08-27T21:43:42.147851 #1] INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres peer in /etc/postgresql/13/main/pg_hba.conf
I, [2024-08-27T21:43:42.148557 #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, [2024-08-27T21:43:42.149423 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*::1\\/128.*$) with host all all ::/0 md5 in /etc/postgresql/13/main/pg_hba.conf
I, [2024-08-27T21:43:42.149931 #1] INFO -- : > if [ -f /root/install_postgres ]; then
/root/install_postgres && rm -f /root/install_postgres
elif [ -e /shared/postgres_run/.s.PGSQL.5432 ]; then
socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
fi
2024/08/27 21:43:42 socat[28] E connect(, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): Connection refused
I, [2024-08-27T21:43:42.217004 #1] INFO -- : Generating locales (this might take a while)...
Generation complete.
I, [2024-08-27T21:43:42.217327 #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, [2024-08-27T21:43:42.220344 #1] INFO -- : Terminating async processes
2024-08-27 21:43:42.300 UTC [30] LOG: starting PostgreSQL 13.16 (Debian 13.16-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-08-27 21:43:42.300 UTC [30] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-08-27 21:43:42.300 UTC [30] LOG: listening on IPv6 address "::", port 5432
2024-08-27 21:43:42.303 UTC [30] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-08-27 21:43:42.310 UTC [31] LOG: database system was interrupted; last known up at 2024-08-27 21:41:14 UTC
2024-08-27 21:43:42.503 UTC [31] LOG: database system was not properly shut down; automatic recovery in progress
2024-08-27 21:43:42.507 UTC [31] LOG: redo starts at 38C/55C02EA0
2024-08-27 21:43:42.507 UTC [31] LOG: invalid record length at 38C/55C02ED8: wanted 24, got 0
2024-08-27 21:43:42.507 UTC [31] LOG: redo done at 38C/55C02EA0
2024-08-27 21:43:42.540 UTC [30] LOG: database system is ready to accept connections
它就一直卡在那里……从来没有给容器分配端口，也没有启动 rails 应用，据我所知。
如果您运行
./launcher start app
它会重新启动吗？
不……有一个僵尸容器是 ./launcher rebuild app 创建的，它会产生上述输出。这个容器看起来是这样的。它从 discourse 基础镜像开始构建，但随后会挂起，如上所述。它没有注册为 discourse 应用。
/var/discourse# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
02ae320b72a0 discourse/base:2.0.20240825-0027 “/bin/bash -c ‘/usr/…” 7 minutes ago Up 7 minutes sleepy_driscoll
当我运行 ./launcher start app 时，它会出错，因为它试图启动一个新应用，而 PSQL 在僵尸容器上运行在 5432 端口。如果我删除僵尸容器（和/或镜像），它会创建一个新容器并像我之前帖子中的日志一样挂起。
非常令人沮丧和不幸。我不知道我们是怎么走到这一步的。我在 app.yaml 中禁用了所有插件并尝试重建。
我认为这些日志与我论坛的情况最相关
2024-08-27 21:43:42.300 UTC [30] LOG: starting PostgreSQL 13.16 (Debian 13.16-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-08-27 21:43:42.300 UTC [30] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-08-27 21:43:42.300 UTC [30] LOG: listening on IPv6 address "::", port 5432
2024-08-27 21:43:42.303 UTC [30] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-08-27 21:43:42.310 UTC [31] LOG: database system was interrupted; last known up at 2024-08-27 21:41:14 UTC
2024-08-27 21:43:42.503 UTC [31] LOG: database system was not properly shut down; automatic recovery in progress
2024-08-27 21:43:42.507 UTC [31] LOG: redo starts at 38C/55C02EA0
2024-08-27 21:43:42.507 UTC [31] LOG: invalid record length at 38C/55C02ED8: wanted 24, got 0
2024-08-27 21:43:42.507 UTC [31] LOG: redo done at 38C/55C02EA0
2024-08-27 21:43:42.540 UTC [30] LOG: database system is ready to accept connections
它一直卡在这里……从未编译资产，从未启动 rails 应用程序，从未启动 redis 等等。
1 个赞
好的……所以至少有一小部分人遇到了这个问题 
更多信息：
/var/discourse# ./launcher start app
检测到 x86_64 架构。
警告：containers/app.yml 文件是全局可读的。您可以通过运行以下命令来保护此文件：chmod o-rwx containers/app.yml
+ /usr/bin/docker run --shm-size=512m -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=8 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_HEAP_GROWTH_MAX_SLOTS=40000 -e RUBY_GC_HEAP_INIT_SLOTS=400000 -e RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=1.5 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e LETSENCRYPT_DIR=/shared/letsencrypt -e DISCOURSE_FORCE_HTTPS=true -e DISCOURSE_HOSTNAME=redacted.com -e DISCOURSE_DEVELOPER_EMAILS=redacted -e DISCOURSE_SMTP_ADDRESS=smtp.redacted.com -e DISCOURSE_SMTP_PORT=587 -e DISCOURSE_SMTP_USER_NAME=postmaster@redacted -e DISCOURSE_SMTP_PASSWORD=redacted -e DISCOURSE_SMTP_ENABLE_START_TLS=true -e LETSENCRYPT_ACCOUNT_EMAIL=redacted -h discourse-beta-ubuntu-app -e DOCKER_HOST_IP=172.17.0.1 --name app -t -p 80:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:52:ee:ee:62:b2 local_discourse/app /sbin/boot
无法在本地找到镜像 'local_discourse/app:latest'
/usr/bin/docker: daemon 的错误响应：拉取 'local_discourse/app' 镜像失败，仓库不存在或可能需要 'docker login'。
请参阅 '/usr/bin/docker run --help'。
当我尝试启动应用程序时 
……它抱怨镜像 local_discourse/app 不存在。这是正确的：
/var/discourse# docker images
仓库 标签 镜像 ID 创建时间 大小
discourse/base 2.0.20240825-0027 9dc96b6115cb 2天前 3.38GB
但由于数据库挂起，尝试拉取和构建镜像不起作用。
2 个赞