[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Windows ignoring HIGHPORT/LOWPORT?
- Date: Fri, 12 Feb 2016 16:36:45 -0500
- From: Ben Cotton <ben.cotton@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Windows ignoring HIGHPORT/LOWPORT?
On Fri, Feb 12, 2016 at 2:57 PM, Todd Tannenbaum <tannenba@xxxxxxxxxxx> wrote:
> For your scenario below, I am curious if setting IN_LOWPORT and IN_HIGHPORT
> instead of setting LOWPORT and HIGHPORT respectively solves the problem....
I suggested that and it doesn't appear to make a difference.
For example (from the MasterLog this time):
02/12/16 11:36:49 get_port_range - (IN_LOWPORT,IN_HIGHPORT) is (10000,25100).
02/12/16 11:36:49 Sock::bindWithin - bound to 247...
02/12/16 11:36:49 LISTEN <172.20.130.210:247> fd=608
02/12/16 11:36:49 InitCommandSocket(IPv4, -1, want UDP, fatal errors)
02/12/16 11:36:49 Daemoncore: Listening at <0.0.0.0:247> on TCP
(ReliSock) and UDP (SafeSock).
02/12/16 11:36:49 DaemonCore: command socket at
02/12/16 11:36:49 DaemonCore: private command socket at
> 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.
I think shared_port with a defined port argument might be the
workaround here for now, but I didn't want to just silently work
around it if it's a real bug.
Better Answers. Faster.