Remote rejected unpacker error

Bitbucket Support

Knowledge base

Products

Jira Software

Project and issue tracking

Jira Service Management

Service management and customer support

Jira Work Management

Manage any business project

Confluence

Bitbucket

Git code management

Resources

Documentation

Usage and admin help

Answers, support, and inspiration

Suggestions and bugs

Feature suggestions and bug reports

Marketplace

Billing and licensing

Frequently asked questions

Viewport

Confluence

Error: Unpack Failed: Unpack-objects Abnormal Exit

Related content

Still need help?

The Atlassian Community is here for you.

Symptoms

Trying to GIT push to remote repository gets to the following error (in command prompt/terminal)

Diagnosis

1. Single user failed to push to remote repository. See #1 cause and resolution.
2. Multiple users failed to push to remote repository. See #2 cause and resolution.

Cause

1. The local repository may be corrupted. See #1 resolution.
2. Disk space in the server hosting Bitbucket Server is full. See #2 resolution.

Resolution

The following resolution shown are referring to the respective cause above.

1. To verify that the local repository is corrupted, you can clone your remote repository to another new directory and then push again. Running git repack might help in case the local repository is indeed corrupted.
2. If disk space is indeed full for Bitbucket Server, clear them and push again.

Источник

Cannot push to remote git repo from one machine to another in LAN

I’ve created bare repo on my machine with Linux, also cloned it into local repo (on the same machine) and I can push/pull with no problems.

On my workstation with Windows I’ve cloned that repo via ssh using git clone ssh://user@linuxhost/srv/git/repo.git and now cannot push anything. Git gives me following error:

Found no correct answer to my problem, or answers were to complex to understand. I’m pretty new and unfamiliar with Linux and configurating my own gitserver.

Thanks in advance

1 Answer 1

This means literally that when git goes to create a temporary directory to copy your changes into for further processing, the operating system is not allowing it to.

Specifically, as one of the first steps of the push process, git wants to create the directory .git/objects/incoming-XXXXXX where XXXXXX is a unique random identifier. This is what is failing.

The most common causes of this would be either that the security permissions of the repository directory do not allow the user you are SSH’ing as to write to it, or the disk is full.

To verify disk space, on the Linux host, run df -h and confirm that the filesystem the git repo is on does not show a high Use%, a low available number of blocks. Also try simply making a test file in the same location as the git repo.

To verify permissions, cd to the directory where the git repository is hosted on the remote, and run ls -l . Note the user and group that owns the file, and whether the user and/or group have write permissions here. To verify which groups your user is in, run groups $USER where $USER is the username.

If permissions are the problem, you may have to change the ownership of the git repository:

Or you may need to adjust the group membership of your SSH user:

Источник

How to Fix Git Push Insufficient Permission Error for Objects Permanently

Sometimes when you do a git push, you might get the following permission error message.

This error typically happens when multiple users are working on a particular git repository.

The following git push error indicates that it doesn’t have enough permission for adding a new object to the ./objects directory under your repository.

Apart from the obvious permission issue, there is also another underlying problem that needs to be addressed, which is explained in this tutorial.

It also shows that the git unpack failed with unpack-objects abnormal exit. Because of this error, it failed to push some refs as shown above.

First, cd to the git repository which is having this issue. If you don’t see the objects directory directly under your repository folder, then look under the .git folder as shown below.

In this particular case, when john is trying to do ‘git push’, he is getting the above error because some of the directories under the objects folder of git repository are owned by lisa as shown below.

Set the Appropriate Permissions on Objects Directory

