Puppet users - Sep 2011 - issues with puppet service and mco puppetd

Ok so we are running puppet agent via cron jobs and have the puppet
agent set to the following:
   service { "pe-puppet-agent":
     enable     => false,
     ensure     => stopped,
     hasstatus  => true,
     hasrestart => true,
  }
so i need to get something out to all of out servers urgently and used
MCO to run "mco puppetd runonce -I mycomputer" and that works and all,
but on the client side that runs "/opt/puppet/bin/ruby1.8 /opt/puppet/
sbin/puppetd --onetime --splaylimit 120 --splay" which in turns starts
the puppet agent service and then it reads my manifest and says that
agent should be stopped. So how can i get MCO to work like i need it
to, but also not interfere with the "ensure => stopped" of my
manifest?

FYI, everytime that i run the MCO command, i get "Caught TERM; calling
stop", which i am assuming is due to thge fact that it is stopping the
service.

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

You don''t actually need the ensure => stopped. If you are set to
enable => false, that''s good enough - ensure => stopped will kill
the daemon every time it starts.

-Eric

-- 
Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and
23rd in Portland, OR.

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

On Monday, September 26, 2011 at 5:13 PM, mbargar wrote:
> Ok so we are running puppet agent via cron jobs and have the puppet
> agent set to the following:
>  service { "pe-puppet-agent":
>  enable => false,
>  ensure => stopped,
>  hasstatus => true,
>  hasrestart => true,
>  }
> so i need to get something out to all of out servers urgently and used
> MCO to run "mco puppetd runonce -I mycomputer" and that works and
all,
> but on the client side that runs "/opt/puppet/bin/ruby1.8 /opt/puppet/
> sbin/puppetd --onetime --splaylimit 120 --splay" which in turns starts
> the puppet agent service and then it reads my manifest and says that
> agent should be stopped. So how can i get MCO to work like i need it
> to, but also not interfere with the "ensure => stopped" of my
> manifest?
> 
> FYI, everytime that i run the MCO command, i get "Caught TERM; calling
> stop", which i am assuming is due to thge fact that it is stopping the
> service.
> 
> -- 
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com
(mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
(mailto:puppet-users+unsubscribe@googlegroups.com).
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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

----- Original Message -----
> Ok so we are running puppet agent via cron jobs and have the puppet
> agent set to the following:
>    service { "pe-puppet-agent":
>      enable     => false,
>      ensure     => stopped,
>      hasstatus  => true,
>      hasrestart => true,
>   }
> so i need to get something out to all of out servers urgently and
> used MCO to run "mco puppetd runonce -I mycomputer" and that
works and
> all, but on the client side that runs "/opt/puppet/bin/ruby1.8
> /opt/puppet/ sbin/puppetd --onetime --splaylimit 120 --splay" which in
turns
> starts the puppet agent service and then it reads my manifest and says that
> agent should be stopped. So how can i get MCO to work like i need it
> to, but also not interfere with the "ensure => stopped" of my
> manifest?
> 
> FYI, everytime that i run the MCO command, i get "Caught TERM;
> calling stop", which i am assuming is due to thge fact that it is
stopping
> the service.
the RC script is incorrectly reporting any puppet instance as one started using
the RC script, I don''t notice this with the opensource RPM distro maybe
its something
PE specific.

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

OK  so you will have to for give me here. I am not sure what RC
means,
but is what you''re saying is that the PE version puppet is likely
causing the issue?

Eric,
  I added the ensure => stopped as these machine no do get rebooted
that often and enable => false only works to stop the service on boot
up. We dont want the nodes checking in every 30 minutes and we want
it
us the cron jobs.


On Sep 26, 5:20 pm, "R.I.Pienaar" <r...@devco.net>
wrote:
> ----- Original Message -----
> > Ok so we are running puppet agent via cron jobs and have the puppet
> > agent set to the following:
> >    service { "pe-puppet-agent":
> >      enable     => false,
> >      ensure     => stopped,
> >      hasstatus  => true,
> >      hasrestart => true,
> >   }
> > so i need to get something out to all of out servers urgently and
> > used MCO to run "mco puppetd runonce -I mycomputer" and that
works and
> > all, but on the client side that runs "/opt/puppet/bin/ruby1.8
> > /opt/puppet/ sbin/puppetd --onetime --splaylimit 120 --splay"
which in turns
> > starts the puppet agent service and then it reads my manifest and says
that
> > agent should be stopped. So how can i get MCO to work like i need it
> > to, but also not interfere with the "ensure => stopped"
of my
> > manifest?
>
> > FYI, everytime that i run the MCO command, i get "Caught TERM;
> > calling stop", which i am assuming is due to thge fact that it is
stopping
> > the service.
>
> the RC script is incorrectly reporting any puppet instance as one started
using
> the RC script, I don''t notice this with the opensource RPM distro
maybe its something
> PE specific.- Hide quoted text -
>
> - Show quoted text -
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> OK  so you will have to for give me here. I am not sure what RC
> means, but is what you''re saying is that the PE version puppet is
likely
> causing the issue?
the script in /etc/init.d (or your OS equivelant) that starts puppet and
is used to check it''s status.

if puppet is running - but have not been started using the service - 
then the service script should not report it as running. 

This is with the opensource rpm:

# puppet agent --test

now switch to a different window while that runs:

# service puppet status
puppetd is stopped


yours should do the same

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

OK here is my output for the different commands with "puppet agent --
test" running:

# service pe-puppet-agent status
* could not access PID file for agent

# service --status-all | grep puppet
[ - ] pe-puppet-agent

# ps aux | grep puppet
/opt/puppet/bin/ruby1.8 /usr/local/bin/puppet agent --test

-----------------------------------------
Now when i run "mco puppetd runonce -I <ServerName>" from the
puppet
master here is what i get when i run it again:

# service pe-puppet-agent status
* agent is running

# service --status-all | grep puppet
[ + ] pe-puppet-agent

# ps aux | grep puppet
/opt/puppet/bin/ruby1.8 /opt/puppet/sbin/puppetd --onetime --
splaylimit 120 --splay





On Sep 27, 10:46 am, "R.I.Pienaar" <r...@devco.net>
wrote:
> ----- Original Message -----
> > OK  so you will have to for give me here. I am not sure what RC
> > means, but is what you''re saying is that the PE version
puppet is likely
> > causing the issue?
>
> the script in /etc/init.d (or your OS equivelant) that starts puppet and
> is used to check it''s status.
>
> if puppet is running - but have not been started using the service -
> then the service script should not report it as running.
>
> This is with the opensource rpm:
>
> # puppet agent --test
>
> now switch to a different window while that runs:
>
> # service puppet status
> puppetd is stopped
>
> yours should do the same
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> OK here is my output for the different commands with "puppet agent --
> test" running:
> 
> # service pe-puppet-agent status
> * could not access PID file for agent
> 
> # service --status-all | grep puppet
> [ - ] pe-puppet-agent
> 
> # ps aux | grep puppet
> /opt/puppet/bin/ruby1.8 /usr/local/bin/puppet agent --test
> 
> -----------------------------------------
> Now when i run "mco puppetd runonce -I <ServerName>" from
the puppet
> master here is what i get when i run it again:
> 
> # service pe-puppet-agent status
> * agent is running
> 
> # service --status-all | grep puppet
> [ + ] pe-puppet-agent
> 
> # ps aux | grep puppet
> /opt/puppet/bin/ruby1.8 /opt/puppet/sbin/puppetd --onetime --
> splaylimit 120 --splay
right, that''s different my bad should have thought of that difference.

Indeed mine also does report the daemon as running in that case - not sure
what the best approach is, but the rc script should probably not be reporting
that as running, thats the only way you''re going to be able to have
both
ensure stopped and and a mcollective triggered run on the same machine

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