perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

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