perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Phil,

No worries, glad you found the issue. I think it didn’t help that the error you were getting looked like an HTTP 404 even though it was a DNS issue. This is an old bug in the 4.1 clients which should be cleaned-up in 4.2. Thanks for the patience and closing the loop on the cause. 

Thanks,

Andy

On July 15, 2019 at 7:08:01 PM, Phil Reese () wrote:

Andy and others,

While I'm a little embarrassed to send this, my issue has gone away.

I now know I had a typo in my .json file.  The agent host has a DNS name of 'dc3-nw-ps' but the .json file had it as 'dc3-fors-ps'.

Not sure why this caused things to behave as I've described but after finding and fixing my error, things sorted themselves out on the next refresh cycle.

Hat in hand, thanks all,
Phil

On 7/12/19 8:12 AM, Phil Reese wrote:

"> Hi Andy,

Here are the results of your request:
[root@dc3-nw-ps networker]# psconfig validate https://multitool/psconfig/sups-rtt.json
pSConfig JSON is valid