perfSONAR User Q&A and Other Discussion

[Murilo Vetter <>]

Hi list,

I would like to understand how the perfSONAR hosts know when to schedule tasks based on psconfig remote agent.

I am trying to debug a wierd behavior that the host appears on the configuration of PWA and in the following json, but it does not schedule on pscheduler.

[root@monipe-to-perfsonar /]# psconfig remote list
=== pScheduler Agent ===
[
   {
      "url" : "http://monipe-central.rnp.br:8000/pub/config/matriz",
      "configure-archives" : true
   }
]

If I try to troubleshoot the host, it looks it is ok.

[root@monipe-to-perfsonar /]# pscheduler troubleshoot --host monipe-to-atraso.rnp.br
Performing basic troubleshooting of monipe-to-atraso.rnp.br.

monipe-to-atraso.rnp.br:

  Checking path MTU... 65520+
  Checking for pScheduler... OK.
  Checking clock... OK.
  Idle test.... 12 seconds.... Checking archiving... OK.

pScheduler appears to be functioning normally.
[root@monipe-to-perfsonar /]# pscheduler troubleshoot --host monipe-to-banda.rnp.br
Performing basic troubleshooting of monipe-to-banda.rnp.br.

monipe-to-banda.rnp.br:

  Checking path MTU... 65520+
  Checking for pScheduler... OK.
  Checking clock... OK.
  Idle test.... 13 seconds.... Checking archiving... OK.

pScheduler appears to be functioning normally.

It is resolving the server name:

[root@monipe-to-perfsonar /]# hostname -A
monipe-to-atraso.rnp.br monipe-to-banda.rnp.br monipe-to-perfsonar

What am I missing? Is there a way to troubleshoot it in a better way?

Regards,

--

Murilo Vetter
Analista REMEP-FLN/PoP-SC
PoP-SC - Ponto de Presença da RNP em Santa Catarina
REMEP-FLN - Rede Metropolitana de Educação e Pesquisa da Região de Florianópolis
RNP - Rede Nacional de Ensino e Pesquisa
UFSC - Universidade Federal de Santa Catarina
SETIC - Superintendência de Governança Eletrônica e Tecnologia da Informação e Comunicação
Fundações de Apoio FEESC e FEPESE
--/--

www.pop-sc.rnp.br
remep.pop-sc.rnp.br
CHAMADOS:
+55(48)3721-3000
INOC: 11242*100

---

De: "Murilo Vetter" <>
Para: "Mark Feit" <>
Cc: "perfsonar-user" <>
Enviadas: Sexta-feira, 29 de março de 2019 17:43:52
Assunto: Re: [perfsonar-user] Tests are not scheduling on pscheduler

Hi Guys,

It is strange that is is not scheduling.

I am using hostnames to try to schedule. Should it works with hostnames or just IP address?

Some commands below:

[root@monipe-ba-perfsonar tmp]# psconfig remote list
=== pScheduler Agent ===
[
   {
      "url" : "http://monipe-central.rnp.br:8000/pub/config/matriz"
   }
]

[root@monipe-ba-perfsonar tmp]# psconfig pscheduler-tasks
{
   "tasks" : []
}

Any help?

Regards,

--

Murilo Vetter
Analista REMEP-FLN/PoP-SC
PoP-SC - Ponto de Presença da RNP em Santa Catarina
REMEP-FLN - Rede Metropolitana de Educação e Pesquisa da Região de Florianópolis
RNP - Rede Nacional de Ensino e Pesquisa
UFSC - Universidade Federal de Santa Catarina
SETIC - Superintendência de Governança Eletrônica e Tecnologia da Informação e Comunicação
Fundações de Apoio FEESC e FEPESE
--/--

www.pop-sc.rnp.br
remep.pop-sc.rnp.br
CHAMADOS:
+55(48)3721-3000
INOC: 11242*100

---

De: "Mark Feit" <>
Para: "Murilo Vetter" <>, "perfsonar-user" <>
Enviadas: Quinta-feira, 28 de março de 2019 18:45:52
Assunto: Re: [perfsonar-user] Tests are not scheduling on pscheduler

Murilo Vetter writes:

 

I am trying to schedule some tests from the host: monipe-ba-atraso.rnp.br / monipe-ba-banda.rnp.br ( 2 net interfaces in this host, 1 for ping/trace/owamp and 1 for troughput ).

 

I am getting problems since it does not put on schedule.

 

I already check this issues:

- Hostname:

[root@monipe-ba-perfsonar httpd]# hostname -A
monipe-ba-atraso.rnp.br monipe-ba-banda.rnp.br monipe-ba-perfsonar

 

- Troubleshooting:

[root@monipe-ba-perfsonar httpd]# pscheduler troubleshoot monipe-ba-atraso.rnp.br
…

 

If I understand this correctly, you’re trying to troubleshoot from the local host to itself.  That will (and did) work fine for the single-host idle tests.  Once it tries to do something multi-participant (simplestream, throughput), it’s going to fail because the same machine can’t be both ends of a multi-participant test even if they’re different interfaces.  I was able to run tasks to and from that host with no problem, although I did notice that either the system or the network between here and there was a bit sluggish.

 

localhost and monipe-ba-atraso.rnp.br:

  Checking path MTU... 65520+
  Checking timekeeping... OK.
  Simple stream test... Failed.
Unable to post task: Error while tasking monipe-ba-atraso.rnp.br: Unable to post task to monipe-ba-atraso.rnp.br: Internal problem; see system logs.

 

 

Unless there’s some other problem causing that, you should be seeing a message that says “Task already exists.  All participants must be on separate systems.”  Early versions of pScheduler choked like that, but it was corrected before anything went into production.

 

Is there anything of interest in the logs on that system?

 

--Mark

 

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user