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

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

  • Report abuse

  • New issue

  • Report abuse

permissions denied after failed import

Closed

permissions denied after failed import

Created by: koebi001

During importing while creating a new repository a timeout accoutered which leads to a damaged repository.

Create a new repository and add a URL to a large repository for import. The time to import is limited. After some time a message appears about a timeout with the suggestion to clone the repository add the new one as a remote site and use the push command. Put righter pushing via ssh or https is working. Always returns permission denied. To solve the problem it is necessary to delete the repository and recreate it without to use the import function. After that it is possible to use the git push command without problems. The repository I used has only one commit with about 350MB.

I suspect that after the timeout a damaged repository exists on the server which should get removed after the timeout occurs.

System: debian wheezy virtual machine with 2 cores and 2GB ram. Gitlab installed using the deb packlage 7.0.0-omnibus-1

Linked issues
0


  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: fjen

    i can reproduce this issue with gitlab 7.1.0 / gitlab-shell 1.9.6 on debian testing/jessie. After trying to import a new project from a faulty git URL like a non existend repository, gitlab asks for a retry with an other url. When proceeding without a retry, the project is unusable. No clone / push is possible. There is no repository directory on the filesystem.

    $ git clone git@host:fjen/import-test.git
    Klone nach 'import-test'...
    fatal: '/home/git/repositories/fjen/import-test.git' does not appear to be a git repository
    fatal: Could not read from remote repository.
    
    Please make sure you have the correct access rights
    and the repository exists.
    $ git remote add origin git@host...
    $ git push origin master
    Access denied.
    fatal: Could not read from remote repository.
    
    Please make sure you have the correct access rights
    and the repository exists.

    sidekiq.log:

    2014-07-30T13:27:42Z 30326 TID-5wsvo RepositoryImportWorker JID-1f8760ef51b225705a12a443 INFO: start
    Klone in Bare-Repository '/home/git/repositories/fjen/import-test.git'...
    fatal: could not read Username for 'https://github.com': No such device or address
    /home/git/gitlab-shell/lib/gitlab_projects.rb:23:in `symlink': No such file or directory @ sys_fail2 - (/home/git/gitlab-shell/hooks/update, /home/git/repositories/fjen/import-test.git/hooks/update) (Errno::ENOENT)
    from /home/git/gitlab-shell/lib/gitlab_projects.rb:23:in `create_hooks'
    from /home/git/gitlab-shell/lib/gitlab_projects.rb:119:in `import_project'
    from /home/git/gitlab-shell/lib/gitlab_projects.rb:42:in `exec'
    from /home/git/gitlab-shell//bin/gitlab-projects:25:in `<main>'
    2014-07-30T13:27:43Z 30326 TID-5wsvo RepositoryImportWorker JID-1f8760ef51b225705a12a443 INFO: done: 1.067 sec

    By Administrator on 2014-07-30T13:43:56 (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
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