On Wed, Nov 21, 2007 at 07:44:44AM +1100, Matthew Palmer wrote: > severity 452064 minor > thanks > > > I get this when starting our puppet server. Notice how the puppet client > > tries to connect, and fails to connect to the master, before the master is > > started. > > [...] > > > Here's a patch to the postinst of puppet to make it start later: > > > > --- /var/lib/dpkg/info/puppet.postinst.orig 2007-11-20 02:47:41.000000000 > > -0500 > > +++ /var/lib/dpkg/info/puppet.postinst 2007-11-20 02:47:53.000000000 > > -0500 > > @@ -8,7 +8,7 @@ > > > > # Automatically added by dh_installinit > > if [ -x "/etc/init.d/puppet" ]; then > > - update-rc.d puppet defaults >/dev/null > > + update-rc.d puppet defaults 21 >/dev/null > > This won't help existing installations,
Indeed.
> and what's more it doesn't guarantee
> that the Puppetmaster will actually be alive enough to answer connections by
> the time Puppet is started.
Sure, but it's still better than explicitely starting puppetd *before*
puppetmaster.
> I won't be applying this patch.
Isn't that a bit extreme? Why?
Because it doesn't fix existing installations? At least we could fix
future installs...
Because puppetmaster might not have time to start? Well, it sure won't
have time to start if it's started *after* puppetd. For me it's better
to at least *try* to give it a chance to start...
> A real fix for this will need to happen inside of puppetd. Good luck with
> that.
I can file a bug upstream if that's what you mean. I still think that,
even with a fix upstream, puppetd should be started after puppetmasterd.
A.
--
Man really attains the state of complete humanity when he produces,
without being forced by physical need to sell himself as a commodity.
- Ernesto "Che" Guevara
signature.asc
Description: Digital signature
