[condor-users] DEACTIVATE_CLAIM_FORCIBLY

[Scott Koranda <skoranda@xxxxxxxxxxxxxxxxxxxx>]

Hi,

We are seeing this in the StartLogs on a Condor 6.6.0 pool running on
RedHat 7.3:

2/8 13:15:32 Changing activity: Idle -> Busy
2/8 13:15:33 DaemonCore: Command received via TCP from host <129.89.201.233:42077>
2/8 13:15:33 DaemonCore: received command 404 (DEACTIVATE_CLAIM_FORCIBLY), calling handler (command_handler)
2/8 13:15:33 Called deactivate_claim_forcibly()
2/8 13:15:33 Starter pid 3330 exited with status 0
2/8 13:15:33 State change: starter exited
2/8 13:15:33 Changing activity: Busy -> Idle

Can somebody explain under what circumstances a "DEACTIVATE_CLAIM_FORCIBLY
is sent and why?

Thanks,

Scott
Condor Support Information:
http://www.cs.wisc.edu/condor/condor-support/
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>