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
  • #2257

Closed
Open
Created Dec 11, 2012 by Administrator@rootOwner

After upgrading to 3.1 cannot pass gitlab:app:status

Created by: three18ti

Hello,

I performed the steps to upgrade from 3.0 to 3.1, after performing the upgrade I was receiving:

root@gitlab:/home/gitlab/gitlab# sudo -u gitlab -H bundle exec rake gitlab:app:status RAILS_ENV=production --trace
** Invoke gitlab:app:status (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute gitlab:app:status

Starting diagnostics
config/database.yml............exists
config/gitlab.yml............exists
/home/git/repositories/............exists
/home/git/repositories/ is writable?............YES
FATAL: errors found before logging could be setup
FATAL: warn     Bareword found where operator expected at /home/git/.gitolite.rc line 24, near "# comment out if you don't"<<newline>>  (Might be a runaway multi-line '' string starting on line 22)<<newline>>
fatal: The remote end hung up unexpectedly
Can clone gitolite-admin?............NO
rake aborted!
unexpected return
/home/gitlab/gitlab/lib/tasks/gitlab/status.rake:49:in `rescue in block (3 levels) in <top (required)>'
/home/gitlab/gitlab/lib/tasks/gitlab/status.rake:41:in `block (3 levels) in <top (required)>'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/task.rb:227:in `call'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/task.rb:227:in `block in execute'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/task.rb:222:in `each'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/task.rb:222:in `execute'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/task.rb:166:in `block in invoke_with_call_chain'
/usr/local/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/task.rb:159:in `invoke_with_call_chain'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/task.rb:152:in `invoke'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:141:in `invoke_task'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:99:in `block (2 levels) in top_level'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:99:in `each'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:99:in `block in top_level'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:108:in `run_with_threads'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:93:in `top_level'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:71:in `block in run'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:158:in `standard_exception_handling'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/lib/rake/application.rb:68:in `run'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/rake-10.0.1/bin/rake:37:in `<top (required)>'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/bin/rake:23:in `load'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/bin/rake:23:in `<main>'
Tasks: TOP => gitlab:app:status

The error appears to come from the line:

GIT_CONFIG_KEYS             =>  '.*'*',

note the extra ', I have tried both

GIT_CONFIG_KEYS             =>  '*',

and

GIT_CONFIG_KEYS             =>  '.*',

which resolved the above error, however, I now receive the error that the post receive file is missing:

root@gitlab:/home/gitlab/gitlab# sudo -u gitlab -H bundle exec rake gitlab:app:status RAILS_ENV=production --trace
** Invoke gitlab:app:status (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute gitlab:app:status

Starting diagnostics
config/database.yml............exists
config/gitlab.yml............exists
/home/git/repositories/............exists
/home/git/repositories/ is writable?............YES
Can clone gitolite-admin?............YES
Can git commit?............YES
UMASK for .gitolite.rc is 0007? ............YES
/home/git/share/gitolite/hooks/common/post-receive exists? ............YES

Validating projects repositories:
* App-SafeBrowsing.....post-receive file missing
* Web based spam processing.....post-receive file missing

Finished

However, it appears that the post receive file exists:

ls -lah /home/git/repositories/app-safebrowsing.git/hooks/post-receive
lrwxrwxrwx 1 git git 45 Dec 11 12:46 /home/git/repositories/app-safebrowsing.git/hooks/post-receive -> /home/git/.gitolite/hooks/common/post-receive

I tried to get help on IRC but it is a ghost town, I apologize for the impatience.

Thanks!

Assignee
Assign to
Time tracking