perfSONAR User Q&A and Other Discussion

[Murilo Vetter <>]

Hi Mark,

As I could understood, long time tests in versions 4.2.* it is now outputing the results.

And in the versions 4.1.4 and 4.1 it is writing the results from client side, but the server side is not report anything.

Version 4.1 and 4.1.4, when trying to run:

pscheduler result --diags https://10.39.2.2/pscheduler/tasks/43b8933b-a910-4ed3-a031-73a315f094f5/runs/9c7a523f-2b40-4aa0-8d6d-ff927ccc0ac7

The server side outputs:

Diagnostics from 10.39.2.6:

    (No diagnostics)

Error from 10.39.2.6:

    iperf3 returned an error: 

    Process took too long to run.

The schedule tests:

[root@470fce348303 /]# pscheduler schedule -PT1H

2019-12-03T10:17:01-05:00 - 2019-12-04T10:07:03-05:00  (Finished)

rtt --count 85800 --dest 10.39.2.6 --source 10.39.2.2 (Run with tool 'ping')

https://localhost/pscheduler/tasks/a4f8ddd9-0517-4ad3-961f-cbeb2d9105df/runs/c1b4228d-c218-4bfc-9280-1fc4d27416fa

2019-12-03T10:17:04-05:00 - 2019-12-04T10:07:11-05:00  (Finished)

throughput --bandwidth 100000000 --duration PT23H50M --source 10.39.2.2 --dest 10.39.2.6 --interval PT1M --buffer-length 1472 --udp (Run with tool 'iperf3')

https://localhost/pscheduler/tasks/43b8933b-a910-4ed3-a031-73a315f094f5/runs/9c7a523f-2b40-4aa0-8d6d-ff927ccc0ac7

Is something that I am missing?

Regards,

--
Murilo Vetter
Analista de Tecnologia da Informação
REMEP-FLN - Rede Metropolitana Comunitária de Educação e Pesquisa da Região de Florianópolis
PoP-SC - Ponto de Presença da RNP em Santa Catarina
RNP - Rede Nacional de Ensino e Pesquisa
+55 (48) 3721-3000
www.pop-sc.rnp.br | www.rnp.br

---

De: "Mark Feit" <>
Para: "Murilo Vetter" <>
Cc: "perfsonar-user" <>, "monipe-des" <>
Enviadas: Segunda-feira, 2 de dezembro de 2019 12:55:12
Assunto: Re: [perfsonar-user] PSCHEDULER BUG: Pscheduler maximum limit amount of time to schedule a task

Murilo Vetter writes:

 

Hi Mark,

 

We already tried to run this on perfsonar docker images:

- Latest (4.2.2)

- v4.2.1

 

Now I am going to try to run on 4.1.4 to see if it is going to have problem.

Do you know if it is a problem on newer version 4.2.*?

 

The code that covers this hasn’t changed since it was first written, so I would expect the behavior to be the same on all versions.  We’re planning a bugfix release in the next few weeks; whatever fix I come up with will likely ship with that.  I’ve been up to my neck in SC for most of the last month and now am up to my neck in TechEx, so your patience is appreciated.

 

--Mark