Re: [Condor-users] Lazy jobs that never really start running

["Horvatth Szabolcs" <szabolcs@xxxxxxxxxxxxx>]

This is a snippet from the starter log of a machine:

7/7 16:14:29 vm1: Changing activity: Idle -> Busy
7/7 16:14:33 DaemonCore: Command received via TCP from host <192.168.0.71:1851>
7/7 16:14:33 DaemonCore: received command 404 (DEACTIVATE_CLAIM_FORCIBLY), calling handler (command_handler)
7/7 16:14:33 vm1: Called deactivate_claim_forcibly()
7/7 16:14:33 DaemonCore: Command received via UDP from host <192.168.0.101:2784>
7/7 16:14:33 DaemonCore: received command 60001 (DC_PROCESSEXIT), calling handler (HandleProcessExitCommand())
7/7 16:14:33 Starter pid 3604 exited with status 0
7/7 16:14:33 vm1: State change: starter exited
7/7 16:14:33 vm1: Changing activity: Busy -> Idle



What is this DEACTIVATE_CLAIM_FORCIBLY command?
I'd searched the mailing list archive to find something about it but did not find an explanation,
just mentioning it as a problem.

Cheers,
Szabolcs