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.
👍 This happens for 4-0-stable branch for me as well. On 4-0-stable branch, Gitlab presently checks for init script from master branch, and keeps on prompting the error @alexnederlof has pointed above till you fetch init script from master branch.
However, using init script from master branch fixes this message, but brings up issues about sidekiq. So far, I've turned a blind eye to this check and use init script from 4-0-stable.
This needs to be fixed.
By Administrator on 2013-01-20T13:25:13 (imported from GitLab project)
By Administrator on 2013-01-20T13:25:13 (imported from GitLab)
Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes
Checking Environment ... Finished
Checking Gitlab Shell ...
GitLab Shell version? ... OK (1.3.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? ... yes
post-receive hooks in repos are links: ... can't check, you have no projects
Checking Gitlab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
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
Checking GitLab ... Finished
But reloading the script doesnt change anything.
Install Init Script
Download the init script (will be /etc/init.d/gitlab):
System information
System: Ubuntu 12.04
Current User: git
Using RVM: no
Ruby Version: 1.9.3p392
Gem Version: 1.8.23
Bundler Version:1.3.5
Rake Version: 10.0.4
GitLab information
Version: 5.1.0
Revision: a06d9a49
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: http://??.??.??.??
HTTP Clone URL: http://??.??.??.??/some-project.git
SSH Clone URL: git@??.??.??.??:some-project.git
Using LDAP: no
Using Omniauth: no
...
Running? ... no
Try fixing it:
sudo -u gitlab -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.
..
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.
Basically if you download the stable version and run check it says you have
the wrong init script. Pulling from master fixes this but causes other
issues.
On Mar 21, 2014 2:49 AM, "nolar-wills" notifications@github.com wrote:
Hi,
Would you let me know what are you talk about ?
If you incorrectly edit the init script, it will be reported as out-of date, changes has to be made in /etc/default/gitlab not in the init script directly, that was problem in our lab installation.
By Administrator on 2015-02-15T17:58:55 (imported from GitLab project)
By Administrator on 2015-02-15T17:58:55 (imported from GitLab)