perfSONAR User Q&A and Other Discussion

[Phil Reese <>]

Hi Doug,

The following two curls always bring the .json file down:
curl  http://..
curl -k https://...

([root@doa-fors-ps networker]# curl -k https://multitool/psconfig/sups-rtt.json
{"_meta":{"display-name":"SUPS-RTT","psconfig-publisher":{"publish-source":"psconfig-publish-cli","publish-time":"2019-07-07T23:17:31+00:00"}},"addresses":{"dc1-fors-ps.stanford.edu"  ...)

Here is another log snippet (I REALLY do love the grep with GUID option in this version!)

[root@doa-fors-ps networker]# grep 5AF6A9A8-A409-11E9-B6D0-E7C18D3DBF0F /var/log/perfsonar/*
/var/log/perfsonar/psconfig-pscheduler-agent.log:2019/07/11 11:26:09 INFO pid=5971 prog=main:: line=176 guid=5AF6A9A8-A409-11E9-B6D0-E7C18D3DBF0F msg=Running agent...
/var/log/perfsonar/psconfig-pscheduler-agent.log:2019/07/11 11:26:14 ERROR pid=5971 prog=perfSONAR_PS::PSConfig::BaseAgent::_process_psconfig line=371 guid=5AF6A9A8-A409-11E9-B6D0-E7C18D3DBF0F config_url=http://172.24.20.6/psconfig/sups-rtt.json config_src=remote msg=Error loading psconfig: HTTP/1.1 404 Not Found
/var/log/perfsonar/psconfig-pscheduler-agent.log:2019/07/11 11:26:14 INFO pid=5971 prog=main:: line=178 guid=5AF6A9A8-A409-11E9-B6D0-E7C18D3DBF0F msg=Agent completed running
/var/log/perfsonar/psconfig-pscheduler-agent.log:2019/07/11 11:26:14 INFO pid=5971 prog=main:: line=189 guid=5AF6A9A8-A409-11E9-B6D0-E7C18D3DBF0F msg=Time until next record refresh is 3595 seconds

Very puzzling when other systems work.

Phil

On 7/11/19 11:19 AM, Southworth, Doug Jontz wrote:

">

Phil,

Sorry to butt in, but in your curl command you need the -k switch to allow it 
to work with https and without proper certs in place. That should allow you to 
pull the file from a node. Can you give that a shot and reply back? I just 
want to confirm that 443 is indeed open.

Doug Southworth
Network Systems Analyst, Indiana University
2709 E 10th St. Bloomington In 47408
(812) 855-3172