Sorry, slack of me: *Running:* * * mco puppet -v runall 2
*Agent Config:* * * [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates [agent] server = puppetmaster ca_server = puppetmaster report = true *And as I am using Debian, /etc/default/puppet:* * * # Defaults for puppet - sourced by /etc/init.d/puppet # Enable puppet agent service? # Setting this to "yes" allows the puppet agent service to run. # Setting this to "no" keeps the puppet agent service from running. START=no # Startup options DAEMON_OPTS="" *Server Config:* * * [main] logdir = /var/log/puppet vardir = /var/lib/puppet ssldir = /var/lib/puppet/ssl rundir = /var/run/puppet factpath = $vardir/lib/facter [master] certname = training-puppetmaster.plus.net ca = true pluginsync = true manifest = $confdir/manifests/unknown_environment.pp modulepath = $confdir/modules ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY [agent] server = puppetmaster ca_server = puppetmaster [production] manifest = /local/puppet/env/$environment/manifests/site.pp manifestdir = /local/puppet/env/$environment/manifests *The error message is in the output of mco, puppet. Copied verbatim:* * * root@training-puppetmaster:~# mco puppet -v runall 2 2013-04-12 11:37:05: Running all nodes with a concurrency of 2 2013-04-12 11:37:05: Discovering enabled Puppet nodes to manage Discovering hosts using the mc method for 3 second(s) .... 2 2013-04-12 11:37:08: Found 2 enabled nodes Discovering hosts using the mc method for 3 second(s) .... 0 2013-04-12 11:37:15: training-puppetmaster schedule status: Started a background Puppet run using the 'puppet agent --onetime --daemonize --color=false' command 2013-04-12 11:37:21: training-node1 schedule status: execution expired Thanks Josh On Friday, April 12, 2013 10:55:51 AM UTC+1, R.I. Pienaar wrote: > > > > ----- Original Message ----- > > From: "Josh" <[email protected] <javascript:>> > > To: [email protected] <javascript:> > > 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.
