I've been banging my head against this problem for a day and I need some
help. We recently updated the machine hosting our svn repo, and this broke
commits using svn+ssh. Here's the setup:
* Machine runs debian 3.16.7, svn 1.8.10.
* svn runs as user "www-data" (the apache user).
* svn+ssh access uses a forced ssh command which sudos to the www-data
user and executes an svnserve wrapper.
* svnserve wrapper sets umask to 022 and then executes "svnserve -t" with
a specific tunnel user.
This setup is identical to what it was on the old machine. However, there
must be something different about it, because now https commits work fine,
but the svn+ssh commits give the error:
Transmitting file data .svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 255) with no
If I access the repository directly using file:// and sudo to the www-data
user when executing svn, commits work fine. This, in combination with the
fact that https access works, makes me conclude it is not a permissions or
hook problem on any of the files since all these access methods run as the
www-data user. Nevertheless, the error comes from the hook, because if I
remove the hook file completely, the failure moves to the post-commit hook.
It's not a problem finding !#/bin/sh either, because I tried replacing the
hook with a compiled C program that just returns 1, and I still got the 255
When I attempt to commit, I can see successful authentication in the
sudo: <user> : TTY=unknown ; PWD=/home/<user> ; USER=www-data ;
GROUP=www-data ; COMMAND=/usr/local/bin/svnserve-wrapper
sudo: pam_unix(sudo:session): session opened for user www-data by (uid=0)
sshd: Received disconnect from <ip>: 11: disconnected by user
sshd: pam_unix(sshd:session): session closed for user <user>
The svnserve log file gets this (the name of the repo here is "test")
<user> test open 2 cap=(edit-pipeline svndiff1 absent-entries depth
mergeinfo log-revprops) / SVN/1.8.10%20(x86_64-pc-linux-gnu) -
and then nothing. (I don't know what the "open" command does, it's not
included in the list of commands on e.g.
I've seen some similar reports of this, but no suggestions apart from
permissions or corrupted hook files, which this can't be. I don't even know
how to proceed with debugging this. Is it possible to see what svnserve
attempts to do with the hook file? Since it's spawned on demand, I don't
know how to attach to it with a debugger, or where in the source code this
Any ideas would be much appreciated,
Received on 2016-08-01 04:08:06 CEST