#mcollective

Hey Volcane: my mco ping commands returns lot of duplicate hosts, and those hosts not even live anymore. they been terminated last week.

Can you please give me any idea how to fix that. I want to use mcollective as my main framework for other tools as well, but seems like its not giving you the trustworthy information

ping replies are actual mcollectived instances replying, no caching or anything like that

you probably have nodes with miss configured identity

or multiple instances running on nodes with miss configured identity etc

okay… I am facing issue now with just one host, which is showing many times.

and this host is not live, its been terminated like 2-3 weeks back...

Volcane: anything in activemq queues?

nope

do mco inventory on the node and see its ip etc

IP of the host is different, as showing in mco ping

mco ping shows the hostname of AWS instance which is like ip-10-30-166-229.us-west-2.compute.internal

it suppose to have IP:10.30.166.229

but on mco inventory it shows different IP

yeah like i said, you probably have nodes with miss configured identities somehow

how can i fix that,

you now know which one, so go look?

all of my nodes have same configs, i am managing them via puppet

thats still what is happening

you can either keep saying its all fine, or believe your eyes and go look?

yeah… I am taking a look at that host now.. But i am wonding why its happening just on one host, as all of my hosts have same mco configs

identity is set using identity=... in server.cfg or it gets it from your TCP stack

TCP stack is used when identity isnt set

ok

its getting set using my tcp stack

i am not setting it up in my server.cfg

can you please suggest, if its a good idea to setup identity in server.cfg

?

ruby -r socket -e 'puts Socket.gethostname'

is what it would use by default

if thats no good, set it

ok

seems like problem is with all the hosts

whenever I am running mco inventory against the duplicate host, its shows me different IP

Thanks Volcane: identity option fixed the issue

I am not seeing duplicate nodes anymore… :)