perfSONAR User Q&A and Other Discussion

[Phil Reese <>]

A bit more feedback on PS 4.2beta

I wondered if the PXE boot had anything to do with the issue, so I 
rebuilt one of the Centos systems by hand and it exhibited the same 
problem of not downloading the work file json and the same 'pscheduler 
troubleshoot' output.

I then rebuilt it with a production PS 4.1.6.  This system downloaded 
the json and joined the grid without issue.  I then upgraded this host 
to the beta by using the suggested commands:
yum install perfSONAR-repo-staging
yum update

Rebooted the system and now it responds as the original beta install 
responded, no json download and  'pscheduler troubleshoot' fails as below.

One other comment for the Debian beta build.  The three systems I built 
with the beta code all got their json and responded to Ping and 
traceroute tests.  However, the throughput tests never worked. After 
some poking I found that the permissions on iperf3 were wrong, a chmod 
u+x to iperf3 solved the issue and they then joined the grid.

Phil

On 8/1/19 9:24 AM, Phil Reese wrote:
> I ran 'pscheduler troubleshoot' on all the four host and all came back 
> with the same results:
>
> [root@asus1 rc.d]# pscheduler troubleshoot
> Traceback (most recent call last):
>   File "/usr/libexec/pscheduler/commands/troubleshoot", line 17, in 
> <module>
>     import pscheduler
>   File "/usr/lib/python2.7/site-packages/pscheduler/__init__.py", line 
> 11, in <module>
>     from .enummatcher import *
>   File "/usr/lib/python2.7/site-packages/pscheduler/enummatcher.py", 
> line 6, in <module>
>     from jsonval import json_validate
>   File "/usr/lib/python2.7/site-packages/pscheduler/jsonval.py", line 
> 7, in <module>
>     import jsonschema
>   File "/usr/lib/python2.7/site-packages/jsonschema/__init__.py", line 
> 32, in <module>
>     from pkg_resources import get_distribution
> ImportError: No module named pkg_resources
>
> Looks like 'pkg_resources' is lost in this beta version.