perfSONAR User Q&A and Other Discussion

[Izzi <>]

Hello, thanks for checking for me. I tried running pscheduler from CLI:

[perftester@dynamic8 ~]# pscheduler task rtt --dest 192.101.107.152
Submitting task...
Task URL:
https://dynamic8.nas.nasa.gov/pscheduler/tasks/d33ac98c-e7ae-428e-bd6a-ea5ebbb2f80a
Running with tool 'ping'
Fetching first run...

Next scheduled run:
https://dynamic8.nas.nasa.gov/pscheduler/tasks/d33ac98c-e7ae-428e-bd6a-ea5ebbb2f80a/runs/416e8777-5369-488a-a91b-fe6ebdfc0a98
Starts 2018-01-24T04:48:38Z (~7 seconds)
Ends   2018-01-24T04:48:49Z (~10 seconds)
Waiting for result...
Run did not complete: Missed

Checking /var/log/pscheduler/pscheduler.log gives this output:

Jan 23 20:04:31 dynamic8 journal: runner ERROR    3635: Failed to fetch run info: could not receive data from server: Bad file descriptor
Jan 23 20:09:00 dynamic8 journal: runner ERROR    3636: Failed to fetch run info: could not receive data from server: Bad file descriptor

What do you think the problem is, it doesn't look like it is FW restrictions

thanks

Eze

On Mon, Jan 22, 2018 at 1:24 AM, Szymon Trocha <> wrote:

W dniu 19.01.2018 o 22:44, pisze:

I am new to perfsonar and we got a request to install it on our end.
I followed the installation guide from perfsonar,net and installed it with the
following services running:
bwctl
esmond
lsregistration
meshconfig-agent
owamp pscheduler

I randomly selected a node from the global directory and configured a BW
troughput between us to run every hour.
its been a few days now but I don't see any results.
What am I doing wrong? I pinged the remote node and pings/traceroutes are
successful so I am reachable.
Anyone know what I'm missing?

my node is dynamic8.nas.nasa.gov

Hi ,

Did you maybe try to run some pscheduler tests from CLI towards these remote hosts?

This may be a firewall issue (if you pick up some host randomly from service directory there is no guarantee it's publicly available).

I also tried to run some tests towards your side but not all of them succeed so again this may be fw issue:

[psudouser@cowania2 ~]$ pscheduler task rtt --dest 198.9.7.8
Submitting task...
Task URL:
https://cowania2.man.poznan.pl/pscheduler/tasks/24e64909-bf9f-45ac-9f90-354f6c473ea6
Running with tool 'ping'
Fetching first run...

Next scheduled run:
https://cowania2.man.poznan.pl/pscheduler/tasks/24e64909-bf9f-45ac-9f90-354f6c473ea6/runs/33c8a493-585e-436d-b424-69c02a7a27a8
Starts 2018-01-22T09:16:03Z (~7 seconds)
Ends   2018-01-22T09:16:14Z (~10 seconds)
Waiting for result...

1       dynamic8.nas.nasa.gov (198.9.7.8)  64 Bytes  TTL 47  RTT 175.0000 ms
2       dynamic8.nas.nasa.gov (198.9.7.8)  64 Bytes  TTL 47  RTT 175.0000 ms
3       dynamic8.nas.nasa.gov (198.9.7.8)  64 Bytes  TTL 47  RTT 175.0000 ms
4       dynamic8.nas.nasa.gov (198.9.7.8)  64 Bytes  TTL 47  RTT 175.0000 ms
5       dynamic8.nas.nasa.gov (198.9.7.8)  64 Bytes  TTL 47  RTT 175.0000 ms

0% Packet Loss  RTT Min/Mean/Max/StdDev = 175.465000/175.556000/175.645000/0.379000 ms

No further runs scheduled.

[psudouser@cowania2 ~]$ pscheduler task throughput --dest 198.9.7.8
Submitting task...
Unable to determine the lead participant: Can't find pScheduler or BWCTL on 198.9.7.8
[psudouser@cowania2 ~]$

Regards,

--
Szymon Trocha

Poznań Supercomputing & Networking Center
Tel. +48 618582022 ::: http://noc.pcss.pl