perfSONAR User Q&A and Other Discussion

[David Szydloski <>]

Hello All,

I've seen a few threads here on the same issue but I'm still having some problems with seeing results in the webui even though, as far as I can tell: 

1) the tests are indeed running 

dszydloski@netperf01-lon1:~$ sudo pscheduler schedule -PT10M +PT5M

sudo: unable to resolve host netperf01-lon1

2018-01-07T15:11:02Z - 2018-01-07T15:11:11Z  (Finished)

rtt --count 10 --dest 10.5.8.30 --interval PT1S --ip-version 4 --source 10.67.8.23 --length 1000 --ttl 255 (Run with tool 'ping')

https://localhost/pscheduler/tasks/301b5d03-fc79-4f09-a4d8-3336a5c4fb46/runs/c458eb0c-06a4-47fd-a4fc-c6d8f755a0da

2018-01-07T15:13:09Z - 2018-01-07T15:13:09Z  (Finished)

trace --dest 159.117.204.175 --ip-version 6 (Run with tool 'traceroute')

https://localhost/pscheduler/tasks/e47cc6d7-c7d7-4f51-bb13-c9f9eeaa560d/runs/2ca64f99-8c22-40b2-9933-6ec4c3856a10

2018-01-07T15:14:21Z - 2018-01-07T15:14:21Z  (Finished)

trace --dest 10.5.8.30 --ip-version 6 (Run with tool 'traceroute')

https://localhost/pscheduler/tasks/7295644d-12fe-4b32-b9b9-ad8979975be6/runs/be03eff6-861a-4e2d-bdb3-c572296c6b94

2018-01-07T15:15:09Z - 2018-01-07T15:15:09Z  (Finished)

rtt --count 10 --dest 10.5.8.30 --interval PT1S --ip-version 6 --length 1000 --ttl 255 (Run with tool 'ping')

https://localhost/pscheduler/tasks/dfd70906-6361-4b17-a991-4cfe902d8173/runs/ecbb13fd-067d-4c80-9eb1-2c1def6cdfdb

2018-01-07T15:15:58Z - 2018-01-07T15:15:58Z  (Finished)

rtt --count 10 --dest 159.117.204.175 --interval PT1S --ip-version 6 --length 1000 --ttl 255 (Run with tool 'ping')

https://localhost/pscheduler/tasks/b5b221e8-afbc-4b2b-84ca-3e9468d79e31/runs/ebe31c2b-9032-48da-8443-ab9c52d85624

2018-01-07T15:19:23Z - 2018-01-07T15:19:32Z  (Finished)

rtt --count 10 --dest 10.5.8.30 --interval PT1S --ip-version 4 --source 10.67.8.23 --length 1000 --ttl 255 (Run with tool 'ping')

https://localhost/pscheduler/tasks/301b5d03-fc79-4f09-a4d8-3336a5c4fb46/runs/e69e2f5f-7699-4eb2-840d-5f15eeeb9216

2) When I do a dump of the pscheduler postgres database I see what looks like a JSON including the results:

8       b5b221e8-afbc-4b2b-84ca-3e9468d79e31    {"test": {"spec": {"ttl": 255, "dest": "159.117.204.175", "count": 10, "length": 1000, "schema": 1, "interval": "PT1S", "ip-version": 6}, "type": "rtt"}, "tool": "ping", "schema": 1, "archives": [{"ttl": "PT900S", "data": {"url": "https://localhost/esmond/perfsonar/archive/", "_auth-token": "<removed>", "retry-policy": [{"wait": "PT60S", "attempts": 1}, {"wait": "PT300S", "attempts": 1}]}, "archiver": "esmond"}], "schedule": {"slip": "PT300S", "until": "2018-01-08T15:10:40Z", "repeat": "PT300S", "sliprand": true}, "reference": {"created-by": {"uuid": "1b9d8239-1263-44b5-8ab8-53815a1e1073", "user-agent": "perfsonar-meshconfig"}, "description": "test"}}     3       2018-01-07 15:11:08.863497+00        \N      00:05:00        00:00:16        00:05:00        2018-01-08 15:10:40+00  \N      88      18      ["127.0.0.1"]   1       0       \N      t       {"server": "127.0.0.1", "requester": "127.0.0.1"}    ["--count", "10", "--dest", "159.117.204.175", "--interval", "PT1S", "--ip-version", "6", "--length", "1000", "--ttl", "255"]\n 00:00:00    2018-01-07 15:15:58+00   []      {"test": {"spec": {"ttl": 255, "dest": "159.117.204.175", "count": 10, "length": 1000, "schema": 1, "interval": "PT1S", "ip-version": 6}, "type": "rtt"}, "tool": "ping", "detail": {"cli": ["--count", "10", "--dest", "159.117.204.175", "--interval", "PT1S", "--ip-version", "6", "--length", "1000", "--ttl", "255"], "post": "P0D", "runs": 88, "slip": "PT5M", "added": "2018-01-07T15:11:08Z", "start": null, "anytime": true, "enabled": true, "duration": "PT16S", "exclusive": false, "participant": 0, "multi-result": false, "participants": ["127.0.0.1"], "spec-limits-passed": []}, "schema": 1, "archives": [{"ttl": "PT900S", "data": {"url": "https://localhost/esmond/perfsonar/archive/", "_auth-token": <removed>", "retry-policy": [{"wait": "PT60S", "attempts": 1}, {"wait": "PT300S", "attempts": 1}]}, "archiver": "esmond"}], "schedule": {"slip": "PT300S", "until": "2018-01-08T15:10:40Z", "repeat": "PT300S", "sliprand": true}, "reference": {"created-by": {"uuid": "1b9d8239-1263-44b5-8ab8-53815a1e1073", "user-agent": "perfsonar-meshconfig"}, "description": "test"}}

So far I haven't had much with scouring the logs. Any idea on what else to try here would be greatly appreciated.

Host Info:

OpenStack Nova VM running Ubuntu 16.04

Kernel: 4.4.0-104-generic

perfSONAR version: 4.0.2.1-2~bpo70+1

Toolkit version: same

-

--

David Szydloski

Core Deployment Engineer

VidScale, Inc.