Re: Fwd: Re: git send-pack: protocol error: bad band #50

[Jeff King]

On Sat, Apr 13, 2013 at 12:03:15PM +0100, João Joyce wrote:

 I have tried to remove and recreate my git folder and remove some
 files to get more logs. Here they are:

Your output looks quite odd.

 packet: push  
 capabilities^{}\0 report-status delete-refs side-band-64k quiet ofs-delta
 packet: push 

So this is the server advertising its refs. It doesn't have any, so it
just gives a blank capabilities string, followed by a flush. OK.

 packet: push  
 17c420b8bd99856aee6da9c1743f6df0ec18a9ca refs/heads/master\0report-status 
 side-band-64k
 packet: push 

And we want to push up one ref, so we send it, along its old and new
sha1s, its name, and our own capabilities list. And then we flush. OK.

 packet: push 
 20b8bd99856aee6da9c1743f6df0ec18a9cac28267338c198573ad59e89d0acc445a62b3d127
 acf853d0a30287d9455dbe1707edeb16cc3e9b22

Now what the heck is this? We should be sending the packfile next,
and the server should send us back the ref status. It would look
something like:

packet: push  
capabilities^{}\0 report-status delete-refs side-band-64k quiet ofs-delta
packet: push 
packet: push  
662bbff2308c7e72f417d3419f4984222faf7ef8 refs/heads/master\0 report-status 
side-band-64k
packet: push 
packet: push \1000eunpack ok0019ok refs/heads/master
packet: push 
packet: push unpack ok
packet: push ok refs/heads/master
packet: push 

What is generating that output on the server? Do you have any hooks on
the server repository that might generate output (we _should_ be
channeling their output over the sideband, but we might have missed a
case). What transport are you using (git-over-ssh, git-over-http, etc)?

-Peff
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Fwd: Re: git send-pack: protocol error: bad band #50

[João Joyce]

/readme.md7c187a1f2a58391032833d64230848c380b7aab8 
server_files/libraries/restler/public/examples/_003_multiformatc49bc802bf0ae84473727b94a7386cd914c85423 
server_files/libraries/restler/public/examples/_003_multiformat/BMI.php9da7ae6f117734c6117a6c8b54393e91af6e742f 
server_files/libraries/restler/public/examples/_003_multiformat/index.php10f91065493c3e09c07a94afa8e5ddeef96f3ea3 
server_files/libraries/restler/public/examples/_003_multiformat/readme.html427d73c1e3e7b3fe17b012884b99d657f7f3f578 
server_files/libraries/restler/public/examples/_003_multiformat/readme.mdd82721c7b2ca5ab27bf5481553f7d6ab611d4405 
server_files/libraries/restler/public/examples/_004_error_response4cd66b540f1808b740ac111a4025baa4a0ab03ec 
server_files/libraries/restler/public/examples/_004_error_response/Currency.php8100292b2350e778532a4f8c069381454a55e1bd 
server_files/libraries/restler/public/examples/_004_error_response/index.phpc1e22f76f20d7e7a40b8b6746824ecb21c3b0edf 
server_files/libraries/restler/public/examples/_004_error_response/readme.html37c7c3d1f106ae143099d1899efe111454a44dd7 
server_files/libraries/restler/public/examples/_004_error_response/readme.md9d0b58ccb1b725a7356b8cd1fb8f57a55ad18b17 
server_files/libraries/restler/public/examples/_005_protected_api472b59421e5154a4a9d9bae69b2bc89cb8c96e7b 
server_files/libraries/restler/public/examples/_005_protected_api/Secured.php13869b74f5020934c2575d43639d33ddada1cd9c 
server_files/libraries/restler/public/examples/_005_protected_api/Simple.phpfa9b07eb5b0a3b71e0f91c106d6df440adafe1c9 
server_files/libraries/restler/public/examples/_005_protected_api/SimpleAuth.phpe7412bea250fa574e1beadd428dfcd2c0770e34e 
server_files/libraries/r
packet: push  
capabilities^{}\0 report-status delete-refs side-band-64k quiet ofs-delta

