Skip to content

Supervisor errors

Starting an application from Manage makes the application go into a backoff-loop and then fatal. Solution: Are you sure the binaries are in the server that is running your application? Are you using correct tags?

[program:my-app.attracs.com]
command=/bin/bash /etc/attracs-supervisor/run-process.sh -p my-app-1.0.0.tar.gz ...

Double-check the tagged version you are running, for example here my-app-1.0.0.tar.gz there are no versions tagged that match your supervisor configs

2024-01-10 08:51:12,236 INFO spawned: 'my-app.attracs.com' with pid 3516347
2024-01-10 08:51:12,391 INFO exited: my-app.attracs.com (exit status 127; not expected)
2024-01-10 08:51:13,467 INFO spawned: 'my-app.attracs.com' with pid 3516348
2024-01-10 08:51:13,624 INFO exited: my-app.attracs.com (exit status 127; not expected)
2024-01-10 08:51:15,984 INFO spawned: 'my-app.attracs.com' with pid 3516349
2024-01-10 08:51:16,136 INFO exited: my-app.attracs.com (exit status 127; not expected)
2024-01-10 08:51:19,327 INFO spawned: 'my-app.attracs.com' with pid 3516354
2024-01-10 08:51:19,481 INFO exited: my-app.attracs.com (exit status 127; not expected)
2024-01-10 08:51:19,850 INFO gave up: my-app.attracs.com entered FATAL state, too many start retries too quickly

Running the bootstrap results in an error when trying to start supervisor.service

TASK [start supervisor service] ************************************************************************************************************************************************************************************
fatal: [tms-confidential-instance-nightly]: FAILED! => {"changed": false, "msg": "Unable to start service supervisord: Job for supervisord.service failed because the control process exited with error code.\nSee \"systemctl status supervisord.service\" and \"journalctl -xeu supervisord.service\" for details.\n"}
fatal: [tms-confidential-instance-nightly]: FAILED! => {"changed": false, "msg": "Unable to start service supervisord: Job for supervisord.service failed because the control process exited with error code.\nSee \"systemctl status supervisord.service\" and \"journalctl -xeu supervisord.service\" for details.\n"}
Jan 25 15:33:06 tms-confidential-instance-nightly supervisord[24798]: Error: could not find config file /etc/supervisor/supervisord.conf

Solution: Is the instance part of the configs/hosts/ JSON templates in the repository?