Mcollective/Puppet Connector

[Worker Bee]

When attempting to execute the mcollective puppet plugin:

# mco puppet runonce -v

    aixl                                   : execution expired
    aixj                                   : execution expired


I get an error, 'execution expired' on some hosts.  However, these hosts respond via mco ping and, I have verified the date/time on the servers.  The puppet agent is also working fine with the puppetmaster.  Can anyone shed any light on this?

Thanks!
Bee

[R.I.Pienaar]

----- Original Message -----
> From: "Worker Bee" <beewo...@gmail.com>
> To: puppet...@googlegroups.com
> Sent: Tuesday, March 5, 2013 9:26:06 PM
> Subject: [Puppet Users] Mcollective/Puppet Connector
>
> When attempting to execute the mcollective puppet plugin:
>
> # mco puppet runonce -v
>
> aixl : execution expired
> aixj : execution expired

for whatever reason it took more than 5 seconds to just get puppet
started - it daemonizes and dissociates from mcollectived on run
so this really should not take 5 seconds unless your machines are very
very slow etc?

did you change any of the mco puppet agent configuration?

[Worker Bee]

Ahh...

We do not run the puppet agents as daemons, we just call the agent manually when needed.

Is there a way I can increase this timeout?

Thanks!

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[R.I.Pienaar]

----- Original Message -----
> From: "Worker Bee" <beewo...@gmail.com>
> To: puppet...@googlegroups.com
> Sent: Tuesday, March 5, 2013 9:31:10 PM
> Subject: Re: [Puppet Users] Mcollective/Puppet Connector
>
> Ahh...
>
> We do not run the puppet agents as daemons, we just call the agent manually
> when needed.

that's what the mco agent does too - so back to the questions, are your
machines particularly slow/busy? did you change the config in server.cfg
or /etc/mcollective/plugin.d/puppet.cfg?

> Is there a way I can increase this timeout?

you'd need to adjust the DDL files everywhere, best to find out what the
cause is

[Worker Bee]

Ok, thanks.

I did not change anything in the config files other than to add the required settings for the connector in server.cfg

#Puppet Plugin
plugin.puppet.command = /opt/puppet/bin/puppet agent --test
plugin.puppet.splay = false
plugin.puppet.daemonize = true
plugin.puppet.splaylimit = 30
plugin.puppet.config = /etc/puppet/puppet.conf


connector = stomp
plugin.stomp.host = puppet05
plugin.stomp.port = 61613
plugin.stomp.user = mcollective
plugin.stomp.password = secret


I do not even have this file :/etc/mcollective/plugin.d/puppet.cfg   ????

I do not think my servers are particularly slow, but then again, I have other servers that are answering just fine...

Thanks SO MUCH!

[Worker Bee]

Am I looking at the wrong Configuration Guide?
http://docs.puppetlabs.com/mcollective/reference/basic/configuration.html

I do not see anything about the puppet.cfg file.

Also, my puppetmaster and my ActiveMQ are on seperate boxes...

On Tue, Mar 5, 2013 at 4:35 PM, R.I.Pienaar <r...@devco.net> wrote:

[R.I.Pienaar]

----- Original Message -----
> From: "Worker Bee" <beewo...@gmail.com>
> To: puppet...@googlegroups.com
> Sent: Tuesday, March 5, 2013 9:40:58 PM
> Subject: Re: [Puppet Users] Mcollective/Puppet Connector
>

> Ok, thanks.
>
> I did not change anything in the config files other than to add the
> required settings for the connector in server.cfg
>
> #Puppet Plugin
> plugin.puppet.command = /opt/puppet/bin/puppet agent --test
> plugin.puppet.splay = false
> plugin.puppet.daemonize = true
> plugin.puppet.splaylimit = 30
> plugin.puppet.config = /etc/puppet/puppet.conf

these are not required parameters for the connector :)

You're specifically changing the way puppet is being run to use
--test thus causing it to not daemonize and dissociate from the
running mcollectived.

Take away your plugin.puppet.command setting

[Worker Bee]

Ok, thanks!

I also found this...
#plugin.puppet.timeout = 20

Will this increase the period of time it waits for execution against the puppetmaster?

[R.I.Pienaar]

----- Original Message -----
> From: "Worker Bee" <beewo...@gmail.com>
> To: puppet...@googlegroups.com
> Sent: Tuesday, March 5, 2013 10:02:37 PM
> Subject: Re: [Puppet Users] Mcollective/Puppet Connector
>

> Ok, thanks!
>
> I also found this...
> #plugin.puppet.timeout = 20
>
> Will this increase the period of time it waits for execution against the
> puppetmaster?

no, you have to not set it to use --test, for any reasons, just dont do it.

[Worker Bee]

Ok, Thanks!!!

:)