Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Bad psconfig template

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Bad psconfig template


Chronological Thread 
  • From: Tristan Sullivan <>
  • To: Andrew Lake <>, "" <>
  • Subject: Re: [perfsonar-user] Bad psconfig template
  • Date: Thu, 27 Jun 2024 04:46:14 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uvic.ca; dmarc=pass action=none header.from=uvic.ca; dkim=pass header.d=uvic.ca; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=U3RLaRJmxIuNAAwYWEIK2TRwsPETpBvsbpwaI3Kat7w=; b=gG91h6t/ZFx0WGVLmBIvE3A2B1KKEaVYY8qmuYsTt5Gh6a5Io25wE1lWBkn9re9EvfKuZwkB9lg46YskhVKInMGSJvGqkEAcvJGAACf665Bw77mwItbOMTg/eGlZgMxglV10iATN+PwEwEaPZEQavF1VpF5NR/Us8ng0rVX3wad//qBgaXJ/TDJoYW+FxzfGVqJeKvInxG90THhwWuDS59CGoaLdmVpIXeWYxuXd5fJwb0geB9sLtpLAfeEU96Ty/ypJTh0P8NHxlUAxS6+rTVdf8NkjhVJmM/cnkNXJOQECd5hJypm6+bx054JFL3CWp5LmtwgfzqQzsok1K0ewGw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fNipS3ei1967z+I5sITc34KkohpPYILXZbcSBppfe3+8yEjU3+kFTQhzKA+DHQCHqfPtBXc4GxkS3hIM18iQKWlhHEaYmpi1y4KcUFosH8WAthf/KqKx/bCbfxpQq2y74dhsdGYxqRBzisU4FgznxSk/GQbR6Qzom8zAKvnfvjIGgDFQmWdIWS4vc/SzsGFw5kqkJ//K74/SGhdxcpdTjeb4Wmlqzj+s3Ep/P0vrZh/dZHm/KCNcNO7RGBNIRKuG6vupWSLSYwtDiNyVkmESF32VfxJLg3ofGp4CZdfR0MVBIJB/C5IGqsnPzebih3tUAxgVoaMHWvVGtF2Gr7ITsg==
  • Msip_labels:

Hi Andy,

Okay, thanks. So it's not a problem that PWA is leaving out the "archives" block inside the host object? 

Tristan

From: Andrew Lake <>
Sent: June 26, 2024 12:29 PM
To: Tristan Sullivan <>; <>
Subject: Re: [perfsonar-user] Bad psconfig template
 
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



Archive powered by MHonArc 2.6.24.

Top of Page