Skip to Content.
Sympa Menu

perfsonar-user - RE: [perfsonar-user] Problem with getting pscheduler tasks to archive locally

Subject: perfSONAR User Q&A and Other Discussion

List archive

RE: [perfsonar-user] Problem with getting pscheduler tasks to archive locally


Chronological Thread 
    < Chronological >      < Thread >
  • From: Brian Tehan <>
  • To: Mark Feit <>, "" <>
  • Subject: RE: [perfsonar-user] Problem with getting pscheduler tasks to archive locally
  • Date: Thu, 27 Jul 2023 14:18:00 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nebraska.edu; dmarc=pass action=none header.from=nebraska.edu; dkim=pass header.d=nebraska.edu; 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=wC9Jgly+H6NOXtx2pfzEE+phXskdG0l4zilVdKmAmww=; b=T9M9GwYMV/AXT6AraNFHzOlrDPzsm8Tb1kweS9HD77OB2SyuXyPFZMleijzKVbNhRgaC9YMkF8L/D7YQ7F4fSmdExZxZY2rXmctuTIXLGFtDYaSU9M2ItZQPJCFiVxE1trEoLhLgafVmkNPNtZlSwMZ4WGCbeD2IZGlWkXUDEqlb9N553VIsT04Ic1IeB/Lxoj7zDAKyR1YqPQ1NcJ/VneRlueqHNBrnEL09IYswkUYjAnBq8VNXgIfpajPFlKdEqSuyTS5n0kRt8ZgcCPsIBgnfR/msI0kvsSS9A41w1iJLBeatLffRqcOxZW1fDsbGj+dvnEUSwgCUMrWHsl0aNQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=g00ry8kOKzE7uHJmgyt0cXci+mzhG26DJ8RzRvxBDLArn8nV1rtoTGP0m3VO54QOJizBKgaQMDQl51j1NndsCZllKPXpLbq7EQxyo1LqQovUJVmn7/rQBI2ILawS0iU8L2Orc1pX6UCX4jjMrIDkQ/bYwxnn1M6/75X29uv0lxd2/QQNv6c7SkWGtY0SFvXvKjLB/mXjlbj1YW5RdaTU+uOhAsrurTtYuamXI0KleTpTHD7AmM7vgY8isk/JFXbbRt5b0sTRJJ6y2WWs+KS4c3YFFOdbMJ7R4lw+Lme4zU8yW7vzSILnFxyXH/FyM8ckhO4Ng23O1e9XUvDcvOm7Vw==

Mark,

 

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

 

I ran a quick test between two nodes:

 

 

 

 

$ 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

Submitting task...

Task URL:

https://162.127.1.81/pscheduler/tasks/d4cb2662-bb44-4f91-97d9-f3e3c423275d

Running with tool 'iperf3'

Fetching first run...

 

Next scheduled run:

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

Starts 2023-07-27T09:09:48-05:00 (~7 seconds)

Ends   2023-07-27T09:10:32-05:00 (~43 seconds)

Waiting for result...

 

* Stream ID 5

Interval       Throughput     Retransmits    Current Window

0.0 - 1.0      52.42 Mbps     0              278.02 KBytes   (omitted)

1.0 - 2.0      52.43 Mbps     0              278.02 KBytes   (omitted)

2.0 - 3.0      52.43 Mbps     0              278.02 KBytes   (omitted)

3.0 - 4.0      52.43 Mbps     0              278.02 KBytes   (omitted)

4.0 - 5.0      52.43 Mbps     0              278.02 KBytes   (omitted)

0.0 - 1.0      52.43 Mbps     0              278.02 KBytes 

1.0 - 2.0      53.47 Mbps     0              278.02 KBytes 

2.0 - 3.0      51.39 Mbps     0              278.02 KBytes 

3.0 - 4.0      52.43 Mbps     0              278.02 KBytes 

4.0 - 5.0      53.48 Mbps     0              278.02 KBytes 

5.0 - 6.0      51.38 Mbps     0              278.02 KBytes 