To solve this problem, execute the following, which will set the group to git (or whatever group where all the users belongs to. Also make sure the user and group has read and write permission to the directory.

• Make sure all your users who need access to git are part of the git group. Change the “git” in the above chgrp command to whatever group where all your developers belong to.
• The “s” option in the “g+rws” is to set the setuid bit on the objects folder. This will make sure any new directory created under objects folder will make the group name from the objects folder which is owned by git group.

You may be tempted to execute the following on your objects directory, which will solve the problem that you are having. But, as you can imagine, it is not a good idea to do 777. Instead execute the above chgrp and chmod command.

But, even after doing the above, the same problem might return again, and you may have to do the above chgrp and chmod whenever the problem occurs.

So, apart from fixing the permission error as explained above, we also need to fix the underlying problem.

In this case, the git repository (for example: myproj) is not setup as shared repository for groups. It might just be a bare repository.

If it is not setup as shared repository, you’ll see the above “insufficient permission on objects directory” issue starts to show-up again.

To verify whether your repository is already setup for group sharing, do the following git config -l option inside your git repository that has the problem.

In the above output, we don’t see a parameter called “core.sharedrepository”. So, this particular repository (i.e myproj is not setup as shared repository).

The above command displays the configuration values from the “config” file that is located under your git repository.

The above is setup as a bare repository. To convert a bare repository to shared repository, do the following:

Note: In the above command, don’t replace the keyword “group” with your groupname (for example: git). Use the above above command exactly as shown without changing anything. The “group” in the above command should be typed exactly as it is.

Now, if you view the git config as shown below, you’ll see the “core.sharedrepository” parameter set to group.

The above will solve the insufficient permission issue permanently.

After you set the sharedrepository, if you view the config file under your git repository, you’ll notice that the value of sharedrepository parameter is set to 2 (which is group) as shown below.

Источник

Remote unpack failed: unpack-objects abnormal exit #13203

Description

After updating Gitea from 1.12.1 to 1.12.4 I am unable to push changes. Everytime I try to do that I got the following error:

Enter passphrase for key ‘/path/to/.ssh/id_rsa’:
Enumerating objects: 29, done.
Counting objects: 100% (29/29), done.
Delta compression using up to 16 threads
Compressing objects: 100% (14/14), done.
Writing objects: 100% (15/15), 5.13 KiB | 5.13 MiB/s, done.
Total 15 (delta 13), reused 3 (delta 1), pack-reused 0
remote: fatal: not a git repository: ‘.’
error: remote unpack failed: unpack-objects abnormal exit
To ssh://git.com:9999/group/repo.git
! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to ‘ssh://git.com:9999/group/repo.git’

This happens to all repositories hosted at Gitea. I tried to launch git fsck on server side and found no errors. I can clone repository, browse it via webui, etc, just cannot push changes back to remote.
I am pretty sure, you will need some additional data. Please let me know what I can do in order to investigate this.

The text was updated successfully, but these errors were encountered:

@belliash do you use the build in ssh server?

Yes, I use ssh server that is built into gitea, listening on custom port.
In logs I found just this:

2020/10/18 21:49:43 modules/ssh/ssh.go:63:sessionHandler() [T] SSH: Payload: git-receive-pack ‘/group/repo.git’
2020/10/18 21:49:43 modules/ssh/ssh.go:66:sessionHandler() [T] SSH: Arguments: [serv key-5 —config=/path/to/app.ini]

There are also some SQL queries like:
SELECT id , owner_id , name , fingerprint , content , mode , type , login_source_id , created_unix , updated_unix FROM public_key WHERE (content like ?) LIMIT 1

and permissions loaded:
2020/10/18 21:49:44 . s/repo_permission.go:154:func1() [T] Permission Loaded for 1:user in 41:group/repo:
Permissions: AccessMode: 4:owner, 5 Units, 0 UnitsMode(s): [
Units[0]: ID: 281 RepoID: ? Type: 1:UnitTypeCode Config: <>
Units[1]: ID: 326 RepoID: ? Type: 2:UnitTypeIssues Config: <«EnableTimetracker»:false,»AllowOnlyContributorsToTrackTime»:false,»EnableDependencies»:true>
Units[2]: ID: 327 RepoID: ? Type: 3:UnitTypePullRequests Config: <«IgnoreWhitespaceConflicts»:false,»AllowMerge»:true,»AllowRebase»:true,»AllowRebaseMerge»:true,»AllowSquash»:true>
Units[3]: ID: 282 RepoID: ? Type: 4:UnitTypeReleases Config: <>
Units[4]: ID: 325 RepoID: ? Type: 5:UnitTypeWiki Config: <> ]
2020/10/18 21:49:44 . ters/private/serv.go:363:ServCommand() [D] Serv Results:
IsWiki: false
IsDeployKey: false
KeyID: ? KeyName: user@host
UserName: user
UserID: ?
OwnerName: group
RepoName: repo
RepoID: ?

I obfuscated logs from some sensitive data.

I have just found out that I cannot edit files online via web interface, because I got another error:

I checked permissions and they look ok. I can write under that path as well as git user. On the other hand setting chmod recursively to 777 does not resolve this.

The second problem looks somehow similar to #12085 except I got xattr enabled. I wonder if both are connected.

Источник

Git, ошибка: сбой удаленной распаковки: невозможно создать каталог временных объектов — путем создания новой ветки

Я пытаюсь создать новую ветку в своем репо.

Это сработало. Итак, я изменил несколько файлов и сделал:

Это сработало хорошо, но я попытался подтолкнуть его, и это не сработало:

Не знаю, почему не работает.

У меня есть права администратора на репо. Я подверг цензуре ссылку на репо, потому что это внутреннее репо с частной ссылкой.

Если кто-то придет к выводу, моим решением было просто удаление файлов на моем сервере разработки. Оказывается, мое хранилище на сервере разработки было переполнено.

Просто для справки, я получил это, потому что я случайно клонировал репо, используя учетную запись пользователя, которая была действительна на сервере, но не имела доступа на запись в репо (D’Oh!). Я исправил это, отредактировав запись «удаленное происхождение» в .git / config.

Проверьте права на каталог .git на стороне сервера (или создайте git init на стороне сервера от пользователя, отправившего запрос)

@MartinCR что вы редактировали в записи remote-origin в .git / config? Это было на удаленном сервере? или местный клон?

@ m4l490n в локальном клоне: в разделе [remote «origin»] я просто изменил имя пользователя в строке url = . на имя, у которого был доступ на запись

@MartinCR похоже, что это не сработает для меня. В используемом мной URL-адресе нет пользователя. Мой URL: ssh://git.server.com:2222/path/to/repo/repo.git

@ m4l490n интересно . у меня url = my.git.user@my.git.server:/path/to/repo.git — поэтому я предполагаю, что ваш сервер использует ssh с аутентификацией сертификата. У вас есть действующий сертификат в правильном месте?

@MartinCR У меня, должно быть, была опечатка. Проблема заключалась в том, что мне действительно нужно указывать пользователя при клонировании, а не только git.server.com . Должен быть user@git.server.com

Это сообщение об ошибке:

указывает на то, что в репозитории Git в сервер (а не в вашем Git) не хватает места или возникают аналогичные проблемы с сервером, 1 или он установлен неправильно. То есть, учитывая:

вам нужно будет войти в систему на машине, которая обслуживает HTTP-трафик на git.int.censoredlink , перейти в каталог scm/freeb/freebrep.git и исправить там установку. Скорее всего, это проблема с разрешениями: принимающий Git должен иметь возможность создать в области объектов каталог с именем incoming-XXXXXX с замененными идентификаторами X на уникальный идентификатор, а затем создать в этом каталоге подкаталог pack .

Все входящие объекты и файлы пакетов помещаются в эти каталоги в виде процедуры карантина, пока серверные обработчики Git не будут удовлетворены запросами на обновление ссылочного имени. Если push не удается, карантинный каталог просто удаляется. Если отправка прошла успешно, помещенные в карантин объекты и / или файлы пакетов переносятся (и тонкие пакеты корректируются) в обычную область хранилища объектов. Обратите внимание, что миграция может завершиться неудачно, даже если процесс карантина завершится успешно; но если это произойдет, вы получите сообщение об ошибке разные клиенту. (Эта ошибка также должна быть исправлена ​​на сервере.)

Примечание: довольно необычно отправлять URL-адреса http:// , а не https:// или ssh:// . Изучите конфигурацию вашего сервера, чтобы узнать, кому будут принадлежать различные файлы, созданные таким образом, и какие разрешения будут у веб-сервера.

1 Если жесткий диск выходит из строя, Linux иногда помечает диск и / или его файловые системы только для чтения. Или, даже если у вас есть место на диске, у вас могут закончиться inodes. Ряд различных основных причин приведет к одинаковому наблюдаемому поведению на стороне вашего клиента. Если вы администратор Linux, проверяющий сервер, ищите сообщения системного журнала и учитывайте как вывод df , так и df -i .

Не совсем правильно, но, тем не менее, я проголосовал за это, поскольку он содержал подсказки, необходимые для быстрой отладки: mkdir objects/incoming-XXXXXX показал «на устройстве не осталось места» в случае, когда администратору сервера необходимо исправить это, с чем я только что столкнулся. Если бы вы могли переформулировать или перестроить ответ на это, было бы здорово. (Я согласен с все вашими замечаниями, включая последний абзац, но это не единственная причина такого эффекта.)

@mirabilos Это возможная причина Другой. Неправильные разрешения — более типичная проблема.

Источник

Sometimes when you do a git push, you might get the following permission error message.

This error typically happens when multiple users are working on a particular git repository.

The following git push error indicates that it doesn’t have enough permission for adding a new object to the ./objects directory under your repository.

Apart from the obvious permission issue, there is also another underlying problem that needs to be addressed, which is explained in this tutorial.

$ git push
counting objects: 6, done.
Delta compression using upto 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 388 bytes, | 0 bytes/s, done.
Total: 4 (delta 1), reused 0 (delta 0)

error: insufficient permission for adding an object to repository database ./objects
fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
 ! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to john@192.168.100.1:/home/git/myproj

It also shows that the git unpack failed with unpack-objects abnormal exit. Because of this error, it failed to push some refs as shown above.

First, cd to the git repository which is having this issue. If you don’t see the objects directory directly under your repository folder, then look under the .git folder as shown below.

[john@devdb]$ cd /home/git/myproj
(or)
[john@devdb]$ cd /home/git/myproj/.git

In this particular case, when john is trying to do ‘git push’, he is getting the above error because some of the directories under the objects folder of git repository are owned by lisa as shown below.

[john@devdb]$ ls -l objects
drwxr-xr-x 2 john  git 4096 Oct  8  2016 01
drwxr-xr-x 2 john  git 4096 Oct  8  2016 02
drwxr-xr-x 2 lisa lisa 4096 Oct  8  2016 03
drwxr-xr-x 2 lisa lisa 4096 May  1  2017 04
drwxr-xr-x 2 john  git 4096 May  1  2017 05
drwxr-xr-x 2 john  git 4096 May  6  2017 06

Set the Appropriate Permissions on Objects Directory

To solve this problem, execute the following, which will set the group to git (or whatever group where all the users belongs to. Also make sure the user and group has read and write permission to the directory.

cd /your/git/repo

chgrp -R git objects

chmod -R g+rws objects

In the above:

• Make sure all your users who need access to git are part of the git group. Change the “git” in the above chgrp command to whatever group where all your developers belong to.
• The “s” option in the “g+rws” is to set the setuid bit on the objects folder. This will make sure any new directory created under objects folder will make the group name from the objects folder which is owned by git group.

You may be tempted to execute the following on your objects directory, which will solve the problem that you are having. But, as you can imagine, it is not a good idea to do 777. Instead execute the above chgrp and chmod command.

chmod -R 777 objects

Share the Git Repository with a Group

But, even after doing the above, the same problem might return again, and you may have to do the above chgrp and chmod whenever the problem occurs.

So, apart from fixing the permission error as explained above, we also need to fix the underlying problem.

In this case, the git repository (for example: myproj) is not setup as shared repository for groups. It might just be a bare repository.

If it is not setup as shared repository, you’ll see the above “insufficient permission on objects directory” issue starts to show-up again.

To verify whether your repository is already setup for group sharing, do the following git config -l option inside your git repository that has the problem.

$ cd /home/git/myproj

$ git config -l
user.name=John Smith
user.email=john@thegeekstuff.com
core.repositoryformatversion=0
core.filemode=true
core.bare=true
core.logallrefupdates=true

In the above output, we don’t see a parameter called “core.sharedrepository”. So, this particular repository (i.e myproj is not setup as shared repository).

The above command displays the configuration values from the “config” file that is located under your git repository.

$ cd /your/git/repo

$ cat config 
[core]
        repositoryformatversion = 0
        filemode = true
        bare = true
        logallrefupdates = true

The above is setup as a bare repository. To convert a bare repository to shared repository, do the following:

git config core.sharedRepository group

Note: In the above command, don’t replace the keyword “group” with your groupname (for example: git). Use the above above command exactly as shown without changing anything. The “group” in the above command should be typed exactly as it is.

Now, if you view the git config as shown below, you’ll see the “core.sharedrepository” parameter set to group.

$ git config -l
user.name=John Smith
user.email=john@thegeekstuff.com
core.repositoryformatversion=0
core.filemode=true
core.bare=true
core.logallrefupdates=true
core.sharedrepository=group

The above will solve the insufficient permission issue permanently.

After you set the sharedrepository, if you view the config file under your git repository, you’ll notice that the value of sharedrepository parameter is set to 2 (which is group) as shown below.

$ cat config 
[core]
        repositoryformatversion = 0
        filemode = true
        bare = true
        sharedrepository = 2
[receive]
        denyNonFastforwards = true

Also, anytime you make a git repository as sharedrepository for group using the above command, it will also set the receive.denyNonFastforwards to true automatically as shown above.