perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

The “no route to host” looks like a routing issue. Do you have multiple interfaces? is the test getting run using a different source interface than the default route you used for ping? Does “owping” to the remote side work?

Thanks,

Andy

On April 19, 2017 at 11:55:54 AM, Andreas Demetriou () wrote:

Hi,

 

I’m now getting these error messages from syslog, both hosts can ping each other but cannot do open an owamp session.

 

I’m struggling to find the cause of this.

Are you able to help?

 

 

Thanks,

Andreas Demetriou| Placement Network Engineer

 

Gigaclear plc, Windrush Court, Abingdon, Oxfordshire, OX14 1SY

M: 07976649731 T: 01865591142 W: www.gigaclear.com

Gigaclear plc is registered in England and Wales with company number 07476617

 

From: Andreas Demetriou
Sent: 12 April 2017 16:44
To: 'Andrew Lake' <>;
Subject: RE: [perfsonar-user] RE: Perfsonar 4 adding to Mesh

 

Hi Andy,

 

 

Here is the “owping -S 172.16.0.12 172.16.0.11” it looks like no packets where sent, running owping on host 172.16.0.11 which is perfsonar 4.0 does not complete.

 

Here is the pscheduler task:

 

 

 

 

This is a fresh install using “wget http://downloads.perfsonar.net/debian/perfsonar-jessie-4.0.list”

With perfsonar testpoint installed.

This is an ARM based Linux Debian jessie 8.3 64bit.

 

 

Thanks,

 

 

Andreas Demetriou| Placement Network Engineer

 

Gigaclear plc, Windrush Court, Abingdon, Oxfordshire, OX14 1SY

M: 07976649731 T: 01865591142 W: www.gigaclear.com

Gigaclear plc is registered in England and Wales with company number 07476617

 

From: Andrew Lake []
Sent: 12 April 2017 15:59
To: Andreas Demetriou <>;
Subject: Re: [perfsonar-user] RE: Perfsonar 4 adding to Mesh

 

Hi,

 

Are you able to run “owping -S 172.16.0.12 172.16.0.11”? How about “pscheduler task rtt —dest 172.16.0.11” instead of to localhost? Errors are a bit all over the place so hard to tell exactly what is going on. How did you install your host (ISO, upgrade from 3.5, RPM/debian packages etc)? What OS are you running?

 

Thanks,

Andy

 

On April 11, 2017 at 12:49:46 PM, Andreas Demetriou () wrote:

Just to add another error from the regulartesting.log from the node on perfsonar 3.5

 

Thanks,

 

Andreas Demetriou| Placement Network Engineer

 

Gigaclear plc, Windrush Court, Abingdon, Oxfordshire, OX14 1SY

M: 07976649731 T: 01865591142 W: www.gigaclear.com

Gigaclear plc is registered in England and Wales with company number 07476617

 

From: Andreas Demetriou
Sent: 11 April 2017 14:13
To: '' <>
Subject: RE: Perfsonar 4 adding to Mesh

 

Hi,

 

Just to add to the below.

 

If a node is running on Perfsonar 4.0 and testing to a node running Perfsonar 3.5 will this work as normal or do both need to be on the same version?

 

 

Is there some configuration that I’m missing?

 

The meshconfig-agent.conf has been modified to pull the central config file and then restart the perfsonar-meshconfig-agent service and this updated the meshconfig-agent-tasks.conf with the correct test parameters.

Does anything have to be done with pscheduler config files?

 

Regards,

 

Andreas Demetriou| Placement Network Engineer

 

Gigaclear plc, Windrush Court, Abingdon, Oxfordshire, OX14 1SY

M: 07976649731 T: 01865591142 W: www.gigaclear.com

Gigaclear plc is registered in England and Wales with company number 07476617

 

From: Andreas Demetriou
Sent: 10 April 2017 16:48
To: '' <>
Subject: Perfsonar 4 adding to Mesh

 

Hi,

 

I’m trying to run two nodes, one is running perfsonar 4.0 the other 3.5.

But it looks the node on 4.0 is giving out errors when trying to add to mesh.

 

 

Here are the logs.

 

From the meshconfig-agent log I’m getting:

 

This is the pschedular.log

 

Are you able to help?

 

 

Thanks

 

 

Andreas Demetriou| Placement Network Engineer

 

Gigaclear plc, Windrush Court, Abingdon, Oxfordshire, OX14 1SY

M: 07976649731 T: 01865591142 W: www.gigaclear.com

Gigaclear plc is registered in England and Wales with company number 07476617