[Bug 4231] New: abort: error: An existing connection was forcibly closed by the remote host after server security patch

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Thu Apr 24 10:52:55 CDT 2014


http://bz.selenic.com/show_bug.cgi?id=4231

          Priority: normal
            Bug ID: 4231
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: abort: error: An existing connection was forcibly
                    closed by the remote host after server security patch
          Severity: bug
    Classification: Unclassified
                OS: Windows
          Reporter: philip.w.mcadams at intel.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

Engineer in our environment received a corporate security message to patch
their server with OpenSSL patch.  After patching the system and rebooting the
engineer can no longer pull from Mercurial. We are reaching out to our security
team to see what changes occurred with the patch. Engineer receives the
following error:

C:\Users\xxx\xxx\xxx\xxx\xxx>hg pull --debug --traceback
using https://xxx.com/index.py/XXX
proxying through http://xxx.xxx.com:xxx
sending capabilities command
using auth.xxx.xxxx.com.* for authentication
Traceback (most recent call last):
  File "mercurial\dispatch.pyo", line 138, in _runcatch
  File "mercurial\dispatch.pyo", line 810, in _dispatch
  File "mercurial\dispatch.pyo", line 590, in runcommand
  File "mercurial\dispatch.pyo", line 901, in _runcommand
  File "mercurial\dispatch.pyo", line 872, in checkargs
  File "mercurial\dispatch.pyo", line 807, in <lambda>
  File "mercurial\util.pyo", line 511, in check
  File "mercurial\extensions.pyo", line 151, in wrap
  File "mercurial\util.pyo", line 511, in check
  File "hgext\mq.pyo", line 3383, in mqcommand
  File "mercurial\util.pyo", line 511, in check
  File "mercurial\extensions.pyo", line 151, in wrap
  File "mercurial\util.pyo", line 511, in check
  File "hgext\rebase.pyo", line 919, in pullrebase
  File "mercurial\util.pyo", line 511, in check
  File "mercurial\commands.pyo", line 4609, in pull
  File "mercurial\hg.pyo", line 129, in peer
  File "mercurial\hg.pyo", line 106, in _peerorrepo
  File "mercurial\httppeer.pyo", line 238, in instance
  File "mercurial\httppeer.pyo", line 57, in _fetchcaps
  File "mercurial\httppeer.pyo", line 171, in _call
  File "mercurial\httppeer.pyo", line 118, in _callstream
  File "urllib2.pyo", line 404, in open
  File "urllib2.pyo", line 422, in _open
  File "urllib2.pyo", line 382, in _call_chain
  File "mercurial\httpconnection.pyo", line 254, in https_open
  File "mercurial\httpconnection.pyo", line 219, in do_open
URLError: <urlopen error [Errno 10054] An existing connection was forcibly
closed by the remote host>
abort: error: An existing connection was forcibly closed by the remote host

C:\xxx\xxx\xxx\xxx\xxx\xxx>

On our end we're trying a variety of things to resolve the issue to no avail. 
Wondering if you could provide some BKMs on resolving this issue.  We've
perused and tried a lot of fixes outlined on the web and they haven't helped
us.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list