6.0 - 7.0      52.43 Mbps     0              278.02 KBytes 

7.0 - 8.0      52.43 Mbps     0              278.02 KBytes 

8.0 - 9.0      53.48 Mbps     0              278.02 KBytes 

9.0 - 10.0     52.43 Mbps     0              278.02 KBytes 

10.0 - 11.0    51.38 Mbps     0              278.02 KBytes  

11.0 - 12.0    53.47 Mbps     0              278.02 KBytes 

12.0 - 13.0    52.43 Mbps     0              278.02 KBytes 

13.0 - 14.0    51.38 Mbps     0              278.02 KBytes 

14.0 - 15.0    52.43 Mbps     0              278.02 KBytes 

15.0 - 16.0    52.43 Mbps     0              278.02 KBytes 

16.0 - 17.0    52.43 Mbps     0              278.02 KBytes 

17.0 - 18.0    52.43 Mbps     0              278.02 KBytes 

18.0 - 19.0    52.43 Mbps     0              278.02 KBytes 

19.0 - 20.0    53.47 Mbps     0              278.02 KBytes 

20.0 - 21.0    51.38 Mbps     0              278.02 KBytes 

21.0 - 22.0    52.43 Mbps     0              278.02 KBytes 

22.0 - 23.0    53.47 Mbps     0              278.02 KBytes 

23.0 - 24.0    51.38 Mbps     0              278.02 KBytes 

24.0 - 25.0    52.43 Mbps     0              278.02 KBytes 

25.0 - 26.0    52.43 Mbps     0              278.02 KBytes 

26.0 - 27.0    52.43 Mbps     0              278.02 KBytes 

27.0 - 28.0    52.43 Mbps     0              278.02 KBytes 

28.0 - 29.0    52.43 Mbps     0              278.02 KBytes 

29.0 - 30.0    52.43 Mbps     0              278.02 KBytes 

 

Summary

Interval       Throughput     Retransmits    Receiver Throughput

0.0 - 30.0     52.43 Mbps     0              52.42 Mbps

 

No further runs scheduled.


 

And here’s the archivings info:

$ 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:

 

throughput --source 162.127.1.81 --dest 162.127.1.85 --duration PT30S --bandwidth 52428800 --ip-version 4 --omit PT5S

 

* Stream ID 5

Interval       Throughput     Retransmits    Current Window

0.0 - 1.0      52.42 Mbps     0              278.02 KBytes   (omitted)

1.0 - 2.0      52.43 Mbps     0              278.02 KBytes   (omitted)

2.0 - 3.0      52.43 Mbps     0              278.02 KBytes   (omitted)

3.0 - 4.0      52.43 Mbps     0              278.02 KBytes   (omitted)

4.0 - 5.0      52.43 Mbps     0              278.02 KBytes   (omitted)

0.0 - 1.0      52.43 Mbps     0              278.02 KBytes 

1.0 - 2.0      53.47 Mbps     0              278.02 KBytes 

2.0 - 3.0      51.39 Mbps     0              278.02 KBytes 

3.0 - 4.0      52.43 Mbps     0              278.02 KBytes 

4.0 - 5.0      53.48 Mbps     0              278.02 KBytes 

5.0 - 6.0      51.38 Mbps     0              278.02 KBytes 

6.0 - 7.0      52.43 Mbps     0              278.02 KBytes 

7.0 - 8.0      52.43 Mbps     0              278.02 KBytes 

8.0 - 9.0      53.48 Mbps     0              278.02 KBytes 

9.0 - 10.0     52.43 Mbps     0              278.02 KBytes 

10.0 - 11.0    51.38 Mbps     0              278.02 KBytes 

11.0 - 12.0    53.47 Mbps     0              278.02 KBytes 

12.0 - 13.0    52.43 Mbps     0              278.02 KBytes 

13.0 - 14.0    51.38 Mbps     0              278.02 KBytes 

14.0 - 15.0    52.43 Mbps     0              278.02 KBytes 

