[Bug 1397910] Re: Puppet daemon dies from SIGUSR1 if no certificate
Jurjen Bokma
j.bokma at rug.nl
Mon Dec 1 18:06:56 UTC 2014
On 12/01/2014 06:49 PM, Robie Basak wrote:
> Then isn't something else broken that causes puppet to be started before
> hostname resolution is available? What is on your system that causes
> hostname resolution to not be available? Can we fix that instead?
>
Perhaps we can. Puppet runs from a SystemV init script, which does
require named.
But even a running named is no guarantee that resolution succeeds. So
still, the Puppet daemon shouldn't give up just because it doesn't
immediately succeed, IMHO. That's not robust enough.
If I write an upstart job, do I upload it to Debian or to PuppetLabs?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1397910
Title:
Puppet daemon dies from SIGUSR1 if no certificate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397910/+subscriptions
More information about the Ubuntu-server-bugs
mailing list