sameersbn / sameersbn/docker-gitlab
Terminated /usr/bin/supervisord -nc /etc/supervisor/supervisord.conf
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
/sbin/entrypoint.sh: line 19: 607 Terminated /usr/bin/supervisord -nc /etc/supervisor/supervisord.conf
2020-12-20 00:53:16,762 CRIT Supervisor running as root (no user in config file)
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/gitaly.conf" during parsing
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/groups.conf" during parsing
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/puma.conf" during parsing
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
2020-12-20 00:53:16,762 INFO Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
2020-12-20 00:53:16,775 INFO RPC interface 'supervisor' initialized
2020-12-20 00:53:16,775 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-12-20 00:53:16,775 INFO supervisord started with pid 1
2020-12-20 00:53:17,782 INFO spawned: 'gitaly' with pid 622
2020-12-20 00:53:17,788 INFO spawned: 'puma' with pid 623
2020-12-20 00:53:17,791 INFO spawned: 'gitlab-workhorse' with pid 624
2020-12-20 00:53:17,795 INFO spawned: 'sidekiq' with pid 625
2020-12-20 00:53:17,797 INFO spawned: 'nginx' with pid 626
2020-12-20 00:53:17,801 INFO spawned: 'sshd' with pid 632
2020-12-20 00:53:17,811 INFO spawned: 'cron' with pid 633
2020-12-20 00:53:18,802 INFO success: gitaly entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-20 00:53:18,802 INFO success: puma entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-20 00:53:18,802 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-20 00:53:18,802 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-20 00:53:18,803 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-20 00:53:18,803 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-20 00:53:18,803 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /sbin/entrypoint.sh line 19 and the supervisord command shown in the report. Review the included Supervisor configuration files under /etc/supervisor/conf.d/, especially cron.conf, gitaly.conf, gitlab-workhorse.conf, groups.conf, mail_room.conf, nginx.conf, puma.conf, sidekiq.conf, and sshd.conf. Reproduce the container termination and identify the cause, with a confirmed fix and startup logs showing supervisord remains running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100