#mcollective

hello

can someone tell me what is it: Failed to handle message: incompatible marshal file format (can't be read)

base64 was to yes

k :)

Hello Volcane, could you consider publishing a new version of the snipper gem on rubygems.org ? This would be handy.

lofic: done

thanks

Hi, I have installed mcollective (version 2.8.1 with ssl and rabbitmq 3.2.4, OS = Ubuntu 14.04). It seems to work fine but I have notciced that: if I use the public key /etc/mcollective/ssl/<name>.pem for the client (plugin.ssl_client_public parameter), I must have the same public in /etc/mcollective/ssl/clients/ the server (it's logical), but with exactly the same name (ie <name>.pem).

If the filename is not the same (but it's the same content), it doesn't work.

That's correct

My question: is it the normal behavior?

yes

Ah. :)

Ok. I thought that the filename could be different in fact.

Ok, so all is normal. Thx _rc. :)

Hi there, i'm having a problem with systemd on debian Jessie and mcollective-service plugin. Anyone have seen this? The service restarted with mco (ntp in my pastebin example) becomes owned by the mcollective.service, http://pastebin.com/RZY0wNUH

pbrideau: I've had a lot of issues with jessie's chosen way to make systemd and sysv "compatible" with one another from the CLI

torrancew: did you figure a way to fix it?

I've not even tackled the mco side yet, pbrideau

mostly the puppet side

we actually decided to backburner the migration for now, given how many services were troublesome

too many more critical things happening ATM

a lot of it came down to overriding the provider for a given service

I suspect that mco is probably triggering the sysv wrapper scripts via puppet, instead of systemctl

I see... Well, we are currently building a new infrastructure and it was our way to test jessie... I guess we won't have mcollective in this new infrastructure for now... Or i'll try to go deeper into it when the release of the new environment will be completed... Thanks for your inputs torrancew

pbrideau: np. if you can configure the provider mco is choosing from puppet, it may help clear things up