I have run into what might be the same issue. Can you perform svn log operations using timestamps? Or does that also trigger an internal server error?
My guess is that you have some revisions in your repository that are empty, probably because you did a filter on a dump, but preserved revisions. This leaves "empty" revisions around, which then trigger a problem. I worked around the problem by adding svn:date revprops for the affected repository. Eric On Sep 7, 2015, at 3:08 AM, "sascha.ret...@t-systems.com" < sascha.ret...@t-systems.com> wrote: Hello, I am not subscribed so please be so kind to add me to CC regarding this topic. We are experiencing a problem with Subversion since some days and we are not able to recognize any changes made to the server. As soon as we try to checkout using a timestamp (e.g. svn --username some_user co https://some_u...@some.host/svn/XYZ/sources/.../trunk -r {"2015-09-02 09:00:00"}) we are getting: svn: E175002: Unerwarteter HTTP-Status 500 »Internal Server Error« auf »/svn/XYZ/!svn/me« svn: E175002: Zusätzliche Fehler: svn: E175002: REPORT-Anfrage auf »/svn/XYZ/!svn/me« schlug fehl: 500 Internal Server Error If we checkout using HEAD or any revision-number everything works as expected. Problem is that jenkins’ subversion plugin uses timestamps to checkout for CI builds. Is this a known problem? Do you know any workaround or fix? Should I fill a bug-report for this problem? Best regards, Sascha Retter
