#mcollective

Hi, I'm new to IRC and MCollective but I have been told here is where I could get some answers about my MCollective issues

I'm trying to connect to MCollective from my Rails App using the mcollective-client gem but I am getting the following error:

error 2014/08/06 11:49:03: pluginmanager.rb:171:in `rescue in loadclass' Failed to load Mcollective::Facts::Yaml_facts: cannot load such file -- mcollective/facts/yaml_facts.rb

aceunreal: the mcollective gem is not maintained by Puppet Labs and is quite old. You should uninstall that, and install MCollective from GitHub https://github.com/puppetlabs/marionette-collec...

jorhett: 1 they went. 2 they were talking about the mcollective-client gem

nullck: this is a better book :D http://shop.oreilly.com/product/0636920032472.do

_rc: I answer in case they look to see if someone responded. I often do that, so I assume others do.

what's different with the -client gem?

that's the one PL does release

I thought you said that no gems were supported by PL?

Nope

...?

Sorry, I don't mean you don't think that, I mean I didn't say that.

I get that. Was curious as to the clear answer. Poking around, mcollective-client but not the server?

It appears the confusing "mcollective" gem has disappeared.

confusing = old, broken

Is it the plan for it to stay fhis way (for now) ?

for now, yes. forever, no. https://tickets.puppetlabs.com/browse/MCO-405

Anyway this doesn't qualify as a bug? https://gist.github.com/anonymous/44c3d8bdb3dd7... (it exceed number of active agents) Thanks

yes and no. it stops trying to schedule any more, but it seems green started

_rc, I had an earlier run with "12", and it paused in scheduling, then it seem to schedule about 12 more, and then it was scheduling 1 everytime 1 finished (it seemed)

yeah that's the idea, to keep the concurrency where you asked it

_rc, In larger run, it was way over, and still scheduling. Sorry I didn't grab that log.

'way over'? as in it scheduled too large a batch, or it had completed a long time ago?

here's another strange one: https://gist.github.com/anonymous/e122dee2a5f5d...

it schedule 12, and then waited and suddenly scheduled 12 more.

sure

it's asking the network what state is it in

so if you run one outside of mcollective's control, there's an extra one

Well, I'm not doing actual agent run (external to this command), but I am doing "mco puppet status"

Perhaps that is being misinterpreted.

shouldn't be

[marionette-collective] ploubser pushed 2 new commits to master: http://git.io/Zjl9Lw

marionette-collective/master 52ec41d Richard Clamp: MCO-175 Document the heartbeat options in the connector pages...

marionette-collective/master 2936348 Pieter Loubser: Merge pull request #226 from richardc/MCO-175_keepalive_options...