Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
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
  • #4811

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Hooks Issue

Closed

Hooks Issue

Created by: MrKeiKun

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

how to deal with this?

System information
System:         CentOS release 6.4 (Final)
Current User:   git
Using RVM:      no
Ruby Version:   2.0.0p247
Gem Version:    2.0.3
Bundler Version:1.3.5
Rake Version:   10.1.0

GitLab information
Version:        6.0.0.pre
Revision:       a410bc1
Directory:      /home/git/gitlab
DB Adapter:     mysql2
URL:            http://git.example.com
HTTP Clone URL: http://git.example.com/some-project.git
SSH Clone URL:  git@git.example.com:some-project.git
Using LDAP:     no
Using Omniauth: no

GitLab Shell
Version:        1.7.0
Repositories:   /home/git/repositories/
Hooks:          /home/git/gitlab-shell/hooks/
Git:            /usr/bin/git
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.7.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? ... 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? ...
Group / Project ... yes
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.7.11)

Checking GitLab ... Finished
  1. Oh no!

    You are trying to upload something other than an image. Please upload a .png, .jpg, .jpeg, .gif, .bmp, .tiff or .ico.

    Incoming!

    Drop your designs to start your upload.

Linked issues
0


  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: MrKeiKun

    Just Upgrade to 6.1.0pre still the same i reinstalled it already

    System information
    System:         CentOS release 6.4 (Final)
    Current User:   git
    Using RVM:      no
    Ruby Version:   2.0.0p247
    Gem Version:    2.0.3
    Bundler Version:1.3.5
    Rake Version:   10.1.0
    
    GitLab information
    Version:        6.1.0.pre
    Revision:       fede36f
    Directory:      /home/git/gitlab
    DB Adapter:     mysql2
    URL:            http://git.example.com
    HTTP Clone URL: http://git.example.com/some-project.git
    SSH Clone URL:  git@git.example.com:some-project.git
    Using LDAP:     no
    Using Omniauth: no
    
    GitLab Shell
    Version:        1.7.0
    Repositories:   /home/git/repositories/
    Hooks:          /home/git/gitlab-shell/hooks/
    Git:            /usr/bin/git
    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.7.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? ... 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? ...
    Group / Project ... yes
    Redis version >= 2.0.0? ... yes
    Your git bin path is "/usr/bin/git"
    Git version >= 1.7.10 ? ... yes (1.7.11)
    
    Checking GitLab ... Finished

    By Administrator on 2013-08-21T10:19:17 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: demisx

    Same issue here. It appears that post-receive hook has been replaced by the update hook in the latest gitlab-shell, but the rake check still checks for it (see below). Should the check be updated to check the 'update' hook instead of the 'post-receive'?

    $ bundle exec rake gitlab:gitlab_shell:check  
    (in /home/git/gitlab)
    Checking GitLab Shell ...
    
    GitLab Shell version >= 1.7.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

    By Administrator on 2013-08-23T06:14:50 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: MrKeiKun

    still exist 6.1.0.pre 2b36dee6

    By Administrator on 2013-08-26T00:15:52 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
None
Assign to
Milestone
No milestone
None
None
Time tracking
No estimate or time spent
Due date
None
None
1
Labels
Hooks
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
1
1 participant
user avatar
Reference: gpt/large_projects/gitlabhq1#4811

Menu

Projects Groups Snippets
Help