没有错误，实例在重建后无法恢复

MarcP · 2023 年3 月 8 日 17:08

多年来，在重建后，我的实例第一次无法恢复。我最后一次成功的重建是在昨天。

是不是有什么新的提交可能导致了这种情况？

pfaffman · 2023 年3 月 8 日 17:12

有什么症状？

如果我运行 tail -f /var/discourse/shared/standalone/log/rails/production.log 会看到什么？

MarcP · 2023 年3 月 8 日 17:16

Done in 89.60s.
Downloading MaxMindDB...
Compressing Javascript and Generating Source Maps

I, [2023-03-08T17:11:55.996529 #1]  INFO -- : File > /usr/local/bin/discourse  chmod: +x  chown:
I, [2023-03-08T17:11:55.999205 #1]  INFO -- : File > /usr/local/bin/rails  chmod: +x  chown:
I, [2023-03-08T17:11:56.001899 #1]  INFO -- : File > /usr/local/bin/rake  chmod: +x  chown:
I, [2023-03-08T17:11:56.004616 #1]  INFO -- : File > /usr/local/bin/rbtrace  chmod: +x  chown:
I, [2023-03-08T17:11:56.007306 #1]  INFO -- : File > /usr/local/bin/stackprof  chmod: +x  chown:
I, [2023-03-08T17:11:56.010710 #1]  INFO -- : File > /etc/update-motd.d/10-web  chmod: +x  chown:
I, [2023-03-08T17:11:56.012746 #1]  INFO -- : File > /etc/logrotate.d/rails  chmod:   chown:
I, [2023-03-08T17:11:56.014343 #1]  INFO -- : File > /etc/logrotate.d/nginx  chmod:   chown:
I, [2023-03-08T17:11:56.017963 #1]  INFO -- : File > /etc/runit/1.d/00-ensure-links  chmod: +x  chown:
I, [2023-03-08T17:11:56.020609 #1]  INFO -- : File > /etc/runit/1.d/01-cleanup-web-pids  chmod: +x  chown:
I, [2023-03-08T17:11:56.023663 #1]  INFO -- : File > /root/.bash_profile  chmod: 644  chown:
I, [2023-03-08T17:11:56.026021 #1]  INFO -- : File > /usr/local/etc/ImageMagick-7/policy.xml  chmod:   chown:
I, [2023-03-08T17:11:56.026795 #1]  INFO -- : Replacing (?-mix:server.+{) with limit_req_zone $binary_remote_addr zone=flood:10m rate=$reqs_per_secondr/s;
limit_req_zone $binary_remote_addr zone=bot:10m rate=$reqs_per_minuter/m;
limit_req_status 429;
limit_conn_zone $binary_remote_addr zone=connperip:10m;
limit_conn_status 429;
server {
 in /etc/nginx/conf.d/discourse.conf
I, [2023-03-08T17:11:56.026984 #1]  INFO -- : Replacing (?-mix:location @discourse {) with location @discourse {
  limit_conn connperip $conn_per_ip;
  limit_req zone=flood burst=$burst_per_second nodelay;
  limit_req zone=bot burst=$burst_per_minute nodelay; in /etc/nginx/conf.d/discourse.conf
I, [2023-03-08T17:11:56.029658 #1]  INFO -- : File > /etc/runit/1.d/remove-old-socket  chmod: +x  chown:
I, [2023-03-08T17:11:56.032272 #1]  INFO -- : File > /etc/runit/3.d/remove-old-socket  chmod: +x  chown:
I, [2023-03-08T17:11:56.032398 #1]  INFO -- : Replacing (?-mix:listen 80;) with listen unix:/shared/nginx.http.sock;
set_real_ip_from unix:;
 in /etc/nginx/conf.d/discourse.conf
I, [2023-03-08T17:11:56.032577 #1]  INFO -- : Replacing (?-mix:listen 443 ssl http2;) with listen unix:/shared/nginx.https.sock ssl http2;
set_real_ip_from unix:; in /etc/nginx/conf.d/discourse.conf
I, [2023-03-08T17:11:56.035350 #1]  INFO -- : File > /tmp/add-cloudflare-ips  chmod: +x  chown:
I, [2023-03-08T17:11:56.035435 #1]  INFO -- : > /tmp/add-cloudflare-ips
I, [2023-03-08T17:11:56.359453 #1]  INFO -- : CloudFlare IPs:
set_real_ip_from 173.245.48.0/20; set_real_ip_from 103.21.244.0/22; set_real_ip_from 103.22.200.0/22; set_real_ip_from 103.31.4.0/22; set_real_ip_from 141.101.64.0/18; set_real_ip_from 108.162.192.0/18; set_real_ip_from 190.93.240.0/20; set_real_ip_from 188.114.96.0/20; set_real_ip_from 197.234.240.0/22; set_real_ip_from 198.41.128.0/17; set_real_ip_from 162.158.0.0/15; set_real_ip_from 104.16.0.0/13; set_real_ip_from 104.24.0.0/14; set_real_ip_from 172.64.0.0/13; set_real_ip_from 131.0.72.0/22; set_real_ip_from 2400:cb00::/32; set_real_ip_from 2606:4700::/32; set_real_ip_from 2803:f800::/32; set_real_ip_from 2405:b500::/32; set_real_ip_from 2405:8100::/32; set_real_ip_from 2a06:98c0::/29; set_real_ip_from 2c0f:f248::/32;

I, [2023-03-08T17:11:56.359655 #1]  INFO -- : > rm /tmp/add-cloudflare-ips
I, [2023-03-08T17:11:56.361599 #1]  INFO -- :
I, [2023-03-08T17:11:56.361818 #1]  INFO -- : > echo "Beginning of custom commands"
I, [2023-03-08T17:11:56.363535 #1]  INFO -- : Beginning of custom commands

I, [2023-03-08T17:11:56.367829 #1]  INFO -- : File > /etc/service/monerochan_merchant_rpc/run  chmod: +x  chown:
I, [2023-03-08T17:11:56.368034 #1]  INFO -- : > echo "End of custom commands"
I, [2023-03-08T17:11:56.369958 #1]  INFO -- : End of custom commands

I, [2023-03-08T17:11:56.370117 #1]  INFO -- : Terminating async processes
I, [2023-03-08T17:11:56.370225 #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-03-08T17:11:56.370261 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
2023-03-08 17:11:56.370 UTC [42] LOG:  received fast shutdown request
103:signal-handler (1678295516) Received SIGTERM scheduling shutdown...
2023-03-08 17:11:56.372 UTC [42] LOG:  aborting any active transactions
2023-03-08 17:11:56.374 UTC [42] LOG:  background worker "logical replication launcher" (PID 51) exited with exit code 1
2023-03-08 17:11:56.375 UTC [46] LOG:  shutting down
2023-03-08 17:11:56.392 UTC [42] LOG:  database system is shut down
103:M 08 Mar 2023 17:11:56.469 # User requested shutdown...
103:M 08 Mar 2023 17:11:56.469 * Saving the final RDB snapshot before exiting.
103:M 08 Mar 2023 17:11:56.570 * DB saved on disk
103:M 08 Mar 2023 17:11:56.570 # Redis is now ready to exit, bye bye...
sha256:422bd26e098f3af0623647ebce02770ac1608bfac07260aeb5469ab975696363
a0b91a9cc45e8666352e172143854705faa97b38208fcfe0650ea929989b8570
Removing old container
+ /usr/bin/docker rm app
app

➜  discourse git:(main) ✗ tail -f /var/discourse/shared/standalone/log/rails/production.log


Bye!
Deprecation notice: (siwe) full_screen_login is now forced. The full_screen_login parameter can be removed from the auth_provider. (removal in Discourse 2.9.0)
At /var/www/discourse/lib/plugin/instance.rb:763:in `public_send`
Migrating to MakeChatMentionNotificationIdNullable (20230227172543)
Migrating to DropBadgeGrantedTitleColumn (20230228105851)
Migrating to AddExternalToSidebarUrls (20230303015952)
Theme setting type has changed but cannot be converted.

 #<ThemeSettingsManager::Upload:0x00007f60ff714e38 @name=:background_image, @default="", @theme=#<Theme id: 31, name: "Search Banner", user_id: 2, created_at: "2021-08-03 16:38:09.042735000 +0000", updated_at: "2021-08-03 17:01:41.329058000 +0000", compiler_version: 0, user_selectable: false, hidden: false, color_scheme_id: nil, remote_theme_id: 29, component: true, enabled: true, auto_update: true>, @opts={:description=>"background image for the banner", :textarea=>false, :json_schema=>nil, :refresh=>false}, @types={:integer=>0, :float=>1, :string=>2, :bool=>3, :list=>4, :enum=>5, :upload=>6}>
Bye!
Deprecation notice: (siwe) full_screen_login is now forced. The full_screen_login parameter can be removed from the auth_provider. (removal in Discourse 2.9.0)
At /var/www/discourse/lib/plugin/instance.rb:763:in `public_send`
Migrating to MakeChatMentionNotificationIdNullable (20230227172543)
Migrating to DropBadgeGrantedTitleColumn (20230228105851)
Migrating to AddExternalToSidebarUrls (20230303015952)
Theme setting type has changed but cannot be converted.

 #<ThemeSettingsManager::Upload:0x00007f60ff714e38 @name=:background_image, @default="", @theme=#<Theme id: 31, name: "Search Banner", user_id: 2, created_at: "2021-08-03 16:38:09.042735000 +0000", updated_at: "2021-08-03 17:01:41.329058000 +0000", compiler_version: 0, user_selectable: false, hidden: false, color_scheme_id: nil, remote_theme_id: 29, component: true, enabled: true, auto_update: true>, @opts={:description=>"background image for the banner", :textarea=>false, :json_schema=>nil, :refresh=>false}, @types={:integer=>0, :float=>1, :string=>2, :bool=>3, :list=>4, :enum=>5, :upload=>6}>

我没有看到任何异常。也许 Nginx 的配置行有些问题？（我的 Nginx 配置来自官方 Discourse 维护页面教程）。

pfaffman · 2023 年3 月 8 日 17:19

如果您访问您的网站会发生什么？可以分享网址吗？

MarcP · 2023 年3 月 8 日 17:21

不希望在公开场合说，但我会私信你。

编辑：已将 Nginx 重新路由以忽略 502 错误等。只是一个网关错误。

pfaffman · 2023 年3 月 8 日 17:57

您需要查看日志文件，以了解在尝试加载网站时发生的错误。

如果 Cloudflare（或其他服务）阻止浏览器访问网站，那么您或许可以查看日志以查找 500 错误，从而了解问题所在。

您或许可以从容器内部使用 curl localhost 命令。

MarcP · 2023 年3 月 8 日 17:58

这是个很好的反馈。我会尝试一下，然后回复。

编辑：嗯，我不认为日志里有什么变化，但我看到了以下内容。

➜ ~ tail -f /var/discourse/shared/standalone/log/rails/production.log
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/subscribe.rb:14:in `subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:288:in `_subscription'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/pubsub.rb:20:in `block in subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `block in synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/pubsub.rb:19:in `subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/backends/redis.rb:302:in `global_subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:768:in `global_subscribe_thread'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:739:in `block in new_subscriber_thread'

在我的 nginx 中我看到了：

2023/03/08 17:58:38 [crit] 115962#115962: *448 connect() to unix:/var/discourse/shared/standalone/nginx.http.sock failed (2: No such file or directory) while connecting to upstream, client: IP.XXX server: [domain.com](http://domain.com), request: "GET /service-worker.js HTTP/2.0", upstream: "http://unix:/var/discourse/shared/standalone/nginx.http.sock:/service-worker.js", host: "domain.com", referrer: "https://domain.com/service-worker.js"
2023/03/08 17:59:32 [notice] 318573#318573: signal process started

这有帮助吗？或者我应该完全撤销这个 nginx 设置？

Falco · 2023 年3 月 8 日 18:19

如果您能分享完整的堆栈跟踪（该文件的更多行），我们可以为您提供帮助。

MarcP · 2023 年3 月 8 日 18:30

已完成 200 OK，耗时 25 毫秒（视图：0.1 毫秒 | ActiveRecord：0.0 毫秒 | 内存分配：17734）
于 2023-03-08 16:20:41 +0000 开始为 [IP 已移除] 处理 GET "/categories_and_latest"
正在处理 CategoriesController#categories_and_latest，格式为 JSON
  已渲染文本模板（耗时：0.0 毫秒 | 内存分配：1）
已完成 200 OK，耗时 112 毫秒（视图：0.2 毫秒 | ActiveRecord：0.0 毫秒 | 内存分配：63242）
于 2023-03-08 16:21:00 +0000 开始为 [IP 已移除] 处理 GET "/"
正在处理 CategoriesController#index，格式为 HTML
  已渲染 categories/index.html.erb（位于 layouts/crawler 布局内）（耗时：1.4 毫秒 | 内存分配：1135）
  已渲染布局 layouts/crawler.html.erb（耗时：6.7 毫秒 | 内存分配：3536）
已完成 200 OK，耗时 75 毫秒（视图：7.7 毫秒 | ActiveRecord：0.0 毫秒 | 内存分配：41712）
于 2023-03-08 16:21:35 +0000 开始为 [IP 已移除] 处理 GET "/notifications?limit=30&recent=true&bump_last_seen_reviewable=true"
正在处理 NotificationsController#index，格式为 JSON
  参数：{"limit"=>"30", "recent"=>"true", "bump_last_seen_reviewable"=>"true"}
已完成 200 OK，耗时 60 毫秒（视图：0.1 毫秒 | ActiveRecord：0.0 毫秒 | 内存分配：30822）
于 2023-03-08 16:22:00 +0000 开始为 [IP 已移除] 处理 GET "/"
正在处理 CategoriesController#index，格式为 HTML
  已渲染 categories/index.html.erb（位于 layouts/crawler 布局内）（耗时：1.1 毫秒 | 内存分配：1135）
  已渲染布局 layouts/crawler.html.erb（耗时：5.4 毫秒 | 内存分配：3536）
已完成 200 OK，耗时 86 毫秒（视图：6.1 毫秒 | ActiveRecord：0.0 毫秒 | 内存分配：41842）
正在关闭
正在终止静默线程
调度器正在退出...
获取任务时出错：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）
无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）订阅失败，将在 1 秒后重试。调用堆栈 /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:398:in `rescue in establish_connection'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:379:in `establish_connection'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:115:in `block in connect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:344:in `with_reconnect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:114:in `connect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:409:in `ensure_connected'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:175:in `block in call_loop'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:331:in `with_socket_timeout'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:174:in `call_loop'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/subscribe.rb:44:in `subscription'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/subscribe.rb:14:in `subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:288:in `_subscription'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/pubsub.rb:20:in `block in subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `block in synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/pubsub.rb:19:in `subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/backends/redis.rb:302:in `global_subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:768:in `global_subscribe_thread'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:739:in `block in new_subscriber_thread'
获取任务时出错：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）
获取任务时出错：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）
获取任务时出错：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）
任务异常：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）

获取任务时出错：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）
任务异常：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）

任务异常：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）

任务异常：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）

任务异常：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）

任务异常：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）

处理任务失败：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）["/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:398:in `rescue in establish_connection'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:379:in `establish_connection'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:115:in `block in connect'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:344:in `with_reconnect'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:114:in `connect'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:409:in `ensure_connected'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:85:in `block in profile_method'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:270:in `block in send_command'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `synchronize'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `send_command'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/scripting.rb:110:in `_eval'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/scripting.rb:97:in `evalsha'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/backends/redis.rb:463:in `cached_eval'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/backends/redis.rb:150:in `publish'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:391:in `publish'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:751:in `block in new_subscriber_thread'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/timer_thread.rb:117:in `do_work'", "/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/timer_thread.rb:95:in `block (2 levels) in queue'"]
正在暂停以允许任务完成...
心跳检测：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）
无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）订阅失败，将在 1 秒后重试。调用堆栈 /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:398:in `rescue in establish_connection'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:379:in `establish_connection'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:115:in `block in connect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:344:in `with_reconnect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:114:in `connect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:409:in `ensure_connected'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:85:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:270:in `block in send_command'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `send_command'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/strings.rb:191:in `get'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/backends/redis.rb:401:in `process_global_backlog'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/backends/redis.rb:286:in `block in global_subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/backends/redis.rb:299:in `global_subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:768:in `global_subscribe_thread'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:739:in `block in new_subscriber_thread'
任务异常：无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）

再见！
弃用通知：(siwe) full_screen_login 现已强制启用。可以从 auth_provider 中移除 full_screen_login 参数。（将在 Discourse 2.9.0 中移除）
位于 /var/www/discourse/lib/plugin/instance.rb:763:in `public_send`
正在迁移至 MakeChatMentionNotificationIdNullable (20230227172543)
正在迁移至 DropBadgeGrantedTitleColumn (20230228105851)
正在迁移至 AddExternalToSidebarUrls (20230303015952)
主题设置类型已更改，但无法转换。

 #<ThemeSettingsManager::Upload:0x00007f60ff714e38 @name=:background_image, @default="", @theme=#<Theme id: 31, name: "Search Banner", user_id: 2, created_at: "2021-08-03 16:38:09.042735000 +0000", updated_at: "2021-08-03 17:01:41.329058000 +0000", compiler_version: 0, user_selectable: false, hidden: false, color_scheme_id: nil, remote_theme_id: 29, component: true, enabled: true, auto_update: true>, @opts={:description=>"背景图片用于横幅", :textarea=>false, :json_schema=>nil, :refresh=>false}, @types={:integer=>0, :float=>1, :string=>2, :bool=>3, :list=>4, :enum=>5, :upload=>6}>
弃用通知：(siwe) full_screen_login 现已强制启用。可以从 auth_provider 中移除 full_screen_login 参数。（将在 Discourse 2.9.0 中移除）
位于 /var/www/discourse/lib/plugin/instance.rb:763:in `public_send`
无法连接到 localhost:6379 上的 Redis（Errno::EADDRNOTAVAIL）订阅失败，将在 1 秒后重试。调用堆栈 /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:398:in `rescue in establish_connection'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:379:in `establish_connection'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:115:in `block in connect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:344:in `with_reconnect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:114:in `connect'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:409:in `ensure_connected'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:175:in `block in call_loop'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:331:in `with_socket_timeout'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:174:in `call_loop'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/subscribe.rb:44:in `subscription'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/subscribe.rb:14:in `subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:288:in `_subscription'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/pubsub.rb:20:in `block in subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `block in synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:265:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/pubsub.rb:19:in `subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus/backends/redis.rb:302:in `global_subscribe'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:768:in `global_subscribe_thread'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.2/lib/message_bus.rb:739:in `block in new_subscriber_thread'

这是从“致命”重建发生之前，到移除插件等之后又尝试了几次的日志。

MarcP · 2023 年3 月 8 日 21:19

我删除了以下插件，现在我的实例又能启动了。

所以这可能与其中一个插件的近期提交有关。

pfaffman · 2023 年3 月 8 日 21:27

错误发生在 rails 启动时，因此没有进入日志：

root@test1-web-only:/var/www/discourse# rails c
bundler: failed to load command: pry (/var/www/discourse/vendor/bundle/ruby/3.2.0/bin/pry)
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.6.7/lib/zeitwerk/loader/helpers.rb:135:in `const_get': uninitialized constant PluginInstance (NameError)

    parent.const_get(cname, false)
          ^^^^^^^^^^
Did you mean?  PluginStore

我在另一个安装上复现了此错误。我现在正在尝试找出是哪个插件导致的问题。

Falco · 2023 年3 月 8 日 21:44

请分享插件列表和每个插件的提交记录？

davidkingham · 2023 年3 月 8 日 21:45

我已经发现是Automation和其他插件冲突了。只启用Automation可以重新构建，但启用其他插件就不行了。我快找到另一个罪魁祸首了……

Falco · 2023 年3 月 8 日 21:46

我们实际上在自动化和分配中都存在一个 bug，刚刚都修复了。所以现在重新构建将可以修复它。

抄送 @pfaffman

pfaffman · 2023 年3 月 8 日 21:47

有人刚告诉我

这是插件列表（还有一个私有的）

          - git clone https://github.com/discourse/docker_manager.git
            #- git clone https://github.com/discourse/discourse-docs.git
            #- git clone https://github.com/discourse/discourse-solved.git
            #- git clone https://github.com/discourse/discourse-voting.git
            #- git clone https://github.com/discourse/discourse-reactions.git
            #- git clone https://github.com/discourse/discourse-canned-replies.git
            #- git clone https://github.com/jomaxro/discourse-plugin-site-setting-override.git
            #- git clone https://github.com/discourse/discourse-automation.git

我能够获取到

pfaffman · 2023 年3 月 8 日 21:47

啊哈。所以，我本应确认损坏插件的测试，反而确认了修复。

davidkingham · 2023 年3 月 8 日 21:48

哈哈，我也是，这时间点真是绝了！谢谢你，Falco。

MarcP · 2023 年3 月 8 日 21:55

我将尝试现在重建并恢复已删除的插件。以防万一，这是其余的插件：

编辑：已安装的 3 个已删除插件现已恢复正常。谢谢团队！

discourse 12436d05	最新
docker_manager e90c8f55	最新
discourse-adplugin bfd4438b	最新
discourse-calendar adca3f65	最新
discourse-category-lockdown 2cf5f064	最新
discourse-chat-integration 75cf4136	最新
discourse-chatbot eb9c50ae	最新
discourse-data-explorer 389b8e15	最新
discourse-docs 63bb4629	最新
discourse-encrypt 0f3c612b	最新
discourse-formatting-toolbar d99f3c6d	最新
discourse-gamification a842e183	最新
discourse-patreon 778829aa	最新
discourse-policy b86d520c	最新
discourse-pushover-notifications 30711ac7	最新
discourse-siwe 752687c8	最新
discourse-solved 2c1c64af	最新
discourse-staff-alias 10ae5329	最新
discourse-telegram-notifications d9886998	最新
discourse-whos-online aeee51e4	最新

话题		回复	浏览量
502 bad gateway with clean rebuild and no plugins except discourse docker Self-hosting	5	425	2024 年2 月 14 日
Site down, rebuild failed due to landing plugin Self-hosting	16	1509	2022 年7 月 22 日
Tried to install plugin destroyed site, can't run rebuild Self-hosting	11	1273	2020 年9 月 2 日
Help,rebuild Error Self-hosting	3	651	2022 年2 月 7 日
Latest site upgrade not working Self-hosting	11	1789	2022 年2 月 22 日

没有错误，实例在重建后无法恢复

相关话题