Hi, I want to install discourse with the one-click option. My logs look like this:
redis.1 | 410:M 31 Aug 2021 07:34:15.596 # Server initialized
redis.1 | 410:M 31 Aug 2021 07:34:15.871 * DB loaded from append only file: 0.275 seconds
redis.1 | 410:M 31 Aug 2021 07:34:15.871 * Ready to accept connections
web.1 | [405] Puma starting in cluster mode...
web.1 | [405] * Version 5.0.4 (ruby 2.7.2-p137), codename: Spoony Bard
web.1 | [405] * Min threads: 2, max threads: 4
web.1 | [405] * Environment: production
web.1 | [405] * Process workers: 1
web.1 | [405] * Preloading application
worker.1 | 2021-08-31T07:34:19.878Z pid=406 tid=diy INFO: Booting Sidekiq 6.1.2 with redis options {:host=>"localhost", :port=>6379, :namespace=>"sidekiq"}
logs.1 | Creating scope :open. Overwriting existing method Poll.open.
web.1 | [405] * Listening on unix:///var/www/discourse/tmp/sockets/nginx.http.sock
web.1 | [405] ! WARNING: Detected 3 Thread(s) started in app boot:
web.1 | [405] ! #<Thread:0x000055d018a50468 /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.0.3.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:334 sleep> - /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.0.3.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:337:in `sleep'
web.1 | [405] ! #<Thread:0x000055d01a463fa8 /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/message_bus-3.3.4/lib/message_bus.rb:712 sleep> - /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/redis-4.2.5/lib/redis/connection/ruby.rb:55:in `wait_readable'
web.1 | [405] ! #<Thread:0x000055d01a463c60 /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/message_bus-3.3.4/lib/message_bus/timer_thread.rb:38 sleep> - /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/message_bus-3.3.4/lib/message_bus/timer_thread.rb:130:in `sleep'
web.1 | [405] Use Ctrl-C to stop
logs.1 | Creating scope :open. Overwriting existing method Poll.open.
It looks like the installation completed successfully but then this WARNING: Detected 3 Thread(s) started in app bootappears. From now on nothing happens and the status check will never be successfull. Eventually the deploy times out.
Timed out after waiting for health check to return a successful response code at: http://0.0.0.0:80/srv/status
