gitlab-installer icon indicating copy to clipboard operation
gitlab-installer copied to clipboard

Errors running the diagnostic after installation

Open collegian opened this issue 11 years ago • 1 comments

Hello,

I modified the existing script https://raw.github.com/mattias-ohlsson/gitlab-installer/master/gitlab-install-el6.sh to use the latest git version as well the latest gitlab version and created a customized script https://dl.dropboxusercontent.com/s/bfdlji83llakqbe/gitlab_install.sh. This basically is the original script with the modifications suggested for git 1.7+ as per https://github.com/fjmk/gitlab-installer/commit/cd98231fe9ae181ba4b3f7969194855190a677b4 and gitlab 5.4 as per https://github.com/fjmk/gitlab-installer/commit/d792ae32e724cfb2c43716a4105bac5078698648.

However, running the diagnostic after installation returns errors:

Checking Environment ...

Git configured for git user? ... yes Has python2? ... yes python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.4.0 ? ... OK (1.7.0) 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 post-receive hook up-to-date? ... can't check because of previous errors post-receive hooks in repos are links: ... can't check because of previous errors

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... no Try fixing it: sudo -u git -H bundle exec rake sidekiq:start RAILS_ENV=production For more information see: doc/install/installation.md in section "Install Init Script" see log/sidekiq.log for possible errors Please fix the error above and rerun the checks.

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? ... no Try fixing it: Redownload the init script For more information see: doc/install/installation.md in section "Install Init Script" Please fix the error above and rerun the checks. Projects have satellites? ... can't check, you have no projects Redis version >= 2.0.0? ... yes Your git bin path is "/usr/bin/git" Git version >= 1.7.10 ? ... yes (1.8.3) Checking GitLab ... Finished

Any suggestions as to what could be going wrong would be highly appreciated. I am not sure if this is the right place to post it, please let me know if it isn't.

Thanks.

collegian avatar Aug 06 '13 22:08 collegian

Ok, so it turns out that the init script URL was returning a 404 due to which the script wasn't getting downloaded. However, even on using the correct URL I get this:

03:25:17 # service gitlab start
Using /usr/local/rvm/gems/ruby-1.9.3-p392
Starting puma: ERROR: Gem bundler is not installed, run `gem install bundler` first.
                                                       [FAILED]
Starting sidekiq: ERROR: Gem bundler is not installed, run `gem install bundler` first.
                                                       [FAILED]

I can see 1.3.5 version of bundler installed so I am not sure why it would complain.

collegian avatar Aug 27 '13 14:08 collegian