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

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

  • Report abuse

  • New issue

  • Report abuse

Empty repo after import

Closed

Empty repo after import

Created by: Thijmen

Hi,

After I imported old projects by using: bundle exec rake gitlab:import:repos RAILS_ENV=production

The projects are being generated, but when I try to view the files, I am getting the screen what you usually see when you create a project.

Bug of fuckup of me?

Linked issues
0

Related merge requests

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: jaymzcd

    I'm having a similar issue - did an install of 5.0 as per the instructions.md. The import all worked ok but any sort of cloning or interaction with the repo's tells me that they dont exist or are empty - yet the bare repos exist in the correct folder and gitlab:check tells me it's configured correctly.

    Trying to make a new project via the admin completes ok but nothing is ever created in the repos folder and trying to push gives errors due to it not existing.

    Other than that it runs fine and without error - can't see anything suggesting a serious misconfiguration in logs or the interface itself.

    git@koopa:~/gitlab$ ls /home/git/repositories/redmine.git/
    branches  config  description  HEAD  hooks  info  objects  refs
    
    git@koopa:~/gitlab$ bundle exec rake gitlab:check RAILS_ENV=production #
    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? ... OK (1.1.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: ... 
    Administrator / redmine ... 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? ... 
    
    Administrator / redmine ... can't create, repository is empty
    
    ...

    On a local machine:

    [12:31][bowser][jaymz][tmp]$ git clone git@gitlab-host:root/redmine.git
    Cloning into 'redmine'...
    fatal: Could not read from remote repository.
    
    Please make sure you have the correct access rights
    and the repository exists.
    
    [12:31][bowser][jaymz][tmp]$ ssh git@gitlab-host
    PTY allocation request failed on channel 0
    Welcome to GitLab, !
    Connection to gitlab-host closed.
    

    If I use a user for that gitlab server that has shell access I can clone out the repo ok:

    [12:33][bowser][jaymz][tmp]$ git clone ssh://jaymz@gitlab-host/home/git/repositories/redmine.git
    Cloning into 'redmine'...
    remote: Counting objects: 2366, done.
    remote: Compressing objects: 100% (1887/1887), done.
    remote: Total 2366 (delta 434), reused 2131 (delta 338)
    Receiving objects: 100% (2366/2366), 3.99 MiB, done.
    Resolving deltas: 100% (434/434), done.

    By Administrator on 2013-03-25T12:37:10 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: magJ

    +1

    By Administrator on 2013-04-03T23:09:50 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: escaped

    The pull request from #2932 might fix this. It has not been applied to branch 4-2-stable or 5-0-stable or master. I am on version 4.1 so i can't test it.

    By Administrator on 2013-04-05T07:17:19 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: dblessing

    Definitely seeing this issue in 5.0.1. It's going to complicate our migration to GitLab for sure.

    By Administrator on 2013-04-10T21:56:22 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: jwthomp

    I've encountered this on stable as well.

    By Administrator on 2013-04-11T04:56:04 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: anlek

    +1 to this. I also get a 404 when I try to view my gitlab homepage. (after logging in)

    By Administrator on 2013-04-12T05:40:06 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: Razer6

    Maybe related to #3693?

    By Administrator on 2013-05-13T19:23:21 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: tnarik

    definitely related.

    By Administrator on 2013-05-29T22:09:51 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: bbodenmiller

    Does this issue still exist on the latest master? Thanks for the issue report. Please reformat your issue to conform to the issue tracker guidelines found in our contributing guidelines.

    By Administrator on 2013-06-15T21:30:17 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: Razer6

    @bbodenmiller Yes

    By Administrator on 2013-06-22T12:09:44 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: Razer6

    Closing this as a duplicate of #3693 which has more information/logs.

    By Administrator on 2013-06-22T12:16:15 (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
2
Labels
Awaiting feedback Git/Grit
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