You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Timothy Astle <ti...@caris.com> on 2015/05/11 13:16:25 UTC

Error checking out project that contains a large amount of binary data

I've browsed through the mailing list* but I'm not certain if there is a 
clear answer for the problem I'm seeing.

When checking out a project that contains a large amount of binary data 
(24 GB), we are seeing the following error in the apache logs from 
time-to-time (not consistent) and the checkout aborts:

     Error writing base64 data. Software caused connection abort [500. #103]

Some configuration information:

- The Subversion mod_dav_svn version is 1.7.4, clients are > 1.7.4 
(including 1.8 clients)
- The HTTPD info is:

Server version: Apache/2.2.15 (Unix)
Server built:   Feb 13 2012 22:31:42
Server's Module Magic Number: 20051115:24
Server loaded:  APR 1.3.9, APR-Util 1.3.9
Compiled using: APR 1.3.9, APR-Util 1.3.9
Architecture:   64-bit
Server MPM:     Prefork
   threaded:     no
     forked:     yes (variable process count)
Server compiled with....
  -D APACHE_MPM_DIR="server/mpm/prefork"
  -D APR_HAS_SENDFILE
  -D APR_HAS_MMAP
  -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
  -D APR_USE_SYSVSEM_SERIALIZE
  -D APR_USE_PTHREAD_SERIALIZE
  -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
  -D APR_HAS_OTHER_CHILD
  -D AP_HAVE_RELIABLE_PIPED_LOGS
  -D DYNAMIC_MODULE_LIMIT=128
  -D HTTPD_ROOT="/etc/httpd"
  -D SUEXEC_BIN="/usr/sbin/suexec"
  -D DEFAULT_PIDLOG="run/httpd.pid"
  -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
  -D DEFAULT_LOCKFILE="logs/accept.lock"
  -D DEFAULT_ERRORLOG="logs/error_log"
  -D AP_TYPES_CONFIG_FILE="conf/mime.types"
  -D SERVER_CONFIG_FILE="conf/httpd.conf"

I've checked the changes list and the closest thing I see is a note in 
1.7.2 that references base64, but we're beyond that version in clients 
and servers.
http://svn.apache.org/repos/asf/subversion/trunk/CHANGES

Any tips on what to look at?


Tim


* 
https://www.google.ca/search?client=opera&q=Error+writing+base64+data.+Software+caused+connection+abort&sourceid=opera&ie=UTF-8&oe=UTF-8#q=Error+writing+base64+data.+Software+caused+connection+abort+site:subversion.open.collab.net

Re: Error checking out project that contains a large amount of binary data

Posted by Timothy Astle <ti...@caris.com>.
I looked it up and it doesn't give me any leads:

#define ECONNABORTED    103     /* Software caused connection abort */

Any other ideas?




On 11/05/2015 10:29 PM, Daniel Shahaf wrote:
> Timothy Astle wrote on Mon, May 11, 2015 at 08:16:25 -0300:
>>      Error writing base64 data. Software caused connection abort [500. #103]
> "103" is the apr_status_t error number.  It's probably an errno number.
> You might want to look up what's errno code 103 on your system.
>
>

Re: Error checking out project that contains a large amount of binary data

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Timothy Astle wrote on Mon, May 11, 2015 at 08:16:25 -0300:
>     Error writing base64 data. Software caused connection abort [500. #103]

"103" is the apr_status_t error number.  It's probably an errno number.
You might want to look up what's errno code 103 on your system.