On Fri, Oct 29, 2010 at 2:35 PM, Bagnall, Martin
<Martin.Bagnall_at_hmhpub.com> wrote:
> In the Apache SSL error log on the server the corresponding message is:
>
> [Fri Oct 29 13:10:15 2010] [error] [client <IP_Address>] Provider
> encountered an error while streaming a REPORT response. [500, #0]
>
> [Fri Oct 29 13:10:15 2010] [error] [client <IP_Address>] A failure occurred
> while driving the update report editor [500, #721450]
>
> [Fri Oct 29 13:10:15 2010] [error] [client <IP_Address>] Can't read file
> 'E:\\repository\\<repo_name>\\db\\revs\\20\\20795': Insufficient system
> resources exist to complete the requested service.
>
<snip>
>
> The “Insufficient system resources” message suggests a problem with the
> server but I don’t see anything hogging memory or CPU and available disk
> space is fine. The repository is quite large if that makes a difference (278
> Gb on the server).
Wow, 278 Gb for a repository is *huge* IMHO. Are there a lot of large
binary files in there?
Maybe the "insufficient resource" is related to the number of open
file handles? I don't know how this works on Windows (or how you can
configure it), but on *nix you have things like "ulimit" to limit the
maximum number of file descriptors a process can have open
simultaneously.
Is there anything special about revision 20795, the one that is
referenced in the "insufficient system resources" message? Is it a
very large rev file in the repository (the file
'E:\\repository\\<repo_name>\\db\\revs\\20\\20795')?
Cheers,
Johan
>
> Server: Apache 2.2.15 with Subversion 1.6.11 on Windows Server 2003
>
> Client: TortoiseSVN 1.6.11 on Windows 7
Received on 2010-10-29 15:44:26 CEST