#mcollective

I've run 1k clients with 2GB memory so that should be more than enough

double-check your connectors between the instances. you may need two rather than one if that isn't resolved yet

anyone know how to easily add another MCollective client in PE?

I don't think it's straightforward, best reach out to support.

does anyone know what file is used within mcollective to determine fqdn or host name?

uses whatever your hostname is set by default, but you can also just set identity=whatever in config

Volcane: would you have any idea why on some hosts puppet pulls hostname.+domain and mco only pulls hostname?

your debian machines probably return just hostname while redhat ones do fqdn?

you know me, and i hate to say it but - all windows machines

ah

well, whatever Socket.gethostname says

figure out wtf you need to do on windows to configure the ip stack to have fqdn as hostnames :)

or just use puppet to templates to set identity=xxx.com

ya, it seems like socket.gethostname doesnt work as many people want it to. found numerous forums where it doesnt pull correct info on fqdns that are not attached to a domain, but have a dns suffix

nods, well mco really doesnt try hard - thats all it does

too many crazy OS specific shit and i didnt see why facter needed to be redeveloped for that, so okish default or configurable

puppet via facter probably get fqdn right, so just set it in the config file that way

Ya that is just what i was going to ask. I should be able to use the fqdn from facter at the beginning of a run and set the hostname to that. but i can do that in mcollective? Ive never hard set a hostname in mco.

client.cfg?

server.cfg

woops ya, thats what i meant. I assume Ill have to restart the mcollective service, once that is set?

yes

alright. tyvm Volcane

hey, all. has anyone seen issues with memory leaks in mcollective after running for awhile?

on its own no not really much, grows a bit with use then tends to settle down. but plugins can load random ruby libraries and cant speak for them - they live in the same ruby vm so leaks in them would affect mco

ah, okay. i suspected as much.

thanks