Puppet users - Apr 2008 - Puppetd exits when "puppet" can't be resolved

Heya,

I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s a problem
with
the default setup of Ubuntu.
Ubuntu uses network-manager to start the network in the background,
which in turn causes puppet to start before the network is up. Puppet
will then exit because it can''t resolve the server name.

Currently I "solve" this problem by uninstalling network-manager (and
restoring /etc/network/interfaces) through some post commands in my
preseed file, but obviously this is an ugly hack.

In the future I will be going to this on laptops and then network-
manager will most likely come in handy yet at the same time it renders
puppet useless.

Any suggestions on how to properly fix this?

Just to be sure, a snippet from the logfile displaying the error I
get:

Apr 22 15:00:19 newton2 puppetd[25254]: Starting Puppet client version
0.24.4
Apr 22 15:00:20 newton2 puppetd[25254]: Could not find server puppet:
getaddrinfo: Name or service not known
Apr 22 15:00:20 newton2 puppetd[25254]: Could not retrieve catalog:
Could not find server puppet

Regards,

Jelmer Jaarsma
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

A couple of suggestions:

a) Run puppet from cron instead of in daemon mode - a few people here
on the list advocate the approach.

b) Trigger a puppet run AFTER the network is configured

c) Use a service monitoring framework (like runit or daemontools) to
ensure that the application is restarted.

d) Run puppet from init (eeeew)

On 22/04/2008, Jelmer Jaarsma <diskaa@gmail.com>
wrote:
>
>  Heya,
>
>  I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s a
problem with
>  the default setup of Ubuntu.
>  Ubuntu uses network-manager to start the network in the background,
>  which in turn causes puppet to start before the network is up. Puppet
>  will then exit because it can''t resolve the server name.
>
>  Currently I "solve" this problem by uninstalling network-manager
(and
>  restoring /etc/network/interfaces) through some post commands in my
>  preseed file, but obviously this is an ugly hack.
>
>  In the future I will be going to this on laptops and then network-
>  manager will most likely come in handy yet at the same time it renders
>  puppet useless.
>
>  Any suggestions on how to properly fix this?
>
>  Just to be sure, a snippet from the logfile displaying the error I
>  get:
>
>  Apr 22 15:00:19 newton2 puppetd[25254]: Starting Puppet client version
>  0.24.4
>  Apr 22 15:00:20 newton2 puppetd[25254]: Could not find server puppet:
>  getaddrinfo: Name or service not known
>  Apr 22 15:00:20 newton2 puppetd[25254]: Could not retrieve catalog:
>  Could not find server puppet
>
>  Regards,
>
>
>  Jelmer Jaarsma
>  >
>

-- 
/peter

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Apr 22, 2008, at 8:04 AM, Jelmer Jaarsma wrote:
>
> Heya,
>
> I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s a
problem with
> the default setup of Ubuntu.
> Ubuntu uses network-manager to start the network in the background,
> which in turn causes puppet to start before the network is up. Puppet
> will then exit because it can''t resolve the server name.
>
> Currently I "solve" this problem by uninstalling network-manager
(and
> restoring /etc/network/interfaces) through some post commands in my
> preseed file, but obviously this is an ugly hack.
>
> In the future I will be going to this on laptops and then network-
> manager will most likely come in handy yet at the same time it renders
> puppet useless.
>
> Any suggestions on how to properly fix this?
I don''t know how to fix your service ordering issue -- that''s
a
general problem, not a Puppet problem, but puppetd shouldn''t be  
exiting because of DNS resolution issues.  If it''s actually failing  
and exiting, rather than just throwing an error and sleeping for the  
runinterval, then that should be filed as a bug.
>
> Just to be sure, a snippet from the logfile displaying the error I
> get:
>
> Apr 22 15:00:19 newton2 puppetd[25254]: Starting Puppet client version
> 0.24.4
> Apr 22 15:00:20 newton2 puppetd[25254]: Could not find server puppet:
> getaddrinfo: Name or service not known
> Apr 22 15:00:20 newton2 puppetd[25254]: Could not retrieve catalog:
> Could not find server puppet

It doesn''t look like it''s exiting here, just that the first
run isn''t
working.

-- 
Tradition is what you resort to when you don''t have the time or the
money to do it right. -- Kurt Herbert Alder
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Jelmer Jaarsma wrote:
> Currently I "solve" this problem by uninstalling network-manager
(and
> restoring /etc/network/interfaces) through some post commands in my
> preseed file, but obviously this is an ugly hack.
We are using the following manifest to fix that.

  file {"/etc/network/if-up.d/puppetd":
    ensure => present,
    mode   => 655,
    source => "puppet:///puppet/puppetd.if-up",
  }

  file {"/etc/network/if-down.d/puppetd":
    ensure => present,
    mode => 655,
    source => "puppet:///puppet/puppetd.if-down",
  }

with those two scripts:

puppetd.if-up:

#!/bin/sh
/etc/init.d/puppet start


puppetd.if-down:

#!/bin/sh
/etc/init.d/puppet stop


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Why not just drop an /etc/hosts with your preseed file?

I''ve always used the /etc/hosts method with Puppet, as you can manage
it with a native resource quite happily in the event of an IP address move, and
it takes DNS out of the equation entirely :)

Regards,

Arjuna Christensen | Systems Engineer 
Maximum Internet Ltd
DDI: + 64 9 913 9683 | Ph: +64 9 915 1825 | Fax:: +64 9 300 7227
arjuna.christensen@maxnet.co.nz| www.maxnet.co.nz

-----Original Message-----
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of Francois Deppierraz
Sent: Wednesday, 23 April 2008 7:43 a.m.
To: puppet-users@googlegroups.com
Subject: [Puppet Users] Re: Puppetd exits when "puppet" can''t
be resolved


Jelmer Jaarsma wrote:
> Currently I "solve" this problem by uninstalling network-manager
(and
> restoring /etc/network/interfaces) through some post commands in my
> preseed file, but obviously this is an ugly hack.
We are using the following manifest to fix that.

  file {"/etc/network/if-up.d/puppetd":
    ensure => present,
    mode   => 655,
    source => "puppet:///puppet/puppetd.if-up",
  }

  file {"/etc/network/if-down.d/puppetd":
    ensure => present,
    mode => 655,
    source => "puppet:///puppet/puppetd.if-down",
  }

with those two scripts:

puppetd.if-up:

#!/bin/sh
/etc/init.d/puppet start


puppetd.if-down:

#!/bin/sh
/etc/init.d/puppet stop




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

I can confirm that, I''ve just tried it out, and if you have factsync
enabled, the following is printed and puppet service exist:

2008-04-22T05:36:49+02:00 hostname puppetd[17835]: Could not retrieve facts:
execution expired


On Tue, Apr 22, 2008 at 10:28 PM, Luke Kanies <luke@madstop.com> wrote:
>
> On Apr 22, 2008, at 8:04 AM, Jelmer Jaarsma wrote:
>
> >
> > Heya,
> >
> > I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s
a problem with
> > the default setup of Ubuntu.
> > Ubuntu uses network-manager to start the network in the background,
> > which in turn causes puppet to start before the network is up. Puppet
> > will then exit because it can''t resolve the server name.
> >
> > Currently I "solve" this problem by uninstalling
network-manager (and
> > restoring /etc/network/interfaces) through some post commands in my
> > preseed file, but obviously this is an ugly hack.
> >
> > In the future I will be going to this on laptops and then network-
> > manager will most likely come in handy yet at the same time it renders
> > puppet useless.
> >
> > Any suggestions on how to properly fix this?
>
> I don''t know how to fix your service ordering issue --
that''s a
> general problem, not a Puppet problem, but puppetd shouldn''t be
> exiting because of DNS resolution issues.  If it''s actually
failing
> and exiting, rather than just throwing an error and sleeping for the
> runinterval, then that should be filed as a bug.
>
> >
> > Just to be sure, a snippet from the logfile displaying the error I
> > get:
> >
> > Apr 22 15:00:19 newton2 puppetd[25254]: Starting Puppet client version
> > 0.24.4
> > Apr 22 15:00:20 newton2 puppetd[25254]: Could not find server puppet:
> > getaddrinfo: Name or service not known
> > Apr 22 15:00:20 newton2 puppetd[25254]: Could not retrieve catalog:
> > Could not find server puppet
>
>
> It doesn''t look like it''s exiting here, just that the
first run isn''t
> working.
>
> --
> Tradition is what you resort to when you don''t have the time or
the
> money to do it right. -- Kurt Herbert Alder
> ---------------------------------------------------------------------
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

