perfSONAR User Q&A and Other Discussion

["Kern, Paul" <>]

Hi Aaron,

It does happen randomly.  I also have another institution that I work with 
that is experiencing the same behavior.  In both cases, we configured the 
tests by hand.

As for the 'duplicate checksum', I will try your suggestion.  Thanks.

Paul

-----Original Message-----
From: Aaron Brown 
[mailto:]
 
Sent: Wednesday, December 17, 2014 8:27 AM
To: Kern, Paul
Cc: Trey Dockendorf; 

Subject: Re: [perfsonar-user] Regular testing stops and box loses global 
registration

Hey Paul,

> On Dec 16, 2014, at 3:41 PM, Kern, Paul 
> <>
>  wrote:
> 
> I see the same thing here.  Below is what I am seeing in my 
> /var/log/perfsonar/regular_resting.log, before the service failed:
> 
> 2014/12/15 15:22:37 (3670) DEBUG> Master.pm:198 
> perfSONAR_PS::RegularTesting::Master::handle_child_exit - Received SIGCHLD 
> for PID: 3676
> 2014/12/15 15:22:37 (3670) DEBUG> Master.pm:198 
> perfSONAR_PS::RegularTesting::Master::handle_child_exit - Received SIGCHLD 
> for PID: 3675
> 2014/12/15 15:22:37 (3670) DEBUG> Master.pm:198 
> perfSONAR_PS::RegularTesting::Master::handle_child_exit - Received SIGCHLD 
> for PID: 3679
> 2014/12/15 15:22:37 (3670) DEBUG> Master.pm:198 
> perfSONAR_PS::RegularTesting::Master::handle_child_exit - Received SIGCHLD 
> for PID: 3674
> 2014/12/15 15:22:37 (3670) DEBUG> Master.pm:258 
> perfSONAR_PS::RegularTesting::Master::handle_exit - Process 'perfSONAR_PS 
> Regular Testing’ exiting

That’s strange. That’s the normal “the service is being stopped” set of 
lines. Does it just happen randomly? Are you running the mesh configuration, 
or did you just configure tests by hand?

> I also see the 'duplicate checksum' entries in ls_registration_daemon.log.  
> Not sure if that is normal behavior or not.  It looks like it has been 
> going on for quite some time.

This ‘duplicate_checksum' error is relatively common. Could you edit 
/opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon-logger.conf
 and replace the “INFO” with “DEBUG”, and then restart the 
“ls_registration_daemon” service? This all may be a red herring because it 
may be that the main page isn’t doing the lookups as expected or something, 
not that the service isn’t registered.

Cheers,
Aaron

> 
> Paul
> 
> From: Trey Dockendorf 
> [mailto:]
>  
> Sent: Tuesday, December 16, 2014 2:32 PM
> To: Kern, Paul
> Cc: 
> 
> Subject: Re: [perfsonar-user] Regular testing stops and box loses global 
> registration
> 
> Thought I'd add that I'm seeing this on two of my perfsonar boxes too.  So 
> far the regular testing seems to show as "Not Running" more frequently on 
> the host performing bandwidth tests than the host performing latency tests.
> 
> Below are last entries in /var/log/perfsonar/regular_testing.log.1 before I 
> manually restarted the regular testing daemon.
> 
> 2014/12/11 00:29:14 (2299) DEBUG> Master.pm:198 
> perfSONAR_PS::RegularTesting::Master::handle_child_exit - Received SIGCHLD 
> for PID: 2304
> 2014/12/11 00:29:14 (2299) DEBUG> Master.pm:198 
> perfSONAR_PS::RegularTesting::Master::handle_child_exit - Received SIGCHLD 
> for PID: 2305
> 2014/12/11 00:29:14 (2299) DEBUG> Master.pm:198 
> perfSONAR_PS::RegularTesting::Master::handle_child_exit - Received SIGCHLD 
> for PID: 2303
> 2014/12/11 00:29:14 (2299) DEBUG> Master.pm:258 
> perfSONAR_PS::RegularTesting::Master::handle_exit - Process 'perfSONAR_PS 
> Regular Testing' exiting
> 
> The global registration service seems to get hung on both systems equally.  
> I see no obvious errors in /var/log/perfsonar/ls_registration_daemon.log.  
> I do notice that there are a few entries that mention "Duplicate checksum".
> 
> - Trey
> 
> 
> =============================
> 
> Trey Dockendorf 
> Systems Analyst I 
> Texas A&M University 
> Academy for Advanced Telecommunications and Learning Technologies 
> Phone: (979)458-2396 
> Email: 
> 
>  
> Jabber: 
> 
> 
> On Tue, Dec 16, 2014 at 1:06 PM, Kern, Paul 
> <>
>  wrote:
> Hello all,
>  
> I am dealing with an issue in which regular testing on our perfsonar box 
> (3.4.2) stops sporadically, and the box appears to lose its global 
> registration – global registration changes from “yes” to “no”.  I have not 
> seen anything in the logs that would indicate why this is happening, but I 
> am a novice with this tool and I may be missing something.  Restarting the 
> services seems to resolve the issue temporarily, but it always crops back 
> up. 
>  
> Regards,
>  
> Paul Kern
> South Dakota Board of Regents
>  
>