You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Detlef Braungardt <de...@CoseB.de> on 2019/12/05 15:58:00 UTC
error 'Network connection closed unexpectedly' while svn update
Hi everyone,
we use TortoiseSVN for our development.
But in a special situation we get an error 'Network connection closed unexpectedly' during a svn update. The
steps to reproduce the situation is writed down in the Google Groups thread.
I posted this error as a bug on the Tortoise list.
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/tortoisesvn/MSaacoX73DU
After a short communication we found out that the bug is probably contained in the libsvn.
C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15749
Updating 'D:\Develop\FIRMA\trunk\Tests':
svn: E235000: In file '/build/subversion-Lv3Qkk/subversion-1.9.7/subversion/libsvn_fs_base/trail.c' line
97: assertion failed (! bfd->in_txn_trail)
svn: E210002: Network connection closed unexpectedly
Can you help us to fix this bug?
Thanks in advance.
Best regards
Detlef
--
*********************************************************
* Computerservice Braungardt *
*********************************************************
* Dipl.-Wirtsch.-Inf. Detlef Braungardt *
*********************************************************
* email: develop@CoseB.de *
* www: www.CoseB.de *
*********************************************************
Re: error 'Network connection closed unexpectedly' while svn update
Posted by Nathan Hartman <ha...@gmail.com>.
On Thu, Dec 5, 2019 at 1:30 PM Detlef Braungardt <de...@coseb.de> wrote:
> we use TortoiseSVN for our development.
>
> But in a special situation we get an error 'Network connection closed unexpectedly' during a svn update. The steps to reproduce the situation is writed down in the Google Groups thread.
> I posted this error as a bug on the Tortoise list.
>
> https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/tortoisesvn/MSaacoX73DU
>
> After a short communication we found out that the bug is probably contained in the libsvn.
>
> C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15749
> Updating 'D:\Develop\FIRMA\trunk\Tests':
>
> svn: E235000: In file '/build/subversion-Lv3Qkk/subversion-1.9.7/subversion/libsvn_fs_base/trail.c' line 97: assertion failed (! bfd->in_txn_trail)
> svn: E210002: Network connection closed unexpectedly
>
> Can you help us to fix this bug?
> Thanks in advance.
Hello Detlef,
Thank you for your report.
I'll try the reproduction procedure you described in the Tortoise forum...
Thank you,
Nathan
Re: EXTERNAL: error 'Network connection closed unexpectedly' while
svn update
Posted by Detlef Braungardt <de...@CoseB.de>.
Hi Andrew and everyone,
I do not think it is a bug in the network connection.
The root cause is, the patch over two commits is empty.
It means one commit makes a change and the next commit is a revert.
If you now try to update both commits at once, you will get the described error.
Thanks in advance for your help.
Best regards
Detlef
---
On 06.12.2019 08:04, Marlow, Andrew wrote:
> Hello everyone and thank you Detlef for reporting this situation. I want to add that I also see this from time
> to time and would like to see a fix.
>
> It is very easy for me to see network errors from subversion because I am in an environment where the network
> is extremely unreliable. This fact has revealed several software products that, IMHO, do not take transient
> network errors into account. I think it is a common failing, especially as networks have generally become more
> reliable over the years (so it’s easy to take it for granted when writing socket code).
>
> *From:*Detlef Braungardt <de...@CoseB.de>
> *Sent:* 05 December 2019 15:58
> *To:* users@subversion.apache.org
> *Subject:* EXTERNAL: error 'Network connection closed unexpectedly' while svn update
>
> Hi everyone,
>
>
> we use TortoiseSVN for our development.
>
> But in a special situation we get an error 'Network connection closed unexpectedly' during a svn update. The
> steps to reproduce the situation is writed down in the Google Groups thread.
> I posted this error as a bug on the Tortoise list.
>
> https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/tortoisesvn/MSaacoX73DU
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fforum%2F%3Futm_medium%3Demail%26utm_source%3Dfooter%23!topic%2Ftortoisesvn%2FMSaacoX73DU&data=02%7C01%7CAndrew.Marlow%40fisglobal.com%7C3be8fcabcd524657e61008d779b13c9e%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C637111674440227133&sdata=anRTPgDrrRH5khIM7WFKsvXYwPqoYrANept%2Bmzd9ybY%3D&reserved=0>
>
> After a short communication we found out that the bug is probably contained in the libsvn.
>
> C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15749
> Updating 'D:\Develop\FIRMA\trunk\Tests':
>
> svn: E235000: In file '/build/subversion-Lv3Qkk/subversion-1.9.7/subversion/libsvn_fs_base/trail.c' line
> 97: assertion failed (! bfd->in_txn_trail)
> svn: E210002: Network connection closed unexpectedly
>
> Can you help us to fix this bug?
> Thanks in advance.
>
>
> Best regards
>
> Detlef
>
> --
>
> *********************************************************
>
> * Computerservice Braungardt *
>
> *********************************************************
>
> * Dipl.-Wirtsch.-Inf. Detlef Braungardt *
>
> *********************************************************
>
> * email:develop@CoseB.de <ma...@CoseB.de> *
>
> * www:www.CoseB.de <https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.CoseB.de&data=02%7C01%7CAndrew.Marlow%40fisglobal.com%7C3be8fcabcd524657e61008d779b13c9e%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C637111674440227133&sdata=3vZ1LN5KLTKknDIiojGXKsVP1JWq1aBb36vpA8%2FXdyQ%3D&reserved=0> *
>
> *********************************************************
>
> The information contained in this message is proprietary and/or confidential. If you are not the intended
> recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message
> in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message
> addressed to our domain is subject to archiving and review by persons other than the intended recipient. FIS
> is a trading name of the following companies: Advanced Portfolio Technologies Ltd (No: 6312142) | Clear2Pay
> Limited (No: 5792457) | Decalog (UK) Limited (No: 2567370) | FIS Apex (International) Limited (No: 2999960) |
> FIS Apex (UK) Limited (No. 3573008) | FIS Consulting Services (UK) Limited (No: 2486794) | FIS Derivatives
> Utility Services (UK) Limited (No: 9398140) | FIS Energy Solutions Limited (No: 1889028) | FIS Global
> Execution Services Limited (No. 3127109) | FIS Global Trading (UK) Limited (No: 2523114) | FIS Investment
> Systems (UK) Limited (No: 1366010) | FIS Sherwood Systems Group Limited (No: 982833) | FIS Systems Limited
> (No: 1937159) | FIS Treasury Systems (Europe) Limited (No: 2624209) | FIS Treasury Systems (UK) Limited (No:
> 2893376) | GL Settle Limited (No: 2396127) | Integrity Treasury Solutions Europe Limited (No: 3289271) | Monis
> Software Limited (No: 2333925) | Reech Capital Limited (No: 3649490) | Solutions Plus Consulting Services
> Limited (No: 3839487) | Valuelink Information Services Limited (No: 3827424) all registered in England & Wales
> with their registered office at 25 Canada Square, London E14 5LQ | FIS Global Execution Services Limited is
> authorised and regulated by the Financial Conduct Authority | Certegy Card Services Limited (No: 3517639) |
> Certegy France Limited (No: 2557650) | eFunds International Limited (No: 1930117) | Fidelity Information
> Services Limited (No: 2225203) | FIS Payments (UK) Limited (No: 4215488) | Metavante Technologies Limited (No:
> 2659326) all registered in England & Wales with their registered office at 1st Floor Tricorn House, 51-53
> Hagley Road, Edgbaston, Birmingham, West Midlands, B16 8TU, United Kingdom | FIS Payments (UK) Limited is
> authorised and regulated by the Financial Conduct Authority; some services are covered by the Financial
> Ombudsman Service (in the UK). Clear2Pay Limited, Registered in Scotland (No SC157659), Registered Office:
> Clear2Pay House, Pitreavie Court, Pitreavie Business Park Queensferry Rd, Dunfermline, Fife, SS, KY11 8UU,
> Scotland | FIS eProcess Intelligence LLC (UK Branch), UK Establishment Registered in England & Wales (No:
> FC16527/Branch No. BR000355), Registered Branch Office: 25 Canada Square, London, E14 5LQ; FIS eProcess
> Intelligence LLC is a limited liability company formed in the USA registered on file with the Office of the
> Delaware Secretary of State, Division of Corporations (File No. 2032143), Head Office: 601 Riverside Avenue,
> Jacksonville Florida, FL32204, USA | FIS Investment Systems LLC, UK Establishment Registered in England &
> Wales (No: FC033836/Branch No. BR018923), Registered Branch Office: 25 Canada Square, London, E14 5LQ; FIS
> Investment Systems LLC is a limited liability company formed in the USA registered on file with the Office of
> the Delaware Secretary of State, Division of Corporations (File No. 0881255), Head Office: 377 E. Butterfield
> Road, Suite 800, Lombard, IL 60148, USA | Calls to and from the companies may be recorded for quality
> purposes. | All of the named companies are part of FIS (Fidelity National Information Services, Inc.).
--
*********************************************************
* Computerservice Braungardt *
*********************************************************
* Dipl.-Wirtsch.-Inf. Detlef Braungardt *
*********************************************************
* email: develop@CoseB.de *
* www: www.CoseB.de *
*********************************************************
RE: EXTERNAL: error 'Network connection closed unexpectedly' while
svn update
Posted by "Marlow, Andrew" <An...@fisglobal.com>.
Hello everyone and thank you Detlef for reporting this situation. I want to add that I also see this from time to time and would like to see a fix.
It is very easy for me to see network errors from subversion because I am in an environment where the network is extremely unreliable. This fact has revealed several software products that, IMHO, do not take transient network errors into account. I think it is a common failing, especially as networks have generally become more reliable over the years (so it’s easy to take it for granted when writing socket code).
From: Detlef Braungardt <de...@CoseB.de>
Sent: 05 December 2019 15:58
To: users@subversion.apache.org
Subject: EXTERNAL: error 'Network connection closed unexpectedly' while svn update
Hi everyone,
we use TortoiseSVN for our development.
But in a special situation we get an error 'Network connection closed unexpectedly' during a svn update. The steps to reproduce the situation is writed down in the Google Groups thread.
I posted this error as a bug on the Tortoise list.
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/tortoisesvn/MSaacoX73DU<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fforum%2F%3Futm_medium%3Demail%26utm_source%3Dfooter%23!topic%2Ftortoisesvn%2FMSaacoX73DU&data=02%7C01%7CAndrew.Marlow%40fisglobal.com%7C3be8fcabcd524657e61008d779b13c9e%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C637111674440227133&sdata=anRTPgDrrRH5khIM7WFKsvXYwPqoYrANept%2Bmzd9ybY%3D&reserved=0>
After a short communication we found out that the bug is probably contained in the libsvn.
C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15749
Updating 'D:\Develop\FIRMA\trunk\Tests':
svn: E235000: In file '/build/subversion-Lv3Qkk/subversion-1.9.7/subversion/libsvn_fs_base/trail.c' line 97: assertion failed (! bfd->in_txn_trail)
svn: E210002: Network connection closed unexpectedly
Can you help us to fix this bug?
Thanks in advance.
Best regards
Detlef
--
*********************************************************
* Computerservice Braungardt *
*********************************************************
* Dipl.-Wirtsch.-Inf. Detlef Braungardt *
*********************************************************
* email: develop@CoseB.de<ma...@CoseB.de> *
* www: www.CoseB.de<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.CoseB.de&data=02%7C01%7CAndrew.Marlow%40fisglobal.com%7C3be8fcabcd524657e61008d779b13c9e%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C637111674440227133&sdata=3vZ1LN5KLTKknDIiojGXKsVP1JWq1aBb36vpA8%2FXdyQ%3D&reserved=0> *
*********************************************************
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. FIS is a trading name of the following companies: Advanced Portfolio Technologies Ltd (No: 6312142) | Clear2Pay Limited (No: 5792457) | Decalog (UK) Limited (No: 2567370) | FIS Apex (International) Limited (No: 2999960) | FIS Apex (UK) Limited (No. 3573008) | FIS Consulting Services (UK) Limited (No: 2486794) | FIS Derivatives Utility Services (UK) Limited (No: 9398140) | FIS Energy Solutions Limited (No: 1889028) | FIS Global Execution Services Limited (No. 3127109) | FIS Global Trading (UK) Limited (No: 2523114) | FIS Investment Systems (UK) Limited (No: 1366010) | FIS Sherwood Systems Group Limited (No: 982833) | FIS Systems Limited (No: 1937159) | FIS Treasury Systems (Europe) Limited (No: 2624209) | FIS Treasury Systems (UK) Limited (No: 2893376) | GL Settle Limited (No: 2396127) | Integrity Treasury Solutions Europe Limited (No: 3289271) | Monis Software Limited (No: 2333925) | Reech Capital Limited (No: 3649490) | Solutions Plus Consulting Services Limited (No: 3839487) | Valuelink Information Services Limited (No: 3827424) all registered in England & Wales with their registered office at 25 Canada Square, London E14 5LQ | FIS Global Execution Services Limited is authorised and regulated by the Financial Conduct Authority | Certegy Card Services Limited (No: 3517639) | Certegy France Limited (No: 2557650) | eFunds International Limited (No: 1930117) | Fidelity Information Services Limited (No: 2225203) | FIS Payments (UK) Limited (No: 4215488) | Metavante Technologies Limited (No: 2659326) all registered in England & Wales with their registered office at 1st Floor Tricorn House, 51-53 Hagley Road, Edgbaston, Birmingham, West Midlands, B16 8TU, United Kingdom | FIS Payments (UK) Limited is authorised and regulated by the Financial Conduct Authority; some services are covered by the Financial Ombudsman Service (in the UK). Clear2Pay Limited, Registered in Scotland (No SC157659), Registered Office: Clear2Pay House, Pitreavie Court, Pitreavie Business Park Queensferry Rd, Dunfermline, Fife, SS, KY11 8UU, Scotland | FIS eProcess Intelligence LLC (UK Branch), UK Establishment Registered in England & Wales (No: FC16527/Branch No. BR000355), Registered Branch Office: 25 Canada Square, London, E14 5LQ; FIS eProcess Intelligence LLC is a limited liability company formed in the USA registered on file with the Office of the Delaware Secretary of State, Division of Corporations (File No. 2032143), Head Office: 601 Riverside Avenue, Jacksonville Florida, FL32204, USA | FIS Investment Systems LLC, UK Establishment Registered in England & Wales (No: FC033836/Branch No. BR018923), Registered Branch Office: 25 Canada Square, London, E14 5LQ; FIS Investment Systems LLC is a limited liability company formed in the USA registered on file with the Office of the Delaware Secretary of State, Division of Corporations (File No. 0881255), Head Office: 377 E. Butterfield Road, Suite 800, Lombard, IL 60148, USA | Calls to and from the companies may be recorded for quality purposes. | All of the named companies are part of FIS (Fidelity National Information Services, Inc.).
Re: error 'Network connection closed unexpectedly' while svn update
Posted by Branko Čibej <br...@apache.org>.
On 09.12.2019 13:54, Detlef Braungardt wrote:
> Hi Nathan,
>
>
> thanks for your information.
>
> I tried the TortoiseSVN version 1.13.1 now. But the failure persists.
The issue Nathan linked to was a server-side problem, changing the
client version would not be expected to make a difference.
> It is not so easy to update the subversion version on the server. This
> is a production system.
> I will try to set up a test system and repeat the test. And then I
> will send you an anwer.
Thanks for that. It's sometimes really difficult to reproduce a failure
without access to the original dataset.
-- Brane
Re: error 'Network connection closed unexpectedly' while svn update
Posted by Detlef Braungardt <de...@CoseB.de>.
Hi Nathan,
thanks for your information.
I tried the TortoiseSVN version 1.13.1 now. But the failure persists.
It is not so easy to update the subversion version on the server. This is a production system.
I will try to set up a test system and repeat the test. And then I will send you an anwer.
Best regards
Detlef
---
On 08.12.2019 06:29, Nathan Hartman wrote:
> On Thu, Dec 5, 2019 at 1:30 PM Detlef Braungardt <de...@coseb.de> wrote:
>> we use TortoiseSVN for our development.
>>
>> But in a special situation we get an error 'Network connection closed unexpectedly' during a svn update. The steps to reproduce the situation is writed down in the Google Groups thread.
>> I posted this error as a bug on the Tortoise list.
>>
>> https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/tortoisesvn/MSaacoX73DU
>>
>> After a short communication we found out that the bug is probably contained in the libsvn.
>>
>> C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15749
>> Updating 'D:\Develop\FIRMA\trunk\Tests':
>>
>> svn: E235000: In file '/build/subversion-Lv3Qkk/subversion-1.9.7/subversion/libsvn_fs_base/trail.c' line 97: assertion failed (! bfd->in_txn_trail)
>> svn: E210002: Network connection closed unexpectedly
>
> Hello Detlef,
>
>>From my reading of the reproduction procedure you posted to the
> TortoiseSVN list, a 'svn update' that traverses two revisions whose
> net effect is no change causes the 'Network connection closed
> unexpectedly' error shown above.
>
> For the record, you are using TortoiseSVN 1.12.2 Build 28653 64-bit on
> the client and Subversion 1.9.7-4ubuntu1 on the server.
>
> I could not reproduce what you described. I tried to reproduce it
> using the latest release of Subversion, 1.13.0. I don't have a 1.9.7
> server available to test with. I could build it from source, but
> before I do that, I'd like to offer the following thoughts:
>
> Subversion 1.12.x is no longer a supported release, since that is a 6-
> month Regular Release. Subversion 1.13.0 was released on October 30th
> and is a supported release. It contains some bug fixes not present in
> 1.12.x. Could you try to upgrade your TortoiseSVN clients to
> TortoiseSVN-1.13.1?
>
> Subversion 1.9.7 contains the following bug:
>
> https://issues.apache.org/jira/browse/SVN-4722?issueNumber=4722
>
> This bug and others are fixed in later 1.9.x. The latest 1.9.x release
> is 1.9.12, released earlier this year.
>
> Is it feasible for you to update Subversion on the server, either to
> 1.9.12 or 1.10.6?
>
> If so, would you please try to reproduce the 'Network connection
> closed unexpectedly' error and let us know if the issue is resolved or
> still present?
>
> Thank you,
> Nathan
>
--
*********************************************************
* Computerservice Braungardt *
*********************************************************
* Dipl.-Wirtsch.-Inf. Detlef Braungardt *
*********************************************************
* email: develop@CoseB.de *
* www: www.CoseB.de *
*********************************************************
Re: error 'Network connection closed unexpectedly' while svn update
Posted by Nathan Hartman <ha...@gmail.com>.
On Thu, Dec 5, 2019 at 1:30 PM Detlef Braungardt <de...@coseb.de> wrote:
> we use TortoiseSVN for our development.
>
> But in a special situation we get an error 'Network connection closed unexpectedly' during a svn update. The steps to reproduce the situation is writed down in the Google Groups thread.
> I posted this error as a bug on the Tortoise list.
>
> https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/tortoisesvn/MSaacoX73DU
>
> After a short communication we found out that the bug is probably contained in the libsvn.
>
> C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15749
> Updating 'D:\Develop\FIRMA\trunk\Tests':
>
> svn: E235000: In file '/build/subversion-Lv3Qkk/subversion-1.9.7/subversion/libsvn_fs_base/trail.c' line 97: assertion failed (! bfd->in_txn_trail)
> svn: E210002: Network connection closed unexpectedly
Hello Detlef,
From my reading of the reproduction procedure you posted to the
TortoiseSVN list, a 'svn update' that traverses two revisions whose
net effect is no change causes the 'Network connection closed
unexpectedly' error shown above.
For the record, you are using TortoiseSVN 1.12.2 Build 28653 64-bit on
the client and Subversion 1.9.7-4ubuntu1 on the server.
I could not reproduce what you described. I tried to reproduce it
using the latest release of Subversion, 1.13.0. I don't have a 1.9.7
server available to test with. I could build it from source, but
before I do that, I'd like to offer the following thoughts:
Subversion 1.12.x is no longer a supported release, since that is a 6-
month Regular Release. Subversion 1.13.0 was released on October 30th
and is a supported release. It contains some bug fixes not present in
1.12.x. Could you try to upgrade your TortoiseSVN clients to
TortoiseSVN-1.13.1?
Subversion 1.9.7 contains the following bug:
https://issues.apache.org/jira/browse/SVN-4722?issueNumber=4722
This bug and others are fixed in later 1.9.x. The latest 1.9.x release
is 1.9.12, released earlier this year.
Is it feasible for you to update Subversion on the server, either to
1.9.12 or 1.10.6?
If so, would you please try to reproduce the 'Network connection
closed unexpectedly' error and let us know if the issue is resolved or
still present?
Thank you,
Nathan