perfSONAR User Q&A and Other Discussion

[Zhi-Wei Lu <>]

Hi all,

 

One of our perfsonar box (out of six) failed to show any test results after yesterday’s  perfsonar 4.0 upgrade. It appears that no test was configured after the upgrade on that box.   There were many error message in the log file meshconfig-agent.log

 

Use of uninitialized value $key in string eq at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/Utils/HTTPS.pm line 83.

2017/04/18 03:32:47 (23063) ERROR> perfsonar_meshconfig_agent:402 main:: - Problem contacting pScheduler, will try again later.

2017/04/18 03:33:26 (25002) ERROR> perfsonar_meshconfig_agent:402 main:: - Problem contacting pScheduler, will try again later.

2017/04/18 03:34:26 (25002) INFO> perfsonar_meshconfig_agent:456 main:: - Retrying pscheduler after failure

2017/04/18 03:34:28 (25002) INFO> perfsonar_meshconfig_agent:405 main:: - pScheduler is back up, resuming normal operation

2017/04/18 03:34:28 (25002) ERROR> BwctlBase.pm:440 perfSONAR_PS::RegularTesting::Tests::BwctlBase::__ANON__ - Error determining local address, skipping test: Unable to find a matching pair of IPv4 or IPv6 addresses for interface eth0 and target address tc1-teng8-2.net.ohio-state.edu

2017/04/18 03:34:28 (25002) ERROR> BwctlBase.pm:440 perfSONAR_PS::RegularTesting::Tests::BwctlBase::__ANON__ - Error determining local address, skipping test: Unable to find a matching pair of IPv4 or IPv6 addresses for interface eth0 and target address tc1-teng8-2.net.ohio-state.edu

2017/04/18 03:34:28 (25002) ERROR> BwctlBase.pm:440 perfSONAR_PS::RegularTesting::Tests::BwctlBase::__ANON__ - Error determining local address, skipping test: Unable to find a matching pair of IPv4 or IPv6 addresses for interface eth1 and target address perfsonar-011.net.berkeley.edu

2017/04/18 03:34:29 (25002) WARN> perfsonar_meshconfig_agent:145 main::__ANON__ - Warned: Use of uninitialized value $address in exists at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/RegularTesting/Tests/BwctlBase.pm line 384.

2017/04/18 03:34:29 (25002) WARN> perfsonar_meshconfig_agent:145 main::__ANON__ - Warned: Use of uninitialized value $address in exists at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/RegularTesting/Tests/BwctlBase.pm line 384.

2017/04/18 03:34:29 (25002) WARN> perfsonar_meshconfig_agent:145 main::__ANON__ - Warned: Use of uninitialized value $address in exists at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/RegularTesting/Tests/BwctlBase.pm line 384.

2017/04/18 03:34:29 (25002) ERROR> BwctlBase.pm:440 perfSONAR_PS::RegularTesting::Tests::BwctlBase::__ANON__ - Error determining local address, skipping test: Unable to find a matching pair of IPv4 or IPv6 addresses for interface eth0 and target address b06sr1-vlan254.tele.iastate.edu

2017/04/18 03:34:29 (25002) ERROR> BwctlBase.pm:440 perfSONAR_PS::RegularTesting::Tests::BwctlBase::__ANON__ - Error determining local address, skipping test: Unable to find a matching pair of IPv4 or IPv6 addresses for interface eth0 and target address b06sr1-vlan254.tele.iastate.edu

2017/04/18 03:57:49 (25002) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test, continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine participants: Process took too long to run.

2017/04/18 03:57:49 (25002) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test: 400 BAD REQUEST: Can't find pScheduler or BWCTL on hongkong-nms-1.ps.jgn-x.jp

 

2017/04/18 03:57:49 (25002) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test: 400 BAD REQUEST: Can't find pScheduler or BWCTL on hongkong-nms-1.ps.jgn-x.jp

 

…

 

2017/04/19 15:28:49 (5430) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test, continuing with rest of config: 500 Can't connect to 2607:f810:330:1ffe::f:443 (connect: No route to host): 500 Can't connect to 2607:f810:330:1ffe::f:443 (connect: No route to host)

2017/04/19 15:28:49 (5430) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test, continuing with rest of config: 500 Can't connect to 2607:f810:330:1ffe::f:443 (connect: No route to host): 500 Can't connect to 2607:f810:330:1ffe::f:443 (connect: No route to host)

2017/04/19 15:28:49 (5430) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test: 400 BAD REQUEST: At /dest: u'2001:400:6201:1150:' is not valid under any of the given schemas

 

2017/04/19 15:28:49 (5430) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test: 400 BAD REQUEST: At /source: u'2001:400:6201:1150:' is not valid under any of the given schemas

 

2017/04/19 15:28:49 (5430) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test: 400 BAD REQUEST: At /dest: u'2001:400:d01:1150:' is not valid under any of the given schemas

 

2017/04/19 15:28:49 (5430) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test: 400 BAD REQUEST: At /source: u'2001:400:d01:1150:' is not valid under any of the given schemas

 

2017/04/19 15:28:49 (5430) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test: 400 BAD REQUEST: At /dest: u'2001:400:101:1150:' is not valid under any of the given schemas

 

2017/04/19 15:28:49 (5430) WARN> perfsonar_meshconfig_agent:430 main:: - Problem determining which pscheduler to submit test to for creation, skipping test: 400 BAD REQUEST: At /source: u'2001:400:101:1150:' is not valid under any of the given schemas

 

…

 

I wonder how I can configure perfsonar so that I can get my previously configured tests goging again.

 

Thank you.

 

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155