Git push - fatal: write error: Bad file descriptor

The name of the picture


Git push - fatal: write error: Bad file descriptor



I'm new to Git, so please forgive me if this is a stupid question.



On my initial push to GitHub, using git push origin master


git push origin master



I'm getting following error(s):



Counting objects: 1499, done.
Delta compression using up to 16 threads.
Compressing objects: 100% (1455/1455), done.
error: pack-objects died of signal 923 MiB | 9.10 MiB/s
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
fatal: write error: Bad file descriptor



Am I missing something?





Maybe the remote hard drive disk is full?
– jbaptperez
Mar 10 '16 at 9:07





Would that effect a push to GitHub?
– Carl Johnston
Mar 10 '16 at 9:26





Your right, on github, you shouldn't have this kind of problem... Your kind of problem is analysed here, and a possibly solution is here
– jbaptperez
Mar 10 '16 at 9:32







Thanks. Unfortunately that doesn't seem to have solved the problem. But thanks for the resources!
– Carl Johnston
Mar 10 '16 at 9:38




2 Answers
2



When I got this same error, the following command fixed this issue
git config --global pack.windowMemory "32m".


git config --global pack.windowMemory "32m"





Thanks very much. I still get the same issue, but thanks for your help none the less!
– Carl Johnston
Mar 10 '16 at 12:02



I was getting same error few days back what worked for me was that default file post size for Git has been exceeded.So navigate to repo and run this command to increase the buffer to 500MB after navigating to the repository git config http.postBuffer 524288000


git config http.postBuffer 524288000





Thanks for the response. I tried it, and it still returns the same error. I'm not sure what's going wrong, to know how to fix it.
– Carl Johnston
Mar 10 '16 at 9:23






By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Popular posts from this blog

Stripe::AuthenticationError No API key provided. Set your API key using “Stripe.api_key = ”

CRM reporting Extension - SSRS instance is blank

Keycloak server returning user_not_found error when user is already imported with LDAP