Skip to Content.
Sympa Menu

perfsonar-user - RE: [perfsonar-user] perfSONAR 3.4rc2 Mesh Errors

Subject: perfSONAR User Q&A and Other Discussion

List archive

RE: [perfsonar-user] perfSONAR 3.4rc2 Mesh Errors


Chronological Thread 
  • From: "Lixin Liu" <>
  • To: "'Shawn McKee'" <>
  • Cc: "'perfsonar-user'" <>
  • Subject: RE: [perfsonar-user] perfSONAR 3.4rc2 Mesh Errors
  • Date: Fri, 1 Aug 2014 13:54:45 -0700 (PDT)

Hi Shawn,

 

I am not sure what this really means. The example given in both 3.4rc2

and 3.3.2 are the same.

 

I wonder this is because host sask1pfs2.canarie.ca is set to do both

bandwidth and latency tests:

 

  <host>

    description    CANARIE Saskatoon

    address        sask1pfs2.canarie.ca

 

    <measurement_archive>

      type        traceroute

      read_url    http://sask1pfs2.canarie.ca:8086/perfSONAR_PS/services/tracerouteMA

      write_url   http://sask1pfs2.canarie.ca:8086/perfSONAR_PS/services/tracerouteCollector

    </measurement_archive>

 

    <measurement_archive>

      type        perfsonarbuoy/bwctl

     read_url    http://sask1pfs2.canarie.ca:8085/perfSONAR_PS/services/pSB

      write_url   sask1pfs2.canarie.ca:8570

    </measurement_archive>

 

    <measurement_archive>

      type        perfsonarbuoy/owamp

      read_url    http://sask1pfs2.canarie.ca:8085/perfSONAR_PS/services/pSB

      write_url   sask1pfs2.canarie.ca:8569

    </measurement_archive>

 

    <measurement_archive>

      type       pinger

      read_url   http://sask1pfs2.canarie.ca:8075/perfSONAR_PS/services/pinger/ma

      # No 'write_url' for PingER measurement archives

    </measurement_archive>

  </host>

 

so same read_url appears twice (perfsonarbuoy/bwctl and perfsonarbuoy/owamp).

We did not have any problem with 3.3.2.

 

Thanks,

 

Lixin.

 

 

 

From: Shawn McKee [mailto:]
Sent: August-01-14 12:38 PM
To: Lixin Liu
Cc: perfsonar-user
Subject: Re: [perfsonar-user] perfSONAR 3.4rc2 Mesh Errors

 

Hi  Lixin,

 

If you  haven't  done it yet, you must  update  the  MA  urls  used  in  your  mesh  config to  use  the  new Esmond  URL.    

 

All  the  read  and  write  MA URLs for this  host  in  the  mesh config should  be  updated  to  look  like:

 

http://ndt-sfu.westgrid.ca/esmond/perfsonar/archive/

 

 

Shawn

 

On Fri, Aug 1, 2014 at 3:24 PM, Lixin Liu <> wrote:

Hi,

I upgraded a perfSONAR test VM from 3.3.2 to 3.4rc2 and start
getting Mesh Errors from the daily cron job.

I have no problem with 3.3.2. This host (ndt-sfu.westgrid.ca)
is a VM for installation test only.

Here is the section for mesh-config:

<mesh>
    configuration_url
https://ps-dashboard.computecanada.ca/mesh-config/ComputeCanada-tests.json
    validate_certificate        0
</mesh>

<mesh>
    configuration_url
https://ps-dashboard.computecanada.ca/mesh-config/westgrid-tests.json
    validate_certificate        0
</mesh>

Thanks,

Lixin.

> -----Original Message-----
> From:
> [mailto:]
> Sent: August-01-14 2:00 AM
> To:
> Subject: Mesh Errors
>
> Mesh Error:
>   Mesh: Compute Canada sites
>   Host:
>   Error: Invalid mesh configuration: Multiple hosts match
> sask1pfs2.canarie.ca at
> /opt/perfsonar_ps/mesh_config/bin/../lib/perfSONAR_PS/MeshConfig/Config/Mesh
> .pm line 56.
>
>
> Mesh Error:
>   Mesh: Compute Canada sites
>   Host:
>   Error: Invalid mesh configuration: Multiple hosts match
> sask1pfs2.canarie.ca at
> /opt/perfsonar_ps/mesh_config/bin/../lib/perfSONAR_PS/MeshConfig/Config/Mesh
> .pm line 56.
>
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to .

 




Archive powered by MHonArc 2.6.16.

Top of Page