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

Access to repository hangs with Apache 2

From: James Davis <jamesd_at_jml.net>
Date: 2005-06-29 22:36:59 CEST

New to the mailing list... been using subversion for a few months now.

I'm running Subversion 1.1.4 using Apache 2.0.54 as the server under
Debian testing (Linux 2.6.8-2-686-smp). I've only recently moved from
using svnserve to provide network access to the repository.

Apache is configured with one virtual hosts that runs the mod_perl based
application stored in the repository and repository itself is run from
the main configuration. I've configured it as follows.

<Location /svn>
  DAV svn
  SVNParentPath /var/repos
  AuthType Basic
  AuthName "Subversion repository"
  AuthUserFile /etc/svn-auth-file
  Require valid-user
</Location>

Our working cycle is for the developers to make and test the changes
locally before committing to the repository. The code is then exported
from the repository into the DocumentRoot off the application as required.

Under these scheme we're experiencing a number of problems whereby
access to the repository appears to lock up hanging the client (svn or
TortoiseSVN). It doesn't appear to happen on any particular operation as
sometimes it's been a commit and at other times the export. Whilst the
subversion repository appears to be hung the mod_perl application and
indeed the rest of Apache continues to run without any impact.

I'm able to fix the problem by stopping Apache, svnadmin recover on the
repository, reset the permissions on the repository and restart Apache.
A simple restart of Apache doesn't fix the problem. Upon closing down
Apache when subversion hangs I get errors such as the following:

[Wed Jun 29 20:18:00 2005] [warn] child process 4551 still did not exit,
sending a SIGTERM
[Wed Jun 29 20:18:00 2005] [warn] child process 4414 still did not exit,
sending a SIGTERM
[Wed Jun 29 20:18:02 2005] [warn] child process 4551 still did not exit,
sending a SIGTERM
[Wed Jun 29 20:18:02 2005] [warn] child process 4414 still did not exit,
sending a SIGTERM
[Wed Jun 29 20:18:04 2005] [warn] child process 4551 still did not exit,
sending a SIGTERM
[Wed Jun 29 20:18:04 2005] [warn] child process 4414 still did not exit,
sending a SIGTERM
[Wed Jun 29 20:18:06 2005] [error] child process 4551 still did not
exit, sending a SIGKILL
[Wed Jun 29 20:18:06 2005] [error] child process 4414 still did not
exit, sending a SIGKILL
[Wed Jun 29 20:18:07 2005] [notice] caught SIGTERM, shutting down

Does anyone have any ideas or hints as to what I should be investigating
next? I'd rather not fall back to svnserve if possible as I'd like to be
able to control detailed permissions for the developer's access.

James

-- 
http://jamesd.ukgeeks.co.uk/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 29 22:43:03 2005

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