Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] PingER won't return any graphed results

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] PingER won't return any graphed results


Chronological Thread 
  • From: Casey Russell <>
  • To:
  • Subject: [perfsonar-user] PingER won't return any graphed results
  • Date: Tue, 9 Jul 2013 10:03:03 -0500
  • Authentication-results: sfpop-ironport04.merit.edu; dkim=neutral (message not signed) header.i=none

Group,

     Our installation of PerfSonar has been in place for a bit over a year.  I recently took over management of it, and I'll start off by pointing out that our overall installation is a bit non-standard, however, the PingER portion is typical.  

     I think this particular problem has been present since very early on, and perhaps from day one.  However it's also possible that it worked early on, but yum updating broke it many months ago.  

     Basically what's happening is the hosts (as near as I can tell from the logs) are collecting the PingER data appropriately, but when you try to pull up a graph, you get a page that simply says "no data".  The PingER log shows the following:

2013/07/09 09:59:19 (15974) INFO> Scheduler.pm:632 perfSONAR_PS::Services::MP::Scheduler::doTest - Collecting measurements for 'urn:ogf:network:domain=test.6300600:node=7462695:port=164.113.32.17:packetSize=1000:count=10:interval=1:ttl=255'
2013/07/09 09:59:19 (15976) INFO> Scheduler.pm:632 perfSONAR_PS::Services::MP::Scheduler::doTest - Collecting measurements for 'urn:ogf:network:domain=test.6300600:node=2429288:port=164.113.32.25:packetSize=1000:count=10:interval=1:ttl=255'
2013/07/09 09:59:19 (15976) INFO> Scheduler.pm:632 perfSONAR_PS::Services::MP::Scheduler::doTest - Collecting measurements for 'urn:ogf:network:domain=test.6300600:node=2429288:port=164.113.32.25:packetSize=1000:count=10:interval=1:ttl=255'
2013/07/09 09:59:19 (15978) INFO> Scheduler.pm:632 perfSONAR_PS::Services::MP::Scheduler::doTest - Collecting measurements for 'urn:ogf:network:domain=test.6300600:node=13704503:port=164.113.32.9:packetSize=1000:count=10:interval=1:ttl=255'
2013/07/09 09:59:19 (15978) INFO> Scheduler.pm:632 perfSONAR_PS::Services::MP::Scheduler::doTest - Collecting measurements for 'urn:ogf:network:domain=test.6300600:node=13704503:port=164.113.32.9:packetSize=1000:count=10:interval=1:ttl=255'
2013/07/09 09:59:25 (800) INFO> daemon.pl:567 main::psService - Received incoming connection from:	127.0.0.1
2013/07/09 09:59:25 (15990) INFO> Request.pm:357 perfSONAR_PS::Request::finish - Total service time for request from 127.0.0.1: 0.006542 seconds
2013/07/09 09:59:25 (800) INFO> daemon.pl:567 main::psService - Received incoming connection from:	127.0.0.1
2013/07/09 09:59:27 (15991) WARN> daemon.pl:424 main::__ANON__ - Warned: Use of uninitialized value in concatenation (.) or string at /opt/perfsonar_ps/PingER/bin/../lib/perfSONAR_PS/Services/MA/PingER.pm line 468.
2013/07/09 09:59:27 (15991) INFO> Request.pm:357 perfSONAR_PS::Request::finish - Total service time for request from 127.0.0.1: 1.823071 seconds

The request for a graph began at 09:59:25.

Does anyone have any insight into what's failing here, or why?
 
Casey Russell
Network Engineer
Kansas Research and Education Network
1405 Wakarusa Dr., Ste B
Lawrence, KS 66049
(785)856-9820  ext 9809



Archive powered by MHonArc 2.6.16.

Top of Page