[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Windows ignoring HIGHPORT/LOWPORT?

Hi Ben,

For your scenario below, I am curious if setting IN_LOWPORT and IN_HIGHPORT instead of setting LOWPORT and HIGHPORT respectively solves the problem....

Personally I've never liked LOWPORT/HIGHPORT, since I'd bet that 95% of folks really only care about incoming connections (listen port) which means better handled via IN_LOWPORT and IN_HIGHPORT.

Hopefully as we move to having the shared_port on by default everywhere, nobody will ever have to think about these low-level knobs again.


On 2/12/2016 11:51 AM, Ben Cotton wrote:
One of our customers noticed their Windows machines don't seem to be
respecting HIGHPORT/LOWPORT settings, in that the condor_startd ends
up listening on a port outside that range. This is a problem, since
the hosts are behind a firewall with port restrictions that match the

 From the StartLog:
02/12/16 10:15:20 Daemoncore: Listening at <> on TCP
(ReliSock) and UDP (SafeSock).
02/12/16 10:15:20 DaemonCore: command socket at
02/12/16 10:15:20 DaemonCore: private command socket at

The host has the following defined:
HIGHPORT = 25100
LOWPORT = 10000
(shared port is not in use. Version 8.4.3)

After a few restarts, the startd ends up listening within the desired
range. Digging through the code, I saw comments referencing
https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4711 . I'm not
sure if the behavior here is related or not. Is disabling
BIND_ALL_INTERFACES and binding to a single interface a reasonable
solution here?


Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132                  Madison, WI 53706-1685