Re: [HTCondor-users] Condor not spawning secondary collectors on specified ports

[Brian Bockelman <bbockelm@xxxxxxxxxxx>]

Hi Iain,

Yup - that's the problem I think.

When shared port is enabled, it's assumed all public traffic will go over shared_port; this overrides the specified port on the CLI.

The daemon does keep a randomly-assigned network port open for internal communications (this is what you're seeing), but that's not meant for the worker nodes to connect through.

Brian

> On Apr 22, 2015, at 12:15 PM, Iain Bradford Steers <iain.steers@xxxxxxx> wrote:
> 
> Hi Ben,
> 
> I've attached the start-up section to the bottom of mail(*).
> 
> It's just occurred to me but does it matter that I'm using the shared port functionality on the cm?
> 
> I've just remember that it was set-up as shared-port but I'm outside of work now..
> 
> Cheers, Iain
> 
> (*)
> 04/22/15 13:30:56 Using config source: /etc/condor/condor_config
> 04/22/15 13:30:56 Using local config sources:
> 04/22/15 13:30:56    /etc/condor/config.d/10_security.config
> 04/22/15 13:30:56    /etc/condor/config.d/11_fairshares.config
> 04/22/15 13:30:56    /etc/condor/config.d/14_network.config
> 04/22/15 13:30:56    /etc/condor/config.d/22_manager.config
> 04/22/15 13:30:56    /etc/condor/config.d/23_ganglia.config
> 04/22/15 13:30:56    /etc/condor/condor_config.local
> 04/22/15 13:30:56 config Macros = 350, Sorted = 350, StringBytes = 20999, TablesBytes = 12688
> 04/22/15 13:30:56 CLASSAD_CACHING is ENABLED
> 04/22/15 13:30:56 Daemon Log is logging: D_ALWAYS D_ERROR
> 04/22/15 13:30:56 SharedPortEndpoint: waiting for connections to named socket 1983164_317e
> 04/22/15 13:30:56 DaemonCore: command socket at <128.142.152.233:9618?noUDP&sock=1983164_317e>
> 04/22/15 13:30:56 DaemonCore: private command socket at <128.142.152.233:9618?noUDP&sock=1983164_317e>
> 04/22/15 13:30:56 In ViewServer::Init()
> 04/22/15 13:30:56 In CollectorDaemon::Init()
> 04/22/15 13:30:56 In ViewServer::Config()
> 04/22/15 13:30:56 In CollectorDaemon::Config()
> 04/22/15 13:30:56 ABSENT_REQUIREMENTS = None
> 04/22/15 13:30:56 OfflineCollectorPlugin::configure: no persistent store was defined for off-line ads.
> 04/22/15 13:30:56 Will forward ads on to View Server condorcm1.cern.ch
> 04/22/15 13:30:56 enable: Creating stats hash table
> 04/22/15 13:30:56 Enabling CCB Server.
> 04/22/15 13:30:56 m_reconnect_fname = /var/lib/condor/spool/128.142.152.233-9618.ccb_reconnect
> 
> ________________________________________
> From: HTCondor-users [htcondor-users-bounces@xxxxxxxxxxx] on behalf of Ben Cotton [ben.cotton@xxxxxxxxxxxxxxxxxx]
> Sent: 22 April 2015 17:18
> To: HTCondor-Users Mail List
> Subject: Re: [HTCondor-users] Condor not spawning secondary collectors on specified ports
> 
> On Wed, Apr 22, 2015 at 6:58 AM, Iain Bradford Steers
> <iain.steers@xxxxxxx> wrote:
>> Anyone got any suggestions, have I perhaps got a typo on the collector
>> spawning that you can spot.
> 
> Your config looks good to me. I can't reproduce the issue with 8.3.2
> or 8.3.5. If the port were in use, the condor_collector process would
> exit, so that's not the problem. On mine, I see the process still
> using the randomly-selected port in addition to the specified port,
> but the main collector does that, too.
> 
> Can you share one of your CollectorXLog files (or at least the part
> where it starts up)?
> 
> --
> Ben Cotton
> main: 888.292.5320
> 
> Cycle Computing
> Better Answers. Faster.
> 
> http://www.cyclecomputing.com
> twitter: @cyclecomputing
> _______________________________________________
> 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/
> 
> _______________________________________________
> 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/