puppet-users@googlegroups.com wrote on 23/04/2008 00:56:11:
> 
> Why not just drop an /etc/hosts with your preseed file?
> 
> I''ve always used the /etc/hosts method with Puppet, as you can 
> manage it with a native resource quite happily in the event of an IP
> address move, and it takes DNS out of the equation entirely :)
I would say this having your puppet server in /etc/hosts is always 
sensible: it means your hosts will still contact your puppet server, and 
consequently remain "fixable", if you
a) Screw up your resolv.conf with puppet
b) You lose your DNS servers and need to push out a new resolv.conf 
quickly.

-ross


-- 
Ross McKerchar
Systems Analyst, Sophos

Tel: 01235 559933
Web: http://www.sophos.com
Sophos - security and control


Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon,
OX14 3YP, United Kingdom.

Company Reg No 2096520. VAT Reg No GB 348 3873 20.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi
>> I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s
a problem with
>> the default setup of Ubuntu.
>> Ubuntu uses network-manager to start the network in the background,
>> which in turn causes puppet to start before the network is up. Puppet
>> will then exit because it can''t resolve the server name.
>>
>> Currently I "solve" this problem by uninstalling
network-manager (and
>> restoring /etc/network/interfaces) through some post commands in my
>> preseed file, but obviously this is an ugly hack.
>>
>> In the future I will be going to this on laptops and then network-
>> manager will most likely come in handy yet at the same time it renders
>> puppet useless.
>>
>> Any suggestions on how to properly fix this?
> 
> I don''t know how to fix your service ordering issue --
that''s a
> general problem, not a Puppet problem, but puppetd shouldn''t be  
> exiting because of DNS resolution issues.  If it''s actually
failing
> and exiting, rather than just throwing an error and sleeping for the  
> runinterval, then that should be filed as a bug.
as I thought that our problem with a died puppetmaster and this letting
exiting all client daemons might be related to this problem. I filed bug
#1197 [1].

greets Pete

[1] http://reductivelabs.com/trac/puppet/ticket/1199

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On 4/22/2008 8:04 AM, Jelmer Jaarsma wrote:
> Ubuntu uses network-manager to start the network in the background,
> which in turn causes puppet to start before the network is up. Puppet
> will then exit because it can''t resolve the server name.
I have a similar error without network-manager (regular Debian 4.0 under 
Xen). But my puppetmaster''s hostname isn''t
''puppet'', so I have a
different root cause. Log entries:

==Jul 11 00:20:15 ch314d puppetd[1519]: Reopening log files
Jul 11 00:20:16 ch314d puppetd[1519]: Could not find server puppet: 
getaddrinfo: Name or service not known
Jul 11 00:20:16 ch314d puppetd[1519]: Could not request certificate: 
Certificate retrieval failed: Could not find server puppet
Jul 11 00:20:17 ch314d puppetd[1392]: Did not receive certificate
==
This can be fixed by setting "ca_server" in puppet.conf''s
[main]
section. 0.23.1 had this set to $server, and all was ok. 0.24.4 and HEAD 
have it explicitly set to "puppet".

Filed as http://reductivelabs.com/redmine/issues/show/1413

-- 
Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
931 372-3601 / Tennessee Technological University

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Fri, Jul 11, 2008 at 10:30 AM, Mike Renfro <renfro@tntech.edu>
wrote:
>
> On 4/22/2008 8:04 AM, Jelmer Jaarsma wrote:
>
>> Ubuntu uses network-manager to start the network in the background,
>> which in turn causes puppet to start before the network is up. Puppet
>> will then exit because it can''t resolve the server name.
>
> I have a similar error without network-manager (regular Debian 4.0 under
> Xen). But my puppetmaster''s hostname isn''t
''puppet'', so I have a
> different root cause. Log entries:
>
> ==> Jul 11 00:20:15 ch314d puppetd[1519]: Reopening log files
> Jul 11 00:20:16 ch314d puppetd[1519]: Could not find server puppet:
> getaddrinfo: Name or service not known
> Jul 11 00:20:16 ch314d puppetd[1519]: Could not request certificate:
> Certificate retrieval failed: Could not find server puppet
> Jul 11 00:20:17 ch314d puppetd[1392]: Did not receive certificate
> ==>
> This can be fixed by setting "ca_server" in
puppet.conf''s [main]
> section. 0.23.1 had this set to $server, and all was ok. 0.24.4 and HEAD
> have it explicitly set to "puppet".
>
> Filed as http://reductivelabs.com/redmine/issues/show/1413
>
I got around this issue by putting a CNAME record in DNS pointing
puppet to the real server name.

Evan

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---