URLError: <urlopen error >

[Augie Fackler]

On Oct 18, 2011, at 11:46 AM, Smith, DAVID wrote:

>> -----Original Message-----
>> From: Augie Fackler [mailto:durin42 at gmail.com]
>> Sent: Tuesday, October 18, 2011 10:26 AM
>> To: Smith, DAVID
>> Cc: mercurial at selenic.com
>> Subject: Re: URLError: <urlopen error >
>> 
>> 
>> On Oct 18, 2011, at 11:24 AM, Smith, DAVID wrote:
>> 
>>>> -----Original Message-----
>>>> From: Augie Fackler [mailto:durin42 at gmail.com]
>>>> Sent: Tuesday, October 18, 2011 10:21 AM
>>>> To: Smith, DAVID
>>>> Cc: mercurial at selenic.com
>>>> Subject: Re: URLError: <urlopen error >
>>>> 
>>>> 
>>>> On Oct 18, 2011, at 10:53 AM, Smith, DAVID wrote:
>>>> 
>>>>>> -----Original Message-----
>>>>> _call_chain  File "mercurial\httpconnection.pyo", line 246, in
>>>>> https_open  File "mercurial\httpconnection.pyo", line 213, in
>>>>> do_open File "mercurial\httpclient\__init__.pyo", line 674, in
>>>>> getresponse File "mercurial\httpclient\__init__.pyo", line 161, in
>>>>> _select KeyboardInterrupt interrupted!
>>>>> INFO:mercurial.httpclient:445:closed connection to dlp_cm on 443
>>>> 
>>>> 
>>>> Hm. What version of Mercurial was this? This looks like an error I
>>>> fixed recently, but I'd like to be sure.
>>>> 
>>> 
>>> Mercurial 1.9.3 on the server (Win Server 2008 w/ IIS 7), and
>> TortoiseHg 2.1.4 (with 1.9.3) on the PC (WinXP 32-bit).
>> 
>> Okay. This looks like a failure mode in the client side I recently fixed.
>> If you can try with one of the -rc builds of 2.0 I'd appreciate it. It
>> probably won't /work/, but it might die with a more coherent error.
> 
> Yeah, it still died, but with more info.  I think it's safe to ignore the first bit where the keyring extension didn't load for 2.0.0-rc -- it appears the authentication still worked okay.

Yeah, agreed.

> 
> E:\test>"c:\Program Files\Mercurial\hg.exe" pull -b v10.7.4 --debug --verbose --traceback --config ui.usehttp2=true --config ui.
> http2debuglevel=INFO

<snip> uninteresting parts

> INFO:mercurial.httpclient:495:sending GET request for /dlpc/master/dlp_composer?cmd=listkeys to dlp_cm on port 443
> http auth: user toolbld, password ********
> using auth.dlp_cm.* for authentication
> INFO:mercurial.httpclient:495:sending GET request for /dlpc/master/dlp_composer?cmd=listkeys to dlp_cm on port 443
> http error while sending listkeys command

Yeah, this following traceback is what I expected. Can you run again with DEBUG level logging and send it to me privately as an attachment? It won't contain anything sensitive (though double check in case I'm wrong!), but it'd probably be rather large for the mailing list.

> Traceback (most recent call last):
>  File "mercurial\httprepo.pyc", line 117, in _callstream
>  File "urllib2.pyc", line 397, in open
>  File "urllib2.pyc", line 510, in http_response
>  File "urllib2.pyc", line 429, in error
>  File "urllib2.pyc", line 369, in _call_chain
>  File "urllib2.pyc", line 864, in http_error_401
>  File "mercurial\url.pyc", line 429, in http_error_auth_reqed
>  File "urllib2.pyc", line 842, in http_error_auth_reqed
>  File "urllib2.pyc", line 852, in retry_http_basic_auth
>  File "urllib2.pyc", line 391, in open
>  File "urllib2.pyc", line 409, in _open
>  File "urllib2.pyc", line 369, in _call_chain
>  File "mercurial\httpconnection.pyc", line 246, in https_open
>  File "mercurial\httpconnection.pyc", line 213, in do_open
>  File "mercurial\httpclient\__init__.pyc", line 682, in getresponse
>  File "mercurial\httpclient\__init__.pyc", line 181, in _select
> HTTPRemoteClosedError: server appears to have closed the socket mid-response
> Traceback (most recent call last):
>  File "mercurial\dispatch.pyc", line 87, in _runcatch
>  File "mercurial\dispatch.pyc", line 684, in _dispatch
>  File "mercurial\dispatch.pyc", line 466, in runcommand
>  File "mercurial\dispatch.pyc", line 738, in _runcommand
>  File "mercurial\dispatch.pyc", line 692, in checkargs
>  File "mercurial\dispatch.pyc", line 681, in <lambda>
>  File "mercurial\util.pyc", line 444, in check
>  File "mercurial\commands.pyc", line 4206, in pull
>  File "mercurial\bookmarks.pyc", line 180, in updatefromremote
>  File "mercurial\wireproto.pyc", line 114, in plain
>  File "mercurial\wireproto.pyc", line 162, in _submitone
>  File "mercurial\httprepo.pyc", line 169, in _call
>  File "mercurial\httprepo.pyc", line 125, in _callstream
> IOError: [Errno None] server appears to have closed the socket mid-response
> abort: server appears to have closed the socket mid-response
> INFO:mercurial.httpclient:453:closed connection to dlp_cm on 443
>