As I pointed out on 14th of May SAM made new release of sensors:
* installed RPMs on SAM UIs
* updated its YUM/APT repos
* tagged the release to PROD tag in SAM CVS
-t is only used if lcg_util is < 1.7.2-1 or lcg-* CLI doesn't support --version
(very old installations)
If you see -t is still used (from time to time?):
* your WNs are not homogeneous - some of them still have lcg_util < 1.7.2-1
If you are sure that WNs have lcg_util >= 1.7.2-1, then:
* if jobs are coming as ops VO, then probably SAM AP is probing you, which
didn't update itself yet
* if other VOs - then, you should ask them to update their respective SAM UIs
(via RPM or CVS)
Hope this helps,
Konstantin
Arnau Bria wrote:
> On Tue, 19 May 2009 13:13:31 +0300
> Dimitris Zilaskos wrote:
>
>> Dear Andreas,
>>
>> Andreas Unterkircher wrote:
>>> Hi Dimitris,
>>>
>>> as Konstantin wrote, the SAM tests have been updated since nearly a
>>> week. Now I quickly scanned the production SAM results and found at
>>> least 30 sites that upgraded to lcg_util 1.7.2/GFAL 1.11.4 and
>>> which pass the relevant SAM tests (CE-sft-lcg-*). So I see no
>>> reason to take these rpms out of the release.
>>
>> So it is my understanding that SAM results were not distorted by this
>> problem. Is that correct?
>
> Original problem did affect SAM test... but as Andreas said, it was
> solved few days later (SAM test did change its syntax):
>
>
> lcg-cr --connect-timeout 10 --sendreceive-timeout 120 --bdii-timeout 20 --srm-timeout 180 -v --vo ops -d srm.pic.es -l lfn:sft-lcg-rm [...]
> ^^^^^^^^^^^^^^^^^^^^^^
>
> but if I check las CE test:
>
> lcg-cr -t 120 -v --vo ops -d srm.pic.es -l lfn:sft-lcg-rm-cr-td176.pic.es.090519060354.13271654 file:///home/ops014/globus-tmp.td176. [...]
> ^^^^^^^^^^
>
> little confused now :-)
>
> Cheers,
> Arnau
|