invalid cron_job lines in production.log of CE edition
Summary
The following error/warning lines appear in production.log for Gitlab CE 8.14.4 on Centos 6 and Ubuntu 12:
Invalid cron_jobs config key: 'historical_data_worker'. Check your gitlab config file.
Invalid cron_jobs config key: 'update_all_mirrors_worker'. Check your gitlab config file.
Invalid cron_jobs config key: 'update_all_remote_mirrors_worker'. Check your gitlab config file.
Invalid cron_jobs config key: 'ldap_sync_worker'. Check your gitlab config file.
Invalid cron_jobs config key: 'geo_bulk_notify_worker'. Check your gitlab config file.
I believe some of these are all Gitlab EE items (update mirror jobs, for example), but I am not sure if they all are and removing them from gitlab.rb (and running reconfigure) does not remove them from reoccurring in the production.log file the next time the gitlab service is restarted. These log lines were discovered on the Centos system first after the gitlab.rb had been updated, although further investigation revealed that the Ubuntu system also displayed the same errors in production.log. Both systems have had older versions of Gitlab installed and then upgraded over time to the latest releases.
Steps to reproduce
This only started showing up after an updated Gitlab CE 8.14.4 instance with a gitlab.rb that had not been changed since an 8.8.x release had it's gitlab.rb file updated using the gitlab.rb template found here: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template so that it would provide access to all Gitlab 8.14.4 features.
Note: Gitlab was installed and updated using the omnibus package.
Expected behavior
EE cron jobs should not show up as invalid config key errors and CE cron jobs should not throw errors.
Actual behavior
The below lines appear in production.log every time the gitlab service is rebooted:
Invalid cron_jobs config key: 'historical_data_worker'. Check your gitlab config file.
Invalid cron_jobs config key: 'update_all_mirrors_worker'. Check your gitlab config file.
Invalid cron_jobs config key: 'update_all_remote_mirrors_worker'. Check your gitlab config file.
Invalid cron_jobs config key: 'ldap_sync_worker'. Check your gitlab config file.
Invalid cron_jobs config key: 'geo_bulk_notify_worker'. Check your gitlab config file.
Results of GitLab application Check
The output in this section and the one below are both generated from the Centos 6 system:
Checking GitLab Shell ...
GitLab Shell version >= 4.0.3 ? ... OK (4.0.3)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
2/1 ... ok
4/2 ... ok
2/5 ... ok
2/6 ... ok
2/7 ... ok
2/8 ... ok
8/9 ... ok
8/10 ... repository is empty
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
[redacted]
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... skipped (no tmp uploads folder yet)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
projects have namespace: ...
2/1 ... yes
4/2 ... yes
2/5 ... yes
2/6 ... yes
2/7 ... yes
2/8 ... yes
8/9 ... yes
8/10 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.1)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.7.4)
Active users: 7
Checking GitLab ... Finished
Results of GitLab environment info
System information
System: CentOS 6.6
Current User: git
Using RVM: no
Ruby Version: 2.3.1p112
Gem Version: 2.6.6
Bundler Version:1.13.6
Rake Version: 10.5.0
Sidekiq Version:4.2.1
GitLab information
Version: 8.14.4
Revision: gitlab-org/gitlab-ce@3ea6c8d730200c3811126ee0ab25495b9fab1b16
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://[GitlabServer]
HTTP Clone URL: https://[GitlabServer]/some-group/some-project.git
SSH Clone URL: git@[GitlabServer]:some-group/some-project.git
Using LDAP: yes
Using Omniauth: no
GitLab Shell
Version: 4.0.3
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/
Git: /opt/gitlab/embedded/bin/git
Possible fixes
Is there some setting that needs to be changed for these cron jobs to work?