15.0 - 16.0    52.43 Mbps     0              278.02 KBytes 

16.0 - 17.0    52.43 Mbps     0              278.02 KBytes 

17.0 - 18.0    52.43 Mbps     0              278.02 KBytes 

18.0 - 19.0    52.43 Mbps     0              278.02 KBytes 

19.0 - 20.0    53.47 Mbps     0              278.02 KBytes 

20.0 - 21.0    51.38 Mbps     0              278.02 KBytes 

21.0 - 22.0    52.43 Mbps     0              278.02 KBytes 

22.0 - 23.0    53.47 Mbps     0              278.02 KBytes 

23.0 - 24.0    51.38 Mbps     0              278.02 KBytes 

24.0 - 25.0    52.43 Mbps     0              278.02 KBytes 

25.0 - 26.0    52.43 Mbps     0              278.02 KBytes 

26.0 - 27.0    52.43 Mbps     0              278.02 KBytes 

27.0 - 28.0    52.43 Mbps     0              278.02 KBytes 

28.0 - 29.0    52.43 Mbps     0              278.02 KBytes 

29.0 - 30.0    52.43 Mbps     0              278.02 KBytes 

 

Summary

Interval       Throughput     Retransmits    Receiver Throughput

0.0 - 30.0     52.43 Mbps     0              52.42 Mbps

 

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


 

And here’s the local_archive.json file:

 

 

 

$ cat local_archive.json

{

    "archiver": "http",

    "data": {

        "schema": 2,

        "_url": https://{% scheduled_by_address %}/logstash,

        "op": "put",

        "_headers": {

            "x-ps-observer": "{% scheduled_by_address %}",

            "content-type": "application/json",

            "Authorization":"Basic ***token***"

        }

    }

}

 

Thoughts?

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

university of nebraska logo lockup with campuses

 

 

From: Mark Feit <>
Sent: Monday, July 24, 2023 2:21 PM
To: Brian Tehan <>;
Subject: Re: Problem with getting pscheduler tasks to archive locally

 

Non-NU Email

Brian Tehan writes:

 

I saw that archiving tasks has changed, I ran the  “/usr/lib/perfsonar/archive/perfsonar-scripts/psconfig_archive.sh -n localhost > local_archive.json” command.  I then attempted to run another pscheduler throughput task following the example given but it errors out:

pscheduler task --archive @local_archive.json --slip PT1H --sliprand --repeat-cron "36 0-5 * * *" throughput --source 162.127.1.81 --dest 162.127.1.1 --duration PT30S --bandwidth 3221225472 --ip-version 4 --omit PT5S

Unable to read archive file: [Errno 2] No such file or directory: 'local_archive.json'

 

The bit of code that interprets the “@local_archive.json” strips off the @, does user expansion on the rest (see https://docs.python.org/3/library/os.path.html#os.path.expanduser) and opens whatever path comes out of that.  The text in the error messages says it was correctly interpreted as “local_archive.json” and, while I hate to ask such an obvious question, I need to.  Does that file actually exist?


I am able to setup throughput tasks with this command (I can see traffic on our monitoring of the upstream ports) … However, this task doesn’t show on the /toolkit/ page for the node or in a maddash throughput mesh.

 

I’ll have to check to be sure, but I think the only tasks that show up in the toolkit GUI are those that were set up there.  Ad hoc tests from the CLI don’t.

 

There is a handy “pscheduler monitor” command that will give you a real-time, top(1)-like display of what pScheduler is doing.

 

I feel that I’ve got something wrong in my pscheduler commands and that’s why the data isn’t being archived.  Does anyone have an example of a pscheduler CLI command that archives locally that they could share, please?

 

A better thing would be to run the task giving you trouble again, grab the run URL the CLI shows and hand it to “pscheduler result --archivings RUN-URL”.  That will dump out diagnostics for where each archiving went that include success or failure and any diagnostic information the archiver provided.  Your archive spec might be valid and the problem is being caused by something else.

 

--Mark

 


Archive powered by MHonArc 2.6.24.

Top of Page