Re: E730054: Error running context: An existing connection was forcibly closed by the remote host.

[Branko Čibej]

On 17.01.2017 18:40, Maloney, Daniel wrote:
> I've got a Collabnet Subversion Edge instance that I've been running for 
> years with no issues. Got a complaint from a user about a month ago that she 
> couldn't checkout a repo. I verified the issue, error text in TortoiseSVN 
> client window was "E730054: Error running context: An existing connection was 
> forcibly closed by the remote host." I've tried other repos, and they all 
> fail with this same error. Same thing happens with TortoiseSVN or the command 
> line client. All repos were working fine and everyone's permissions were 
> correct before the issue cropped up, and everyone can still browse the repos 
> on ViewVC. The same error is happening on multiple repos and even happens on 
> new test repos. The error seems to crop up at random places in the checkout 
> process - sometimes a few files into the checkout, sometimes dozens. It never 
> stops at the same file, or even a similar file in terms of size. It seems 
> pretty random. And again, it's happening on multiple repos.

This is suspiciously similar to the issue described in this thread:

https://lists.apache.org/thread.html/2dd0f5dcd44e66515b70c6cbc07caec21afb67d77085af348a237e2e@1388873289@%3Cusers.subversion.apache.org%3E


-- Brane

Re: E730054: Error running context: An existing connection was forcibly closed by the remote host.

[Mark Phippard]

On Tue, Jan 17, 2017 at 12:40 PM, Maloney, Daniel 
wrote:

> I've got a Collabnet Subversion Edge instance that I've been running for
> years with no issues. Got a complaint from a user about a month ago that
> she couldn't checkout a repo. I verified the issue, error text in
> TortoiseSVN client window was "E730054: Error running context: An existing
> connection was forcibly closed by the remote host." I've tried other repos,
> and they all fail with this same error. Same thing happens with TortoiseSVN
> or the command line client. All repos were working fine and everyone's
> permissions were correct before the issue cropped up, and everyone can
> still browse the repos on ViewVC. The same error is happening on multiple
> repos and even happens on new test repos. The error seems to crop up at
> random places in the checkout process - sometimes a few files into the
> checkout, sometimes dozens. It never stops at the same file, or even a
> similar file in terms of size. It seems pretty random. And again, it’s
> happening on multiple repos.
>
> I've tried restarting Subversion Edge, rebooting the server, upgrading the
> Tortoise client, and I went so far as to upgrade Subversion Edge on the
> server to 5.1.4-4353.41. I can't see anything useful in the logs from the
> times I try to check out and get errors. Haven't found much useful when I
> Google this, so I thought I'd ask for help from the forum.
>
>
>
> OS is RHEL 4.4.7-4, SVN Edge is providing Apache 2.4.23 and SVN 1.8.17
>
>
>

Is this accurate in terms of the OS?  RHEL 4?  I am somewhat surprised SVN
Edge would run on that OS as we have never tested it.  Not even 8 years ago
when SVN Edge first came out and RHEL 4 was only "old".


-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

RE: E730054: Error running context: An existing connection was forcibly closed by the remote host.

[Maloney, Daniel]

Sorry, my bad - it’s actually RHEL 6.5 (Santiago)

DPM

From: Mark Phippard [mailto:markp...@gmail.com]
Sent: Wednesday, 18 January, 2017 05:55
To: Maloney, Daniel 
Cc: users@subversion.apache.org
Subject: Re: E730054: Error running context: An existing connection was 
forcibly closed by the remote host.

On Tue, Jan 17, 2017 at 12:40 PM, Maloney, Daniel 
mailto:daniel.malo...@bms.com>> wrote:
I've got a Collabnet Subversion Edge instance that I've been running for years 
with no issues. Got a complaint from a user about a month ago that she couldn't 
checkout a repo. I verified the issue, error text in TortoiseSVN client window 
was "E730054: Error running context: An existing connection was forcibly closed 
by the remote host." I've tried other repos, and they all fail with this same 
error. Same thing happens with TortoiseSVN or the command line client. All 
repos were working fine and everyone's permissions were correct before the 
issue cropped up, and everyone can still browse the repos on ViewVC. The same 
error is happening on multiple repos and even happens on new test repos. The 
error seems to crop up at random places in the checkout process - sometimes a 
few files into the checkout, sometimes dozens. It never stops at the same file, 
or even a similar file in terms of size. It seems pretty random. And again, 
it’s happening on multiple repos.

I've tried restarting Subversion Edge, rebooting the server, upgrading the 
Tortoise client, and I went so far as to upgrade Subversion Edge on the server 
to 5.1.4-4353.41. I can't see anything useful in the logs from the times I try 
to check out and get errors. Haven't found much useful when I Google this, so I 
thought I'd ask for help from the forum.

OS is RHEL 4.4.7-4, SVN Edge is providing Apache 2.4.23 and SVN 1.8.17



Is this accurate in terms of the OS?  RHEL 4?  I am somewhat surprised SVN Edge 
would run on that OS as we have never tested it.  Not even 8 years ago when SVN 
Edge first came out and RHEL 4 was only "old".


--
Thanks

Mark Phippard
http://markphip.blogspot.com/

This message (including any attachments) may contain confidential, proprietary, 
privileged and/or private information. The information is intended to be for 
the use of the individual or entity designated above. If you are not the 
intended recipient of this message, please notify the sender immediately, and 
delete the message and any attachments. Any disclosure, reproduction, 
distribution or other use of this message or any attachments by an individual 
or entity other than the intended recipient is prohibited.

UNSUBSCRIBE

[Paul Delany]

