Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Difficulties getting mesh configuration

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Difficulties getting mesh configuration


Chronological Thread 
  • From: Valentin Vidic <>
  • To:
  • Subject: Re: [perfsonar-user] Difficulties getting mesh configuration
  • Date: Tue, 16 May 2017 08:54:46 +0200
  • Ironport-phdr: 9a23:Ub5AORfTMx5MrTY6lAEz0sdtlGMj4u6mDksu8pMizoh2WeGdxcS8ZB7h7PlgxGXEQZ/co6odzbGH7Oa5BSdZuMfJmUtBWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnYdFRrlKAV6OPn+FJLMgMSrzeCy/IDYbxlViDanb75/KBe7oR/MusQZjoduN7s9xx/UqXZUZupawn9lK0iOlBjm/Mew+5Bj8yVUu/0/8sNLTLv3caclQ7FGFToqK2866tHluhnFVguP+2ATUn4KnRpSAgjK9w/1U5HsuSbnrOV92S2aPcrrTbAoXDmp8qlmRAP0hCoBKjU09nzchM5tg6JBuB+vqRxxzZDXboGbO/VxYr7SctEUSmRcRctRSzBNDp+gY4cTFecNI+BVpJT9qVsUqhu+ABGhC+z1xT9MmHD227E60+UnEQrb0wMgHs8BsHXIo97oM6odXvq6zK3WwjXFc/NW2DH95JLHfRAgvP6MXK5/fNHPxEQzCw3LlkufqZD/MzOVzOQAqm6W5PduW+Kojm4osQBxoj63y8gwkIbJnIQVxU7Y9SljwIY1P8W0R1Jlbt6iEZtfqzuWN41oTcM+RWxjpSU0yqUetJKlYCQG1IkryhvEZPGGcIWF5xzjVOiULDtmgX9ofbOyiw6s/US81uHwS8y5301LoydGl9TMuH4N2hnO5sSZT/Zw+1qt1DiS2w3V9+pKO1o7lbDBJJ4k2rMwloQcsUDEHiLunUX5lq6WdkE+9ue08evneLPmqYGAN4NuigH+KLwims25AesmLggDR3aX9fig2LH++ED2W7RHg/4zn6nXvpDXINoXq6u8DgJUyooj7gywDzai0NQWh3kHK1dFdQqIgIfzP1HBPvb4Deu+g1SqijtkyPHGMaDgAprRNXXMjK3ufax760FC1Ao/19Bf54hMBrEbPP3zQlPxtMDfDhIhKwy73fznCNtm1oMZX2KAGLWZPLrPsV+T+O0vOfKBZIsUuDbmN/gl/ODigWU4mV8bYammw4EXaHamEfR6PUmVe2TjjcocETRCgg1rVOHwhkaFVzdJImupUrgU5zcnBZigAJuZAI2hne+vxiC+S6NfYm1AFlGKWUnpe4SPE6MyYSafJNNglHo6VLSgQKcK/CuIuRO8y6AxfbmcwTERqZ+2jIs93ObUjxxnrTE=

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:

# 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

--
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



Archive powered by MHonArc 2.6.19.

Top of Page