perfSONAR User Q&A and Other Discussion

[Valentin Vidic <>]

On Tue, May 16, 2017 at 03:30:12PM -0700, Joshua Baker-LePain wrote:
> It's definitely not trying to talk to 137.164.85.52.  The only port 443
> connections are to localhost:
> 
> socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 6
> bind(6, {sa_family=AF_INET, sin_port=htons(0), 
> sin_addr=inet_addr("0.0.0.0")}, 16) = 0
> connect(6, {sa_family=AF_INET, sin_port=htons(443), 
> sin_addr=inet_addr("127.0.0.1")}, 16) = 0
> getpeername(6, {sa_family=AF_INET, sin_port=htons(443), 
> sin_addr=inet_addr("127.0.0.1")}, [16]) = 0

Yes, these should be local connections to pscheduler API.

> Prior to this, I see a lot of errors that look like this:
> 
> socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 6
> bind(6, {sa_family=AF_INET, sin_port=htons(0), 
> sin_addr=inet_addr("0.0.0.0")}, 16) = 0
> getpeername(6, 0x4e98c20, [256])        = -1 ENOTCONN (Transport endpoint 
> is not connected)
> sendto(6, 
> "\7\361\1\0\0\1\0\0\0\0\0\0\0011\0010\0010\003127\7in-addr\4a"..., 40, 0, 
> {sa_family=AF_INET, sin_port=htons(53), 
> sin_addr=inet_addr("169.230.239.25")}, 16) = 40
> recvfrom(6, 
> "\7\361\205\200\0\1\0\1\0\1\0\2\0011\0010\0010\003127\7in-addr\4a"..., 512, 
> 0, {sa_family=AF_INET, sin_port=htons(53), 
> sin_addr=inet_addr("169.230.239.25")}, [16]) = 121
> 
> where 169.230.239.25 is the nameserver configured in /etc/resolv.conf (it's
> actually a proxy).  Just for grins, at this point I set the mesh
> configuration_url to https://137.164.85.52/CENIC-Dashboard.json to try to
> get around any DNS issues (which don't exist at the command line), and the
> results are the same.

Try to find a DNS request resolving ps-dashboard.cenic.net in strace
and a TCP connection request after that.

-- 
Valentin Vidic
Computer Systems Engineer - Expert
Department of Computer Infrastructure and Services
Croatian Academic and Research Network - CARNet
Josipa Marohnica 5, HR-10000 Zagreb, Croatia
tel: +385 1 6661 714, fax. +385 1 6661 635
gsm: +385 91 2480 919
www.CARNet.hr