On Tue, Jan 7, 2014 at 7:34 PM, Philip Martin wrote:
>
> So you used dump/load to create a new repository and then replaced the
> old repository with the new repository? If you did that while Apache
> was running, without restarting Apache, then that explains the 'Corrupt
> node-revision' error as you changed the data on disk.
Ah, thanks a lot for explaining that. Yes, I did dump/load the old
repository into a new one because I wanted to test if it would solve
the problem
(on client)
svn: E000054: Error retrieving REPORT: Connection reset by peer
(on server)
[dav:error] [pid 3613] [client <ip>] Unable to deliver content. [500, #0]
[dav:error] [pid 3613] [client <ip>] Could not write data to
filter. [500, #175002]
which it didn't. It only added a few additional problems until I
restarted Apache (I'm sorry for confusing you with those), but the
initial error E000054/175002 is still causing problems.
> What you are left with is some sort of intermittent network problem. I
> don't know what is causing that.
Is there any way to debug that?
Thank you very much,
Mojca
