----- Original Message ----- > From: "Josh" <[email protected]> > To: [email protected] > Sent: Friday, April 12, 2013 10:33:17 AM > Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled > > On Friday, April 12, 2013 10:13:28 AM UTC+1, R.I. Pienaar wrote: > > > you do not need to have puppet running for the agent to work, just stop it > > entirely and then trigger runs through mcollective - in that setup it will > > happily pass custom arguments like --noop or --no-noop etc > > > > Right, I was kind of hoping that would be how it works but I still get the > message "execution expired" back from the node ... what is that even meant > to mean? If you compare the output from my node and my puppetmaster (where > I am running mco from): > > 2013-04-12 10:31:45: training-puppetmaster schedule status: Started a > background Puppet run using the 'puppet agent --onetime --daemonize > --color=false --no-noop' command > 2013-04-12 10:31:51: training-node1 schedule status: execution expired > > Is that just what I should be expecting? >
no idea - you're not showing us what command you run, your configs, what logs these are from etc. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
