Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Problem determining which pscheduler to submit test to for deletion, skipping test throughput/iperf3

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Problem determining which pscheduler to submit test to for deletion, skipping test throughput/iperf3


Chronological Thread 
  • From: Andrew Lake <>
  • To: Danny <>,
  • Subject: Re: [perfsonar-user] Problem determining which pscheduler to submit test to for deletion, skipping test throughput/iperf3
  • Date: Tue, 27 Mar 2018 06:02:17 -0700
  • Ironport-phdr: 9a23:FQyYmBQ2wfRYle7CgMQlZH3gANpsv+yvbD5Q0YIujvd0So/mwa69ZBKN2/xhgRfzUJnB7Loc0qyK6/umATRIyK3CmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+KPjrFY7OlcS30P2594HObwlSizexfb1/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbDVwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4qF2QxHqlSgHLSY0/mHVhcx+i6xUrxyvqR9izYDKfI6YL+Bxcr/HcN4AX2dNQsRcWipcCY28dYsPCO8BMP5Eoon7ulQOtwWxBAexD+3p0DBIhWH51rA93us7FwHJwQwhEskQv3TPttn1MrkdUfyswaTO0D7NbOtW1C/g5ITWcR0tu/+BUah/fMbM00UiFR7Jgk2SpIHqJT+Zy/oBvmiB4+djS+6jkXMrpgVzrzWp28wikJPGhpgPxVDB7Sh5wJg6Jdm/SENjb96rDpRduzueN4RtRsMuWW5ouCEkyrEeuJ67ejYFyIg/yhLCdfCKcJKE7xz5WOuePDt0nnBodK+nixa360egy+n8Vseu0FZNqypIisPDtnYQ2B3T8cWIVOB98l2n2TmRywDf8vtELlwslarHN54hxaY9loINvkTZEC/2g0L2jKmMeUU+4+So9v/nbav8ppKHM490ixr+Mrg1msChG+g4Mw4OX3SF9uSm0r3s41H5TKtQgvIoj6bZrcOSGcNOiqe/BR4dhoou9RqyCWr7+NsdlHgDallCfUTDx5DkIV/VJ/bxF7KimFm2uDZt2/3cOLD9WNPAImWQvq3meONU7UJGxRV76dlc6toAA7cNMdr+QQn3ucCOXUxxCBC93+uyUIY17YgZQ2/aWqI=
That happens when pscheduler can’t connect to port 443 (the standard https port on which pscheduler runs) or port 4823 (the BWCTL port). Make sure a host firewall or ACL is not blocking 443 if you have pscheduler on the other end. You can also try running “pscheduler troubleshoot” on the host giving problems to make sure the local pscheduler is OK and also can run “pscheduler troubleshoot —host X.X.X.X” on the problematic machine where X.X.X.X is the remote machine it complains about in the message below to see if it can reach pscheduler on the far end.

Thanks,
Andy



On March 27, 2018 at 6:30:29 AM, Danny () wrote:

I am having following error on one of the machine running perfSONAR. The
results for bandwidth, latency loss are not coming for any of the connected
nodes. The destination machine is however running and giving results.

(4232) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which
pscheduler to submit test to for deletion, skipping test
throughput/iperf3(X.X.X.X->X.X>X.X): 400 BAD REQUEST: Can't find pScheduler or
BWCTL on X.X.X.X

What is the possible solution to this error? Can you please help.
Thanks,

Archive powered by MHonArc 2.6.19.

Top of Page