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: "'Andrew Lake'" <>
  • Cc: "'perfsonar-user'" <>
  • Subject: RE: [perfsonar-user] perfSONAR 3.4rc2 Mesh Errors
  • Date: Wed, 6 Aug 2014 14:29:17 -0700 (PDT)

Hi Andy,

Thank you very much. Yes you are correct that sites-CANARIE.json
was out of date (I am actually using ps-mesh/sites-CANARIE.json
in production servers). After I fixed it, the meshconfig loads
correctly.

I am still confused about the change of read_url format. The page
http://ndt-sfu.westgrid.ca/esmond/perfsonar/archive/?format=json
gives me a very long line and there is no "read_url" in the line.
All my json files are converted from .conf files using build_json
command. So what kind of changes I need to do for .conf files?

Thanks again!

Lixin.


> -----Original Message-----
> From: Andrew Lake
> [mailto:]
> Sent: August-04-14 6:53 AM
> To: Lixin Liu
> Cc: 'Shawn McKee'; 'perfsonar-user'
> Subject: Re: [perfsonar-user] perfSONAR 3.4rc2 Mesh Errors
>
> Hi Lixin,
>
> The host block you sent looks fine. Is there a second block anywhere? or
> have you run build_json recently? Looking at https://ps-
> dashboard.computecanada.ca/mesh-config/sites-CANARIE.json I see two
> separate
> hosts named sask1pfs2.canarie.ca. I am wondering if that file is
> out-of-sync
> with your .conf file, build_json just needs to be run and the output
> uploaded.
>
> Also, as a separate issue, you will need to update all the read_urls for
> your 3.4 host in the central meshconfig file. This is not causing the
> error
> you reported, but will result in orange in the dashboard if not changed.
> It
> looks like ndt-sfu.westgrid.ca is the updated host so you will need to
> make
> the read_url for each of its measurement_archive blocks http://ndt-
> sfu.westgrid.ca/esmond/perfsonar/archive/.
>
> Thanks,
> Andy
>
> > <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>
> On Aug 1, 2014, at 4:54 PM, Lixin Liu
> <>
> wrote:
>
> > 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