On Apr 21, 2010, at 11:43 AM, Kim Gert Nielsen wrote: > > On Apr 21, 2010, at 2:51 PM, Ken wrote: > >> More data is needed I think. >> >> Can you run puppetd --no-daemonize --debug in 'screen' or by piping >> the output somewhere? It may give you a better clue. >> > > debug: Service[puppet](provider=debian): Executing 'ps -ef' > debug: Service[puppet](provider=debian): PID is 29733 > debug: Service[puppet](provider=debian): Executing '/etc/init.d/puppet > restart' > notice: Caught TERM; calling stop > > so it see an update to puppet.conf and runs a restart .. then it stops .. > then I guess the hack with 1 sec delay is not enough
Is restarting puppet using itself supported? I had always assumed it wasn't. -- 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.