packet: push 
packet: push  
bbadedcc30b580f950f9023b060769c620c963c7 refs/heads/master\0 
report-status side-band-64k

packet: push 


On 04/11/2013 07:37 PM, Jonathan Nieder wrote:
 Hello,

 João Joyce wrote:

 I am not sure this is the right place to ask this.
 You're in the right place.

 [...]
 I am trying to push some files to a server with git push. I have
 configured the server to push the files:
  git remote set-url test ssh://u...@location.com:2200/fullpath/

 but I am getting the following error:
  git send-pack: protocol error: bad band #50
  fatal: The remote end hung up unexpectedly
 That means that where git expected to read a binary sideband number,
 it instead received the byte \x32 (ASCII '2').

 Without more details, it's hard to debug this further.  Can you get
 a trace of the communication by setting the envvar
 GIT_TRACE_PACKET=/tmp/log on the client?

 Thanks and hope that helps,
 Jonathan


Hi,

Thank you for the help. Here is the trace:

packet: push  
capabilities^{}\0 report-status delete-refs side-band-64k quiet ofs-delta

packet: push 
packet: push  
17c420b8bd99856aee6da9c1743f6df0ec18a9ca refs/heads/master\0 
report-status side-band-64k

packet: push 
packet: push 
20b8bd99856aee6da9c1743f6df0ec18a9cac28267338c198573ad59e89d0acc445a62b3d127 
acf853d0a30287d9455dbe1707edeb16cc3e9b22 
conf.php845ecef1e4aaece71ef357285c2df71056ae0314 
db98699a6c68b653be1fa8dceb64204397d9814cd1 
db/db.sqlfed89aa6a337c6ab5a89dba13702a65ab70372bd 
httpff2a325bfd33f1fb7098b5688ffe99fe67bf5874 
http/apifbf53a7bcd223485e56d30715a794a7e067df8d2 
http/api/.htaccess84d1f0580e88c6351df884200ebcd526d8b145ea 
http/api/index.php9b8a7a21fa6e4c3a9672469b9b4a7e51a336d015 
http/www9a464b3db152808bc74512304054ac25a63cb9b7 
http/www/files8cab2dab60f85385de1ef984a976a038176c2015 
http/www/files/foundationa5cb50f4203d7176a505857ac80ffbbcf562c91f 
http/www/files/foundation/cssc2a844c8a00ef41d912f53c40026580f2b10fd00 
http/www/files/foundation/css/accessibility_foundicons.css699d805b9f5858111d4bc95705df22f6137ec14a 
http/www/files/foundation/css/accessibility_foundicons_ie7.css8e0ddf1ac316d9231277a77bcd550895f291b5c7 
http/www/files/foundation/css/foundation.css1d592b3fc77c4b44af67b82edbee4cc51b8a97d9 
http/www/files/foundation/css/foundation.min.css3c308c85cf36052810d35c08d4f5bbc233cf61ea 
http/www/files/foundation/css/general_foundicons.cssd5b3776730a16e4ec61bad31526cc0a5a24096bc 
http/www/files/foundation/css/general_foundicons_ie7.cssa9c6f52f05e50c6fd8dab6c30e22c8d4ea2f15ea 
http/www/files/foundation/css/normalize.css914f6472ffce7135f191048a923e07e7886f192b 
http/www/files/foundation/css/social_foundicons.css6a3c9c07729fc466c38e6a40d36b298de881706b 
http/www/files/foundation/css/social_foundicons_ie7.cssd44839248d958fdc96fa044dae0ea71dffd35bde 
http/www/files/foundation/fonts5008ddfcf53c02e82d7eee2e57c38e5672ef89f6 
http/www/files/foundation/fonts/.DS_Store237a0ca97e568531dc58bf7c81202028af1e881c 
http/www/files

git send-pack: protocol error: bad band #50

[João Joyce]

Hello,

I am not sure this is the right place to ask this. If it isn't I would 
be grateful if you could help me find the best place to do it.


I am trying to push some files to a server with git push. I have 
configured the server to push the files:

git remote set-url test ssh://u...@location.com:2200/fullpath/

but I am getting the following error:
git send-pack: protocol error: bad band #50
fatal: The remote end hung up unexpectedly

