Name or service not known issue

[Sumith Sudhakaran]

Hi,

When I am trying update from puppet client, getting error like blow

err: Could not request certificate: getaddrinfo: Name or service not known
 
puppetd --test output:-

err: Could not request certificate: getaddrinfo: Name or service not known
Exiting; failed to retrieve certificate and waitforcert is disabled



Please help to solve the same..

--

  Regards

 Sumith

[Nicolas Jungers]

On 2011-05-27 10:39, Sumith Sudhakaran wrote:
>
> Hi,
>
> When I am trying update from puppet client, getting error like blow
>

> *err: Could not request certificate: getaddrinfo: Name or service not known

>
> puppetd --test output:-
>
> err: Could not request certificate: getaddrinfo: Name or service not known

> Exiting; failed to retrieve certificate and waitforcert is disabled*

Seems like you have a name resolution error. Can you ping your server by
name?

N.

>
>
>
> Please help to solve the same..
>
>
>
>
> --

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

[Felix Frank]

Hi,

you need to do one of these:
a) create a DNS entry for "puppet" pointing to your master
b) create a hosts entry for "puppet" pointing to your master
c) specify the --server parameter with an address resolving to your master
d) add a server= entry to your puppet.conf

HTH,
Felix

On 05/27/2011 10:39 AM, Sumith Sudhakaran wrote:
>
> Hi,
>
> When I am trying update from puppet client, getting error like blow
>

> *err: Could not request certificate: getaddrinfo: Name or service not known

>
> puppetd --test output:-
>
> err: Could not request certificate: getaddrinfo: Name or service not known

> Exiting; failed to retrieve certificate and waitforcert is disabled*

>
>
>
> Please help to solve the same..
>
>
>
>
> --

> / Regards///

[Felix Frank]

Wow, this is like a voice from the past coming to haunt me ;-)
Way to find this thread years later.

On 02/15/2013 05:42 PM, Adam Turner wrote:
> Felix -

> "d) add a server= entry to your puppet.conf"

> This needs to be a fully qualified domain name (FQDN) - correct?

Technically it doesn't have to, but in most cases it is. That's because
the agent expects the master's certificate to match its name (as they do
where SSL is concerned), and your master likely does not use "puppet"
(or another hostname) as its CN.

Long story short, check what the master considers its name to be, use
that as 'server' for the agent and make sure the agent machine can
resolve that name to the master's IP address.

HTH,
Felix

[Guillermo Castellon]

I ran into this problem and after much debugging it turned out to be a problem of whom is running the command.

In my I had set the credentials to use ssh for a user but I was running the command as a different user and that was the issue.  Minor details :)