[torqueusers] Hardcoded CPU time limit?

Zachary, Brian S. zacharybs at ornl.gov
Tue Oct 9 13:13:42 MDT 2012


Looks like a bunch of moderated messages were just let loose on the list… we've since figured out the problem, that our resources_default.cput was set to 10,000 hours and our users weren't specifying a cpu time constraint in their submission scripts.

Thanks,
Brian

On Aug 20, 2012, at 2:40 PM, Zachary, Brian S. wrote:

> Hello,
> We are running torque 3.0.2, and are seeing an issue where jobs that run longer than 10,000 hours are killed with a message similar to "PBS: job killed: cput job total 36010171 secs exceeded limit 36000000 secs". This despite that the queue we are seeing the problem on is configured with "resources_max.cput = 24000:00:00".
> 
> Does anyone know how to get around this limit, either through source modification, configuration changes, use a different version of torque, etc.?
> 
> Thanks,
> Brian Zachary
> 
> 
> _______________________________________________
> torqueusers mailing list
> torqueusers at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torqueusers

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2942 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20121009/792e4cdb/attachment-0001.bin 


More information about the torqueusers mailing list