[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] How to investigate matchmaking internals?
- Date: Fri, 15 Sep 2017 10:44:51 -0500
- From: Greg Thain <gthain@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] How to investigate matchmaking internals?
On 09/15/2017 09:34 AM, Anthony R Tiradani wrote:
to add, that StartLog showed in that case no activity - not even
rejecting requests that the negotiator had matched??
There are a number of reasons a job could match but not make it to the
startd. The ShadowLog or SchedLog may yield some clues.
Common problems include:
Firewall between schedd and startd
Condor permission problem on startd
Another unrelated problem that looks like this problem is
Job does actually start running under the startd, but exits immediately
for some reason, and goes back to idle. Running condor_q periodically
never catches it in the "R"unning state, so it looks like it doesn't
match. The job log file shows what is going on in this case.