On 10/21/2010 02:56 PM, Douglas Garstang wrote:
On Thu, Oct 21, 2010 at 2:48 PM, Patrick<[email protected]> wrote:
On Oct 21, 2010, at 2:30 PM, Douglas Garstang wrote:
Having some issues disabling puppet. I want to use scripts to update
RPM's, and obviously you need to quiesce puppet first.
The pid file directory is empty:
[pax] app01 ~:# ls -l /var/run/puppet/
total 0
Puppet is stopped:
[pax] app01 ~:# service puppet status
puppetd is stopped
Really really stopped:
[pax] app01 ~:# ps -ef | grep puppet
root 13079 7958 0 21:27 pts/0 00:00:00 grep puppet
So, I start puppet:
[pax] app01 ~:# service puppet start
Starting puppet: [ OK ]
The pid file exists, and it's pid matches the running puppet:
[pax] app01 ~:# cat /var/run/puppet/agent.pid
13612
[pax] app01 ~:# ps -ef | grep puppet
root 13612 1 22 21:28 ? 00:00:08 /usr/bin/ruby
/usr/sbin/puppetd
root 13978 7958 0 21:28 pts/0 00:00:00 grep puppet
And, then I try and disable puppet:
[pax] app01 ~:# puppetd disable
Could not prepare for execution: Could not create PID file:
/var/run/puppet/agent.pid
What's up with that?
This is puppet 2.6.1.
If you are going this far, why not use "service puppet stop"? That sounds
safer to me.
Because.... puppet might be in the middle of a run when you stop it, and
does anyone know what the worse case scenario is there?
I believe puppet finishes the current catalog run when it receives a
SIGTERM.
--
Russell A Jackson <[email protected]>
Network Analyst
California State University, Bakersfield
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
