FS#24202 - SVN server stops working with Apache 2.2.17-2 (2.2.17-1 is ok)

Attached to Project: Arch Linux
Opened by Vytenis (DisLike) - Tuesday, 10 May 2011, 07:57 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 10 May 2011, 20:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

SVN (server) stops working properly with Apache 2.2.17-2. Downgrading to Apache 2.2.17-1 solves the problem.

Additional info:
* Apache 2.2.17-2
* svn 1.6.15

Steps to reproduce:

1) Install apache 2.2.17-2 and svn 1.6.15
2) Create an empty repository for testing (svnadmin create test)
3) Configure svn to work with apache without SSL. Use configuration file similar to this:

<Location /storage/smth>
DAV svn
SVNPath /media/svn_storage/repositories/smth
AuthType Basic
AuthName "Smth"
AuthUserFile /srv/svn/.svn-auth-file
Require valid-user
AuthzSVNAccessFile /srv/svn/.policy_for_smth
</Location>

4) Try to checkout from it using svn checkout

It should produce a message "Could not read status line: connection was closed by server". When looking into /var/log/httpd it should be written that a segmentation fault occured:
"[Tue May 10 09:53:40 2011] [notice] child pid 4164 exit signal Segmentation fault (11)"
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Tuesday, 10 May 2011, 20:54 GMT
Reason for closing:  Duplicate
Additional comments about closing:  Please follow  FS#24208  and reopen in case this issue persists even after  FS#24208  has been fixed.
Comment by Ciriaco Garcia de Celis (cgarcia) - Tuesday, 10 May 2011, 19:45 GMT
I confirm this severe bug, which may also ruin the server by leaving 100% CPU usage threads. It can be tested by running a simple svn client against the web server:

svn --non-interactive --config-dir /tmp log --xml "http://server/path/@" --limit 1

With the latest apache update, this command does not return. With apache 2.2.17-1 it works fine.

Even worse: when manually aborted the request (eg. interrupting the above command) the apache server leaves a running worker taking 100% of CPU load, at least under mpm. This is a very severe problem, because when the client connection gets lost, 100% CPU threads start flooding the machine. Perhaps there is a compatibility problem with mod_dav_svn.so provided by subversion.

Loading...