perfSONAR User Q&A and Other Discussion

[Michael Johnson <>]

Hi Tao,

On Fri, Mar 16, 2018 at 06:01:00PM +0000, Tao Zhang wrote:
> Hi team,
> I have been struggling with a weird OWPING problem related to two perfSONAR 
> nodes:
> http://lat-pe.upei.ca/toolkit/ (UPEI)  and  
> http://lat-vctr3pfs1.canarie.ca/toolkit/ (Victoria)

> The weird thing is that both nodes are working well with other nodes. The 
> problem only happens in one direction when doing the OWPING test from UPEI 
> node.
>
> I did some curl testing from the UPEI node, apparently, it cannot access the 
> archive of Victoria node. But it doesn’t have any problem accessing other 
> nodes’ archives.

> owping: FILE=protocol.c, LINE=1270, _OWPReadTestRequest: Unable to read from 
> socket.
> owping: FILE=owping.c, LINE=1838, Unable to fetch data for 
> sid(cdbd209ede567ff0087b7aca7ccba298)

I'm not sure what those owping errors mean. You could try restarting the 
owamp server or checking the owamp-server logs:

/var/log/perfsonar/owamp_bwctl.log

> curl -v http://lat-vctr3pfs1.canarie.ca/esmond/perfsonar/archive/
> * About to connect() to lat-vctr3pfs1.canarie.ca port 80 (#0)
> *   Trying 205.189.32.158...
> * Connected to lat-vctr3pfs1.canarie.ca (205.189.32.158) port 80 (#0)
> > GET /esmond/perfsonar/archive/ HTTP/1.1
> > User-Agent: curl/7.29.0
> > Host: lat-vctr3pfs1.canarie.ca
> > Accept: */*
> * Recv failure: Connection reset by peer
> * Closing connection 0
> curl: (56) Recv failure: Connection reset by peer
>
> Any ideas?

I  am able to run the same curl command:
curl -v http://lat-vctr3pfs1.canarie.ca/esmond/perfsonar/archive/

on a couple of my nodes and reach the archive, so I think that the Victoria 
archive is wide open (unless it's somehow open to my organization, but not 
yours).

Could there be something blocking you from reaching it (firewall, router ACL, 
etc)? Either that, or some other local network config issue -- routes, DNS, 
...?

You could try running curl with this flag to enable debug logging:
--trace-ascii debug.log

And then see if the log file gives you more information.

It looks like both hosts are set to MTU 9000, but I wonder if the path 
between them is all 9000-capable.

Let me know if that gets you anywhere.

Thanks,
Michael

Attachment: smime.p7s
Description: S/MIME cryptographic signature