Runit service does not start crond properly
Summary
There is an issue when using the let's encrypt auto-renew cron job.
2019-05-03_20:19:41.83260 go-crond: Got signal: terminated
2019-05-03_20:19:41.83264 go-crond: Stop runner
2019-05-03_20:19:41.83265 go-crond: Terminated
2019-05-03_20:20:43.53625 go-crond: Starting go-crond version 0.6.1
2019-05-03_20:20:43.53668 go-crond: Path does not exists
2019-05-03_20:20:43.53737 go-crond: Start runner with 0 jobs
Steps to reproduce
- Enable let's encrypt and the auto-renew setting:
letsencrypt['enable'] = true letsencrypt['contact_emails'] = [] letsencrypt['auto_renew'] = true letsencrypt['auto_renew_hour'] = 0 letsencrypt['auto_renew_minute'] = nil # Should be a number or cron expression, if specified. letsencrypt['auto_renew_day_of_month'] = "*/4"
- Reconfigure
What is the current bug behavior?
Job will log:
Path does not exists
ubuntu@ip-172-31-18-91:~$ ps aux |grep go-crond
ubuntu 25582 0.0 0.0 10468 936 pts/0 S+ 14:56 0:00 grep —color=auto go-crond
root 29144 0.0 0.0 387020 5896 ? Ssl 03:00 0:00 /opt/gitlab/embedded/bin/go-crond —no-auto —include=
What is the expected correct behavior?
Crond will work with --include=/var/opt/gitlab/crond/
:
root@04:52:27:/etc/gitlab# /opt/gitlab/embedded/bin/go-crond --no-auto --include=/var/opt/gitlab/crond/
go-crond: Starting go-crond version 0.6.1
go-crond: Add cron job spec:'5 0 */4 * *' usr:root cmd:'/opt/gitlab/bin/gitlab-ctl renew-le-certs'
go-crond: Start runner with 1 jobs
Replicated with v11.10.0
Reported in https://gitlab.zendesk.com/agent/tickets/122266 (for internal use) in version 11.10.4-ee.
Edited by Cindy Pallares 🦉