perfSONAR User Q&A and Other Discussion

["Jennewein, Douglas M" <>]

Understood - Internet2-staging has been removed.

Trying to add a different (3.5) measurement host to the MA is still not working.

Our JSON config includes a measurement-archive section for our site: https://perfsonar-management.usd.edu/usd-mesh.json 

I created IP address users in esmond, specifying the IP address of each measurement host (e.g. python esmond/manage.py add_user_ip_address smallnode_user1 192.236.58.240), and ran generate_configutation on each measurement host.

The regulartesting.conf file on the measurement host contains this <measurement_archive> entry:

<measurement_archive>

    database   http://perfsonar-management.usd.edu/esmond/perfsonar/archive

    <summary>

        event_type   throughput

        summary_window   86400

        summary_type   average

    </summary>

    type   esmond/throughput

    added_by_mesh   1

</measurement_archive>

However, it appears that no measurements are being archived: http://perfsonar-management.usd.edu/esmond/perfsonar/archive/

Is additional configuration necessary, or are the steps above incomplete?

-- 
Doug

On September 15, 2016 at 3:33:32 PM, Andrew Lake () wrote:

Then you’re pointing at the staging repo, which you shouldn’t be if you don’t want this type of thing to happen. generate_configuration is gone by design in 4.0 and is replaced by the perfsonar-meshconfig-agent daemon, we will be providing more details next week when we officially release 4.0. If you don’t want this type of thing to happen in the future I would recommend reinstalling the host. A default install will not install the package Internet2-repo-staging, it will just install Internet2-repo which is our production repository.

Thanks,

Andy 

On September 15, 2016 at 4:21:53 PM, Jennewein, Douglas M () wrote:

No, it is CentOS 6.8.

-- 
Doug 

On September 15, 2016 at 3:12:54 PM, Andrew Lake () wrote:

Is this a debian host? If so, see Antoine’s previous note to the list this afternoon on how to downgrade. 

On September 15, 2016 at 4:01:20 PM, Jennewein, Douglas M () wrote:

The central mesh config is located here: https://perfsonar-management.usd.edu/usd-mesh.json

The configured tests seem to work normally.

I am attempting to specify (in the above central mesh config) a measurement archive for one of the hosts, authenticated by IP address.

To the best of my knowledge, no data is being archived: http://perfsonar-management.usd.edu/esmond/perfsonar/archive/ contains no data. And on the measurement host, /etc/perfsonar/regulartesting.conf contains only <measurement_archive> entries for localhost.

There is an additional problem: my measurement host just auto-updated to PS 4.0 and now /usr/lib/perfsonar/bin/generate_configuration no longer exists!

[root@vlan35-35-36 ~]# /usr/lib/perfsonar/bin/generate_configuration

-bash: /usr/lib/perfsonar/bin/generate_configuration: No such file or directory

[root@vlan35-35-36 ~]# 

-- 
Doug

On September 12, 2016 at 2:33:47 AM, Szymon Trocha () wrote:

Hi Doug,

W dniu 10.09.2016 o 00:06, Jennewein, Douglas M pisze:

I am trying to add a central MA to a <host> entry in an existing central mesh config file.

Just to understand - are you trying to build a central configuration file to be published and consumed by MPs (as json file) or are you trying to configure a regular testing file on a single MP by hand?

The docs here (http://docs.perfsonar.net/multi_ma_install.html) show measurement_archive sections containing type, username, database, password, where type is something like esmond/latency, followed by a bunch of <summary> sections.

These are entries for local storage (in addition to central MA) - see database URL. There are autheticated by esmond key i.e. password.
According to the above page data storage in a central MA are auithenticated by IP of MPs or username/key. What is your choice?

ESnet examples like https://github.com/esnet/esnet-perfsonar-mesh/blob/master/conf/osc-mesh.conf show only type, read_url, and write_url, and type is something like perfsonarbuoy/owmp, with no <summary> sections.

This is a central configuration file published somewhere in a central server, converted to json file. This file is then consumed by MPs participating in a mesh and appropriate entries are then added to hosts's regulartesting.conf.

My measurement host’s /etc/perfsonar/regulartesting.conf has a measurement_archive section like this:

<measurement_archive>

    database   http://localhost/esmond/perfsonar/archive/

    password   xxxxxxxxxx

    <summary>

So this is local storage.
In case you want to store data to remote central MA you would need to add another entries pointing to remote host. But again this is usually done automatically when publishing a central mesh config file.

…

When I try to add a <measurement_archive> section to my central config file, I get errors from build_json when including the password or database attributes:

2016/09/09 16:44:07 (13648) ERROR> Utils.pm:80 perfSONAR_PS::MeshConfig::Utils::load_mesh - Invalid mesh configuration: Unknown attribute: password at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/MeshConfig/Config/Base.pm line 172.

Resulting mesh is invalid: Invalid mesh configuration: Unknown attribute: password at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/MeshConfig/Config/Base.pm line 172.

When I configure the <measurement_archive> section with type, read_url, and write_url, build_json does not complain, but the measurement_archive is not added to my measurement host’s /etc/perfsonar/regulartesting.conf after running /usr/lib/perfsonar/bin/generate_configuration.

Look at your /etc/perfsonar/meshconfig-agent.conf file. Do you have configure_archives set to 1? If not change it and then try again to generate.

What is the config file syntax for adding a measurement_archive to a host defined in a mesh?

 

It would be much easier when you post a central mesh config file so that we can have a look.

Regards,

--

Szymon Trocha

Poznań Supercomputing & Networking Center
Tel. +48 618582022 ::: http://noc.pcss.pl