Constantly getting "fatal: The remote end hung up unexpectedly"

Home Community Forums Amazon Web Services Certifications AWS Certified Developer โ€“ Associate Constantly getting "fatal: The remote end hung up unexpectedly"

This topic contains 6 replies, has 4 voices, and was last updated by Melissa Stephen Mike Stephen 5 months, 4 weeks ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #100034485
    Melissa Stephen
    Melissa Stephen
    Participant

    When pushing to my repository I get “fatal: The remote end hung up unexpectedly” a lot. Pushing again and again will eventually let the push through, sometimes after toying with different values in “git config –global http.postBuffer xxxx”. Why is this? I can see why it would happen when I have large files that are being pushed, but it doesn’t seem to matter much how much is in the commits I am pushing.

    If I google the issue, all solutions seems to be to move to ssh, but I am already on ssh so that is not the problem.

    It is very annoying and time consuming…

    EDIT: Now I have a few commits that I can’t push at all. I constantly get the error above, meaning I cn’t push my changes to the repo.

    #100034486
    Mathew George
    Mathew George
    Participant

    Please follow the instructions from the following link to turn on verbose logging, and re-run your git command. Please send us the output.

    http://docs.aws.amazon.com/codecommit/latest/userguide/troubleshooting.html#troubleshooting-debug

    #100034487
    Melissa Stephen
    Melissa Stephen
    Participant

    I actually got it through by using https instead of ssh, but I can post the verbose output if I get the error again.
    I did, however, try with verbose output myself to see what seemed to be the problem and it gave no extra clues. The push is fine through the “Writing objects…”-step, reaching 100% but after it throws the error with no extra messages in verbose mode compared to non-verbose.

    #100034488
    Mathew George
    Mathew George
    Participant

    The longer the distance and the longer the connection remains open (usually, but not exclusively, proportional to the amount of data transferred), the higher probability of a network interruption occurring.

    If possible, I would recommend using the closest AWS region available to you where CodeCommit is available. For an up-to-date list of regional CodeCommit endpoints, check http://docs.aws.amazon.com/codecommit/latest/userguide/regions.html. Another potential solution would be to access your repository from an EC2 instance in the same region as your CodeCommit repository.

    #100034489
    Saim Qadeer
    Saim Qadeer
    Participant

    I have noticed this issue too, pushes by ssh frequently time out, but https is fast and reliable. I am using the closet region to my location.

    #100034490
    Mike Stephen
    Mike Stephen
    Participant

    Same issue here. First time this has happened after months of multiple pushes throughout the day. Verbose gives no clues:

    Counting objects: 5, done.
    Delta compression using up to 4 threads.
    Compressing objects: 100% (5/5), done.
    Writing objects: 100% (5/5), 788 bytes | 0 bytes/s, done.
    Total 5 (delta 2), reused 0 (delta 0)
    An unknown error occurred.
    fatal: The remote end hung up unexpectedly
    fatal: The remote end hung up unexpectedly

    This is for only a few lines of code on a single file. Been going on for over an hour now.

    #100034491
    Mike Stephen
    Mike Stephen
    Participant

    got an alert from aws:

    12:21 PM PDT We can confirm that some customers are receiving throttling errors accessing S3. We are currently investigating the root cause.

    further:

    12:28 PM PDT We are investigating increased error rates for Git Push, Git Pull and API calls in the US-EAST-1 Region.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.

Translate ยป