Clone failure: 'abort: unexpected response from remote server: empty string'

[David Razzetti]

Hi,
Thanks for the reply.  The clone attempt succeeded when the '--stream' option was omitted 😊
So far three developers who previously could not clone can now successfully clone.
I have asked other developers to try and I am waiting for the results.  The clone takes ~50 minutes due to the presence of some fairly large binary files (~16Mb) within the repository.

-----Original Message-----
From: Mercurial [mailto:mercurial-bounces at mercurial-scm.org] On Behalf Of Steve - Gadget Barnes
Sent: 06 May 2018 05:09
To: mercurial at mercurial-scm.org
Subject: Re: Clone failure: 'abort: unexpected response from remote server: empty string'



On 03/05/2018 12:12, David Razzetti wrote:
> Hello,
> 
> Server: Win64: Mercurial Hg v4.5.3
> 
> Client: Win64: Tortoise Hg v4.5.3
> 
> Attempts to clone a repository from a server to client PCs fail.  An 
> example clone command and the responses look like this:
> 
> hg clone --stream http://sourceserver/hg/Foo c:\Development\Foo
> 
> streaming all changes
> 
> 100412 files to transfer, 4.24 GB of data
> 
> abort: unexpected response from remote server: empty string
> 
> Clients with existing copies of the repository (the repository has 
> existed for some time) continue to be able to pull and push to it.
> 
> I have verified the remote repository by running hg verify locally on 
> the server and all appears to be ok:
> 
> hg verify
> 
> checking changesets
> 
> checking manifests
> 
> crosschecking files in changesets and manifests
> 
> checking files
> 
> 99485 files, 55876 changesets, 338410 total revisions
> 
> I cannot find much information on the web about this issue.  I saw a 
> response suggesting that the CGI timeout on the internet server might 
> be too small, but it is set at two hours and the clone attempts fail 
> after about five minutes.
> 
> How do I go about resolving this issue?
> 
> *David Razzetti*
> 
> 

What happens if you try cloning without the --stream option? Also if you use the --rev to only clone the first few revisions and then try pull to get the remainder, (possibly in chunks).

A while back I had similar error, (with a much older version of Mercurial), when cloning and updating an SVN repository that a co-worker had checked in a 5 GB zip file (twice and against all of the rules).

--
Steve (Gadget) Barnes
Any opinions in this message are my personal opinions and do not reflect those of my employer.

---
This email has been checked for viruses by AVG.
http://www.avg.com

_______________________________________________
Mercurial mailing list
Mercurial at mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial