1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #4537 resolved

About The Exit Code 128

Hong Sam
created an issue

Hey guys,I used git tool to download the source code about one month,but today,i can't pull the code from server,here are the error tips:

git.exe clone --progress -v "https://hsam@bitbucket.org/sym1987/ctow.git" "D:\CTOW\ctow"

Cloning into 'D:\CTOW\ctow'... remote: Counting objects: 4767
remote: Compressing objects: 100% (4496/4496)
Receiving objects: 11% (533/4841), 892.00 KiB | 2 KiB/s fatal: early EOF fatal: The remote end hung up unexpectedly fatal: index-pack failed error: RPC failed; result=18, HTTP code = 200

git did not exit cleanly (exit code 128)

Hope your guys give me help,thanks!

Comments (26)

  1. Dylan Etkin

    Hi Hong,

    Are you still seeing this issue? We did rollout some changes yesterday and you may have gotten that error while we were right in the middle.

    Cheers,

    Dylan

  2. Hong Sam reporter

    Hi Dylan, I just redo that,it still doen't work well. Here are the tips: git.exe clone --progress -v "https://hsam@bitbucket.org/sym1987/ctow.git" "D:\CTOW\ctow"

    Cloning into 'D:\CTOW\ctow'... remote: Counting objects: 4787 remote: Compressing objects: 100% (4582/4582) Receiving objects: 19% (979/4927), 1.50 MiB fatal: early EOF fatal: The remote end hung up unexpectedly fatal: index-pack failed error: RPC failed; result=18, HTTP code = 200

    git did not exit cleanly (exit code 128)

    Thanks.

    Hong

  3. Mouhong Lin

    Hi Dylan,

    I also got this error (Hong and I are both working on this project). Some days ago, I got an error "Remote: The remote end hung up unexpectedly" while I was pushing changes to the server. I fixed that by executing this command "git config –global http.postBuffer 524288000“. I have other repositories in bitbucket, but they all work fine.

  4. Erik van Zijst staff

    Your repository was quite fragmented, which would have made everything a lot slower. I have repacked everything and tested cloning and was not able to reproduce your errors.

    Can you give it another go?

  5. Hong Sam reporter

    Hi Erik, I just redo try again, and the show the same tips. you may check out with my account,let me know if you want to try.

    git.exe clone --progress -v "https://hsam@bitbucket.org/sym1987/ctow.git" "D:\CTOW\ctow"

    Cloning into 'D:\CTOW\ctow'... POST git-upload-pack (174 bytes) remote: Compressing objects: 100% (1626/1626) Receiving objects: 20% (1040/5006), 4.80 MiB | 6 KiB/s fatal: early EOF fatal: The remote end hung up unexpectedly fatal: index-pack failed error: RPC failed; result=18, HTTP code = 200

    git did not exit cleanly (exit code 128)

  6. Bobby Dean

    I am having this same issue....

    remote: Counting objects: 7106, done. remote: Compressing objects: 100% (6484/6484), done. fatal: The remote end hung up unexpectedlyGiB | 1.39 MiB/s fatal: early EOF fatal: index-pack failed

  7. Francois Gaspard

    Hi guys, Same issue over here... Any solution yet?

    remote: Counting objects: 11204, done.

    remote: Compressing objects: 100% (3646/3646), done.

    Read from remote host bitbucket.org: Connection reset by peer

    fatal: The remote end hung up unexpectedly

    fatal: early EOF

    fatal: index-pack failed

  8. Thuan Do The

    Still not working :( Here is my log

    POST git-upload-pack (174 bytes)
    remote: Compressing objects: 100% (304/304)   
    Receiving objects:  25% (118/472), 7.35 MiB | 1 KiB/s
    fatal: early EOF
    fatal: The remote end hung up unexpectedly
    fatal: index-pack failed
    error: RPC failed; result=18, HTTP code = 200
    
    git did not exit cleanly (exit code 128) (971184 ms @ 5/3/2013 4:27:55 PM)
    
  9. Nate Pendleton

    I am having this problem as well. I have tried to clone multiple times without success over the last few days. The genius that set it up included some test video files, so I am sure that is not helping.

  10. Dragon Hill

    same here... I have a working repository that works fine with an existing cloned folder. But when I try to clone it on another machine it bombs out. I first observed this when I tried to fork the project. To debug I thought I should make sure I could clone it and that's where I hit a brick wall

  11. churi24

    I had the same problem and I solved adding this to .gitconfig fixes: [core] packedGitLimit = 512m packedGitWindowSize = 512m [pack] deltaCacheSize = 2047m packSizeLimit = 2047m windowMemory = 2047m

  12. Oscar Galvis

    Hi,

    we are getting this error since yesterday on our Bamboo Agents. Has anything changed?

    03-Nov-2015 11:49:44 Caused by: com.atlassian.bamboo.repository.RepositoryException: Cannot fetch branch 'refs/heads/master' from 'https://bitbucket.org/....' to source directory 'C:\build-dir\INTERNAL-JWTAUT-JOB1'. command 'c:\Program Files (x86)\Git\bin\git.exe' fetch https://**@bitbucket.org/asdfadsf/jwt-authenticator +refs/heads/master:refs/heads/master --update-head-ok failed with code 128. Working directory was [C:\build-dir\INTERNAL-JWTAUT-JOB1]., stderr: 03-Nov-2015 11:49:44 fatal: Not a git repository (or any of the parent directories): .git

  13. David Cattley

    I too have been seeing errors between Bamboo (cloud) and Bitbucket. Bamboo is logging errors indicating it cannot detect changes as well as logging errors that it cannot detect branches.

    Both error types (there are many many instances) are all ultimately caused by error return 128 from Bitbucket while attempting to access <repo>/info/refs or perform a ls-remote.

  14. Log in to comment