[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-users] ClaimLease got expired when the job is about to start and in between (claimWorklifeExpired)
- Date: Tue, 04 Aug 2009 20:51:08 +0530
- From: Johnson koil Raj <johnson.raj@xxxxxxxxx>
- Subject: [Condor-users] ClaimLease got expired when the job is about to start and in between (claimWorklifeExpired)
In our pool we submitted job with JobLeaseDuration = 7200, I have
modified the claim_worklife = 0.
what are the other configuration need to be take care while changing
one job is not able to start after slot preparation.
8/4 18:39:00 slot1.2: Remote job ID is 23.0
8/4 18:39:00 slot1.2: Remote global job ID is
8/4 18:39:00 slot1.2: JobLeaseDuration defined in job ClassAd: 7200
8/4 18:39:00 slot1.2: Resetting ClaimLease timer (44) with new duration
8/4 18:39:00 slot1.2: About to Create_Process "condor_starter -f -a
8/4 18:39:00 Create_Process: using fast clone() to create child process.
8/4 18:39:00 slot1.2: Got RemoteUser (idealgrid@xxxxxxxxxxxxxxxxx) from
8/4 18:39:00 slot1.2: Got universe "VM" (13) from request classad
8/4 18:39:00 slot1.2: State change: claim-activation protocol successful
8/4 18:39:00 slot1.2: Changing activity: Idle -> Busy
8/4 18:39:00 Received UDP command 60008 (DC_CHILDALIVE) from
<10.201.214.92:10039>, access level DAEMON
8/4 18:39:01 condor_read(): Socket closed when trying to read 5 bytes
8/4 18:39:01 IO: EOF reading packet header
8/4 18:39:04 slot1.2: Sent update to 2 collector(s)
8/4 18:39:26 slot1.2: Computing claimWorklifeExpired(); ClaimAge=26,
8/4 18:39:26 slot1.2: Called deactivate_claim_forcibly()
8/4 18:39:26 slot1.2: In Starter::kill() with pid 3460, sig 3 (SIGQUIT)
8/4 18:39:26 Send_Signal(): Doing kill(3460,3) [SIGQUIT]
8/4 18:39:26 slot1.2: Canceled ClaimLease timer (44)
8/4 18:39:26 slot1.2: Changing state and activity: Claimed/Busy ->
8/4 18:39:26 slot1.2: In Starter::kill() with pid 3460, sig 15 (SIGTERM)
8/4 18:39:26 Send_Signal(): Doing kill(3460,15) [SIGTERM]
8/4 18:39:26 slot1.2: Got ACTIVATE_CLAIM while in Preempting state,
8/4 18:39:26 slot1.2: Got KILL_FRGN_JOB while in Preempting state, ignoring.
8/4 18:39:26 slot1.2: Got RELEASE_CLAIM while in Preempting state, ignoring.
8/4 18:39:28 condor_read(): Socket closed when trying to read 5 bytes
8/4 18:39:28 IO: EOF reading packet header
8/4 18:39:28 slot1.2: Closing job ClassAd update socket from starter.
8/4 18:39:28 DaemonCore: No more children processes to reap.
8/4 18:39:28 Starter pid 3460 died on signal 11 (signal 11 (Segmentation
8/4 18:39:28 slot1.2: Canceled hardkill-starter timer (52)
8/4 18:39:28 slot1.2: State change: starter exited
8/4 18:39:28 slot1.2: State change: No preempting claim, returning to owner
8/4 18:39:28 Publishing ClassAd for 'MEMCALC'
8/4 18:39:28 slot1.2: Changing state and activity: Preempting/Vacating
8/4 18:39:28 slot1.2: State change: IS_OWNER is false
8/4 18:39:28 slot1.2: Changing state: Owner -> Unclaimed
8/4 18:39:28 slot1.2: Changing state: Unclaimed -> Delete
what is the ClaimAge ? what is pointing to?
The following log for another job has more claimage which was runing
fine but stopped suddenly.
8/4 19:29:25 slot1.4: Got ACTIVATE_CLAIM while in Claimed/Busy state,
8/4 19:29:25 slot1.4: Computing claimWorklifeExpired(); ClaimAge=12925,
8/4 19:29:25 slot1.4: Called deactivate_claim_forcibly()
8/4 19:29:25 slot1.4: In Starter::kill() with pid 28138, sig 3 (SIGQUIT)
8/4 19:29:25 Send_Signal(): Doing kill(28138,3) [SIGQUIT]
I am using condor-7.2.3
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.