On 10/4/2016 12:26, Karen Pease wrote:
>
> As it says on the tin, our connections via svn+ssh are painfully slow,
> yet we can ssh into the server without any delays whatsoever. A find
> on the subversion repository likewise whips through without delay, and
> there's no memory or CPU load on the server when people are
> connecting. So all signs point to some sort of connection or
> authentication delay.
>
>
> I ran ssh through strace and compared that to a svn connection through
> strace. Here's where things go awry. First, SSH which works:
>
>
> socket(AF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 3
>
> connect(3, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("{{Our IP}}")}, 16) = 0
>
> Now, note the difference on the socket call. Ssh uses a socket call
> with SOCK_STREAM / TCP, while svn+ssh uses SOCK_DGRAM|SOCK_NONBLOCK /
> IP. Why would it do that? That doesn't make any sense to me. How
> can I change this?
>
Note the port number on that SOCK_DGRAM socket: 53. That's DNS. Is your
DNS server working properly? It sounds like it's timing out waiting for
a response from the DNS server.
Received on 2016-10-04 23:05:51 CEST