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

Re: Trouble with "mco ping"






From: "s madathilthattantav" <s madathilthattantav accenture com>
To: markllama gmail com, kraman gmail com
Cc: users lists openshift redhat com
Sent: Thursday, December 5, 2013 9:09:25 AM
Subject: RE: Trouble with "mco ping"

Hi Mark

 

I am facing something similar now.

 

I am trying to install origin in ec2 using puppet script.The broker is up and running

 

Here is what is happening

1.       I have used nameserver  Ip as IP address for eth0 (internal ip of broker )

2.       On Broker node – I have done

 

keyfile=/var/named/example.com.key

oo-register-dns -h node1 -d example.com -n 174.129.70.68 -k ${keyfile}  ( public ip of node ,I have no elastic associated as of now to node)

                dig @127.0.0.1 node1.example.com   (resolves to public ip of node)

                ssh is enabled from broker to node

but script fails on node :Error is a pointer to DNS communication not happening between Node and Broker  L Marked in red

 

I had faced this while Installation of ose in ec2 ,but adding up tcp 61613 to the security group did the job

Ø  mco ping in broker yields no response

Ø  Mcollective is running on node –see the response for service mcollective status

 

mcollective.service - The Marionette Collective

   Loaded: loaded (/usr/lib/systemd/system/mcollective.service; enabled)

   Active: active (running) since Thu 2013-12-05 11:51:35 UTC; 2h 12min ago

Main PID: 3005 (ruby-mri)

   CGroup: name=systemd:/system/mcollective.service

           ââ3005 /usr/bin/ruby-mri /usr/sbin/mcollectived --config=/etc/mcollective/server.cfg --pidfile=/var/run/mcollective.pid

 

 

I am trying all possible stuff to get this goin since it’s a priority task –but missing something.Even tried service iptables stop !!

So kind of cluelessly debugging..Any pointers will be great!

Notice: /Stage[main]/Openshift_origin::Role::Node/Register_dns[register node dns]/Exec[Register node1.example.com]/returns: ; Communication with 10.180.194.23#53 failed: timed out

Notice: /Stage[main]/Openshift_origin::Role::Node/Register_dns[register node dns]/Exec[Register node1.example.com]/returns: could not talk to specified name server

Error: (

  echo server 10.180.194.23

  echo update delete node1.example.com A

  echo update add node1.example.com 180 A 10.170.36.171

  echo send

) | nsupdate -y example.com:tsGD77RCMf7LqLuI9CMMdTat3aHQ0A==

returned 1 instead of one of [0]

Error: /Stage[main]/Openshift_origin::Role::Node/Register_dns[register node dns]/Exec[Register node1.example.com]/returns: change from notrun to 0 failed: (

  echo server 10.180.194.23

  echo update delete node1.example.com A

  echo update add node1.example.com 180 A 10.170.36.171

  echo send

) | nsupdate -y example.com:tsGD77RCMf7LqLuI9CMMdTat3aHQ0A==

returned 1 instead of one of [0]

 

 



So yes, this points to DNS problems, and not much is going to work without DNS, so there's not much point debugging anything else until that's right.

Wherever you are running this script that has this output, it is trying to access 10.170.36.171 as the nameserver where it makes DNS updates, and that's not working. The IP and port are the same as it would be for querying the nameserver, so your node probably won't know how to connect mcollective to activemq either.

So the first question is, is that the right IP for the nameserver? If not, then wherever that IP is coming from (probably /etc/openshift/plugins.d/openshift-origin-dns-nsupdate.conf), you need to fix it.
If that's right, then you need to figure out why you can't reach it from the host, iptables is one reason; another would be if 10.180.* is your floating IP, then security group rules may apply, and you either need to adjust your security group or use an internal IP for the nameserver.
You can check whether you can reach the nameserver with:
dig whatever @10.180.194.23
If you're able to connect at all, then you can try another puppet run. Until you can reach the nameserver, you won't get far.

 

From: users-bounces lists openshift redhat com [mailto:users-bounces lists openshift redhat com] On Behalf Of Mark Lamourine
Sent: Tuesday, October 15, 2013 5:26 AM
To: Kyle Crumpton (kcrumpto)
Cc: users lists openshift redhat com
Subject: Re: Trouble with "mco ping"

 

 

 

On Mon, Oct 14, 2013 at 4:55 PM, Kyle Crumpton (kcrumpto) <kcrumpto cisco com> wrote:

Hi all,

 

 

I got to section 9. I have made a node host that is registered by DNS, installed mcollective, and started the service. 

 

I run an mco ping and receive nothing on the broker.

 

So I went to my node to check the logs and they read as: 

 

I, [2013-10-14T20:52:43.596114 #4405]  INFO -- : activemq.rb:111:in `on_connectfail' TCP Connection to stomp://mcollective broker dsx org:61613 failed on attempt 14

I, [2013-10-14T20:53:13.626790 #4405]  INFO -- : activemq.rb:96:in `on_connecting' TCP Connection attempt 15 to stomp://mcollective broker dsx org:61613

I, [2013-10-14T20:53:43.658280 #4405]  INFO -- : activemq.rb:111:in `on_connectfail' TCP Connection to stomp://mcollective broker dsx org:61613 failed on attempt 15

I, [2013-10-14T20:54:13.688968 #4405]  INFO -- : activemq.rb:96:in `on_connecting' TCP Connection attempt 16 to stomp://mcollective broker dsx org:61613

 

So I checked to make sure. Here is my config for server.cfg on the node:

 

topicprefix = /topic/

main_collective = mcollective

collectives = mcollective

libdir = /opt/rh/ruby193/root/usr/libexec/mcollective

logfile = /var/log/mcollective.log

loglevel = debug

daemonize = 1

direct_addressing = 1

registerinterval = 30

 

# Plugins

securityprovider = psk

plugin.psk = unset

 

connector = activemq

plugin.activemq.pool.size = 1

plugin.activemq.pool.1.host = broker.dsx.org

plugin.activemq.pool.1.port = 61613

plugin.activemq.pool.1.user = mcollective

plugin.activemq.pool.1.password = marionette

 

# Facts

factsource = yaml

plugin.yaml = /etc/mcollective/facts.yaml

 

 

I see that the connector is set to activemq. Any idea why it's trying to connect to stomp, and why it's failing?

 

It's using Stomp because the activemq plugin is just an optimization of stomp for activemq:

  

http://docs.puppetlabs.com/mcollective/reference/plugins/connector_activemq.html

 

I'd check too that the DNS for broker.dsx.org *from the perspective of the node host* resolves to an IP address which is routeable from the node to the broker.

 

Check that you can ping both the name and the IP address, that the firewalls between and on the broker allow inbound connections on port 61613/tcp

 

It looks like the node can't find or can't talk to the real destination.

 

________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users



 

--

----

Mark Lamourine <markllama gmail com>

Dad, Hubbie, Software Developer, System Administrator, Road Cyclist




This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. .
______________________________________________________________________________________

www.accenture.com

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users


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