我们正在我们的客户和主人上运行傀儡2.7.11-1ubuntu2.4 (Ubuntu12.04)。客户端似乎不会自动更新,但当我运行时:
sudo puppet agent --test一切都很好。
当前正在客户端上运行的进程:
root 1764 1 0 Sep10 ? 00:00:05 /usr/bin/ruby1.8 /usr/bin/puppet agent/etc/木偶/木偶
[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
pluginsync=true
[master]
# These are needed when the puppetmaster is run by passenger
# and can safely be removed if webrick is used.
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
[agent]
server=<URL_REMOVED>
configtimeout=300/var/log/syAdd.1-.log
Sep 11 16:12:48 <HOSTNAME_REMOVED> puppet-agent[1764]: Did not receive certificate
Sep 11 16:14:48 <HOSTNAME_REMOVED> puppet-agent[1764]: Did not receive certificate
Sep 11 16:16:49 <HOSTNAME_REMOVED> puppet-agent[1764]: Did not receive certificate
Sep 11 16:18:49 <HOSTNAME_REMOVED> puppet-agent[1764]: Did not receive certificate
Sep 11 16:20:49 <HOSTNAME_REMOVED> puppet-agent[1764]: Did not receive certificate/etc/默认/傀儡
# Defaults for puppet - sourced by /etc/init.d/puppet
# Start puppet on boot?
START=yes
# Startup options
DAEMON_OPTS=""有人知道会有什么问题吗?
发布于 2013-11-12 17:43:16
我们最近发现了这个问题的原因。
有些节点的puppet.conf中有一个与服务器证书中的主机名不匹配的主机名。
另外,一些节点在与服务器联系时没有使用它们的FQDN,这会导致与客户端证书不匹配。通过将FQDN添加到/etc/host中,我们对此进行了修正:
127.0.1.1 hostename.domain.edu hostename发布于 2013-11-11 12:44:14
看看这个故障排除页面。不确定您的问题是否准确,但我在日志中看到了类似的错误:“没有收到证书”。在我的例子中,这些步骤帮助了我:在主人跑
puppet cert clean <NODE NAME>特工:
rm -rf $(puppet agent --configprint ssldir)
puppet agent --testhttps://stackoverflow.com/questions/18743937
复制相似问题