From: Maloney, Daniel [mailto:daniel.malo...@bms.com]
Sent: 18 January 2017 14:30
To: Mark Phippard
Cc: users@subversion.apache.org
Subject: RE: E730054: Error running context: An existing connection was 
forcibly closed by the remote host.

Sorry, my bad - it’s actually RHEL 6.5 (Santiago)

DPM

From: Mark Phippard [mailto:markp...@gmail.com]
Sent: Wednesday, 18 January, 2017 05:55
To: Maloney, Daniel mailto:daniel.malo...@bms.com>>
Cc: users@subversion.apache.org
Subject: Re: E730054: Error running context: An existing connection was 
forcibly closed by the remote host.

On Tue, Jan 17, 2017 at 12:40 PM, Maloney, Daniel 
mailto:daniel.malo...@bms.com>> wrote:
I've got a Collabnet Subversion Edge instance that I've been running for years 
with no issues. Got a complaint from a user about a month ago that she couldn't 
checkout a repo. I verified the issue, error text in TortoiseSVN client window 
was "E730054: Error running context: An existing connection was forcibly closed 
by the remote host." I've tried other repos, and they all fail with this same 
error. Same thing happens with TortoiseSVN or the command line client. All 
repos were working fine and everyone's permissions were correct before the 
issue cropped up, and everyone can still browse the repos on ViewVC. The same 
error is happening on multiple repos and even happens on new test repos. The 
error seems to crop up at random places in the checkout process - sometimes a 
few files into the checkout, sometimes dozens. It never stops at the same file, 
or even a similar file in terms of size. It seems pretty random. And again, 
it’s happening on multiple repos.

I've tried restarting Subversion Edge, rebooting the server, upgrading the 
Tortoise client, and I went so far as to upgrade Subversion Edge on the server 
to 5.1.4-4353.41. I can't see anything useful in the logs from the times I try 
to check out and get errors. Haven't found much useful when I Google this, so I 
thought I'd ask for help from the forum.

OS is RHEL 4.4.7-4, SVN Edge is providing Apache 2.4.23 and SVN 1.8.17



Is this accurate in terms of the OS?  RHEL 4?  I am somewhat surprised SVN Edge 
would run on that OS as we have never tested it.  Not even 8 years ago when SVN 
Edge first came out and RHEL 4 was only "old".


--
Thanks

Mark Phippard
http://markphip.blogspot.com/

This message (including any attachments) may contain confidential, proprietary, 
privileged and/or private information. The information is intended to be for 
the use of the individual or entity designated above. If you are not the 
intended recipient of this message, please notify the sender immediately, and 
delete the message and any attachments. Any disclosure, reproduction, 
distribution or other use of this message or any attachments by an individual 
or entity other than the intended recipient is prohibited.
The information in this email is confidential and may be legally privileged.  
It may not represent the views of the SSE Group.  It is intended solely for the 
addressees.  Access to this email by anyone else is unauthorised.  If you are 
not the intended recipient, any disclosure, copying, distribution or any action 
taken or omitted to be taken in reliance on it, is prohibited and may be 
unlawful.  Any unauthorised recipient should advise the sender immediately of 
the error in transmission.  Unless specifically stated otherwise, this email 
(or any attachments to it) is not an offer capable of acceptance or acceptance 
of an offer and it does not form part of a binding contractual agreement. 

SSE Renewables Holdings Limited is part of the SSE Group 
The Registered Office of SSE Renewables Holdings Limited is Red Oak South, 
South County Business Park, Leopardstown, Dublin 18, Ireland. 
Registered in Ireland No. 314061 
www.sserenewables.com

ApacheCon CFP closing soon (11 February)

[Rich Bowen]

Hello, fellow Apache enthusiast. Thanks for your participation, and
interest in, the projects of the Apache Software Foundation.

I wanted to remind you that the Call For Papers (CFP) for ApacheCon
North America, and Apache: Big Data North America, closes in less than a
month. If you've been putting it off because there was lots of time
left, it's time to dig for that inspiration and get those talk proposals in.

It's also time to discuss with your developer and user community whether
there's a track of talks that you might want to propose, so that you
have more complete coverage of your project than a talk or two.

We're looking for talks directly, and indirectly, related to projects at
the Apache Software Foundation. These can be anything from in-depth
technical discussions of the projects you work with, to talks about
community, documentation, legal issues, marketing, and so on. We're also
very interested in talks about projects and services built on top of
Apache projects, and case studies of how you use Apache projects to
solve real-world problems.

We are particularly interested in presentations from Apache projects
either in the Incubator, or recently graduated. ApacheCon is where
people come to find out what technology they'll be using this time next
year.

Important URLs are:

To submit a talk for Apache: Big Data -
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp
To submit a talk for ApacheCon -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp

To register for Apache: Big Data -
http://events.linuxfoundation.org/events/apache-big-data-north-america/attend/register-
To register for ApacheCon -
http://events.linuxfoundation.org/events/apachecon-north-america/attend/register-

Early Bird registration rates end March 12th, but if you're a committer
on an Apache project, you get the low committer rate, which is less than
half of the early bird rate!

For further updated about ApacheCon, follow us on Twitter, @ApacheCon,
or drop by our IRC channel, #apachecon on the Freenode IRC network. Or
contact me - rbo...@apache.org - with any questions or concerns.

Thanks!

Rich Bowen, VP Conferences, Apache Software Foundation

-- 
(You've received this email because you're on a dev@ or users@ mailing
list of an Apache Software Foundation project. For subscription and
unsubscription information, consult the headers of this email message,
as this varies from one list to another.)

Svndumpfilter crash on Windows 10

[Brian Colavito]

This was using the binary bundled with VisualSVN.  I got similar results using 
the one from TortoiseSVN.



svn-crash-log20170118163543.log
Description: Binary data