gitlab:satellites:create fails
Created by: steve-todorov
Hey,
I'm having a strange problem when trying to run:
gitlab@machine:~/gitlab$ bundle exec rake gitlab:satellites:create RAILS_ENV=production
Updating repo permissions ...
... done
Creating satellites for ...
testing ... skipping, because the repo is empty
project_name.eu ...
rake aborted!
No such file or directory - chdir
/home/gitlab/gitlab/lib/gitlab/popen.rb:9:in `popen'
/home/gitlab/gitlab/lib/gitlab/satellite/satellite.rb:33:in `create'
/home/gitlab/gitlab/lib/tasks/gitlab/enable_automerge.rake:30:in `block (3 levels) in <top (required)>'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:21:in `block (2 levels) in find_each'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:21:in `each'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:21:in `block in find_each'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:72:in `find_in_batches'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:20:in `find_each'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/querying.rb:8:in `find_each'
/home/gitlab/gitlab/lib/tasks/gitlab/enable_automerge.rake:18:in `block (2 levels) in <top (required)>'
Tasks: TOP => gitlab:satellites:create => gitlab:enable_automerge
(See full trace by running task with --trace)Any ideas what's wrong?
Gitla: 4-2-stable
Activity
Created by: alexanderte
Same problem here. Not sure if it matters where you run the command from, but I notice that you’ve run it from /home/gitlab. I run it from /home/gitlab/gitlab.
I’m using 4-2-stable branch, and GitLab is installed on a fresh Debian unstable box with nothing else running. It’s set up using my Ansible playbook that is based on the 4-2-stable installation guide – which by the way is identical to the stable branch installation guide.
Here’s my output:
gitlab@machine:/home/gitlab/gitlab# bundle exec rake gitlab:satellites:create RAILS_ENV=production Updating repo permissions ... ... done Creating satellites for ... ansible / ansible-playbook-gitlab ... rake aborted! No such file or directory - chdir /home/gitlab/gitlab/lib/gitlab/popen.rb:9:in `popen' /home/gitlab/gitlab/lib/gitlab/satellite/satellite.rb:33:in `create' /home/gitlab/gitlab/lib/tasks/gitlab/enable_automerge.rake:30:in `block (3 levels) in <top (required)>' /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:21:in `block (2 levels) in find_each' /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:21:in `each' /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:21:in `block in find_each' /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:72:in `find_in_batches' /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/relation/batches.rb:20:in `find_each' /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/querying.rb:8:in `find_each' /home/gitlab/gitlab/lib/tasks/gitlab/enable_automerge.rake:18:in `block (2 levels) in <top (required)>' Tasks: TOP => gitlab:satellites:create => gitlab:enable_automerge (See full trace by running task with --trace)By Administrator on 2013-03-14T12:58:53 (imported from GitLab project)
By Administrator on 2013-03-14T12:58:53 (imported from GitLab)
Created by: rtripault
According to you logs
No such file or directory - chdirit seems you are missing a folder. I remind having the problem too, i guess i solved it by manually creating/home/git/gitlab-satellites/Hope it will help
By Administrator on 2013-03-14T14:28:31 (imported from GitLab project)
By Administrator on 2013-03-14T14:28:31 (imported from GitLab)
Created by: alexanderte
@rtripault, the installation guide states that gitlab-satellites should reside under user gitlab – not git. Which location is correct? This is from the installation guide:
sudo -u gitlab -H mkdir /home/gitlab/gitlab-satellitesBy Administrator on 2013-03-14T14:44:58 (imported from GitLab project)
By Administrator on 2013-03-14T14:44:58 (imported from GitLab)
Created by: rtripault
@alexanderte sorry, in my haste i completely skipped the part you wrote you were using 4.2 branch, my comment was about 5.0, sorry for the noise.
As a side note, you might want to give a try to the Google Group
By Administrator on 2013-03-14T14:57:34 (imported from GitLab project)
By Administrator on 2013-03-14T14:57:34 (imported from GitLab)
Created by: alexanderte
@rtripault No problem. Didn’t know about that group – so thanks. :)
By Administrator on 2013-03-14T14:58:57 (imported from GitLab project)
By Administrator on 2013-03-14T14:58:57 (imported from GitLab)
Created by: gabriel403
I'm having the same problem, has anyone managed to solve it? @steve-todorov @alexanderte ?
By Administrator on 2013-03-15T11:01:15 (imported from GitLab project)
By Administrator on 2013-03-15T11:01:15 (imported from GitLab)
Created by: steve-todorov
@Gabriel403 try running
bundle exec rake gitlab:check RAILS_ENV=productionPay attention to what it will return for "Projects have satellites". In my case, it said:
testing ... can't create, repository is empty project_name.eu ... no Try fixing it: sudo -u gitlab -H bundle exec rake gitlab:satellites:create RAILS_ENV=producti 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.So I tried to create "/home/gitlab/gitlab/tmp/repo_satellites" and then executed
bundle exec rake gitlab:satellites:create RAILS_ENV=productionThat seems to have fixed it for me. Hope that helps.
By Administrator on 2013-03-15T11:19:59 (imported from GitLab project)
By Administrator on 2013-03-15T11:19:59 (imported from GitLab)
Created by: gabriel403
Hey that worked, thanks @steve-todorov
So when it says remove the dir it actually meant create it lol
By Administrator on 2013-03-15T12:33:06 (imported from GitLab project)
By Administrator on 2013-03-15T12:33:06 (imported from GitLab)
Created by: alexanderte
Thanks for pointing me in the right direction @steve-todorov. The reason why it didn’t work here is because I misspelled satellites. I created /home/gitlab/gitlab-satelittes – and that is wrong – satellites is right. I will update my Ansible playbook.
Here is a “patch” to anyone who might be affected by the typo in my playbook – it has not been verified because of all the trial and error leading to the solution:
sudo -u gitlab mv /home/gitlab/gitlab-satelittes /home/gitlab/gitlab-satellites cd /home/gitlab/gitlab sudo -u gitlab bundle exec rake gitlab:satellites:create RAILS_ENV=production sudo /etc/init.d/gitlab restart sudo /etc/init.d/nginx restart sudo -u gitlab -H bundle exec rake sidekiq:start RAILS_ENV=productionBy Administrator on 2013-03-15T13:40:33 (imported from GitLab project)
By Administrator on 2013-03-15T13:40:33 (imported from GitLab)
Created by: joshgillingham
If found that v4.2 has a config setting for the satellites path
GitLab Satellites
satellites:
Relative paths are relative to Rails.root (default: tmp/repo_satellites/)
path: /home/gitlab/gitlab-satellites/
When that directory was created or the path was corrected in the configuration gitlab.yml, everything started to work...
By Administrator on 2013-03-15T13:52:25 (imported from GitLab project)
By Administrator on 2013-03-15T13:52:25 (imported from GitLab)
Created by: steve-todorov
@senny I haven't tried the latest 5.x due to the changes it requires. I'm still using 4.2-stable, thus I don't know.
By Administrator on 2013-05-06T13:50:22 (imported from GitLab project)
By Administrator on 2013-05-06T13:50:22 (imported from GitLab)
Created by: ghost
the problem persists in 5.1. Manually created satellite dir solved the problem for me: 'su - git' 'mkdir /home/git/gitlab-satellites' 'bundle exec rake gitlab:satellites:create RAILS_ENV=production' (went through with no issues) If I remember correctly, somewhere in the upgrade 4.2-->5.0 doc is (was) that gitlab-satellites dir was suppose to be removed..
By Administrator on 2013-05-07T14:20:36 (imported from GitLab project)
By Administrator on 2013-05-07T14:20:36 (imported from GitLab)
Created by: ghost
after upgrade. but strangely enough not from 4.2-->5.0 but from 5.0-->5.1. (Could be that I just overlooked the problem before)
in upgrade guide https://github.com/gitlabhq/gitlabhq/blob/master/doc/update/4.2-to-5.0.md in section 4 it reads to remove 'sudo rm -rf /home/gitlab/gitlab-satellites' which is of course not in use in versions 5+. But the bottom line is that '/home/git/gitlab-satellites' wasn't created automatically.
By Administrator on 2013-05-10T08:04:58 (imported from GitLab project)
By Administrator on 2013-05-10T08:04:58 (imported from GitLab)
Created by: bbodenmiller
It's been at least 2 weeks since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.
By Administrator on 2013-06-11T17:01:12 (imported from GitLab project)
By Administrator on 2013-06-11T17:01:12 (imported from GitLab)
