This repository was archived by the owner on Nov 30, 2021. It is now read-only.
This repository was archived by the owner on Nov 30, 2021. It is now read-only.
git push: insufficient permission for adding an object to repository database #1843
Closed
Description
This just happened out of nowhere. I was able to push to my deis master just fine until this happened.
> git push deis master
Counting objects: 9, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 477 bytes | 0 bytes/s, done.
Total 5 (delta 3), 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
To ssh://git@deis.staging.asia.gce.redacted.com:2222/redacted-website.git
! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to 'ssh://git@deis.staging.asia.gce.redacted.com:2222/redacted-website.git'
Edit:
Permissions log: http://pastebin.com/zjsER1e8
Edit 2:
For anyone else that is experiencing this issue, the fix was we deleted the repository from the builder. It works but it's not ideal.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Participants
Activity
gabrtv commentedon Sep 15, 2014
@vincentpaca can you take a look at disk space inside the
deis-buildercomponent? I wonder if a disk space error could result in an I/O error that looks like a permissions error.vincentpaca commentedon Sep 16, 2014
@gabrtv thanks for your help.
If you look at the logs it looks like the permissions got messed up somehow. Take a look at
line 2120on pastebin. That's when it started to add root.Could it probably be caused by a failed deploy?
gabrtv commentedon Sep 16, 2014
Note this is on CoreOS 410 and an older version of Deis (which I'm not sure).
It appears
rootstarted to own files that should be owned bygitstarting on Sept 6. Not sure how that happened given how we execute thegit-shelland hooks.vincentpaca commentedon Sep 16, 2014
We're currently using Deis v0.11.0
carmstrong commentedon Sep 26, 2014
We had another customer report this happening on EC2. We need to figure out the root cause of this.
vincentpaca commentedon Sep 27, 2014
Hmm. I haven't had this issue since. This thing is hard to reproduce too and it seems that it was very edge case. I've had this similar issue before though when I had self-hosted git.
justinhennessy commentedon Oct 24, 2014
Just letting you know we have had this issue a couple of times. We are currently stuck can't seem to get deploys/builds working again for this app. We are on Deis v0.12
bfosberry commentedon Oct 30, 2014
We came across this issue also just now
Solution was
carmstrong commentedon Oct 30, 2014
@bfosberry Any insight as to what would have changed around that time to cause this? Node restart? Builder restart?
bfosberry commentedon Oct 30, 2014
Nah, no idea. deis-builder was still running, I dont think anything restarted. We will keep an eye out for this in the future and grab logs
jorihardman commentedon Nov 14, 2014
This has been happening to me once a day since upgrading to 1.0.0. I haven't noticed any pattern yet, but will check my logs the next time it happens.
carmstrong commentedon Nov 14, 2014
@jorihardman I think that's the most often we've seen this occur, so while I'm sorry you're seeing it, I'm glad that it's reproducible. Please let us know if anything jumps out at you as relevant. We really want to get to the bottom of this, but it seems hard to reproduce.
jorihardman commentedon Nov 17, 2014
I just noticed something that may have caused this. I canceled a push (^C) just after compressing and writing objects. I pushed about 10 seconds later and got this error.
34 remaining items