BigW Consortium Gitlab

maintenance.md 4.61 KB
Newer Older
1 2
# Maintenance

3
## Gather information about GitLab and the system it runs on
4

5
This command gathers information about your GitLab installation and the System it runs on. These may be useful when asking for help or reporting issues.
6 7

```
8 9 10
# omnibus-gitlab
sudo gitlab-rake gitlab:env:info

11
# installation from source
12
bundle exec rake gitlab:env:info RAILS_ENV=production
13 14 15 16 17 18
```

Example output:

```
System information
19 20 21 22 23 24 25 26
System:           Debian 7.8
Current User:     git
Using RVM:        no
Ruby Version:     2.1.5p273
Gem Version:      2.4.3
Bundler Version:  1.7.6
Rake Version:     10.3.2
Sidekiq Version:  2.17.8
27 28

GitLab information
29 30 31 32 33 34 35 36 37
Version:          7.7.1
Revision:         41ab9e1
Directory:        /home/git/gitlab
DB Adapter:       postgresql
URL:              https://gitlab.example.com
HTTP Clone URL:   https://gitlab.example.com/some-project.git
SSH Clone URL:    git@gitlab.example.com:some-project.git
Using LDAP:       no
Using Omniauth:   no
38

39
GitLab Shell
40 41 42 43
Version:          2.4.1
Repositories:     /home/git/repositories/
Hooks:            /home/git/gitlab-shell/hooks/
Git:              /usr/bin/git
44 45
```

46
## Check GitLab configuration
47

48 49
Runs the following rake tasks:

50 51 52
- `gitlab:gitlab_shell:check`
- `gitlab:sidekiq:check`
- `gitlab:app:check`
53 54 55 56

It will check that each component was setup according to the installation guide and suggest fixes for issues found.

You may also have a look at our [Trouble Shooting Guide](https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide).
57 58

```
59 60 61
# omnibus-gitlab
sudo gitlab-rake gitlab:check

62
# installation from source
63
bundle exec rake gitlab:check RAILS_ENV=production
64 65
```

66 67
NOTE: Use SANITIZE=true for gitlab:check if you want to omit project names from the output.

68 69 70
Example output:

```
71 72
Checking Environment ...

73
Git configured for git user? ... yes
74 75 76 77 78
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

79
Checking GitLab Shell ...
80

81
GitLab Shell version? ... OK (1.2.0)
82
Repo base directory exists? ... yes
83
Repo base directory is a symlink? ... no
84
Repo base owned by git:git? ... yes
85
Repo base access is drwxrws---? ... yes
86
post-receive hook up-to-date? ... yes
87
post-receive hooks in repos are links: ... yes
88

89
Checking GitLab Shell ... Finished
90

91
Checking Sidekiq ...
92 93 94

Running? ... yes

95
Checking Sidekiq ... Finished
96 97 98 99

Checking GitLab ...

Database config exists? ... yes
100
Database is SQLite ... no
101 102
All migrations up? ... yes
GitLab config exists? ... yes
103
GitLab config outdated? ... no
104 105 106 107
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
108
Redis version >= 2.0.0? ... yes
109 110

Checking GitLab ... Finished
111 112
```

113 114 115 116
## Rebuild authorized_keys file

In some case it is necessary to rebuild the `authorized_keys` file.

117
For Omnibus-packages:
118 119 120 121 122 123
```
sudo gitlab-rake gitlab:shell:setup
```

For installations from source:
```
124
cd /home/git/gitlab
125 126 127 128 129 130 131
sudo -u git -H bundle exec rake gitlab:shell:setup RAILS_ENV=production
```

```
This will rebuild an authorized_keys file.
You will lose any data stored in authorized_keys file.
Do you want to continue (yes/no)? yes
132 133 134 135
```

## Clear redis cache

136
If for some reason the dashboard shows wrong information you might want to
137 138 139 140 141 142 143 144 145 146 147 148 149 150
clear Redis' cache.

For Omnibus-packages:
```
sudo gitlab-rake cache:clear
```

For installations from source:
```
cd /home/git/gitlab
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
```

## Precompile the assets
151

152 153 154
Sometimes during version upgrades you might end up with some wrong CSS or
missing some icons. In that case, try to precompile the assets again.

155 156
Note that this only applies to source installations and does NOT apply to
omnibus packages.
157 158 159 160 161

For installations from source:
```
cd /home/git/gitlab
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
162
```
163 164 165 166 167 168 169

For omnibus versions, the unoptimized assets (JavaScript, CSS) are frozen at
the release of upstream GitLab. The omnibus version includes optimized versions
of those assets. Unless you are modifying the JavaScript / CSS code on your
production machine after installing the package, there should be no reason to redo
rake assets:precompile on the production machine. If you suspect that assets
have been corrupted, you should reinstall the omnibus package.
170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188

## Tracking Deployments

GitLab provides a Rake task that lets you track deployments in GitLab
Performance Monitoring. This Rake task simply stores the current GitLab version
in the GitLab Performance Monitoring database.

For Omnibus-packages:

```
sudo gitlab-rake gitlab:track_deployment
```

For installations from source:

```
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:track_deployment RAILS_ENV=production
```