CODEWITHSUNDEEP
ruby-on-railsrubyamazon-web-servicesamazon-elastic-beanstalkpuma
mike927
mike927

Reputation: 774

AWS Beanstalk - Early termination of worker

I wanna host my rails 6.0.3 (ruby 2.7.1) app on AWS Beanstalk using platform Ruby 2.7 AL2 version 3.1.1. I spent hours to solve the following issues and finally, I got one I stucked. When the app is being started I got the following error:

/var/log/puma/puma.log

[10222] Early termination of worker
[10258] + Gemfile in context: /var/app/current/Gemfile
[10258] Early termination of worker
[31408] - Gracefully shutting down workers...
=== puma startup: 2020-09-25 13:33:02 +0000 ===
=== puma startup: 2020-09-25 13:33:02 +0000 ===
[10501] + Gemfile in context: /var/app/current/Gemfile
[10501] Early termination of worker
[10504] + Gemfile in context: /var/app/current/Gemfile
[10504] Early termination of worker

On the other hand in /var/log/web.stdout.log it seems to look fine...

Sep 25 13:33:02 ip-172-31-43-76 web: [10418] Puma starting in cluster mode...
Sep 25 13:33:02 ip-172-31-43-76 web: [10418] * Version 4.3.5 (ruby 2.7.1-p83), codename: Mysterious Traveller
Sep 25 13:33:02 ip-172-31-43-76 web: [10418] * Min threads: 8, max threads: 32
Sep 25 13:33:02 ip-172-31-43-76 web: [10418] * Environment: staging
Sep 25 13:33:02 ip-172-31-43-76 web: [10418] * Process workers: 1
Sep 25 13:33:02 ip-172-31-43-76 web: [10418] * Phased restart available
Sep 25 13:33:02 ip-172-31-43-76 web: [10418] * Listening on unix:///var/run/puma/my_app.sock
Sep 25 13:33:02 ip-172-31-43-76 web: [10418] Use Ctrl-C to stop

I use the same puma version as pointed in official doc 4.3.5

My config/puma.rb look like:

max_threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }
min_threads_count = ENV.fetch("RAILS_MIN_THREADS") { max_threads_count }
threads min_threads_count, max_threads_count

# Specifies the `port` that Puma will listen on to receive requests; default is 3000.
#
port        ENV.fetch("PORT") { 3000 }

# Specifies the `environment` that Puma will run in.
#
environment ENV.fetch("RAILS_ENV") { "development" }

# Specifies the `pidfile` that Puma will use.
pidfile ENV.fetch("PIDFILE") { "tmp/pids/server.pid" }

# Specifies the number of `workers` to boot in clustered mode.
# Workers are forked web server processes. If using threads and workers together,
# the concurrency of the application would be max `threads` * `workers.`
# Workers do not work on JRuby or Windows (both of which do not support
# processes).
#
workers ENV.fetch("WEB_CONCURRENCY") { 2 } # <------ uncomment this line

# Use the `preload_app!` method when specifying a `workers` number.
# This directive tells Puma to first boot the application and load code
# before forking the application. This takes advantage of Copy On Write
# process behavior so workers use less memory.
#
preload_app! # <------ uncomment this line

# Allow Puma to be restarted by the `Rails restart` command.
plugin :tmp_restart

How to fix it and run properly?

Upvotes: 2

Views: 1713

Answers (1)

wenzel
wenzel

Reputation: 13

Please check the following:

  • run production locally. This can show you additional errors (for example Zeitwerk errors)
  • check permissions under vendor dir, where the gem files go. One of our dependencies didn't have read permission for others and was causing error. You can change this by adding script to .ebextensions
  • Check also this link: AWS elastic beanstalk is not getting the environment variables

In our case, we hit jackpot. It was all of the above ...

Upvotes: 1

Related Questions