Re: [HTCondor-users] FULL_HOSTNAME issue with multiple NIC

[Bockjoo Kim <bockjoo@xxxxxxxxxxxx>]

Hi Todd,
If I add these
NETWORK_INTERFACE = <public IP>
BIND_ALL_INTERFACES=FALSE
PRIVATE_NETWORK_INTERFACE = <private IP>
PRIVATE_NETWORK_NAME = <private hostname>
to the condor-ce condor_config file which uses the port 9619 as the 
collector port,
collector does not listen to 9619:

[root@cms ~]# netstat -ntl | grep 96
tcp        0      0 0.0.0.0:9618 0.0.0.0:*                   LISTEN
tcp        0      0 128.227.253.206:9620 0.0.0.0:*                   LISTEN

So, it does not work for me.
Thanks,
Bockjoo
On 4/23/14 4:35 PM, Todd Tannenbaum wrote:
> On 4/22/2014 4:15 PM, Bockjoo Kim wrote:
> > Hi,
> > I installed htcondor via the OSG on a machine that has a private
> > hostname with the public hostname.
> > /bin/hostname -f within the machine shows the private hostname
> > and yet the machine is known via the public hostname from outside.
> > This is the way every single machine we have.
> >
> > But it looks like FULL_HOSTNAME is not respected by condor-ce:
> > Even though I updated FULL_HOSTNAME in all the relevant config files
> > with the
> > hardcoded public hostname, it looks like condor-ce
> > is using its internal full hostname information
> > instead of the superseding config file and it's picking up our priavate
> > hostname
> > in some internal part of the htcondor (also known as condor-ce within
> > OSG.).
> >
> > I think this is a bug in htcondor. I have seen a similar error on the
> > google
> > and am not sure why this bug is not fixed or if fixing it conflicts
> > other solved issue.
> >
> > I had to set the hostname of the CE to the public hostname to make the
> > collector listen to the port 9619.
> > While this works, considering our automated cluster manage system, this
> > is not desirable.
> > So, I am wondering if there is anyway to override FULL_HOSTNAME
> > through the condor config files.
> > Thanks,
> > Bockjoo
>
> Hi Bockjoo -
>
> Re the above, ultimately what do you want to accomplish?  I ask 
> because I am wondering if you climbed up the wrong tree by struggling 
> with hostname and FULL_HOSTNAME etc.  Usually folks deal with 
> public/private network setups via config knobs 
> PRIVATE_NETWORK_INTERFACE and PRIVATE_NETWORK_NAME (and perhaps 
> NETWORK_INTERFACE as well), and do not need to mess around with 
> hostnames.
>
> Take a look in the Manual at
>   http://goo.gl/KBI2fH
> I realize that section of the manual is not as clear as it could be, 
> but hopefully it helps out.  If not, feel free to ask here.
>
> Also be aware that google often turns up posts or blog entries from 
> years ago.  HTCondor development is pretty active; it sees a new 
> release almost every month, and about 40 commits each week... eg
>   https://github.com/htcondor/htcondor/graphs/commit-activity
>   https://htcondor-wiki.cs.wisc.edu/index.cgi/timeline
> Limitations or bugs discussed two years ago may be yesterdays news...
>
> regards,
> Todd
>
>
> > _______________________________________________
> > HTCondor-users mailing list
> > To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx 
> > with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> >
> > The archives can be found at:
> > https://lists.cs.wisc.edu/archive/htcondor-users/