GitLab

Created by: djgreg13

Hello i have this error

Gitlab::SatelliteNotExistError (Satellite doesn't exist): lib/gitlab/satellite/satellite.rb:21:in raise_no_satellite' lib/gitlab/satellite/satellite.rb:55:inlock' lib/gitlab/satellite/action.rb:21:in block in in_locked_and_timed_satellite' lib/gitlab/satellite/action.rb:20:inin_locked_and_timed_satellite' lib/gitlab/satellite/edit_file_action.rb:22:in commit!' app/controllers/tree_controller.rb:30:inupdate'

i rm the repo_sattelites dir and do the command sudo -u gitlab -H bundle exec rake gitlab:satellites:create RAILS_ENV=production

but the problem persist

How can i do ?

Created by: maxlazio

What does sudo -u gitlab -H bundle exec rake gitlab:check RAILS_ENV=production return (for gitlab v4 and up) ?

By Administrator on 2013-03-20T06:47:50 (imported from GitLab project)

Created by: djgreg13

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: Permanently added 'localhost' (ECDSA) to the list of known hosts. 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: ... Greg / FuzzyLogic ... ok Greg / TDCrypto-Signature ... ok Greg / AirDMX ... ok Greg / AIHM-TP1 ... ok Greg / AirDMX-Xcode ... repository is empty Git config in repos: ... Greg / FuzzyLogic ... ok Greg / TDCrypto-Signature ... ok Greg / AirDMX ... ok Greg / AIHM-TP1 ... ok Greg / AirDMX-Xcode ... repository is empty

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? ... Greg / FuzzyLogic ... 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. Greg / TDCrypto-Signature ... 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. Greg / AirDMX ... 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. Greg / AIHM-TP1 ... 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. Greg / AirDMX-Xcode ... can't create, repository is empty

Checking GitLab ... Finished

rake aborted! Don't know how to build task 'return'

(See full trace by running task with --trace)

By Administrator on 2013-03-20T07:23:01 (imported from GitLab project)

Created by: djgreg13

Launch sudo -u gitlab -H bundle exec rake gitlab:satellites:create RAILS_ENV=production will do fine but in real do nothing

By Administrator on 2013-03-20T07:25:43 (imported from GitLab project)

Created by: maxlazio

Can you remove the tmp/repo_satellites and then create an empty directory tmp/repo_satellites before running the task?

By Administrator on 2013-03-20T07:29:59 (imported from GitLab project)

Created by: djgreg13

i do this but this do nothing

By Administrator on 2013-03-20T07:40:57 (imported from GitLab project)

Created by: djgreg13

Fixed when i have upgraded to 5.0

By Administrator on 2013-04-02T13:08:04 (imported from GitLab project)

Created by: C-Duv

On GitLab 6.6.2 I had the issue on a repository that was (in order):

1. Imported from a bare git repository folder via sudo -u $GITLAB_USER -H bundle exec rake gitlab:import:repos RAILS_ENV=production
2. Deleted via web interface
3. Imported another time (git folder content had changed since) via sudo -u $GITLAB_USER -H bundle exec rake gitlab:import:repos RAILS_ENV=production

From there I couldn't commit changes via web interface nor open merge request from forks (forking was working, so was commits to theses forks).

I managed to get it fixed by running (from /home/git/gitlab): sudo -u $GITLAB_USER -H bundle exec rake gitlab:check RAILS_ENV=production which found an issue on the non-working repository and suggested to run: sudo -u $GITLAB_USER -H bundle exec rake gitlab:satellites:create RAILS_ENV=production This one seems to have done things on the say repo. Running sudo -u $GITLAB_USER -H bundle exec rake gitlab:check RAILS_ENV=production once more time shown no errors. And commits/merge on the repository were working again.

(Not sure the fact it was imported once then deleted changes anything in the issue but I rather note it).

Versions : Debian 7 GitLab 6.6.2 GitLab Shell 1.8.0 GitLab API v3 Ruby 1.9.3p194 Rails 4.0.3

Thanks to self-analysis GitLab tools 👍

By Administrator on 2014-03-17T23:45:31 (imported from GitLab project)