subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philip Martin <philip.mar...@wandisco.com>
Subject Re: Seeking help for "E000054: Error retrieving REPORT: Connection reset by peer"
Date Tue, 07 Jan 2014 18:34:08 GMT
Mojca Miklavec <mojca.miklavec.lists@gmail.com> writes:

> Ah, OK, I see it now in the old logs. There are no such lines in the
> latest logs.

> The repository is stored on a local disk. I'm not sure what about
> filesystem is it that you are asking, but here are some possibly
> relevant data:
>
>> cat format
> 5
>> cat db/fs-type
> fsfs
>> cat db/format
> 6
> layout sharded 1000
>
> (and before I upgraded the repository, db/format was 4). Is that what
> you were asking or do did you want to know something else?

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.

What you are left with is some sort of intermittent network problem.  I
don't know what is causing that.

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*

Mime
View raw message