perfSONAR User Q&A and Other Discussion

[Jason Zurawski <>]

Hi Casey;

The short answer is that the PingER service is still collecting data just 
fine, but the database and display are out of sync, so you can't actually see 
the results.  I remember working with Andy and Will about a year ago on this. 
 If I remember correctly the database gets into a weird state because, for a 
brief moment, the host resolution for DNS changes from being the actual 
address to the 127.* localhost.  Its actually a bit of a pain to fix, and it 
has to be done by hand.  The alternative is to nuke/re-create the database, 
but that will jettison years worth of data (if you have any particular value 
on keeping it).  

I attempted to log into the machines to confirm this (I know I used to have 
an account…) but saw this instead:

> [zurawski@poteen
>  ~]$ ssh 
> 
> 's
>  password: 
> You must be a uniquemember of cn=perfsonar,ou=host-access,dc=kanren,dc=net 
> to login.
> Connection closed by 164.113.32.33


If you want to work with me offline on the account issue, I can try to log in 
to one of them and generate some instructions on how to fix the others (and 
for posting on our web site for others that have a similar situation).  

Thanks;

-jason

On Jul 9, 2013, at 11:03 AM, Casey Russell 
<>
 wrote:

> 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
>