It seems that something is failing on the remote side but I can't find 
any reference to this protocol error.


Does anyone know how to solve this error? Or which logs should I search 
to better understand the problem?


Thank you very much,
João Joyce
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: git send-pack: protocol error: bad band #50

[Konstantin Khomoutov]

On Thu, 11 Apr 2013 07:49:44 +0100
João Joyce joao.jo...@netcabo.pt wrote:

[...]

 but I am getting the following error:
  git send-pack: protocol error: bad band #50
  fatal: The remote end hung up unexpectedly
 
 It seems that something is failing on the remote side but I can't
 find any reference to this protocol error.

I should add that the OP first asked this question on SO [1] and I
advised him to simply run `git --version` on the remote via SSH to
verify Git is working there, and it worked OK.

Another thing the OP failed to provide is the info on his setup.
To cite his message posted to git-users [2]:

 I am using ubuntu 12.10 in my local machine and 12.04 in the remote
 (which is a VPS hosting). The git version is 1.7.9.5 on both.

Hope this might help tracking down the issue.

1. http://stackoverflow.com/q/15921202/720999
2. https://groups.google.com/forum/?fromgroups=#!topic/git-users/eJXASG1GlDA
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: git send-pack: protocol error: bad band #50

[Jonathan Nieder]

Hello,

João Joyce wrote:

 I am not sure this is the right place to ask this.

You're in the right place.

[...]
 I am trying to push some files to a server with git push. I have
 configured the server to push the files:
 git remote set-url test ssh://u...@location.com:2200/fullpath/

 but I am getting the following error:
 git send-pack: protocol error: bad band #50
 fatal: The remote end hung up unexpectedly

That means that where git expected to read a binary sideband number,
it instead received the byte \x32 (ASCII '2').

Without more details, it's hard to debug this further.  Can you get
a trace of the communication by setting the envvar
GIT_TRACE_PACKET=/tmp/log on the client?

Thanks and hope that helps,
Jonathan
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: git send-pack: protocol error: bad band #50

[João Joyce]

On 04/11/2013 07:37 PM, Jonathan Nieder wrote:

Hello,

João Joyce wrote:


I am not sure this is the right place to ask this.

You're in the right place.

[...]

I am trying to push some files to a server with git push. I have
configured the server to push the files:
 git remote set-url test ssh://u...@location.com:2200/fullpath/

but I am getting the following error:
 git send-pack: protocol error: bad band #50
 fatal: The remote end hung up unexpectedly

That means that where git expected to read a binary sideband number,
it instead received the byte \x32 (ASCII '2').

Without more details, it's hard to debug this further.  Can you get
a trace of the communication by setting the envvar
GIT_TRACE_PACKET=/tmp/log on the client?

Thanks and hope that helps,
Jonathan



Hi,

Thank you for the help. Here is the trace:

packet: push  
capabilities^{}\0 report-status delete-refs side-band-64k quiet ofs-delta

packet: push 
packet: push  
17c420b8bd99856aee6da9c1743f6df0ec18a9ca refs/heads/master\0 
report-status side-band-64k

