perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Michael,

Actually, I see what is going on, you need to run bwctl-server on the same host as where you are running bwping (i.e. it needs to run on 18.12.1.171). My guess is it got turned-off on the 10th and that’s when everything started failing.  I can recreate your error message exactly by turning off bwctl-server on my local host and trying to run bwping with -E on that same host. 

The bwctl clients (bwctl, bwtraceroute, bwping) works by first trying to talk to talk to a local bwctl server. I don’t recall all the details on BWCTL’s inner-workings in this area, but it needs a BWCTL server on at least one side of the test. In the case where you are not using -E, it can fallback to the one on the remote side. When you add -E to the mix the local side is your only option, so it dies without one. 

Thanks,

Andy

On August 18, 2016 at 3:30:44 PM, Michael Tiernan () wrote:

On 8/18/16 12:25 PM, Andrew Lake wrote:

Not sure what would cause this [...]

It looks like its complaining about being able to connect to 18.12.1.171 which I assume is what p1p1 is assigned.

I've not been able to sort this out and it's very disappointing.

Yes, p1p1 is assigned the 18.12.1.171 (perfsonar01.cmsaf.mit.edu) address and this had been working fine and seemed to fail all at once.

I've gone through everything.

Does anyone know what is happening when this error occurs?
I mean, who (program, application) is generating the error?
(Or what it is trying to tell us at this point?)