perfSONAR User Q&A and Other Discussion

[matt fetting <>]

Thanks David. The pscheduler ping command passed with an "is alive" result. However, the troubleshoot command did produce a failure (see below):

[root@host2]# pscheduler troubleshoot

Performing basic troubleshooting of localhost.

Checking for pScheduler on localhost... OK.

Idle test on localhost.... 9 seconds...404 Resource Not found.

 Failed.

  Did not get a result: Resource Not found.

I rebooted both nodes for grins, and now that troubleshoot command returns a "pScheduler appears to be functioning normally." Not sure if the services were in some broken state based on my past troubleshooting (service restarts, etc). I do not see the 400 errors in my logs anymore, but still don't have any data. Will give it a little time and perhaps start a new thread related to the lack of data if that issue persists. 

mdf

On Thu, Jan 25, 2018 at 11:58 AM, David Szydloski <> wrote:

Matt,

Depending on what information you are trying to get, running toolkit on Node A would likely be sufficient as it should be able to give you one-way latency and, say, TCP throughput both ways as long as minimal tools like perfsonar-testpoint are installed on Node B. (In my experience, this setup is the easiest to start with to familiar yourself with perfSONAR)

1)Have you already tried to see if "sudo pscheduler ping localhost [or a host IP]" and "sudo pscheduler troubleshoot"? Either of those should point you to issues with pscheduler setup. Node A should be able to see pScheduler on itself and Node B.

2) " sudo pscheduler schedule +PT5H" will show you what tests are scheduled based on your test configuration. This is was really helpful to me in troubleshooting problems I had with throughput tests since a pScheduler issue on the remote end was keeping the tests from being scheduled at all.

3) Running "sudo pscheduler debug [whatever service is causing an issue]" will give you more verbose logging in the /var/log/pscheduler/pscheduler.log  

4) trying to run a test manually in debug mode via "sudo pscheduler task --debug [whatever task you want to run]" should give you some more good output to dig through.

Hope that helps,

D

On Thu, Jan 25, 2018 at 10:37 AM, matt fetting <> wrote:

I have 3 centos7 toolkit hosts deployed from the netinstall iso, two of which are intended to run tests and one of which is intended to be a measurement archive. Starting very simple with just owamp, traceroute, and iperf tests between these two testing hosts. My understanding about perfSonar is partial, so please excuse any ignorance here. 

My MaDDash dashboard has some errors around not being able to find data for some tests, and it's been up/running for over 24 hours now without changes. The scheduled tests are frequent and should be showing data by now. pScheduler is running on both hosts, and there is no firewall in between them. I can confirm that with certainty because I am the operator. Since these are internal, I've actually stopped firewalld to make sure there isn't any unintended filtering there. selinux is disabled. There are variations of this error message in the meshconfig-agent.log: 

2018/01/24 10:18:12 (3859) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test throughput(host1->host2): 400 BAD REQUEST: Can't find pScheduler or BWCTL on host2

Can someone help get me started on where to look for resolving this? Past research into the list/google didn't prove fruitful. 

Thanks

mdf

--

David Szydloski

Core Deployment Engineer

VidScale, Inc.