Invalid large, negative Content-Length

[Doug Warner <do...@warner.fm>]

When trying to "svn update" a working copy on Linux (svn 1.6.6) I'm receiving
the error "413 Request Entity Too Large".

Indeed, the Content-Length I'm seeing the client send when I set
neon-debug-mask = 138 in [global] of the servers file is:
Content-Length: -5221747158880878327

This seems similar to bug #3558 [1] but I'm just trying to update a working
repository, I don't have any 2+GB files, and I'm on Linux and not Windows.

Any ideas on what I can do to debug this?

-Doug

[1] http://subversion.tigris.org/issues/show_bug.cgi?id=3558

Re: Invalid large, negative Content-Length

[Doug Warner <do...@warner.fm>]

On 01/25/2010 01:55 PM, Doug Warner wrote:
> On 01/25/2010 10:12 AM, Stefan Sperling wrote:
>> > You could rebuild svn with the --enable-maintainer-mode configure flag.
>> > Then you'll see the file and line number where the error is thrown.
>> > You could then have the client break at the spot in gdb, and post a
>> > backtrace in case it contains anything interesting (like funky-looking
>> > function arguments). This may tell us e.g. if the problem is within
>> > neon or within svn.
> I'll see where I get with this.
> 

Unfortunately, after rebuilding with the specified option the error went away.
 After rebuilding again without it the error was still gone.

I'll post back if I wind up getting a reproducible error.

-Doug

Re: Invalid large, negative Content-Length

[Doug Warner <do...@warner.fm>]

On 01/25/2010 10:12 AM, Stefan Sperling wrote:
> You could rebuild svn with the --enable-maintainer-mode configure flag.
> Then you'll see the file and line number where the error is thrown.
> You could then have the client break at the spot in gdb, and post a
> backtrace in case it contains anything interesting (like funky-looking
> function arguments). This may tell us e.g. if the problem is within
> neon or within svn.

I'll see where I get with this.

> In addition to the complete neon debug output, a tcpdump -s99999 -X
> of the running update would also be nice, to see what client and
> server are sending to each other over the wire.

This won't be too useful for my situation since everything is done over SSL.

Thanks for the tips; I'll post back with what I find.

-Doug

Re: Invalid large, negative Content-Length

[Stefan Sperling <st...@elego.de>]

On Mon, Jan 25, 2010 at 09:45:19AM -0500, Doug Warner wrote:
> When trying to "svn update" a working copy on Linux (svn 1.6.6) I'm receiving
> the error "413 Request Entity Too Large".
> 
> Indeed, the Content-Length I'm seeing the client send when I set
> neon-debug-mask = 138 in [global] of the servers file is:
> Content-Length: -5221747158880878327
> 
> This seems similar to bug #3558 [1] but I'm just trying to update a working
> repository, I don't have any 2+GB files, and I'm on Linux and not Windows.
> 
> Any ideas on what I can do to debug this?

You could rebuild svn with the --enable-maintainer-mode configure flag.
Then you'll see the file and line number where the error is thrown.
You could then have the client break at the spot in gdb, and post a
backtrace in case it contains anything interesting (like funky-looking
function arguments). This may tell us e.g. if the problem is within
neon or within svn.

In addition to the complete neon debug output, a tcpdump -s99999 -X
of the running update would also be nice, to see what client and
server are sending to each other over the wire.

You could post this information here, or attach it to issue #3558,
your call.

TIA,
Stefan