[ARCHIVED] Canvas not running after production setup

[Abhigyan]

I setup Canvas on Ubuntu 16.04 server. I have used NGINX / passenger for deployment. The canvas is getting stuck and I am getting timeout error in passenger log

Production.log

[- -] (0.8ms) SELECT * FROM unnest(current_schemas(false))
[- -] (0.8ms) SELECT * FROM unnest(current_schemas(false)) [production:1 master]
[- -] Switchman::Shard Load (1.9ms) SELECT "switchman_shards".* FROM "switchman_shards" WHERE "switchman_shards"."database_server_id" = 'test' AND "switchman_shards"."name" IS NULL ORDER BY "switchman_shards"."id" ASC LIMIT 1 [production:1 master]
[- -] Switchman::Shard Load (0.9ms) SELECT "switchman_shards".* FROM "switchman_shards" WHERE "switchman_shards"."database_server_id" = 'development' AND "switchman_shards"."name" IS NULL ORDER BY "switchman_shards"."id" ASC LIMIT 1 [production:1 master]
[- -] Setting Load (1.5ms) SELECT "settings".* FROM "settings" WHERE "settings"."name" = 'encryption_key_hash' LIMIT 1 [production:1 master]
[- -] SQL Setting Load (1.0ms) SELECT "settings".* FROM "settings" WHERE "settings"."name" = 'session_secret_key' LIMIT 1 [production:1 master]
[- -] Creating scope :active. Overwriting existing method AssignmentGroup.active.

Passenger log

App 15077 output: /usr/local/rvm/gems/ruby-2.5.3/gems/soap4r-ruby1.9-2.0.5/lib/soap/mapping/encodedregistry.rb:150: warning: constant ::Fixnum is deprecated
App 15077 output: /usr/local/rvm/gems/ruby-2.5.3/gems/soap4r-ruby1.9-2.0.5/lib/soap/mapping/encodedregistry.rb:216: warning: constant ::Fixnum is deprecated
[ E 2020-08-31 06:59:56.4143 14792/To age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /var/app/canvas: A timeout occurred while starting a preloader process.
Error ID: 99348b13
Error details saved to: /tmp/passenger-error-lHKq0U.html

[ E 2020-08-31 06:59:56.4253 14792/Tc age/Cor/Con/CheckoutSession.cpp:276 ]: [Client 3-1] Cannot checkout session because a spawning error occurred. The identifier of the error is 99348b13. Please see earlier logs for details about the error.

I am using ruby version 2.5.3
Yarn 1.10
node 10.18
postgresql 12

bundler 1.17.3

Please help me out here.