Re: [HTCondor-users] not starting jobs in condor ver 8.3.6

[Todd L Miller <tlmiller@xxxxxxxxxxx>]

> I hope you can figure out what I need to change to my my condor jobs to 
> start Thanks for looking in to my issue

	From the negotiator log:

07/02/15 10:45:37 Phase 4.1:  Negotiating with schedds ...
07/02/15 10:45:37   Negotiating with cosy11@xxxxxxxxxxx at 
<198.125.163.121:9601?addrs=10.200.60.19-9601&noUDP>
07/02/15 10:45:37 0 seconds so far
07/02/15 10:45:37 SECMAN: FAILED: Received "DENIED" from server for user 
unauthenticated@unmapped using method (no authentication).
07/02/15 10:45:37 ERROR: SECMAN:2010:Received "DENIED" from server for 
user unauthenticated@unmapped using method (no authentication).
07/02/15 10:45:37     Failed to send NEGOTIATE command to 
cosy11@xxxxxxxxxxx (<198.125.163.121:9601?addrs=10.200.60.19-9601&noUDP>)
07/02/15 10:45:37   Error: Ignoring submitter for this cycle

	The schedd says:

07/02/15 10:45:37 (pid:1818) PERMISSION DENIED to unauthenticated@unmapped 
from host 10.200.60.19 for command 416 (NEGOTIATE), access level 
NEGOTIATOR: reason: NEGOTIATOR authorization policy contains no matching 
ALLOW entry for this request; identifiers used for this host: 
10.200.60.19,cond-b-7212ad3c-320d-4981-9d09-b535053abab8.novalocal, 
hostname size = 1, original ip address = 10.200.60.19 07/02/15 10:45:37 
(pid:1818) DC_AUTHENTICATE: Command not authorized, done!

	Which is what I was trying to fix with my earlier suggestion (B); 
sorry that I asked you to turn the wrong knobs.  Try adding 
ALLOW_NEGOTIATOR and ALLOW_NEGOTIATOR_SCHEDD to your config, setting each 
to 10.200.60.*, or the specific machine hosting the negotiator 
(10.200.60.19).

	Note that HTCondor thinks that 10.200.60.19 is 
cond-b-7212ad3c-320d-4981-9d09-b535053abab8.novalocal, not 
oswrk121.lns.mit.edu.  This makes sense, because (at least for me) 
oswrk121.lns.mit.edu looks up as 198.125.163.121.


	I'm pretty sure what's going on is a disagreement between 
different parts of HTCondor about how to handle TCP_FORWARDING_HOST. 
If you look at the string the negotiator said it was trying to connect to,

<198.125.163.121:9601?addrs=10.200.60.19-9601&noUDP>

you can see that the first and second IP addresses are not the same; the 
first is the TCP_FORWARDING_HOST and the second is the IP address that 
HTCondor found on the machine.

- ToddM