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

[HTCondor-users] CCB private address

Hi all,

I'm currently building a test setup where the central manager runs in a docker container and a schedd runs in a separate container (potentially on a different machine). The workers are running somewhere else, where incoming connections won't be allowed. So using a CCB seemed like the way to go. I'm using version 9.0.15.

I'm still a bit new to HTCondor, so I'm not sure if I understand it correctly. But I think the problem is that the private address of the CCB is not advertised.

The collector and negotiator advertise their addresses correctly:
$ condor_status -collector -l
MyAddress = "<>"

$ condor_status -negotiator -l
MyAddress = "<>"

And the scheduler advertises the CCB, but not the private address:
$ condor_status -schedd -l
MyAddress = "<>"

This leads to the negotiator being unable to connect to the schedd:
$ cat /var/log/condor/NegotiatorLog
08/03/22 10:42:30 Failed to reverse connect to schedd cobald@cobaldtardis via CCB. 08/03/22 10:42:30 Failed to connect to cobald@cobaldtardis (<>)

On my test setup I can allow incoming connections and leave out the CCB. If I do that, everything works perfectly. Just adding the CCB breaks the setup.
So, my question is: shouldn't the private address of the CCB be advertised?
And if this behavior is intended, why is 'PrivNet' included at all?

Thanks for the help,