Guten Tag Daniel Shahaf, am Dienstag, 3. Januar 2017 um 16:02 schrieben Sie:
> It would have helepd to say what was being strace'd. It looks like the > strace was of svnsync of r1397, run with the target repository accessed > via file://. Sorry, but your guess was correct. The sync source is svnserve accessed through a SSH tunnel. >> > 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? I couldn't find it and AFAIK svnserve doesn't have logging facilities? 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. > The error message probably says "Path '%s' is not a directory", so check > that path on the master and mirror repositories; ensure it exists and > has the same content on both of them. Your were correct again, that was the root cause: I had access permissions in the source repo on the mentioned path, visible after running with "strace -s 255 ...", which prevented it from being synced to the mirror in the past and now the commit in that path lead to the error. I changed the permissions, rebuild the mirror-repo to include the path and now everything seems to work again. Thanks a lot! Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
