I replied yesterday, but my post seems to have disappeared.
I figured it out, and the key was your reproduction and my realisation I
wasn't seeing a FIN from my server. It turns out that in every case the last
392598 71.906863000 10.222.3.88 10.14.11.50 HTTP 1434 Continuation or
non-HTTP traffic
Stuart MacDonald writes:
> svn: E175002: REPORT of '/svn/repos/deckard-65x/!svn/me': Could not read
> response body: connection was closed by server (http://foundry51.qnx.com)
I can provoke this on my local LAN by setting the Apache timeout on the
server to a low value such as 5 seconds. Then I
Here's this morning's failure. For testing, I've set http-timeout=67. I am
trying to see if the zero window is a coincidence or not.
The debug output:
Reading 8192 bytes of response body.
Got 8192 bytes.
XML: Parsing 8192 bytes.
XML: char-data (235) returns 0
XML: xmlParseChunk returned 0
Reading
I don't have access to the server log, but you can see from the wireshark
capture that the *client* closed the connection (look for the RST packet),
not the server. The error of "socket closed" is consistent with that.
I suspect that there's an issue handling the "http-timeout" timer; it gets
trig
Philip Martin writes:
> That message comes from ne_request.c and the -3 is NE_SOCK_CLOSED
> defined in ne_socket.h:
>
> #define NE_SOCK_CLOSED (-3)
> /* Connection was reset (e.g. server crashed) */
/* Socket was closed */
#define NE_SOCK_CLOSED (-3)
The comment associated with the constant is
stuartm.cod...@gmail.com writes:
> I have another failure, with some debug info, and some updates.
>
> We're switching to a different system for this particular repository, so I
> may or may not be able to continue debug efforts. :-(
>
> Since there's no debug info available for the svn 1.8 clien
On Mon, Dec 23, 2013 at 4:47 PM, Stuart MacDonald
wrote:
> I took some time last Fri to see what was 180 seconds prior to the FIN
> packet in the trace (this is the 1.7.14 failure):
> 289223259.41852100010.222.3.8810.14.10.32HTTP1434
> Continuation or non-HTTP traffic
> 289224
On Mon, Dec 23, 2013 at 3:51 PM, Lieven Govaerts wrote:
> to be clear, you've tested:
> - svn 1.7.13 with ra_neon, svn 1.7.14 with ra_neon and 1.8.5 with ra_serf.
> - to an svn 1.7.7 server
> - over http, with nginx 1.0.5. as intermediate proxy
> - running 'svn up'
> - on an Ubuntu guest (version
Hi Stu,
On Mon, Dec 23, 2013 at 6:11 PM, wrote:
> On Tuesday, December 17, 2013 10:32:34 AM UTC-5, Branko Čibej wrote:
>>
>> On 17.12.2013 16:19, Stuart MacDonald wrote:
>> > The Wireshark trace shows clearly and conclusively this is a bug in
>> > the client. The client drops the connection by s
On Tuesday, December 17, 2013 10:32:34 AM UTC-5, Branko Čibej wrote:
>
> On 17.12.2013 16:19, Stuart MacDonald wrote:
> > The Wireshark trace shows clearly and conclusively this is a bug in
> > the client. The client drops the connection by sending a FIN packet
> > unexpectedly.
>
> It could be
On Monday, December 16, 2013 1:45:11 PM UTC-5, Branko Čibej wrote:
>
> So your server is using an nginx proxy, and your 1.7 client doesn't work
> with it. The thing to do is to try to reproduce this with 1.8, and if it's
> reproducible, it's still most likely a proxy bug (nginx 1.0.5 is rather
On Mon, Dec 16, 2013 at 12:45 PM, Mark Phippard wrote:
> On Mon, Dec 16, 2013 at 12:31 PM, Stuart MacDonald <
> stuartm.cod...@gmail.com> wrote:
>
>> If someone can point me at a Ubuntu-compatible package, I'm more than
>> happy to upgrade. Last time I looked (within the last two months) I was
>>
On 17.12.2013 16:19, Stuart MacDonald wrote:
> On Monday, December 16, 2013 1:45:11 PM UTC-5, Branko Čibej wrote:
>
> So your server is using an nginx proxy, and your 1.7 client
> doesn't work with it. The thing to do is to try to reproduce this
> with 1.8, and if it's reproducible, it'
Thanks, I'll pass it along. It mentions that commit access is required to
exploit this though, so I think IT will probably ignore this if they
haven't already patched it.
...Stu
On Mon, Dec 16, 2013 at 2:20 PM, Ben Reser wrote:
> On 12/16/13 11:08 AM, Stuart MacDonald wrote:
> > svn is 1.7.7
On 12/16/13 11:08 AM, Stuart MacDonald wrote:
> svn is 1.7.7 (we are not planning to upgrade for some time)
This doesn't help with your issue but if you need ammo to convince IT to
upgrade:
https://subversion.apache.org/security/CVE-2013-4131-advisory.txt
If it's a distribution package it might
IT says we have:
nginx 1.05 with plans to move to 1.3.9
svn is 1.7.7 (we are not planning to upgrade for some time)
...Stu
On Mon, Dec 16, 2013 at 12:45 PM, Stuart MacDonald wrote:
> The link I provided is *exactly* what I'm seeing, so I didn't see the need
> to repeat that post. I'm in a VM,
On 16.12.2013 18:45, Stuart MacDonald wrote:
> The link I provided is *exactly* what I'm seeing, so I didn't see the
> need to repeat that post. I'm in a VM, the client drops the connection
> with an erroneous [FIN, ACK], just after the TCP window opens up again.
>
> Hm, one detail I can provide no
On Mon, Dec 16, 2013 at 12:31 PM, Stuart MacDonald wrote:
> If someone can point me at a Ubuntu-compatible package, I'm more than
> happy to upgrade. Last time I looked (within the last two months) I was
> unable to find anything later than what I'm running. I'd rather not spend
> the time compil
The link I provided is *exactly* what I'm seeing, so I didn't see the need
to repeat that post. I'm in a VM, the client drops the connection with an
erroneous [FIN, ACK], just after the TCP window opens up again.
Hm, one detail I can provide now that's not in that post:
U directory/file1
U direc
Guten Tag Stuart MacDonald,
am Montag, 16. Dezember 2013 um 18:31 schrieben Sie:
> If someone can point me at a Ubuntu-compatible package[...]
We use the package form Wandisco on our LTS 12.04.
http://subversion.apache.org/packages.html#ubuntu
Mit freundlichen Grüßen,
Thorsten Schöning
--
Th
If someone can point me at a Ubuntu-compatible package, I'm more than happy
to upgrade. Last time I looked (within the last two months) I was unable to
find anything later than what I'm running. I'd rather not spend the time
compiling from source if I can avoid it.
Please elucidate "capture traces
On Mon Dec 16 07:56:32 2013, Stuart MacDonald wrote:
>
> I am seeing exactly this
> issue: https://groups.google.com/forum/#!topic/subversion_users/AZ4M62Qwmjc
> but do not find a bug report for it in the database. The linked bug is for
> something similar but unrelated. Can I file this?
>
> ...Stu
On Mon, Dec 16, 2013 at 10:56 AM, Stuart MacDonald wrote:
>
> I am seeing exactly this issue:
> https://groups.google.com/forum/#!topic/subversion_users/AZ4M62Qwmjc but
> do not find a bug report for it in the database. The linked bug is for
> something similar but unrelated. Can I file this?
>
>
I am seeing exactly this issue:
https://groups.google.com/forum/#!topic/subversion_users/AZ4M62Qwmjc but do
not find a bug report for it in the database. The linked bug is for
something similar but unrelated. Can I file this?
...Stu
stumacdonald@stumacdonald-VirtualBox:~/src/ianywhere$ svn --vers
24 matches
Mail list logo
