RE: svn up -r {DATE} returns E1000104

2023-06-13 Thread Mun Johl
Hi Daniel,

Thank you very much for your reply.  Please see my comments below.

Hi all,

Let me start out by saying I know we are on an old version of SVN on RHEL7, and 
I apologize in advance for that fact.  Our SVN revision is: v1.9.12

We had to obsolete our old local SVN server and then we moved to a remote VM 
running the aforementioned version of SVN.  Our old local SVN server was 
running v1.9.3 .  We were trying to keep the SVN revision on the new server 
close to what we were running in the past to try and avoid any disruptions.

You should be able to update to any later server version without any problem. 
Older clients might not be able to use all the features of the new server but 
there should be cross compatibility with all versions.

[Mun] That’s good to know.

Just about everything on the new SVN server works fine, except for: ‘svn up -r 
{DATE}’.  That command returns the following output:
Updating '.':
svn: E000104: Can't read from connection: Connection reset by peer

Which protocol do you use for accessing the repository? (svn info --show-item 
url should give the url, the protocol is the first part)

[Mun] svn:

Do you see anything in the server log files?

[Mun] Our Linux Administrator stated he didn’t see anything pertinent in the 
server logs.  Is there any way to increase verbosity or something so as to log 
debug information?

Is it a large repository and could it by any chance be a network issue, where 
the network connection times out while Subversion is trying to find the 
revision number corresponding with the date?

[Mun] I wouldn’t necessarily consider it a large repository—but it’s not small 
either.  Your network issue concern is interesting since the server is now at a 
different corporate site.  However, empirically I would have expected that 
perhaps the issue would be intermittent if it were a network issue.  This 
problem occurs every time I’ve tried the command—even at different times of the 
day.  Not that that proves anything—it’s just meant to be a data point.

I’ve tried the command in a branch that isn’t very large—but maybe that doesn’t 
make a difference if it’s the total repository size that makes a difference—and 
I still had the same issue with ‘svn up -r {DATE}’.

Thank you very much for your feedback!

Best regards,

--
Mun Johl

Kind regards,
Daniel Sahlberg


Re: svn up -r {DATE} returns E1000104

2023-06-13 Thread Daniel Sahlberg
Den mån 12 juni 2023 kl 20:45 skrev Mun Johl :

> Hi all,
>
>
>
> Let me start out by saying I know we are on an old version of SVN on
> RHEL7, and I apologize in advance for that fact.  Our SVN revision is:
> v1.9.12
>
>
>
> We had to obsolete our old local SVN server and then we moved to a remote
> VM running the aforementioned version of SVN.  Our old local SVN server was
> running v1.9.3 .  We were trying to keep the SVN revision on the new server
> close to what we were running in the past to try and avoid any disruptions.
>

You should be able to update to any later server version without any
problem. Older clients might not be able to use all the features of the new
server but there should be cross compatibility with all versions.


>
> Just about everything on the new SVN server works fine, except for: ‘svn
> up -r {DATE}’.  That command returns the following output:
>
> Updating '.':
>
> svn: E000104: Can't read from connection: Connection reset by peer
>

Which protocol do you use for accessing the repository? (svn info
--show-item url should give the url, the protocol is the first part)

Do you see anything in the server log files?

Is it a large repository and could it by any chance be a network issue,
where the network connection times out while Subversion is trying to find
the revision number corresponding with the date?

Kind regards,
Daniel Sahlberg

>