Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2556

Closed
Open
Created Jan 10, 2013 by Administrator@rootOwner

Resque jobs failing

Created by: notnmeyer

Hi,

I've been testing GitLab 4 and I've run in to an issue where resque jobs are failing after pushes with:

Exception NoMethodError

Error undefined method id' for nil:NilClass /home/gitlab/gitlab/app/models/project.rb:104:infind_with_namespace' /home/gitlab/gitlab/app/workers/post_receive.rb:9:in `perform'

I see that the same error is called out in the troubleshooting guide that occurs if you have symlinked your repo directory, mine however is not a symlink:

$ ls -ld /home/git/repositories/ drwsrws--- 6 git git 4096 Jan 9 14:42 /home/git/repositories/

$ grep repos_path /home/gitlab/gitlab/config/gitlab.yml

repos_path must not be a symlink

repos_path: /home/git/repositories/

This behavior does seem to have started after I moved the repos directory and changed repos_path in gitlab.yml to a new location (but again, I didn't symlink it) and noticed this behavior. I wound up moving the directory back to /home/git/repositories/ (and changing gitlab.yml back). I am currently able to create projects, push, pull, etc.

gitlab:check passes on everything except:

nate / test123 ... no Try fixing it: sudo -u gitlab -H bundle exec rake gitlab:satellites:create 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.

And if I follow it's advice (as the gitlab user):

$ bundle exec rake gitlab:satellites:create rake aborted! cannot load such file -- rb-inotify /usr/local/rvm/gems/ruby-1.9.3-p327@global/gems/bundler-1.2.3/lib/bundler/runtime.rb:68:in require' /usr/local/rvm/gems/ruby-1.9.3-p327@global/gems/bundler-1.2.3/lib/bundler/runtime.rb:68:inblock (2 levels) in require' /usr/local/rvm/gems/ruby-1.9.3-p327@global/gems/bundler-1.2.3/lib/bundler/runtime.rb:66:in each' /usr/local/rvm/gems/ruby-1.9.3-p327@global/gems/bundler-1.2.3/lib/bundler/runtime.rb:66:inblock in require' /usr/local/rvm/gems/ruby-1.9.3-p327@global/gems/bundler-1.2.3/lib/bundler/runtime.rb:55:in each' /usr/local/rvm/gems/ruby-1.9.3-p327@global/gems/bundler-1.2.3/lib/bundler/runtime.rb:55:inrequire' /usr/local/rvm/gems/ruby-1.9.3-p327@global/gems/bundler-1.2.3/lib/bundler.rb:128:in require' /home/gitlab/gitlab/config/application.rb:9:in<top (required)>' /home/gitlab/gitlab/Rakefile:5:in require' /home/gitlab/gitlab/Rakefile:5:in<top (required)>' (See full trace by running task with --trace)

Any suggestions on what potentially could be the problem?

Assignee
Assign to
Time tracking