perfSONAR User Q&A and Other Discussion

["Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.]" <>]

Hi,

 

A number of my tests have begun to fail after I upgraded my pS testnode software from 4.3.4 to 4.4.0 on the night of July 8/9.  It appears that something fairly dramatic has changed with test scheduling causing outbound tests to fail while inbound tests are running on a haphazard schedule sometimes only a few minutes apart.  The graphs below show test results that are scheduled to run on a 2 hour cycle.  These tests are generated though my psconfig test mesh.   There are several instances of this in my mesh and one commonality is that the remote perfsonar servers are designated as no-agent.

 

One week’s throughput test results prior to upgrade:

 

One week’s throughput test results post upgrade:

 

Latest one day’s worth of test results:

 

No issues when running a troubleshoot

 

$ pscheduler troubleshoot 198.124.238.154

Performing basic troubleshooting of localhost and 198.124.238.154.

 

localhost:

 

  Measuring MTU... 65535 (Local)

  Looking for pScheduler... OK.

  Fetching API level... 5

  Checking clock... OK.

  Exercising API... Archivers... Clock... Contexts... Tests... Tools... OK.

  Fetching service status... OK.

  Checking services... Ticker... Scheduler... Runner... Archiver... OK.

  Checking limits... OK.

  Idle test.... 9 seconds.... Checking archiving... OK.

 

xxx.xxx.xxx.xxx:

 

  Measuring MTU... 1500+

  Looking for pScheduler... OK.

  Fetching API level... 5

  Checking clock... OK.

  Exercising API... Archivers... Clock... Contexts... Tests... Tools... OK.

  Fetching service status... OK.

  Checking services... Ticker... Scheduler... Runner... Archiver... OK.

  Checking limits... OK.

  Idle test.... 5 seconds.... Checking archiving... OK.

 

localhost and xxx.xxx.xxx.xxx:

 

  Checking IP addresses... IPv4

  Measuring MTU... 1500+

  Checking timekeeping... OK.

  Simple stream test.... 13 seconds.... OK.

 

pScheduler on both hosts appears to be functioning normally.

 

When running tests between the same two serves on the command line with pscheduler, they fail.  Every so often I get a successful test using the CLI, but it’s rare and inconsistent.  They usually fail with the following errors.

Gave up after too many scheduling conflicts.

Run not found; task may have been canceled.

 

Thanks,

George Uhl

NASA GSFC

 

From: <> on behalf of Szymon Trocha <>
Organization: PCSS
Reply-To: Szymon Trocha <>
Date: Thursday, July 15, 2021 at 10:44 AM
To: Raul Lopes <>
Cc: "" <>
Subject: [EXTERNAL] Re: [perfsonar-user] Node not reporting to Maddash

 

Hi Raul,

 

W dniu 15.07.2021 o 16:03, Raul Lopes pisze:

Hi Szymon,

 

Just to say thank you.

 

All hosts running stable for a week. This link was the solution for the two nasty ones:

 

Perfect! Glad I could help

 

regards,

--

Szymon Trocha
Poznań Supercomputing & Networking Center

General NOC phone +48 61-858-2015 | noc.pcss.pl
Personal desk phone +48 61-858-2022

Wysłaliśmy do Ciebie ten e-mail w odpowiedzi na Twoje zapytanie lub w związku z oferowaną usługą. Przesłanie korespondencji do Centrum Zarządzania PCSS lub zgłoszenie telefoniczne jest równoznaczne z wyrażeniem zgody na przetwarzanie danych osobowych przez Instytut Chemii Bioorganicznej Polskiej Akademii Nauk w Poznaniu adres: ul. Z. Noskowskiego 12/14, 61-704 Poznań. Szczegółowe informacje znajdują się w naszej Polityce prywatności. | This message has been sent as a part of communication with PSNC NOC or your service request sent to us. For more information read our Privacy Policy.

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature