Upgrade to 7.0 has broken the gitlab service
Created by: jbrooksuk
I'm half way through upgrading, just about to restart the gitlab service and got this:
bbtadmin@git:/home/git/gitlab$ sudo service gitlab start
Starting both the GitLab Unicorn and Sidekiq/etc/init.d/gitlab: 178: /etc/init.d/gitlab: /etc/init.d/gitlab: 171: /etc/init.d/gitlab: script/web: not found
script/background_jobs: not found
..............................Waited 30s for the processes to write their pids, something probably went wrong.
bbtadmin@git:/home/git/gitlab$ sudo service nginx restart
bbtadmin@git:/home/git/gitlab$ sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
Instance method "lock!" is already defined in ActiveRecord::Base, use generic helper instead or set StateMachine::Machine.ignore_method_conflicts = true.
System information
System: Ubuntu 13.04
Current User: git
Using RVM: no
Ruby Version: 2.0.0p247
Gem Version: 2.0.3
Bundler Version:1.3.5
Rake Version: 10.3.2
Sidekiq Version:2.17.0
GitLab information
Version: 7.0.0
Revision: d1e424b
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: http://git.bbt
HTTP Clone URL: http://git.bbt/some-project.git
SSH Clone URL: [email protected]:some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 1.9.6
Repositories: /home/git/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/bin/gitWhat do I do now?