On Wed, Nov 30 2022, Christian Weisgerber wrote:
> For at least two weeks, I have observed a strange error on OpenBSD/amd64
> -current, across multiple snapshots and rebuilds from source during
> that time:
>
> When several ssh processes are spawned in quick succession, SOMETIMES
> one of them hangs in connect(2) and will eventually error out because
> connect() to the target host failed.
>
> Unfortunately, I cannot reproduce this at will, but it keeps happening
> from time to time.
>
> On one occasion I managed to attach a ktrace -p to a hanging ssh.
> Nothing to see there, it eventually returned from connect() with
> an error and exited. I don't think this has anything to do with
> ssh itself.
>
> The pattern is that several ssh processes are spawned in parallel
> that connect to different hosts--actually the amd64*.p package build
> machines. I have observed this both from home a continent away,
> and from amd64.p to amd64-*.p on the same network.
I suspect this is a problem local to the ports machines network.
Some SYN packets seem to be lost, as in they don't appear in tcpdump(8)
on the target machine.
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
