perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

The "Can't find pScheduler or BWCTL” means you have a throughput test where the remote end is having trouble reach port 443 for pScheduler or port 4823 for BWCTL on either the source or dest host. It could also be a reverse ping or traceroute test you have configured. It's usually caused because 1) the remote node is not a perfSONAR host or 2) a firewall is blocking the ports listed above. You might want to try running some of the tests you have configured by hand to see if you get better errors like “pscheduler task throughput —source SOURCE —dest DEST” where SOURCE and DEST are the endpoints of the test.

The "400 URL must be absolute” I’m less sure about, it might be that you have a typo in one of the URLs in /etc/perfsonar/meshconfig-agent.conf? In particular be sure that if you are pointing at a local file its not /path/to/file and is instead file:///path/to/file.

Hope that helps,

Andy

On February 26, 2018 at 5:40:53 AM, Danny () wrote:

URL must be absolute