On Thu, Oct 21, 2010 at 2:55 PM, Russell Jackson <r...@csub.edu> wrote:
> On 10/21/2010 02:56 PM, Douglas Garstang wrote: > >> On Thu, Oct 21, 2010 at 2:48 PM, Patrick<kc7...@gmail.com> 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. > > It doesn't look like that's the case. Oct 21 22:14:03 s_...@app02.pax.livegamer.com puppet-agent[26665]: Starting Puppet client version 2.6.1 Oct 21 22:14:05 s_...@app02.pax.livegamer.com puppet-agent[26665]: Caught TERM; calling stop Oct 21 22:14:05 s_...@app02.pax.livegamer.com puppet-agent[26665]: Could not retrieve catalog from remote server: Cannot unlisten -- not currently listening. Oct 21 22:14:05 s_...@app02.pax.livegamer.com puppet-agent[26665]: Not using cache on failed catalog Oct 21 22:14:05 s_...@app02.pax.livegamer.com puppet-agent[26665]: Could not retrieve catalog; skipping run It certainly didn't finish the run. A run that goes to completion always prints my yum clean messages: Oct 21 22:15:21 s_...@app02.pax.livegamer.com puppet-agent[27410]: Starting Puppet client version 2.6.1 Oct 21 22:15:33 s_...@app02.pax.livegamer.com puppet-agent[27410]: (/Stage[pre_yum]/Yum::Client/Exec[yum-clean-all]/returns) executed successfully Oct 21 22:15:45 s_...@app02.pax.livegamer.com puppet-agent[27410]: Finished catalog run in 17.75 seconds Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
