RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 737962 - matahari broker in /etc/sysconfig/matahari ignored
Summary: matahari broker in /etc/sysconfig/matahari ignored
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: matahari
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Russell Bryant
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-13 13:42 UTC by Dave Johnson
Modified: 2011-09-15 11:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-14 15:31:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dave Johnson 2011-09-13 13:42:00 UTC 
Description of problem:
==================================
The value for the broker of /etc/sysconfig/matahari is being ignored

***broker is up and working***
[root@agent ~]# /usr/sbin/matahari-qmf-hostd -vvv -b 10.16.64.96
mh_connect: Trying: amqp:tcp:10.16.64.96:49000
mh_os_uuid: Got uuid: ce76da54cbe7c1d9ed1d44ce00000023
mh_hostname: Got hostname: agent.test.com
mh_os_uuid: Got uuid: ce76da54cbe7c1d9ed1d44ce00000023
mh_hostname: Got hostname: agent.test.com
mainloop_add_qmf: Added source: 1
heartbeat: Updating stats: 1 5
mh_hostname: Got hostname: agent.test.com
run: Starting agent mainloop

*** can't find the broker... ***
[root@agent ~]# /usr/sbin/matahari-qmf-hostd -vvv
mh_hostname: Got hostname: agent.test.com
mh_dnsdomainname: Got dnsdomainname: 'test.com'
mh_connect: SRV query not successful: _matahari._tcp.test.com
mh_connect: Trying: amqp:tcp:localhost:49000
2011-09-13 09:24:08 warning Connect failed: Connection refused
2011-09-13 09:24:08 warning Connection  closed
2011-09-13 09:24:11 warning Connect failed: Connection refused
2011-09-13 09:24:11 warning Connection  closed

*** ...even though it is configured ***
[root@agent ~]# cat /etc/sysconfig/matahari
# Connect to a broker on the named host
# If this is not defined, agents will attempt to connect to the server specified
# by the _matahari._tcp SRV record in DNS if that exists, otherwise to localhost
MATAHARI_BROKER=10.16.64.96

# Connect to a broker on a non-standard port
#MATAHARI_PORT=49000






Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Dave Johnson 2011-09-13 13:59:58 UTC 
This was tested against v0.4.2-2....
Comment 3 Russell Bryant 2011-09-14 11:05:55 UTC 
Once I thought about this again, this is expected behavior.  /etc/sysconfig/matahari is only used when matahari is started as a service, not when you run the agent executable directly.  Can you please try starting it via the init script and verify that it works?
Comment 4 Dave Johnson 2011-09-14 15:31:56 UTC 
Yeah, this is not an issue.  Not sure what I was thinking.
Comment 5 Zane Bitter 2011-09-15 11:33:26 UTC 
I updated the man page to not imply that matahari-brokerd reads /etc/sysconfig/matahari-broker itself:

https://github.com/matahari/matahari/commit/08dd58975db6eeac53c8ccedc6a37b8e37e34bda
Note You need to log in before you can comment on or make changes to this bug.