Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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

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

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[]: Could not evaluate: getaddrinfo: Name or service not known Could not retrieve file metadata for puppet:///modules/MyModule/ 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?

share|improve this question
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 '13 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 '13 at 19:48
Can you post the entire output of the Puppet run? – Joel E Salas Dec 4 '13 at 19:51
@JoelESalas please see the updated example above. – vpetersson Dec 4 '13 at 19:52
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 '13 at 21:00

Most likely caused by a temporary DNS issue.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.