Bug 707222 - [RFE] wallaby - Collector in SharedPort feature
Summary: [RFE] wallaby - Collector in SharedPort feature
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor-wallaby-base-db
Version: Development
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-24 12:59 UTC by Lubos Trilety
Modified: 2016-05-26 20:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 20:04:09 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Lubos Trilety 2011-05-24 12:59:56 UTC
Description of problem:
SharedPort feature should also set Collector daemon to use shared port, for that following parameters have to be set properly:
COLLECTOR_HOST
COLLECTOR_ARGS
(SHARED_PORT_ARGS)

where 
 - COLLECTOR_HOST could be set to '$(CONDOR_HOST):<port>?sock=collector'
 - COLLECTOR_ARGS is needed only on machine with running Collector, but can be set
also on other machines, they simply ignore it. It could be set to '-sock
collector'
 - probably also SHARED_PORT_ARGS has to be set to assure that shared port use particular port, which is needed in COLLECTOR_HOST setting. It could be set for example to '-p 4080'

Version-Release number of selected component (if applicable):
condor-wallaby-base-db-1.12-1

Comment 3 Timothy St. Clair 2011-12-05 20:16:48 UTC
The following is an example

All nodes will need:
USE_SHARED_PORT=True
SHARED_PORT_ARGS = "-p 9620"
DAEMON_LIST = $(DAEMON_LIST),SHARED_PORT
SHARED_PORT_DEBUG = D_FULLDEBUG
DAEMON_SOCKET_DIR = /tmp/$(USERNAME)-condor-test-sock
COLLECTOR_HOST = $(CONDOR_HOST):9620?sock=collector

Collector will need ^above^ +:
COLLECTOR_ARGS = -sock collector

Comment 4 Anne-Louise Tangring 2016-05-26 20:04:09 UTC
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.


Note You need to log in before you can comment on or make changes to this bug.