Created attachment 516564 [details]
Description of problem:
Setup a kerberos server and configured the matahari broker/agents to authenticate through it. The broker would startup but when the agents where started, they always segfaulted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure matahari broker/agents to use kerberos
2. start broker
3. start matahari agent
agent seg faults
agent connects to broker
I should have also attached this which is in /var/log/messages when the seg fault occurs:
Aug 3 15:08:37 ibm-crichton-02 host: int MatahariAgent::init(int, char**, const char*): Connecting host to Qpid broker at amqp:tcp:127.0.0.1:49000
Aug 3 15:08:37 ibm-crichton-02 kernel: matahari-qmf-ho: segfault at 148 ip 00007fc62d6ec354 sp 00007fffc82dfea0 error 4 in libsigar.so[7fc62d6dd000+1e000]
Aug 3 15:08:37 ibm-crichton-02 abrt: saved core dump of pid 4802 (/usr/sbin/matahari-qmf-hostd) to /var/spool/abrt/ccpp-2011-08-03-15:08:37-4802.new/coredump (12480512 bytes)
Aug 3 15:08:37 ibm-crichton-02 abrtd: Directory 'ccpp-2011-08-03-15:08:37-4802' creation detected
Aug 3 15:08:37 ibm-crichton-02 abrtd: Package 'matahari-host' isn't signed with proper key
Aug 3 15:08:37 ibm-crichton-02 abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2011-08-03-15:08:37-4802 (res:2), deleting
Disregard everything in the original comment...this has nothing to do with Kerberos integration. I inadvertently smoke tested the brew rpms on a RHEL 6.1 server and then began immediate testing of kerberos intergration using RHEL 6.2.
The problem is sigar-1.6.5-0.2.git58097d9 which is install with RHEL 6.2 nightly builds. If you go back to RHEL 6.1, the brew rpms work as expected. If you upgrade sigar on RHEL 6.1 to use sigar-1.6.5-0.2.git58097d9, seg faults begin happening.
We've gotten sigar-1.6.5-0.2.git58097d9 tagged into the buildroot and made sure matahari was built against it. Should be good to go now.
Good to with v0.4.2-6
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
No description required
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.