Den mån 27 maj 2024 kl 14:18 skrev Johan Corveleyn <jcor...@gmail.com>:
> On Sat, May 25, 2024 at 12:12 AM Williams, James P. {Jim}
> (JSC-CD4)[KBR Wyle Services, LLC] via users
> <users@subversion.apache.org> wrote:
> >
> > > Den lör 11 maj 2024 kl 03:00 skrev Williams, James P. {Jim}
> (JSC-CD4)[KBR Wyle Services, LLC] via users <users@subversion.apache.org>:
> >
> > > You previously mentioned Subversion 1.14.1, is that on the server or
> on the client?
> >
> > I'm using 1.14.1 on both the client and server.
> >
> > > Still it would be interesting to compare just to rule out a problem
> within the repository. You can use svnserve directly or tunneled over SSH,
> see the Subversion book:
> >
> > With svnserve 1.14.1, I see no problems. Checkouts complete every
> time. I'm not sure what to conclude about that. It's a different
> protocol, so it doesn't necessarily exonerate the client or the network.
> >
> > > > #0 epoll_wait /usr/lib64/libc.so.6
> >
> > > Waiting for a reply from the server ... ?
> >
> > Yeah, that'd be my guess. When the hang occurs, I've got about 90% of
> the working copy checked out. I expect the client is waiting for more
> bytes to arrive on the socket.
> >
> > > Do you see any activity on the server (CPU / disk) during this time?
> >
> > The server is well-behaved throughout all of my tests. It shows no CPU
> spike or log messages hinting that it's noticed a problem.
>
> That's why my bet is still on "something between client and server"
> (proxy, reverse-proxy, security scanning soft, ...) that messes with
> the network transfer (http or https). That would explain the symptoms
> you're seeing (client hangs waiting for network (and sometimes
> crashes), server has nothing to do and doesn't report anything
> special).
>
I agree with Johan and I understand it might be hard to nail down the
actual issue.
I don't think I have asked this before:
- Can you log in to the server and do an svn checkout https://localhost/[...]
locally and does this succeed? You might have to update the Apache HTTPD
configuration to allow the vhost to reply to "localhost" (or you could add
the server name to the local hosts file pointing to 127.0.0.1 and do a
checkout of https://[server]/[url]). What I'd like to accomplish is a
checkout that doesn't leave the machine. Does this make a difference?
Kind regards,
Daniel
