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.
>
Well I partly got something
info: Filebucket[/var/lib/puppet/clientbucket]: Adding
/etc/puppet/puppet.conf(f855be601e533a86b2c86a1e48e40281)
info: //puppet::client/File[/etc/puppet/puppet.conf]: Filebucketed
/etc/puppet/puppet.conf to main with sum f855be601e533a86b2c86a1e48e40281
debug: //puppet::client/File[/etc/puppet/puppet.conf]/checksum: Replacing
/etc/puppet/puppet.conf checksum {md5}f855be601e533a86b2c86a1e48e40281 with
{md5}caeae0319caee30f24bb280916242f29
notice: //puppet::client/File[/etc/puppet/puppet.conf]/content: content changed
'{md5}f855be601e533a86b2c86a1e48e40281' to 'unknown checksum'
info: //puppet::client/File[/etc/puppet/puppet.conf]: Scheduling refresh of
Service[puppet]
debug: Format pson not supported for Puppet::FileServing::Metadata; has not
implemented method 'from_pson'
debug: Format s not supported for Puppet::FileServing::Metadata; has not
implemented method 'from_s'
debug: Service[puppet](provider=debian): Executing 'ps -ef'
debug: Service[puppet](provider=debian): PID is 29733
notice: //puppet/Service[puppet]: Triggering 'refresh' from 1 dependencies
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
/Kim
--
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.
