perfSONAR User Q&A and Other Discussion

[Brian Tehan <>]

Archivings:

 

  To http, Finished

    2023-07-27T15:11:31-05:00 Succeeded


Looks like that did it, thanks!

 

Brian Tehan (he/him/his)

Regional Network Engineer

University of Nebraska System

EAB009 6001 Dodge St

Omaha, NE 68182-0051

Office: (402) 554-6428

 

 

From: Mark Feit <>
Sent: Thursday, July 27, 2023 11:04 AM
To: Brian Tehan <>;
Subject: Re: Problem with getting pscheduler tasks to archive locally

 

Non-NU Email

---

Brian Tehan writes:

 

Yes, I believe that the file is built in the right place: /home/**user**/ local_archive.json

 

Based on the runs below, it looks like it found it.  The file name gets passed straight through to the system, which is where that error came from. 

 

$ pscheduler task --archive @local_archive.json throughput --source 162.127.1.81 --dest 162.127.1.85 --duration PT30S --bandwidth 52428800 --ip-version 4 --omit PT5S

… 

$ pscheduler result --archivings https://162.127.1.81/pscheduler/tasks/d4cb2662-bb44-4f91-97d9-f3e3c423275d/runs/a6143c41-dafb-45e4-8f15-5f60fa013dc2

2023-07-27T09:09:48-05:00 on 162.127.1.81 and 162.127.1.85 with iperf3:

…

Archivings:

  To http, Unfinished

    2023-07-27T09:10:32-05:00 Failed to put result: 400: Could not resolve host: {% scheduled_by_address %}; Name or service not known

 

Ah, there’s the problem.  The “{% … %}” substitutions are a function of pSConfig; pScheduler takes what it’s given literally.  Replace those with a host name and you should be in business.

 

--Mark