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

Re: SVNSERVE Error on Commits

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 12 May 2017 16:23:57 +0000

Nico Kadel-Garcia wrote on Fri, May 12, 2017 at 06:22:15 -0400:
> On Thu, May 11, 2017 at 12:20 PM, Graham, Jonathan - US
> <Jonathan.Graham_at_caci.com> wrote:
> > We have recently gone through and done some software updates to our CentOS
> > 6.9 server that hosts SVN for us. None of the updates appeared to of
> > affected anything for SVN overall, however after these patches occurred we
> > started getting org.apache.subversion.javahl.ClientException: E210004:
> > Commit failed (details follow): E210004: Malformed network data to occur on
> > nearly every commit we have attempted to make to the machine. This also
> > caused our machine to completely crash with a kernel panic. After doing some
> > digging around and getting core dump files to be generated we were able to
> > ascertain that it appears to be something that svnserve is calling that is
> > causing this issue. The following is from the core dump file: #0
> > 0x0000003a752eaebb in accept4 (fd=<value optimized out>, addr=...,
> > addr_len=0x7ffd6d4e9270, flags=524288) at
> > ../sysdeps/unix/sysv/linux/accept4.c:34 34 return INLINE_SYSCALL (accept4,
> > 4, fd, addr.__sockaddr__, addr_len, flags); Any thoughts on what is going
> > on? I’m new to submitting issues, so what are the next steps I need to
> > preform to get this escalated up as currently we are unable to do commits at
> > all unless I completely reinstall SVN on the machine, then it will let some
> > through before erroring out again.
>
> If the machine is crashing, you have a serious kernel and/or hardware
> issue.

Until you can fix the kernel and/or hardware to stop the panics, you
might try switching svnserve from --daemon mode to --inetd mode or
--tunnel mode, so that accept(2) will be called not by svnserve but by
inetd or sshd. (It's possible that something in how svnserve
calls accept(8) tickles a kernel bug, and that sshd / inetd will not
tickle that bug.)

Also, look at the libapr versions if you haven't already. Try upgrading
(or if you had, try downgrading). (libapr abstracts accept(2) for libsvn.)
Received on 2017-05-12 18:24:06 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.