Yes, I had --no-client and listen = true in puppet.conf. With these
settings the agent does not respond to MCollective calls.
On Friday, February 15, 2013 5:29:44 PM UTC+2, Felix.Frank wrote:
>
> Hi,
>
> have you made sure you pass the --listen option alongside --no-client?
>
> On 02/14/2013 11
There is a ignoreschedules option for puppet agent
(http://docs.puppetlabs.com/references/latest/configuration.html#ignoreschedules),
but it does not seem to work. Even if it is set to true the agent is being
run every "runinterval" seconds.
On Thursday, February 14, 2013 12:21:39 PM UTC+2, An
Hi,
have you made sure you pass the --listen option alongside --no-client?
On 02/14/2013 11:21 AM, Andriy Yurchuk wrote:
> This works, but this disables the ability to push configs via
> MCollective, i.e. mco puppet runall/runonce do not work.
>
> On Wednesday, February 13, 2013 5:51:56 PM UTC+2
This works, but this disables the ability to push configs via MCollective,
i.e. mco puppet runall/runonce do not work.
On Wednesday, February 13, 2013 5:51:56 PM UTC+2, Vaidas Jablonskis wrote:
>
> You would have to run your agent daemon wiht '--no-client' parameter. See
> 'man puppet.conf'.
>
>
You would have to run your agent daemon wiht '--no-client' parameter. See
'man puppet.conf'.
On Wednesday, 13 February 2013 13:49:06 UTC, Andriy Yurchuk wrote:
>
> I need puppet agent daemon running because I need to access agent's REST
> API (http://docs.puppetlabs.com/guides/rest_api.html#the-
