Skip to content

GitLab

Closed
Created by Administrator@rootOwner

Projects have no satellites

Created by: pandeybk

It seems like my projects have no satellites.when I run bundle exec rake gitlab:satellites:create RAILS_ENV=production to create new ones after deleting the tmp/repo_satellites directory I get this.

[gitlab@git gitlab]$ bundle exec rake gitlab:satellites:create RAILS_ENV=production
Updating repo permissions ...
... done

Creating satellites for ...
test / workshop ... 
... created
Automation / MakaluAutomation ... skipping, because the repo is empty
test / gitTest ... 
... created

It seems like satellites are created but when I re-run the test bundle exec rake gitlab:check RAILS_ENV=production I got this message.

[gitlab@git gitlab]$ bundle exec rake gitlab:check RAILS_ENV=production
Checking Environment ...

gitlab user is in git group? ... yes
Has no "-e" in ~git/.profile ... yes
Git configured for gitlab user? ... yes
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

Checking Gitolite ...

Using recommended version ... yes
Repo umask is 0007 in .gitolite.rc? ... yes
Allow all Git config keys in .gitolite.rc ... yes
Config directory exists? ... yes
Config directory owned by git:git ... yes
Config directory access is drwxr-x---? ... yes
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
Can clone gitolite-admin? ... ********************************************************************************
WARNING!!!!!!!!!! 
The use of this system is restricted to authorized users, unauthorized access is forbidden and will be prosecuted by law. All information and communications on 
this system are subject to review, monitoring and recording at any time, without notice or permission. Users should have no expectation of privacy.
********************************************************************************

yes
Can commit to gitolite-admin? ... yes
post-receive hook exists? ... yes
post-receive hook up-to-date? ... yes
post-receive hooks in repos are links: ... 
test / workshop ... ok
Automation / MakaluAutomation ... repository is empty
test / gitTest ... ok
Git config in repos: ... 
test / workshop ... ok
Automation / MakaluAutomation ... repository is empty
test / gitTest ... ok

Checking Gitolite ... Finished

Checking Sidekiq ...

Running? ... yes

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
Projects have satellites? ... 
test / workshop ... no
  Try fixing it:
  sudo -u gitlab -H bundle exec rake gitlab:satellites:create RAILS_ENV=production
  If necessary, remove the tmp/repo_satellites directory ...
  ... and rerun the above command
  For more information see:
  doc/raketasks/maintenance.md 
  Please fix the error above and rerun the checks.
Automation / MakaluAutomation ... can't create, repository is empty
test / gitTest ... no
  Try fixing it:
  sudo -u gitlab -H bundle exec rake gitlab:satellites:create RAILS_ENV=production
  If necessary, remove the tmp/repo_satellites directory ...
  ... and rerun the above command
  For more information see:
  doc/raketasks/maintenance.md 
  Please fix the error above and rerun the checks.

Checking GitLab ... Finished

I found that config/gitlab.yml file have this line of code to set the path.

path: /home/gitlab/gitlab-satellites/

so I comment this line to use the default path i.e tmp/repo_satellites/ to check whether it works but no luck.

Please some one look into this issue. Some others info are give below.

bundle exec rake gitlab:env:info RAILS_ENV=production

System information
System:     CentOS 5.4
Current User:   gitlab
Using RVM:  yes
RVM Version:    1.18.15
Ruby Version:   1.9.3p392
Gem Version:    2.0.0
Bundler Version:1.3.1
Rake Version:   10.0.3

GitLab information
Version:    4.2.0
Revision:   d67117b
Directory:  /home/gitlab/gitlab
DB Adapter: mysql2
URL:        http://git.example.com
HTTP Clone URL: http://git.example.com/some-project.git
SSH Clone URL:  [email protected]:some-project.git
Using LDAP: no
Using Omniauth: no

Gitolite information
Version:    v3.2-gitlab-patched-0-g2d29cf7
Admin URI:  git@localhost:gitolite-admin
Admin Key:  gitlab
Repositories:   /home/git/repositories/
Hooks:      /home/git/.gitolite/hooks/
Git:        /usr/bin/git