aws-samples / aws-samples/eb-locustio-sample

Following services are not running: application-locust-follower-1

Open
#5 8 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
106
Forks
57
PR merge metrics
No merged PRs in 30d

Description

Hi, I followed the guide and I got this error in my EB Dashboard:

`Following services are not running: application-locust-follower-1`

When I open the locust dashboard, it says the number of slaves is 0. It looks like a slave process is failing to start, but I can't find anything in logs.
If I manually start it by connecting to my instance and running /bin/bash -c "exec /usr/local/bin/locust -f locustfile.py --port=9876 --slave --master-host=$(<.masterIP)", it works, but this is not a viable solution.

Contributor guide

Open the contributing guide

Research direction

Start with the Elastic Beanstalk Dashboard error and the Locust dashboard's slave count, then compare the deployment behavior with the manually run Locust command in the report. Inspect the startup configuration and available logs to identify why application-locust-follower-1 does not start automatically. Done means the follower starts during deployment and Locust reports the expected slave without manual instance access.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.