Hide Forgot
Description of problem: ================================= I installed the matahari agent on a system to connect to a remote broker but it is not working. /var/log/messages has an error stating: host[7962]: mh_parse_options: Broker 'ibm-hs21-03.lab.bos.redhat.com' is not resolvable - ignoring I get the same thing when configuring the agents to use an IP address for the broker: host[7981]: mh_parse_options: Broker '10.16.44.45' is not resolvable - ignoring I tried all of the agents just to be sure. I also turned iptables off and ran tcpdump on the broker, the packets never make it there. Version-Release number of selected component (if applicable): ================================================================ v0.4.2-6 How reproducible: ================================= 100% Steps to Reproduce: ================================= 1. Install/start a matahari broker 2. Install a agent 3. Actual results: ================================= Fails to resolve Expected results: ================================= Connection to remote broker Additional info: ================================= [root@hp-dl2x170g6-02 init.d]# tail -f /var/log/messages Aug 17 15:39:31 hp-dl2x170g6-02 host[7962]: mh_parse_options: Broker 'ibm-hs21-03.lab.bos.redhat.com' is not resolvable - ignoring Aug 17 15:40:56 hp-dl2x170g6-02 host[7981]: mh_parse_options: Broker '10.16.44.45' is not resolvable - ignoring ^C [root@hp-dl2x170g6-02 init.d]# ping 10.16.44.45 PING 10.16.44.45 (10.16.44.45) 56(84) bytes of data. 64 bytes from 10.16.44.45: icmp_seq=1 ttl=63 time=0.221 ms 64 bytes from 10.16.44.45: icmp_seq=2 ttl=63 time=0.204 ms ^C --- 10.16.44.45 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1537ms rtt min/avg/max/mdev = 0.204/0.212/0.221/0.016 ms [root@hp-dl2x170g6-02 init.d]# ping ibm-hs21-03.lab.bos.redhat.com PING ibm-hs21-03.lab.bos.redhat.com (10.16.44.45) 56(84) bytes of data. 64 bytes from ibm-hs21-03.lab.bos.redhat.com (10.16.44.45): icmp_seq=1 ttl=63 time=0.321 ms 64 bytes from ibm-hs21-03.lab.bos.redhat.com (10.16.44.45): icmp_seq=2 ttl=63 time=0.194 ms [root@hp-dl2x170g6-02 init.d]# cat /etc/sysconfig/matahari # Connect to a broker on the named host # If this is not defined, agents will attempt to connect to localhost # and/or the contents of a _matahari._tcp SRV record if it exists MATAHARI_BROKER=10.16.44.45 # Connect to a broker on a non-standard port MATAHARI_PORT=49000 # Other options that all agents should observe MATAHARI_AGENT_ARGS="--reconnect=yes" # Other options that all consoles should observe # MATAHARI_CONSOLE_ARGS=... # Per agent options # host_AGENT_ARGS=... # network_AGENT_ARGS=... # Per console options # sysconfig_CONSOLE_ARGS=...
This appears to have been introduced in v0.4.2-3
Ahhh, sorry for the spam, just noticed that I failed to finish the steps to reproduce so let me try again Steps to Reproduce: ================================= 1. Install/start a matahari broker 2. Install a agent on a separate system from broker 3. Configure agent to connect to remote broker in step 1 4. Start agent 5. See 'host unresolvable' error in /var/log/messages
A related patch has been committed upstream: https://github.com/beekhof/matahari/commit/ee9336f
With no argument: [root@pcmk-1 ~]# matahari-qmf-hostd -vvv mh_domainname: Got domainname: matahariproject.org mh_connect: SRV record resolved to: www.matahariproject.org mh_connect: Trying: amqp:tcp:localhost:49000 2011-08-18 00:44:43 warning Connect failed: Connection refused 2011-08-18 00:44:43 warning Connection closed ... With a valid broker: [root@pcmk-1 ~]# matahari-qmf-hostd -vvv -b www.beekhof.net mh_connect: Trying: amqp:tcp:www.beekhof.net:49000 ... With an invalid broker: [root@pcmk-1 ~]# matahari-qmf-hostd -vvv -b www.beekhofs.net mh_parse_options: Broker 'www.beekhofs.net' is not resolvable - ignoring ...
good 2 go in v0.4.2-7
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. New Contents: 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. http://rhn.redhat.com/errata/RHBA-2011-1569.html