perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

(I dropped the list out of the distribution; please post a follow-up when this is resolved.)

 

Ahuja, Satish (Exchange) writes:

 

Hi Mark,

Hope you find this email well. I modified the group section of skeleton.json and that seems to fix the configuration file and I see no error. Additionally, I can see remote definitions on maddash and perfSonar nodes. However, I still can’t see anything on maddash dashboard.

…

 Is there anything left from installation point of view or configuration that we are missing. I should be able to get grids of tests results.

 

Some basic diagnostics:

 

On one of your test points, run “pscheduler troubleshoot” to make sure pScheduler is healthy.

 

On the same test point, run “pscheduler schedule -PT1H” to look at what’s run in the last hour (or PT<whatever>H for longer).  You should be seeing measurements if pSConfig is creating tasks.  Yours appears to be doing that, so there’s a whole branch of troubleshooting that can be skipped.

 

If you’re seeing successful measurements, pluck the run URL from one of the runs in the schedule and run “pscheduler result --archivings RUN-URL”.  The bottom of the output should show whether or not sending the measurements to the archive succeeded.  The most-common thing we run into is that the archive hasn’t been configured to accept unauthenticated measurements from the test points.

 

--Mark