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

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

  • Report abuse

  • New issue

  • Report abuse

POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "

Closed

POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "

Created by: Shuro

Hi folks, I noticed an error after deleting some old repositories on my gitlab 4.2 server, found them in ./log/githost.log.

./log/githost.log:March 04, 2013 13:01 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:02 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:02 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:02 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:02 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:02 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:02 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:03 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:03 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:03 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:03 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:03 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:03 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:03 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:03 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:04 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:04 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
./log/githost.log:March 04, 2013 13:04 -> ERROR -> POST-RECEIVE: Triggered hook for non-existing project with full path "gitolite-admin "
sudo -u gitlab -H bundle exec rake gitlab:env:info RAILS_ENV=production

System information
System:         Debian 6.0.7
Current User:   gitlab
Using RVM:      no
Ruby Version:   1.9.3p327
Gem Version:    1.8.23
Bundler Version:1.3.0
Rake Version:   10.0.3

GitLab information
Version:        4.2.0
Revision:       d67117b
Directory:      /home/gitlab/gitlab
DB Adapter:     mysql2
URL:            https://git.xxxx.xx
HTTP Clone URL: https://git.xxxx.xx/some-project.git
SSH Clone URL:  git@git.xxxx.xx:some-project.git
Using LDAP:     no
Using Omniauth: no

Gitolite information
Version:        v3.2-gitlab-patched-0-g2d29cf7
Admin URI:      git@localhost:gitolite-admin
Admin Key:      gitlab
Repositories:   /home/git/repositories/
Hooks:          /home/git/.gitolite/hooks/
Git:            /usr/bin/git

Greetings, Shuro

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: anderiv

      Ditto here:

      gitlab@host:~/gitlab$ bundle exec rake gitlab:env:info RAILS_ENV=production
      
      System information
      System:     Debian 6.0.6
      Current User:   gitlab
      Using RVM:  yes
      RVM Version:    1.18.5
      Ruby Version:   1.9.3p374
      Gem Version:    1.8.25
      Bundler Version:1.2.3
      Rake Version:   10.0.3
      
      GitLab information
      Version:    4.2.0
      Revision:   b0d6b29
      Directory:  /var/local/home/gitlab/gitlab
      DB Adapter: mysql2
      URL:        http://example.com/git
      HTTP Clone URL: http://example.com/git/some-project.git
      SSH Clone URL:  git@example.com:some-project.git
      Using LDAP: no
      Using Omniauth: no
      
      Gitolite information
      Version:    v3.2-gitlab-patched-0-g2d29cf7
      Admin URI:  git@localhost:gitolite-admin
      Admin Key:  gitlab
      Repositories:   /var/local/home/git/repositories/
      Hooks:      /var/local/home/git/.gitolite/hooks/
      Git:        /usr/bin/git

      By Administrator on 2013-03-08T21:45:46 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: kelas

      ditto here

      [gitlab@dss-ng] 16:38:21 [~/gitlab] $ bundle exec rake gitlab:env:info RAILS_ENV=production

      System information System: RedHatEnterpriseServer 6.1 Current User: gitlab Using RVM: no Ruby Version: 1.9.3p392 Gem Version: 1.8.23 Bundler Version:1.3.3 Rake Version: 10.0.3

      GitLab information Version: 4.2.0 Revision: c90a98c5 Directory: /home/gitlab/gitlab DB Adapter: mysql2 URL: http://git.army.mil HTTP Clone URL: http://git.army.mil/some-project.git SSH Clone URL: git@git.army.mil:some-project.git Using LDAP: yes Using Omniauth: no

      Gitolite information Version: v3.2-gitlab-patched-0-g2d29cf7 Admin URI: git@localhost:gitolite-admin Admin Key: gitlab Repositories: /home/git/repositories/ Hooks: /home/git/.gitolite/hooks/ Git: /usr/bin/git

      By Administrator on 2013-03-14T15:44:04 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: bajcsi

      I also have this issue...

      System information System: RedHatEnterpriseServer 6.3 Current User: gitlab Using RVM: no Ruby Version: 1.9.3p392 Gem Version: 2.0.0 Bundler Version:1.3.0 Rake Version: 10.0.3

      GitLab information Version: 4.2.0 Revision: d67117b5 Directory: /home/source_control/gitlab/gitlabhq DB Adapter: mysql2 URL: https://gitlab.xxxxx.com HTTP Clone URL: https://gitlab.xxxxx.com/some-project.git SSH Clone URL: git@gitlab.xxxxx.com:some-project.git Using LDAP: yes Using Omniauth: no

      Gitolite information Version: v3.2-gitlab-patched-0-g2d29cf7 Admin URI: git@gitlab:gitolite-admin Admin Key: gitlab Repositories: /home/source_control/git-gitlab/repositories/ Hooks: /home/source_control/git-gitlab/.gitolite/hooks/ Git: /usr/bin/git

      By Administrator on 2013-03-14T19:17:46 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: Razer6

      With the upcoming release this issue is outdated since GitLab doesn't use gitolite anymore. @maxlazio Please close

      By Administrator on 2013-03-20T19:01:06 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: kelas

      @Razer6 Sorry to say, but how "not relevant in unstable" is supposed to pass for "fixed in stable"? Which of the two - update production systems to unstable code, or suck it up and wait till 5.0 is good enough?

      By Administrator on 2013-03-20T21:04:26 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: Razer6

      GitLab 5.0 (stable) will be released tomorrow which solves the problem.

      By Administrator on 2013-03-21T06:16:07 (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
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    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
    participants
    Reference:

    Menu

    Projects Groups Snippets
    Help