perfSONAR User Q&A and Other Discussion

[Tristan Sullivan <>]

Hi Mark,

Thanks, that did the trick. If you don't mind, could I just clarify something with you about the WLCG test spec, that's confused me since perfsonar 5 was released? If I look at my perfsonar hosts on the PWA interface, they each have the box ticked "use local Esmond MA". I don't see an option for a local http archive. If I look at the resulting psconfig file, I see e.g. the following under the "hosts" block:

    "ps-latency.hepnetcanada.ca": {

      "archives": [

        "host-archive44"

      ]

    },

This points to

    "host-archive44": {

      "archiver": "esmond",

      "data": {

        "url": "https://ps-latency.hepnetcanada.ca/esmond/perfsonar/archive",

        "measurement-agent": "{% scheduled_by_address %}",

        "schema": 1

      }

    },

Which I suppose is why psconfig was complaining about not recognising esmond. But the only file actually present in /etc/perfsonar/psconfig/archives.d/ is http_logstash.json. Am I right in thinking that elmond is translating the http archive entries to esmond, and that's why this works? So after 5.3 or whenever esmond finally disappears, the WLCG test spec will have to change?

Thanks,

Tristan

---

From: Mark Feit <>
Sent: July 11, 2024 10:11 AM
To: Tristan Sullivan <>; <>
Subject: Re: Unknown archiver plugin 'esmond'

 

Tristan Sullivan writes:

 

pscheduler-api[246132] ERROR    Internal error 2607:f8f0:c11:700b::60 POST https://ps-latency.hepnetcanada.ca/pscheduler/tasks: Unable to validate test spec: Unknown archiver plugin 'esmond'

 

The strange thing is that if I run psconfig validate on the same file but on a different perfsonar machine (same OS and perfsonar version, but installed several months ago), it doesn't complain. Any idea whether this is a problem with the WLCG test spec, or a perfsonar problem?

 

In 5.1, the bundles stopped installing pScheduler’s Esmond archiver plugin since it’s obsolete.  The plugin is still available in the repository and can be installed using one of the following:

 

• RPM:                     dnf -y install pscheduler-archiver-esmond
• Debian:               apt-get -y install pscheduler-archiver-esmond

 

We will stop distributing the plugin entirely in a future release, probably 5.3 and recommend switching to our currently-supported, OpenSeach-based archive.

 

Also note that if there are files installed on the system that force pScheduler or pSConfig to add archives that point to Esmond, those will have to be adjusted or removed.

 

The wording of the error messages will be made clearer in the next bugfix.

 

--Mark