On Sat, Apr 17, 2010 at 10:12 PM, Aaron Turner <synfinatic_at_gmail.com> wrote:
> Not sure why, but sometimes svnserve segfaults when it runs via
> xinetd. It turns out to be highly repeatable for specific svn
> transactions/commands. Ie:
>
> svn merge -c 2454 . ../../branches/3.4/src
>
> causes the segfault, but another svn command works fine (I had just
> done a number of commits). I've seen it happen with svn update as
> well, so it doesn't seem specific to merge.
>
> Not really sure why, but here is what I'm getting in /var/log/messages:
>
> Apr 18 04:51:59 lagavulin kernel: svnserve[28484]: segfault at
> b786f2fc ip b7503814 sp bfd4b6e0 error 4 in
> libsasl2.so.2.0.22[b74f4000+18000]
> Apr 18 04:51:59 lagavulin xinetd[2797]: EXIT: svn signal=11 pid=28484
> duration=0(sec)
>
> Note the same command works find when svnserve runs as a daemon. I am
> using SASL auth, but 9/10 times it works just fine.
>
> client is OSX/x86 10.6.3, svn v1.6.9 and v1.6.11
> server is Linux (CentOS 5.3/x86), svn v1.6.9
>
> Anyways, problem has seem to gone away after switching to daemon mode,
> so I don't need anyone to fix my problem, but figured a bug report was
> warranted.
>
> --
> Aaron Turner
> http://synfin.net/ Twitter: @synfinatic
> http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
> Those who would give up essential Liberty, to purchase a little temporary
> Safety, deserve neither Liberty nor Safety.
> -- Benjamin Franklin
> "carpe diem quam minimum credula postero"
>
I would look at the user the svnserve process is being run as. Are the
permissions correct to access to repo files? Is it the same user that
runs the process in deamon mode? This could explain why read only ops
would work, but write ops may not.
However, whether its a permission thing or not, there should be a
meaningful error message, not a core dump. It would be worth it to
the community to figure out what's really happening.
Received on 2010-04-18 20:59:15 CEST