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

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

Date: Wed, 22 Apr 2015 12:31:45 -0500 (CDT)
From: Todd L Miller <tlmiller@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Condor not spawning secondary collectors on specified ports

It's just occurred to me but does it matter that I'm using the sharedport functionality on the cm?

It might. I don't know the expected behavior of configuringshared port but then specifying a single particular one. The othersuggestion was to check if you've got HIGH_PORT and/or LOW_PORT set, whichmay be overriding your -p option.


- Todd Miller

References:
- [HTCondor-users] Condor not spawning secondary collectors on specified ports
  - From: Iain Bradford Steers
- Re: [HTCondor-users] Condor not spawning secondary collectors on specified ports
  - From: Ben Cotton
- Re: [HTCondor-users] Condor not spawning secondary collectors on specified ports
  - From: Iain Bradford Steers

Prev by Date: Re: [HTCondor-users] Condor not spawning secondary collectors on specified ports
Next by Date: Re: [HTCondor-users] Restricting execute nodes to a single group (was: (no subject))
Previous by thread: Re: [HTCondor-users] Condor not spawning secondary collectors on specified ports
Next by thread: Re: [HTCondor-users] Condor not spawning secondary collectors on specified ports
Index(es):
- Date
- Thread