perfsonar-user - Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived
Subject: perfSONAR User Q&A and Other Discussion
List archive
Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived
Chronological Thread
- From: Tao Zhang <>
- To: Mark Feit <>, "" <>
- Subject: Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived
- Date: Thu, 27 Apr 2023 18:30:19 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=canarie.ca; dmarc=pass action=none header.from=canarie.ca; dkim=pass header.d=canarie.ca; 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=fTCfkNU9GcaqePNjLg2rKPPnD9pP9SZ3jfE1OKG63UI=; b=OVbNjSrU2S65j6mYNDwQ3OLDSg6SOGQPvu91q2BnGleq3fx0Rhs/xkFdkqKGNIPgRCX3ktj6ebxAzjtdS226ML7AHXAaeUcsURw11bzvHlrcOUGSNLwPu0gU0DOW4vv/MYN2zCcz/KzlxRjyn05UNw83VtArr/Uq+4kcsgx6c/L4eGufiFsDUBjaHEjuNB1LOU+t6Yo+Z2yrt4wkunxQfDBITZ2FaPmdkoFN+Yk35DyR/8Lem4GBJ8ghrPyPUQRx/1ptN6Yc2PdMF68Y0F8ORj22VG5/koRbImKg0x/GWBASDieyI2LloFeWMxJUiemWNDyYDalnbuTaXx1sZDDpow==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Fby2Ir+YbOzz0cggY/1poorGAgipMoOgxLKFTEdOm9joysbQolyfn+5airDimplK6O0GDe47ZVoydvQHXAP8FFHfNuhJPxBufkoHYfgXP0vgd0R9Lez2XLPKX6vXmyfKs1QD+XM73YZwaq3nlG3oZ5r99siwITA/hkTMauEvs95bmL+mOq88xP05wGf1GwXt6mCLkUU1aTcfBpNOB+rZLJrf1U3lR2bB+PiV3pEiTtPA6fYXtUo7C6THe50daQHYG4GQxu1x7/nEKFh9auTg60vaGC1wv0B0tnKOcKID+v1bFQKQxcGyR1y4+9kmpqJCaoFCPUVroPzpd1Qxod/mcw==
- Msip_labels:
Sent: Friday, April 21, 2023 4:52 PM
To: Tao Zhang <>; <>
Subject: Re: Perfsonar (automatically) upgraded to 5.0 but testing data not archived
Tao Zhang writes:
All our perfSONAR boxes have been upgraded to 5.0, however, the archive shows empty.
…
I checked the pscheduler log. The log filled with something like this:
Apr 21 12:27:31 lat-sask1pfs1 journal: archiver WARNING 120686191: Failed to archive https://lat-sask1pfs1.network.canarie.ca/pscheduler/tasks/b4843fdf-6d63-4a72-a29e-770134ccf853/runs/b7ed7962-377d-4842-90da-952c3e3670ea to esmond: Archiver permanently abandoned registering test after 1 attempt(s): 405: Invalid JSON returned
…
Apr 21 12:27:34 lat-sask1pfs1 journal: archiver WARNING <title>503 Service Unavailable</title>
5.0 replaced Esmond with LogStash and OpenSearch. There is a backward-compatibility layer for Esmond, but it is read-only. If your tasks are archiving to the local system, they will need to use the HTTP archiver and post it to LogStash instead. These two sections of the documentation should get you there:
- https://docs.perfsonar.net/multi_ma_install.html#authenticating-measurement-hosts
- https://docs.perfsonar.net/multi_ma_install.html#configuring-measurement-hosts
Apr 21 12:27:30 lat-sask1pfs1 journal: runner ERROR File "/usr/libexec/pscheduler/classes/tool/traceroute/run", line 239, in <module>
Apr 21 12:27:30 lat-sask1pfs1 journal: runner ERROR run_timeout += send_wait * hops
Apr 21 12:27:30 lat-sask1pfs1 journal: runner ERROR TypeError: unsupported operand type(s) for +=: 'datetime.timedelta' and 'str'
This is a bug in pScheduler that appears to have been introduced in the last release. I’ve already corrected it and added it to the pipeline for the next bugfix release, which should happen sometime during the week of May 1.
Based on what I could pull out of the API on your system, these are the tasks that are failing:
2023-04-21T14:27:24-06:00 - 2023-04-21T14:30:32-06:00 (Failed)
trace --dest lat-gp-mn.nbren.ca --length 40 --probe-type udp --source lat-sask1pfs1.network.canarie.ca --source-node lat-sask1pfs1.network.canarie.ca --hops 30 --wait PT30S --sendwait PT5S (Run with tool 'traceroute')
As a stopgap, removing the ‘sendwait’ option from your trace tasks won’t trip the faulty code. Note that this will alter the character of the measurement.
--Mark
- [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Tao Zhang, 04/21/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Mark Feit, 04/21/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Tao Zhang, 04/27/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Zachary Newell, 04/27/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Tao Zhang, 04/27/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Zachary Newell, 04/27/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Tao Zhang, 04/28/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Mark Feit, 04/28/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Zachary Newell, 04/28/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Tao Zhang, 04/28/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Zachary Newell, 04/27/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Tao Zhang, 04/27/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Zachary Newell, 04/27/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Tao Zhang, 04/27/2023
- Re: [perfsonar-user] Perfsonar (automatically) upgraded to 5.0 but testing data not archived, Mark Feit, 04/21/2023
Archive powered by MHonArc 2.6.24.