perfSONAR User Q&A and Other Discussion

[Joshua Baker-LePain <>]

On Mon, 15 May 2017 at 11:54pm, Valentin Vidic wrote

> On Fri, May 12, 2017 at 12:08:01PM -0700, Joshua Baker-LePain wrote:
> > But everytime I run 'service perfsonar-meshconfig-agent start' this is what
> > I get in meshconfig-agent.log:
> >
> > 2017/05/12 11:58:17 (21950) ERROR> Agent.pm:302 
> > perfSONAR_PS::MeshConfig::Agent::__configure_host - Problem with mesh 
> > configuration: 500 Can't connect to ps-dashboard.cenic.net:443 (): 500 Can't 
> > connect to ps-dashboard.cenic.net:443 ()
> >
> > I can manually pull down
> > <https://ps-dashboard.cenic.net/CENIC-Dashboard.json> via wget or a perl
> > one-liner.  I've even tried shutting down eth1 just to make sure there's no
> > weird routing going on, and it made no difference.  I verified via wireshark
> > that there is absolutely no traffic between our host and
> > ps-dashboard.cenic.net when I start the meshconfig-agent -- it's not even
> > trying to make contact.
>
> Quite strange, you can try a strace and check for communication with 
> 137.164.85.52:

Thanks for the respone.  And yes, yes it is.

> # strace -e trace=network -ff 
> /usr/lib/perfsonar/bin/perfsonar_meshconfig_agent 
> --config=/etc/perfsonar/meshconfig-agent.conf 
> --pidfile=/var/run/perfsonar-meshconfig-agent.pid 
> --logger=/etc/perfsonar/meshconfig-agent-logger.conf --user=perfsonar 
> --group=perfsonar
> ...
> 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("137.164.85.52")}, 16) = 0
> getpeername(6, {sa_family=AF_INET, sin_port=htons(443), 
> sin_addr=inet_addr("137.164.85.52")}, [16]) = 0

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

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.

--
Joshua Baker-LePain
QB3 Shared Cluster Sysadmin
UCSF