Project

General

Profile

Bug #4678

Glidein reports negative retire times

Added by Burt Holzman about 6 years ago. Updated 20 days ago.

Status:
Assigned
Priority:
Low
Assignee:
Category:
Factory
Target version:
Start date:
09/24/2013
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

An example from the other day:

# --- Last Script values ---
-----------------------------------------------------
max wall time, 603000
job max time, 133200
calculated retire time, 469310
Proxy not long lived enough (86065 s left), shortened retire time to -47135
used param retire spead, 1200
Retire time after spread too low (-47339), remove spread
Mon Sep 23 09:21:48 PDT 2013 Error running 'condor_startup.sh'

Negative numbers for retire time are a bit confusing. I'd prefer to shorten the retire time to zero, skip the spread calculation, and add a line in the script
that the job aborted because the proxy wasn't long enough (probably because the max job time is longer than the proxy lifetime).

History

#1 Updated by Burt Holzman about 6 years ago

Igor suggested that we move some of this logic into check_proxy.sh.

#2 Updated by Marco Mambelli over 1 year ago

  • Target version changed from v3_2_x to v3_4_x

#3 Updated by Marco Mambelli about 1 year ago

  • Target version changed from v3_4_x to v3_5_x

#4 Updated by Marco Mambelli 20 days ago

  • Target version changed from v3_5_x to v3_7_x


Also available in: Atom PDF