perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey Winnie,

Ok, that’s a known problem, and should be fixed when the 3.4.2 release comes 
out. Would you like a patch in the interim?

Cheers,
Aaron

> On Feb 9, 2015, at 10:35 AM, Winnie Lacesso 
> <>
>  wrote:
> 
> 
> Bonjour Dottore!
> 
> On Mon, 9 Feb 2015, Aaron Brown wrote:
>> Hey Winnie,
>> Could you send /var/log/perfsonar/service_watcher_error.log?
> 
> Ah yes I had a question about that logfile...... on both Bw+Lat it's 
> overwritten once an hour by  /etc/cron.d/cron-service_watcher that runs
> 
> root /opt/perfsonar_ps/toolkit/scripts/service_watcher &> 
> /var/log/perfsonar/service_watcher_error.log
> 
> output = 11 identical lines in /var/log/perfsonar/service_watcher_error.log 
> 
> Can't exec "runlevel": No such file or directory at 
> /opt/perfsonar_ps/toolkit/scripts/../lib/perfSONAR_PS/NPToolkit/Services/Base.pm
>  line 147.
> 
> I looked that up, the line is
> my $runlevel_output = `runlevel`;
> 
> Now 
> sudo -u perfsonar runlevel
> works fine so why should it be unable to find/execute /sbin/runlevel? 
> Unless perfsonar acct's PATH gets mucked with & /sbin removed? Or something?
> 
> On the Bw box (only) I changed Base.pm:
> 
> my $runlevel_output = `/sbin/runlevel`;
> 
> So, on the Lat box /var/log/perfsonar/service_watcher_error.log consists 
> as before (& as will be forever) of 11 identical lines :
> 
> Can't exec "runlevel": No such file or directory at 
> /opt/perfsonar_ps/toolkit/scripts/../lib/perfSONAR_PS/NPToolkit/Services/Base.pm
>  line 147.
> 
> On the Bw box, the error has changed, now 11 identical lines of
> 
> Use of uninitialized value $chkconfig_output in split at 
> /opt/perfsonar_ps/toolkit/scripts/../lib/perfSONAR_PS/NPToolkit/Services/Base.pm
>  line 167.
> 
> Hmm that line is 
> 
> my $chkconfig_output = `chkconfig --list $self->{INIT_SCRIPT}`;
> 
> oooo don't really / really don't want to debug that!......  =:o
> 
> 
> 
>