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

Quite an odd post-commit error after a successful commit

From: Kobayashi Noritada <nori1_at_dolphin.c.u-tokyo.ac.jp>
Date: 2007-01-09 14:23:07 CET

Hi,

Quite an odd post-commit script error after a successful commit
occurred in a Subversion repository in the Debian JP's server
osdn.debian.or.jp. Here I report the scenario.

== Short description of the issue

When committing with a client, the client dumps core and the entire
working copy is locked (i.e. marked with "L"). Since files have been
sent and the commit have succeeded, the user have to run commands
something like revert or remove in the root of the working copy before
updating.

== Additional descriptions

* The issue occurs only when post-commit hooks are turned on.

* At first the issue had not occurred: any commit with a post-commit
  hook script had succeeded. However, once the issue had occurred, it
  occurred with any commit and with any post-commit hooks (that had
  been set a+rx www-data:www-data), including officially distributed
  post-commit hook scripts and a one-line script only containing
  "#!/bin/sh". When turning post-commit hooks off, the issue did not
  occur. However, turning post-commit hooks on again made it recur.
  Dumping and loading the repository did not resolve the issue.
  Neither running /etc/init.d/apache2 restart nor reload resolved the
  issue. (So, it did not seem to be due to wrong hook scripts,
  hardware issues, nor inode issues...)

* However, turning the post-commit script on made the script behave
  correctly without error today, few days after turning off it. We
  don't know what had worked. During the period the hook was off, the
  administrator had not performed any operations except for running
  /etc/init.d/apache stop and start, maybe. Since at first the issue
  hadn't occurred, there is a possibility that it will occur again
  some time.

* Apache logs accompanying one error is as follows:
  [Fri Jan 05 23:57:18 2007] [error] [client ] Could not MERGE resource "/repos/!svn/act/bd517be3-04e6-42f2-a8cc-9fa669ecf2d6" into "/repos/www/trunk". [409, #0]
  [Fri Jan 05 23:57:18 2007] [error] [client ] An error occurred while committing the transaction. [409, #165007]
  [Fri Jan 05 23:57:18 2007] [error] [client ] Commit succeeded, but post-commit hook failed [409, #165007]

* The issue occurred on Debian GNU/Linux stable ("sarge"), with
  Subversion 1.1.4-2 and 1.3.2-5~bpo1 as the server, 1.1.4-2 and
  1.4.2dfsg1-2 as the client, HTTP(S) as RA, and fsfs as the
  repository type.

* An error report http://svn.haxx.se/users/archive-2004-11/1235.shtml
  (which no one answered) seems to mention the same issue. I also
  checked mailing list archives and IssueZilla, finding no other
  report, and read through CHANGES, finding no fix.

* Note that the administrator Kenshi Muto is a well-skilled Debian
  developer and an old Subversion user. Of course he has been using
  post-commit hooks in many servers, but met this error for the first
  time.

I know it is very hard to resolve the issue with such a little
information: unfortunately the repository was in the actual usage
(with no debug information). Also, the erroneous behaviour was very
odd. However, if someone get a hint from this report, I would be
happy. :-)

Many thanks,

-nori

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 9 14:23:17 2007

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