Note that there are some explanatory texts on larger screens.

plurals
  1. POPuppet agent in Red hat and SUSE
    text
    copied!<p>I have a problem in running puppet agent in Red Hat Enterprise Linux 6.4 and SUSE Linux Enterprise Server 11. In both cases, when I ran "puppet agent --test --verbose", I could see no error and the configuration was applied. However, when I ran "service puppet restart", while the result said that the service was stopped and started okay, the configuration was not applied. That is the problem.</p> <p>For Red Hat, I could not be able to find the log file at "/var/log/puppet" (the directory was empty). However, for SUSE, I found the log file at "/var/log/puppet/puppet.log" and it recorded a couple of errors: "Could not retrieve catalog; skipping run. Could not send report: getaddrinfo: Name or service not know". It is weird because once the "puppet agent --test" could be executed successfully, it implied that the server's address could be resolved !!!</p> <p>Do you have any idea of how this problem happened and how to fix it.</p> <p>Thanks, Henry</p> <p>P/S: below is the content of puppet.conf and site.pp at the server and puppet.conf at the client</p> <pre><code>#puppet.conf at the server [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates prerun_command=/etc/puppet/etckeeper-commit-pre postrun_command=/etc/puppet/etckeeper-commit-post [master] ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY dns_alt_names = puppet, server_name #site.pp at the server node default{ } node 'client_name' { include 'client_config' } #puppet.conf at the client [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl server = server_name certname = client_name report = true pluginsync = true [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload