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

Re: [HTCondor-users] HTCondor-CE behind NAT



Thank you Greg for your tip! 

To elaborate more on your suggestion, I need to set TCP_FORWARDING_HOST on HTCondor-Ce server or inside a config file under /etc/condor-ce/config.d?

And the value is the internal ip of condor-ce?

As currently the public IP is configured on the Cisco ASA firewall static NAT to internal HT-Condor-Ce.

Thank you



Regards,
Saad
Ext. 2229

Sent from my iPhone

On 13 Mar 2024, at 9:17âPM, Greg Thain via HTCondor-users <htcondor-users@xxxxxxxxxxx> wrote:

ï
On 3/12/24 10:22, Saadallah Itani wrote:

Dears,

 

 

> âââââââ[mmascher@vocms0205 tmp]$ grep ce1.hpc4l.org CGAHPWorkerLog.gfactory | tail -n 1

> 03/08/24 10:51:46 [64908] Error connecting to schedd ce1.hpc4l.org: CEDAR:6001:Failed to connect to <192.168.28.130:9619?addrs=192.168.28.130-9619&alias=ce1.hpc4l.org&noUDP&sock=schedd_4736_ad21>â

 


Hi Saddallah:

It looks like the factory is trying to connect to the private address (192.168.x.y), which isn't going to work.  We need to get the schedd to advertise the correct address.  I think if you set TCP_FORWARDING_HOST to the address the NAT exposes to the world, I think it should be able to connect.

-greg


_______________________________________________
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/

Attachment: smime.p7s
Description: S/MIME cryptographic signature