#mcollective

[mcollective-puppet-agent] parisiale closed pull request #35: MCOP-290 Handle case where we don't get a result from runonce (master...MCOP-290_cope_with_no_response) http://git.io/ALHbWw

[mcollective-puppet-agent] parisiale pushed 2 new commits to master: http://git.io/seeWoQ

mcollective-puppet-agent/master e4f7622 Richard Clamp: MCOP-290 Handle case where we don't get a result from runonce...

mcollective-puppet-agent/master 9970c97 Alessandro Parisi: Merge pull request #35 from richardc/MCOP-290_cope_with_no_response...

_rc, I don't know. ActiveMQ, I'll pastebin something....

_rc, https://gist.github.com/anonymous/decda663c6ab1... - this suggest I do not have heartbeats...

it's not suggestive one way or the other

oh sorry, I read the errors first. the first line does say you didn't enable them I see

is the heartbeats an mcollective or activemq setting?

these timeouts https://gist.github.com/anonymous/decda663c6ab1... are from the stomp gem, from when it attapts to updrage the tcp connection to a ssl one

it's an mcollective setting

We install mcollective servers using the puppet module. What is the right way to tweak server.cfg? It seems contained in the module.

mcollective::common::setting lets you tweak those configs

assuming you mean the puppetlabs one

hi, ahnyone use puppetlabs-mcollective

Im trying to use this module to setup the broker, as per module diocs

however, theres no 'middleware' parameter as described

fubada: guess you're using version 2.0

version 2.0 of the module removed it. I don't know why

yes

that sucks