perfSONAR User Q&A and Other Discussion

[Phil Reese <>]

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
[root@dc3-nw-ps networker]# psconfig remote list
=== pScheduler Agent ===
[
   {
      "url" : "https://172.24.20.6/psconfig/sups-rtt.json",
      "configure-archives" : true
   }
]
[root@dc3-nw-ps networker]# psconfig validate https://172.24.20.6/psconfig/sups-rtt.json
pSConfig JSON is valid

and more more bit, just FYI:
[root@dc3-nw-ps networker]# psconfig pscheduler-stats
Agent Last Run Start Time: 2019/07/12 07:56:08
Agent Last Run End Time: 2019/07/12 07:56:08
Agent Last Run Process ID (PID): 7480
Agent Last Run Log GUID: 2E2D490C-A4B5-11E9-91A0-E150B9117C49
Total tasks managed by agent: 0

The json file is at the end of this email.

-----
One of my colleagues worked on one of the non working hosts, and has now gotten 3 of the 4 online systems participating in the MaDDash.  However, I don't think his approach is a good one.

He first stops psconfig-pscheduler-agent on the agent system.

Then, using the results from a previous run of 'systemctl status psconfig-pscheduler-agent' he copies and pastes the ExecStart line.

[root@dc3-nw-ps networker]# systemctl status psconfig-pscheduler-agent
● psconfig-pscheduler-agent.service - pSConfig PScheduler Agent
   Loaded: loaded (/usr/lib/systemd/system/psconfig-pscheduler-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2019-07-12 08:04:49 PDT; 2s ago
  Process: 11594 ExecStart=/usr/lib/perfsonar/bin/psconfig_pscheduler_agent --config=/etc/perfsonar/psconfig/pscheduler-agent.json --logger=/etc/perfsonar/psconfig/pscheduler-agent-logger.conf --pidfile=/var/run/psconfig-pscheduler-agent.pid --user=perfsonar --group=perfsonar (code=exited, status=0/SUCCESS)

This seems to get things operational from a pscheduler-stats point of view and from the MaDDash Dashboard point of view.  Of course, no changes can be made in the json file, as it isn't looking for updates any more.

Still puzzled why this is happening on these freshly built systems.

Phil

On 7/12/19 6:16 AM, Andrew Lake wrote:

">

Hi Phil,

What do you get when you run “psconfig validate https://multitool/psconfig/sups-rtt.json”? Same 404? If you do, anyway you could send me the file?

Thanks,

Andy

----
Here is the sups-rtt.json file:
[root@multitool psconfig]# cat sups-rtt.json
{
    "_meta":{
        "display-name": "SUPS-RTT"
    },

    "archives": {
        "SUPS_esmond_archive": {
            "archiver": "esmond",
            "data": {
                "measurement-agent": "{% scheduled_by_address %}",
                "url": "https://multitool.stanford.edu/esmond/perfsonar/archive/"
            }
        }
    },

    "addresses": {
        "doa-nw-ps.stanford.edu": { "address": "doa-nw-ps.stanford.edu" },
        "moa-west-ps.stanford.edu": { "address": "moa-west-ps.stanford.edu" },
        "noa-press-ps.stanford.edu": { "address": "noa-press-ps.stanford.edu" },
        "woa-west-ps.stanford.edu": { "address": "woa-west-ps.stanford.edu" },
        "doa-fors-ps.stanford.edu": { "address": "doa-fors-ps.stanford.edu" },
        "rwc-j5-ps.stanford.edu": { "address": "rwc-j5-ps.stanford.edu" },
        "dc1-fors-ps.stanford.edu": { "disabled": true, "address": "dc1-fors-ps.stanford.edu" },
        "dc2-fors-ps.stanford.edu": { "disabled": true, "address": "dc2-fors-ps.stanford.edu" },
        "dc3-fors-ps.stanford.edu": { "address": "dc3-fors-ps.stanford.edu" },
        "rwc-j5-srtr-ps.stanford.edu": { "address": "rwc-j5-srtr-ps.stanford.edu" }
    },

    "groups": {
        "SUPS_group_mesh": {
            "type": "mesh",
            "addresses": [
                { "name": "doa-nw-ps.stanford.edu" },
                { "name": "moa-west-ps.stanford.edu" },
                { "name": "noa-press-ps.stanford.edu" },
                { "name": "woa-west-ps.stanford.edu" },
                { "name": "doa-fors-ps.stanford.edu" },
                { "name": "rwc-j5-ps.stanford.edu" },
                { "name": "dc3-fors-ps.stanford.edu" },
                { "name": "rwc-j5-srtr-ps.stanford.edu" }
            ]
        }

    },

    "tests": {
        "test_throughput": {
            "type": "throughput",
            "spec": {
                "source": "{% address[0] %}",
                "dest": "{% address[1] %}",
                "duration": "PT20S"
            }
        },
        "test_rtt": {
            "type": "rtt",
            "spec": {
                "source": "{% address[0] %}",
                "dest": "{% address[1] %}",
                "count": 10,
                "interval": "PT1S",
                "length": 1000
            }
        },
        "test_latencybg": {
            "type": "latencybg",
            "spec": {
                "source": "{% address[0] %}",
                "dest": "{% address[1] %}",
                "flip": "{% flip %}"
            }
        },
        "test_trace": {
            "type": "trace",
            "spec": {
                "source": "{% address[0] %}",
                "dest": "{% address[1] %}"
            }
        }
    },

    "schedules": {
        "SUPS_schedule_PT2H": {
            "repeat": "PT2H",
            "sliprand": true,
            "slip": "PT2H"
        },
        "SUPS_schedule_PT10M": {
            "repeat": "PT10M",
            "sliprand": true,
            "slip": "PT10M"
        }
    },

    "tasks": {
        "task_throughput": {
            "group": "SUPS_group_mesh",
            "test": "test_throughput",
            "schedule": "SUPS_schedule_PT2H",
            "archives": [ "SUPS_esmond_archive" ],
            "_meta": {
                "display-name": "Throughput Tests"
            }
        },
        "task_rtt": {
            "group": "SUPS_group_mesh",
            "test": "test_rtt",
            "schedule": "SUPS_schedule_PT10M",
            "archives": [ "SUPS_esmond_archive" ],
            "_meta": {
                "display-name": "Ping Tests"
            }
        },
        "task_latencybg": {
            "group": "SUPS_group_mesh",
            "test": "test_latencybg",
            "archives": [ "SUPS_esmond_archive" ],
            "_meta": {
                "display-name": "Loss Tests"
            }
        },
        "task_trace": {
            "group": "SUPS_group_mesh",
            "test": "test_trace",
            "schedule": "SUPS_schedule_PT10M",
            "archives": [ "SUPS_esmond_archive" ],
            "_meta": {
                "display-name": "Traceroute Tests"
            }
        }
    }
}