1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
3
Double-check that the worker configuration file (.ebextensions/01-worker.config) contains the correct command to start the worker process, and that the pidfile option is set to /var/pids/worker.pid.
option_settings:
aws:elasticbeanstalk:worker:python:
command: "worker.py"
pidfile: "/var/pids/worker.pid"
Check the worker logs (located at /var/log/eb-worker.log) to see if there are any errors or exceptions being raised that could prevent the worker process from starting or writing to the pid file. Ensure that the worker process has write permissions to the /var/pids directory.
container_commands:
01_change_pids_permission:
command: "chmod 777 /var/pids"
If none of the above steps work, try restarting the environment to see if that resolves the issue.
eb restart
Contenido relevante
- ¿Cómo puedo transferir variables de mi entorno de Elastic Beanstalk a instancias de Linux y Windows?OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace un año
Thank you sdtslmn for the answer. My config file didn't had the pidfile parameter. I will add that, set the permissions and restart to see if it solves the issue.