Skip to content

GitLab

  • Menu
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
  • #5101

Closed
Open
Created Sep 16, 2013 by Administrator@rootOwner

Project appears to be empty after pushing commits

Created by: taypan

Hi, I have just installed gitlab following this doc: https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/installation.md . Installation was AFAIK without problems. After that I have created a new project and pushed some changes into it (using git remote add origin ... ; git push -u origin master ). But now when I look into gitlab I still see commands to setup repository. It appears like it wasn't pushed into repo.

When I look in /home/git/repositories into suitable folder changes are there (git log). I am running gitlab behind apache proxy so i have made some changes in port settings of gitlab and unicorn.

My bundle exec rake gitlab:check RAILS_ENV=production report:

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.1)
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
update hook up-to-date? ... yes
update hooks in repos are links: ... 
taypan / LHE ... repository is empty
taypan / lhe2 ... repository is empty

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? ... yes
Projects have satellites? ... 
taypan / LHE ... can't create, repository is empty
taypan / lhe2 ... can't create, repository is empty
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.8.1)

Checking GitLab ... Finished

sudo netstat -tulpn:

`Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      1148/mysqld     
tcp        0      0 0.0.0.0:6379            0.0.0.0:*               LISTEN      18958/redis-server
tcp        0      0 127.0.0.1:8080          0.0.0.0:*               LISTEN      24485/unicorn.rb -E
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      15062/sshd      
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      17199/master    
tcp6       0      0 :::80                   :::*                    LISTEN      23956/apache2   
tcp6       0      0 :::22                   :::*                    LISTEN      15062/sshd      
tcp6       0      0 :::25                   :::*                    LISTEN      17199/master``

Not sure if gitlab bug or (more like) my fault. Thanks for any help I am desperate after hours of searching for solution. I have found some similar issues here, but I think non of them is my case.

Assignee
Assign to
Time tracking