Elastic Beanstalk environment's health severe: Following services are not running: release

Viewed 926

I deployed a Django application to Elastic Beanstalk (EB) Amazon Linux 2 Python 3.7 platform and everything seems to be working fine. However, the health of the environment is severe and I can't figure out why.

The only information EB gives me is the following:

Overall status: Degraded - Impaired services on all instances.

(there is only one instance running)

Instance status: Severe - Following services are not running: release.

I found no information about what the "release" service is.

From the full logs, the only errors I'm seeing are the following:

daemon.log:

F, [2020-11-07T04:03:03.891398 #5022] FATAL -- : /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/launcher.rb:432:in `block in setup_signals': SIGTERM (SignalException)
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/single.rb:117:in `join'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/single.rb:117:in `run'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/launcher.rb:172:in `run'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/cli.rb:80:in `run'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/healthd-1.0.6/bin/healthd:112:in `block in <top (required)>'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/healthd-1.0.6/bin/healthd:19:in `chdir'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/healthd-1.0.6/bin/healthd:19:in `<top (required)>'
    from /opt/elasticbeanstalk/lib/ruby/bin/healthd:23:in `load'
    from /opt/elasticbeanstalk/lib/ruby/bin/healthd:23:in `<main>'

From what I've read here this SignalException is thrown to shut down a process, so I assume it's normal.

There is no other error in any of the other logs. Turning the enhanced health check off would be the easy "solution" as stated here but I would like to keep them on.

Any help is very much appreciated.

1 Answers

.config commands:

container_commands:
  01_migrate:
    command: "source $(find /var/app/venv/ -name activate) && export $(sudo egrep -v '^#' /opt/elasticbeanstalk/deployment/env | xargs) && python manage.py migrate --noinput"
    leader_only: true
  02_static:
    command: "source $(find /var/app/venv/ -name activate) && export $(sudo egrep -v '^#' /opt/elasticbeanstalk/deployment/env | xargs) && python manage.py collectstatic --noinput"
    leader_only: true
Related