perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Tristan,

You actually hit a known bug that can happen when the 5.1.0 psconfig client tries to read the JSON generated by PWA. PWA sometimes creates a bunch of empty host objects that just look like ‘{}’. Technically that is valid  schema but the client incorrectly produces the error you shared. We have a fix committed and are aiming to do a bug fix release by the end of the week. Sorry for the trouble in the meantime. 

Thanks,

Andy

On June 26, 2024 at 1:40:24 PM, Tristan Sullivan () wrote:

Hello,

I just installed a perfsonar node with Alma 9.4 and perfsonar 5.1. The install seemed to go fine, but no tests are scheduled. When I try to validate the psconfig template (i.e. psconfig validate https://psconfig.opensciencegrid.org/pub/auto/$MYHOSTNAME), I get this:

Loading config ...... OK

Validating JSON schema ...... OK

Verifying object references ...... FAIL

Address ${OTHERHOSTNAME1} references a host object ${OTHERHOSTNAME1} that does not exist.

Address ${OTHERHOSTNAME2} references a host object ${OTHERHOSTNAME2} that does not exist.

Address ${MYHOSTNAME} references a host object ${MYHOSTNAME} that does not exist.

When I look at the psconfig template, I see the three missing hostnames present under "hosts", but they're empty. The other hosts have archivers defined there, e.g.

    "lhcmon.bnl.gov": {

      "archives": [

        "custom-621cd9b8ea8d8100220b28f2",

        "host-archive11"

      ]

    }

For the ones it complains about, it looks like this:

"$MYHOSTNAME": {}

And I find that I don't have a "host-archive" block defined either. But why isn't that there? I installed perfsonar-toolkit, which is supposed to set up a local archive by default. Did I miss a step?

Any help greatly appreciated,

Tristan

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user