[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion 1.6.16 + Apache 2.2.17 crashing

From: <kmradke_at_rockwellcollins.com>
Date: Tue, 3 May 2011 11:04:42 -0500

EJ Ciramella <eciramella_at_casenetinc.com> wrote on 05/03/2011 09:44:07 AM:
> I?ve been struggling to keep a Subversion server (1.6.16) running
> via Apache (2.2.17).
>
> Every so often, it seems that the svn server crashes. Initially, we
> upgraded to SVN 1.6.12 and things would crash regularly every week.
> Restarting brought SVN back up, but now after upgrading to 1.6.16,
> it crashes almost every 2 weeks on the dot. Restarting before the
> server can crash prevents it, but I feel like we shouldn?t have to
> do that. Prior to upgrading, we were running 1.4.X and that ran
> without restarting period.
>
> Here?s what I find in the log when it does crash:
>
> <snip>
> [Mon May 02 14:49:40 2011] [crit] Parent: child process exited with
> status 3 -- Aborting.
>
> This application has requested the Runtime to terminate it in an unusual
way.
> Please contact the application's support team for more information.
> </snip>

Are you running this on a 32-bit Windows server?
In this case, there is a 2GB per process RAM limit. Exceeding that will
cause the above messages. Apache may (or may not) recover gracefully
when it hits the 2GB RAM limit on Windows. It usually doesn't...

There are less well known 64-bit apache and mod_dav_svn versions available
if you are running Server 2008R2 (or something else that is 64-bit).

Kevin R.
Received on 2011-05-03 18:05:17 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.