Keywords: Discourse - AWS - Technical issue - Other
Description:
After migrating discourse version 2.4.1 to 2.5.0, discourse server alone not getting up.
Discourse log
==> apps/discourse/htdocs/log/sidekiq.log <==
/opt/bitnami/apps/discourse/htdocs/config/environment.rb:4:in <top (required)>'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:inrequire'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in block in require'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:291:inload_dependency'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in require'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/cli.rb:252:inboot_system'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/cli.rb:37:in run'
/opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/bin/sidekiq:31:in'
/opt/bitnami/apps/discourse/htdocs/bin/sidekiq:29:in load'
/opt/bitnami/apps/discourse/htdocs/bin/sidekiq:29:in'
