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

Re: svn: E000032: Can't write to connection: Broken pipe

From: Victor Sudakov <sudakov_at_sibptus.tomsk.ru>
Date: Fri, 30 Aug 2013 22:23:06 +0700

Philip Martin wrote:
> >> > On the host running svnserve there is the following in syslog:
> >> >
> >> > Aug 30 09:04:50 <auth.err> relay svnserve: encoded packet size too big (4156 > 4096)
> >> > Aug 30 09:05:03 <auth.err> relay svnserve: encoded packet size too big (4156 > 4096)
> >> >
> >> > What could be the cause of the problem?
> >>
> >> Google suggests that "encoded packet size too big" is a SASL error.
> >> Does you conf/svnserve.conf on the server have "use-sasl = true"?
> >
> > Certainly. I have always used GSSAPI for SVN authentication, but never
> > encountered this problem before.
>
> The obvious question: what has changed?

Volume. It has been a long time since I imported anything large.

If I add a small file or commit a small change, everything still
works. But when trying to import a whole project, it breaks after
committing several files, maybe three or four.

>
> >> If so what are the min/max-enryption settings?
> >
> > These settings are commented out, so I guess some default is being
> > used.
>
> I suppose you could try setting them, perhaps max to zero
> or min to non-zero.

Setting "max-encryption = 0" really fixes the problem. Am I not
supposed to use any encryption or what?

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:sudakov_at_sibptus.tomsk.ru
Received on 2013-08-30 17:23:44 CEST

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