packet: push 
packet: push 
20b8bd99856aee6da9c1743f6df0ec18a9cac28267338c198573ad59e89d0acc445a62b3d127 
acf853d0a30287d9455dbe1707edeb16cc3e9b22 
conf.php845ecef1e4aaece71ef357285c2df71056ae0314 
db98699a6c68b653be1fa8dceb64204397d9814cd1 
db/db.sqlfed89aa6a337c6ab5a89dba13702a65ab70372bd 
httpff2a325bfd33f1fb7098b5688ffe99fe67bf5874 
http/apifbf53a7bcd223485e56d30715a794a7e067df8d2 
http/api/.htaccess84d1f0580e88c6351df884200ebcd526d8b145ea 
http/api/index.php9b8a7a21fa6e4c3a9672469b9b4a7e51a336d015 
http/www9a464b3db152808bc74512304054ac25a63cb9b7 
http/www/files8cab2dab60f85385de1ef984a976a038176c2015 
http/www/files/foundationa5cb50f4203d7176a505857ac80ffbbcf562c91f 
http/www/files/foundation/cssc2a844c8a00ef41d912f53c40026580f2b10fd00 
http/www/files/foundation/css/accessibility_foundicons.css699d805b9f5858111d4bc95705df22f6137ec14a 
http/www/files/foundation/css/accessibility_foundicons_ie7.css8e0ddf1ac316d9231277a77bcd550895f291b5c7 
http/www/files/foundation/css/foundation.css1d592b3fc77c4b44af67b82edbee4cc51b8a97d9 
http/www/files/foundation/css/foundation.min.css3c308c85cf36052810d35c08d4f5bbc233cf61ea 
http/www/files/foundation/css/general_foundicons.cssd5b3776730a16e4ec61bad31526cc0a5a24096bc 
http/www/files/foundation/css/general_foundicons_ie7.cssa9c6f52f05e50c6fd8dab6c30e22c8d4ea2f15ea 
http/www/files/foundation/css/normalize.css914f6472ffce7135f191048a923e07e7886f192b 
http/www/files/foundation/css/social_foundicons.css6a3c9c07729fc466c38e6a40d36b298de881706b 
http/www/files/foundation/css/social_foundicons_ie7.cssd44839248d958fdc96fa044dae0ea71dffd35bde 
http/www/files/foundation/fonts5008ddfcf53c02e82d7eee2e57c38e5672ef89f6 
http/www/files/foundation/fonts/.DS_Store237a0ca97e568531dc58bf7c81202028af1e881c 
http/www/files/foundation/fonts/accessibility_foundicons.eot49c0d07bea6f18cdbc35ee938b1b3f48cacce64c 
http/www/files/foundation/fonts/accessibility_foundicons.svg46a67f8d0223b881ca74ccafb44b64664552b937 
http/www/files/foundation/fonts/accessibility_foundicons.ttf4eae85189fee6930191b69e31a09b34e6a9a9c19 
http/www/files/foundation/fonts/accessibility_foundicons.woff20733a0388ef77572cbc55cbf76cc46babf0a15d 
http/www/files/foundation/fonts/general_foundicons.eota9347515264ac712b5d083eaa231929243ea7142 
http/www/files/foundation/fonts/general_foundicons.svg90a5ccead2d84d036bd8ed66926af93b21621df5 
http/www/files/foundation/fonts/general_foundicons.ttfdaab63141b07e0a1fa8efd931a98945b837bd4aa 
http/www/files/foundation/fonts/general_foundicons.woffa9341f49f12c10aaa5db2bc74ed3889245ce9a3a 
http/www/files/foundation/fonts/social_foundicons.eoteb4189cd70c623deaa25e5bb55ab210d27fe2d14 
http/www/files/foundation/fonts/social_foundicons.svg01158c66b13b6f90e7b7d1cdb5c4e7369c6434ae 
http/www/files/foundation/fonts/social_foundicons.ttfbd1f1e58a692b73205fce579faee81801d3157aa 
http/www/files/foundation/fonts/social_foundicons.woffcd2531e2044a9c1875159ff1278aafac1aaa8944 
http/www/files/foundation/img8b137891791fe96927ad78e64b0aad7bded08bdc 
http/www/files/foundation/img/.gitkeep36b90e58095363e46845d98d979700d16019830e 
http/www/files/foundation/js596287860dbdcd04dd8a78d2ee1999862286515a 
http/www/files/foundation/js/foundation.min.jsec14148b2d83476fffebf3cba39d6516844b7200 
http/www/files/foundation/js/foundationb78a35a14d000346914644cc0e9783a40f64760d 
http/www/files/foundation/js/foundation/foundation.alerts.jsc8ff324991762b763dd936da49415fff1ec2de93 
http/www/files/foundation/js/foundation/foundation.clearing.js862027c8631db60070e8c3ebd7b8953c0283c561 
http/www/files/foundation/js/foundation/foundation.cookie.js24b35e12e7860a80edb9f16a0209715f249f96b0 
http/www/files/foundation/js/foundation/foundation.dropdown.js6a27af4ad0e0865235cd3a84cd251b8f928510ba 
http/www/files/foundation/js/foundation