perfsonar-user - Re: [perfsonar-user] Iperf3 error
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Raul Lopes <>
- To: Andrew Lake <>, "" <>
- Subject: Re: [perfsonar-user] Iperf3 error
- Date: Fri, 6 Oct 2023 13:37:39 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=jisc.ac.uk; dmarc=pass action=none header.from=jisc.ac.uk; dkim=pass header.d=jisc.ac.uk; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=uEFJi37UVpoyu5zriHkvZEOMaReo6kkdvIfm2RZ3BHo=; b=Hm4cEe1Gjzk+O4vxqhCief8P+Fp9N5Gg2Ye/GD6xXrYYVJFkbwSKtGjCjjd/w068i6s+fGYXFtFihGYw1m1JYdr73VhxefOtmzB55zW2Q3cMkSdd7L/tnHqr4cXfGJR//uoghHrzEbs2uIA+1rtRUqBzPavft8PuCl0VKhOiuhvAQMnIJpbErWFAv8CFjjK9duo77ISc2WSBlybgdDyRDFeCg6lgZ/O3oxJbZMurKis2ff8SiKTrYkxwICvgI6zwwvrB+1CyZRcyj6CUdPzJLvZB83F8chLpapJ/PBzoSXaBT5zVXHblO9F+RNJb5DTDLt1nyj3rHQjSH3Y7W5NRXg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eR1K09my99I/mgHFYEKbI1hAmcxkshG5xfLOR2tlEoZgAQ/DUTsrGEedCGJ+uYxG9N+FL14uFAtOxHXpp7gnoBY4sGqsgMFni0ytZX0BIg5HwfdOn+3/zFqa8tnLW8t6sOGTQrqn3mRTykJ69h0rGO24V53jaI4vwoUG97JOvRMHNfTI6EvIU0ujj5IBDWi0Oey3MLJJ5bC2Oyd4NQBuMpqwJhNHVj3cWkACYXlCkMTxqhKGUSGTbuxGyb+/MnLpKRJRA86FHP2K1roVNY90FzI7c/yInvlkuQH9/vwC53f+x241eR02MUsRCMWhGRFpllIYArJlCj2W5B8xQIHv0Q==
Hi Andy,
The hosts are all perfSONAR 5.0.5.
DNS is resolving in less than 0.02s.
And iperf3 is the same: 3.14-1.el7 from @perfSONAR.
And ntp seems fine.
Regards, Raul
From:
Andrew Lake <> Hi Raul,
I’ve run into errors like that when there are timing issues between the hosts and pscheduler is slow to start the server or the client starts after the server gets brought down. There is multiple seconds of buffer built-in to pscheduler so it has to be something that slows things down by multiple seconds. A few things to check:
1. Are all the endpoints running 5.0.4 or later? It has a fix that removes some logic that was causing things to logjam if DNS was taking awhile. 2. Related to #1, is DNS configured properly? are DNS queries returning in < 1s? You can try the pscheduler tests with just IPs. If they work, may be some DNS issues slowing things down. 3. Not timing related: any strange versions of iperf3 running on those hosts? I’ve ran into cases before where the older version of iperf3 in the main Ubuntu repos gets pulled down and causes issues.
Could be something else as well, but above are a few things I’ve ran into before.
Thanks, Andy
On October 5, 2023 at 2:13:15 PM, Raul Lopes () wrote:
|
- [perfsonar-user] Iperf3 error, Raul Lopes, 10/05/2023
- Re: [perfsonar-user] Iperf3 error, Andrew Lake, 10/05/2023
- Re: [perfsonar-user] Iperf3 error, Raul Lopes, 10/06/2023
- Re: [perfsonar-user] Iperf3 error, Andrew Lake, 10/05/2023
Archive powered by MHonArc 2.6.24.