Thorsten Schöning wrote on Tue, Jan 03, 2017 at 17:56:12 +0100: > Guten Tag Daniel Shahaf, > am Dienstag, 3. Januar 2017 um 16:02 schrieben Sie: > > >> > write(4, "( failure ( ( 160016 50:Pfad \302\273t"..., 86) = 86 > > > In subversion/libsvn_ra_svn/protocol in the source tree. > > Does this tell me that svnsync is writing an error message to > svnserve or somewhere else? Where would that message be saved/shown?
Yes, it appears that svnsync is sending a failure response to a replay editor (svn_ra_replay*()) driven by the svnserve serving the master repository. That svnserve then returns an error to svnsync. If the latter error (E210008) does not contain the former error (E160016), then the former error would be logged by the remote svnserve. > I couldn't find it and AFAIK svnserve doesn't have logging facilities? It does: --log-file. > I'm starting svnserve using Upstart currently like the following: > > > exec /usr/bin/svnserve --daemon --root /[...] --listen-host [...] > > --listen-port [...] > > Upstart logs STDERR and STDOUT automatically this way and did for > other errors in the past while e.g. starting the service itself, but > this time no error was logged. Right, svnserve --daemon prints nothing to stdout/stderr if it starts successfully. > Thanks a lot! You're welcome. And I did enjoy the detective work :-) Cheers, Daniel
