Depending on your distro, you might find your package has your pids defined in different directories to your puppet.conf.
The RPM packages had that problem. Check your init script against your puppet.conf On 22/10/2010, at 8:30, Douglas Garstang <doug.garst...@gmail.com> 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. > > 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. -- 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.
