perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Rune,

I believe you've encountered a known bug that will be fixed in our 3.4.2 
release (should be out in a few weeks). You can find more info on it here: 
http://code.google.com/p/perfsonar-ps/issues/detail?id=1049

If you are so inclined, there is also a patch attached to that issue that 
should correct the problem in the interim until 3.4.2 is released.

Thanks,
Andy



On Feb 3, 2015, at 4:54 PM, Rune Stromsness 
<>
 wrote:

> In package perl-perfSONAR_PS-Toolkit-3.4.1-1.pSPS.noarch there is a file
> /etc/cron.hourly/logscraper.cron which is generating error messages like:
> 
>> gzip: /var/log/.messages-20150203.gz: No such file or directory
>> gzip: /var/log/.messages-20150202.gz: No such file or directory
>> gzip: /var/log/.messages-20150201.gz: No such file or directory
>> gzip: /var/log/.messages-20150131.gz: No such file or directory
>> gzip: /var/log/.messages-20150130.gz: No such file or directory
>> gzip: /var/log/.messages-20150129.gz: No such file or directory
>> gzip: /var/log/.messages-20150128.gz: No such file or directory
>> gzip: /var/log/.messages-20150127.gz: No such file or directory
>> gzip: /var/log/.messages-20150126.gz: No such file or directory
>> gzip: /var/log/perfsonar/.owamp_bwctl.log-20150201.gz: No such file or 
>> directory
>> gzip: /var/log/perfsonar/.owamp_bwctl.log-20150126.gz: No such file or 
>> directory
> 
> I believe that is due to extraneous "." characters in these lines:
> 
>>        open( LOGFILE, "gunzip -c $log_dir.$l |" ) or die "can't open pipe 
>> to $log_dir.$l\n";
>>    }
>>    else {
>>        open( LOGFILE, $log_dir.$l ) or die "can't open $log_dir.$l\n";
> 
> and
> 
>>        open( LOGFILE, "gunzip -c $log_dir.$l |" ) or die "can't open pipe 
>> to $log_dir.$l\n";
>>    }
>>    else {
>>        open( LOGFILE, $log_dir.$l ) or die "can't open $log_dir.$l\n";
>> 
> 
> (in two different while blocks in the file).
> 
> 
> Does that look correct to anyone else?
> 
> 
> Rune
> 
> 
>