Unhealthy Status but cant complete migrations manually 11.1.4

I just upgraded from 11.1.2 to 11.1.4 (omnibus install). Now when I go to Monitoring> Health Check, I see a message that says Migrations are pending. To resolve this issue, run: bin/rake db:migrate RAILS_ENV=production
When I try and run this command I keep getting an error that there is no rakefile to be found. I tried running this from /opt/gitlab but that did not work either. What is the course of action here?? And also can someone explain exactly what this means? Thanks!

gitlab-rake gitlab:env:info

System information
System:		Ubuntu 16.04
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.4.4p296
Gem Version:	2.7.6
Bundler Version:1.16.2
Rake Version:	12.3.1
Redis Version:	3.2.11
Git Version:	2.17.1
Sidekiq Version:5.1.3
Go Version:	unknown

GitLab information
Version:	11.1.4-ee
Revision:	d17962f
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
DB Version:	9.6.6
URL:		https://gitlab.mydomain.net
HTTP Clone URL:	https://gitlab.mydomain.net/some-group/some-project.git
SSH Clone URL:	git@gitlab.mydomain.net:some-group/some-project.git
Elasticsearch:	no
Geo:		no
Using LDAP:	no
Using Omniauth:	no

GitLab Shell
Version:	7.1.4
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
Hooks:		/opt/gitlab/embedded/service/gitlab-shell/hooks
Git:		/opt/gitlab/embedded/bin/git
gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...

GitLab Shell version >= 7.1.4 ? ... OK (7.1.4)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
3/5 ... ok
2/6 ... ok
3/8 ... ok
3/9 ... repository is empty
3/10 ... ok
3/11 ... ok
2/12 ... ok
3/15 ... ok
3/16 ... ok
3/17 ... ok
3/20 ... ok
14/23 ... ok
14/24 ... ok
14/25 ... ok
3/26 ... ok
14/28 ... ok
3/31 ... ok
14/32 ... ok
14/33 ... ok
14/34 ... ok
3/35 ... repository is empty
14/36 ... ok
14/37 ... repository is empty
14/38 ... repository is empty
14/39 ... repository is empty
14/40 ... repository is empty
14/41 ... ok
14/42 ... ok
14/43 ... ok
14/44 ... ok
14/45 ... ok
14/46 ... ok
14/47 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK

Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Reply by email is disabled in config/gitlab.yml
Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
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: ...
3/5 ... yes
2/6 ... yes
3/8 ... yes
3/9 ... yes
3/10 ... yes
3/11 ... yes
2/12 ... yes
3/15 ... yes
3/16 ... yes
3/17 ... yes
3/20 ... yes
14/23 ... yes
14/24 ... yes
14/25 ... yes
3/26 ... yes
14/28 ... yes
3/31 ... yes
14/32 ... yes
14/33 ... yes
14/34 ... yes
3/35 ... yes
14/36 ... yes
14/37 ... yes
14/38 ... yes
14/39 ... yes
14/40 ... yes
14/41 ... yes
14/42 ... yes
14/43 ... yes
14/44 ... yes
14/45 ... yes
14/46 ... yes
14/47 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.4.4)
Git version >= 2.9.5 ? ... yes (2.17.1)
Git user has default SSH configuration? ... yes
Active users: ... 11
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)

Checking GitLab ... Finished

The error is misleading in that with Omnibus you run rake with ‘gitlab-rake’ instead. So ‘gitlab-rake db:migrate’.

https://docs.gitlab.com/omnibus/update/

If auto_migrate is not on, then you have to run migrations manually. Migrations modify the database on upgrade.

1 Like

Thanks man. Im all set now.