1. Bitbucket Website
  2. Public Issue Tracker
  3. master

Issues

Issue #9647 closed

Initial push of repo fails with "error: RPC failed; result=22, HTTP code = 502"

Dave Beal
created an issue

Cloned a Linux kernel repo from elsewhere. Created a new Bitbucket repo to hold changes to it. Got this on the initial push to Bitbucket:

mitydsp$ git remote add origin https://dbeal@bitbucket.org/cp-lighting/acuity-controller-linux-critical-link.git
mitydsp$ git push -u origin --all
Password: 
Counting objects: 2320401, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (373955/373955), done.
Writing objects: 100% (2320401/2320401), 443.80 MiB | 1.14 MiB/s, done.
Total 2320401 (delta 1941133), reused 2292256 (delta 1924091)
error: RPC failed; result=22, HTTP code = 502

Tried it again after deleting and recreating the Bitbucket repo. Same result. Also tried importing the source repo directly into a new Bitbucket repo. That also failed.

Comments (5)

  1. Dave Beal reporter

    Hi Zach -

    Yep, still fails:

    mitydsp$ git push -u origin --all
    Password: 
    Counting objects: 2320401, done.
    Delta compression using up to 2 threads.
    Compressing objects: 100% (373955/373955), done.
    Writing objects: 100% (2320401/2320401), 443.80 MiB | 783 KiB/s, done.
    Total 2320401 (delta 1941133), reused 2292256 (delta 1924091)
    error: RPC failed; result=22, HTTP code = 502
    mitydsp$ git remote -v
    critical_link_origin    git://support.criticallink.com/home/git/linux-mityarm-335x.git (fetch)
    critical_link_origin    git://support.criticallink.com/home/git/linux-mityarm-335x.git (push)
    origin  https://dbeal@bitbucket.org/cp-lighting/acuity-controller-linux-critical-link.git (fetch)
    origin  https://dbeal@bitbucket.org/cp-lighting/acuity-controller-linux-critical-link.git (push)
    
  2. Log in to comment