BTW: If this is the issue, and you use torque, it can be worked around
in this way (it's all in the bug report):
-------------------------------------------------------
A quick (though perhaps wrong?) way to get the field into our bdii
output is to add this to my torque settings:
set queue long resources_default.cput = 48:00:00
The new translation script (info-dynamic-pbs) that came on with CREAM
1.16.2 uses resources_default.cput, instead of resources_max.cput (which
the name implies is the correct field).
-------------------------------------------------------
Steve
On 02/27/2014 02:20 PM, Mark Slater wrote:
> Hi All,
>
> It seems our publishing is off for LHCb but I'm not sure how to fix
> it. It seems the MaxCPU time is not publishing correctly and indeed:
>
> [root@epgr02 ~]# ldapsearch -LLL -x -h localhost -p 2170 -b o=grid |
> grep 999999
> ...
> GlueCEPolicyMaxCPUTime: 999999999
> ...
> GlueCEPolicyMaxCPUTime: 999999999
> ...
>
> How can I get this fixed? Is there some dynamic setting/yaim problem
> going on here?
>
> Thanks!
>
> Mark
--
Steve Jones [log in to unmask]
System Administrator office: 220
High Energy Physics Division tel (int): 42334
Oliver Lodge Laboratory tel (ext): +44 (0)151 794 2334
University of Liverpool http://www.liv.ac.uk/physics/hep/
|