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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
