1

I have a very strange issue with Puppet 2.7.18 (on a Raspberry Pi) that started all of the sudden. In simple terms, the agent only partially follows the 'server' directive in puppet.conf.

The following works:

$ sudo puppet agent -t --server my.puppet.server

but, if i instead set it in puppet.conf, it doesn't seem to follow it. 

$ grep server /etc/puppet/puppet.conf
server=my.puppet.server

I even confirmed it with the genconfig variable, which appears to agree with the fact that it is properly configured:

$ sudo puppet agent --configprint server
my.puppet.server

The strange part is that when I'm running it without the explicit server argument, I get the following error repeated:

$ sudo puppet agent -t
[...]
err: /Stage[main]/MyModule::Puppet/File[some_file.sh]: Could not evaluate: getaddrinfo: Name or service not known Could not retrieve file metadata for puppet:///modules/MyModule/some_file.sh: getaddrinfo: Name or service not known at /etc/puppet/modules/MyModule/manifests/another_file.pp:31
[...]
err: Could not send report: getaddrinfo: Name or service not known

Can anyone offer any kind of insight or explanation to why such behavior would happen?

Improve this question
6
  • Do you have an actual problem connecting to the server? Or are you mainly concerned with the error that is printed?
    – Joel E Salas
    Dec 4, 2013 at 19:33
  • @JoelESalas Well, the run fails, since it is unable to retrieve files. Hence it ends with a long list of [...] has failures: true.
    – vpetersson
    Dec 4, 2013 at 19:48
  • Can you post the entire output of the Puppet run?
    – Joel E Salas
    Dec 4, 2013 at 19:51
  • @JoelESalas please see the updated example above.
    – vpetersson
    Dec 4, 2013 at 19:52
  • 1
    You know what, I think it was a very odd DNS issue. Puppet is running across the internat, CloudFlare is being used for the DNS (to accelerate/protect other web properties on the domain). In any case, I can no longer reproduce the issue. I'll just go ahead and close this out as a temporary hiccup.
    – vpetersson
    Dec 4, 2013 at 21:00

1 Answer 1

Reset to default
2

Most likely caused by a temporary DNS issue.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .