perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Mark Maciolek writes:

 

WARN pid=1801 prog=perfSONAR_PS::PSConfig::PScheduler::Agent::_run_end line=229 guid=A8F6FBCA-7728-11EE-92BF-973741A14FEE msg=Problem adding test throughput(perf-unh.unh.edu->132.177.100.142), continuing with rest of config: INTERNAL SERVER ERROR: Error getting tools from 132.177.100.142: Operation timed out after 10001 milliseconds with 0 out of 0 bytes received

… 

Suggestions on how to troubleshoot this further?

 

Here’s how I’d go about it.  I tried asking perf-unh.unh.edu to run these tests but its limit configuration wouldn’t allow it.  These were done from the Internet2 PoP in Cleveland (responses abbreviated):

 

$ pscheduler task psresponse --dest perf-unh.unh.edu

…

Response Time: PT0.218534S

 

That worked.  Let’s try the other end:

 

$ pscheduler task psresponse --dest 132.177.100.142

…

Response Time: Not Measured

Reason: Operation timed out after 10001 milliseconds with 0 out of 0 bytes received

 

That looks familiar.   Can we reach that system at all?

 

$ pscheduler task rtt --dest 132.177.100.142

…

1    perf-rcc.unh.edu (132.177.100.142)  64 Bytes  TTL 56  RTT  18.3000 ms

2    perf-rcc.unh.edu (132.177.100.142)  64 Bytes  TTL 56  RTT  17.9000 ms

3    perf-rcc.unh.edu (132.177.100.142)  64 Bytes  TTL 56  RTT  18.1000 ms

4    perf-rcc.unh.edu (132.177.100.142)  64 Bytes  TTL 56  RTT  18.1000 ms

5    perf-rcc.unh.edu (132.177.100.142)  64 Bytes  TTL 56  RTT  17.8000 ms

 

0% Packet Loss  RTT Min/Mean/Max/StdDev = 17.826000/18.081000/18.347000/0.204000 ms

 

Sure can.  Can we talk to the web server directly?

 

$ curl -vvv  -k https://132.177.100.142/pscheduler

* About to connect() to 132.177.100.142 port 443 (#0)

*   Trying 132.177.100.142...

* Connected to 132.177.100.142 (132.177.100.142) port 443 (#0)

* Initializing NSS with certpath: sql:/etc/pki/nssdb

…Very long delay…

* NSS error -5961 (PR_CONNECT_RESET_ERROR)

* TCP connection reset by peer

* Closing connection 0

curl: (35) TCP connection reset by peer

 

Yes, but the conversation doesn’t get very far.  But I can reach that system just fine from my home internet connection on AS701:

 

$ curl -k https://132.177.100.142/pscheduler/

"This is the pScheduler API server on 132.177.100.142 (perf-rcc.unh.edu)."

 

This sounds to me like access to 132.177.100.142 is being blocked by firewalls, transparent proxies or other obstructions. 

 

HTH.

 

--Mark