perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

You have “#” symbols in that file, one of which is causing the error. I assume that is an attempt to comment things out but JSON does not support comments natively.  You need to remove the line '{ "#name": "ps01-ntu-cp” },’ entirely. The # symbols in the “addresses" section aren’t actually hurting anything, but they also aren’t doing anything since the addresses are not used as long as they are not referenced in the “groups” section.

Hope that helps,

Andy

On July 9, 2019 at 3:29:52 PM, Pete Siemsen () wrote:

Yup, here it is...

-- Pete

On Tue, Jul 9, 2019 at 1:26 PM Andrew Lake <> wrote:

Hi Pete,

Do you have a copy of the pSConfig JSON file (the one you pointed at with the “psconfig remote add” command)? I think something in that file might be the cause. 

Thanks,

Andy

On July 9, 2019 at 3:09:11 PM, Pete Siemsen () wrote:

We have a new MaDDash working to some degree, but we still have some issues. Here is one:

On our central management host, we're seeing messages like these every hour in our psconfig-pscheduler-agent.log file:

2019/07/09 10:31:53 INFO pid=25675 prog=main:: line=166 msg=Starting pSConfig pScheduler agent
2019/07/09 10:31:53 INFO pid=25675 prog=main:: line=176 guid=0F67B656-A267-11E9-B379-F7885CA4F36D msg=Running agent...
2019/07/09 10:32:58 ERROR pid=25675 prog=main::__ANON__ line=131 guid=0F67B656-A267-11E9-B379-F7885CA4F36D msg=Died: Can't call method "select" on an undefined value at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/Client/PSConfig/Groups/BaseGroup.pm line 188.
2019/07/09 10:58:29 INFO pid=31988 prog=main:: line=166 msg=Starting pSConfig pScheduler agent

Version information:

$ yum list installed | grep central
perfsonar-centralmanagement.noarch    4.1.6-1.el7                     @perfSONAR

$ cat /etc/centos-release

CentOS Linux release 7.6.1810 (Core)

Help!

-- Pete

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user