On Apr 24, 2006, at 12:30, Markus Henschel wrote:
> This hook does what it is proposed - for a time. I noticed that
> after running the server for a while sometimes a commit fails
> stating the pre-commit hook failed. There are several strange
> things about that:
>
> 1. The hooks are executed and reach the exit 0. I know that because
> when I output something to stderr before the "exit 0" it is
> displayed to the client.
>
> 2. The failing frequency increases to a point where all (pre-
> commit) hooks fail no matter what's in them. Even a dummy hook only
> containing "exit 0" will fail.
>
> Unfortunately there are no more additional information in the
> apache logs even when the log level is increased to debug. It just
> states that a pre-commit hook failed with an empty error output.
> When I restart the apache everything is fine again for the moment
> but the problem reoccurs again after some uptime.
Try verifying your repository with "svnadmin verify" to see if it's
alright. "svnadmin recover" if necessary.
If you're using a BDB repository, consider switching to FSFS. I don't
think it's necessarily WebSVN that's causing the problem, but
possibly just any concurrent access from another process, possibly
over a different protocol. FSFS doesn't have problems with that; I
believe BDB does. See the FAQ for how to convert.
Please consider upgrading your Apache. 2.0.50 is almost two years old.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 24 12:55:13 2006