■Error Messages
# puppetmasterd --verbose --no-daemonize
info: Creating a new SSL key for puppet-server.xxxx.xxxxxx.jp
info: Creating a new SSL certificate request for puppet-
server.xxxx.xxxxxx.jp
info: Certificate Request fingerprint (md5): 98:39:CB:2B:
33:81:90:39:85:B5:32:C2:B7:BD:63:11
notice: puppet-server.xxxx.xxxxxx.jp has a waiting certificate request
notice: Signed certificate request for puppet-server.xxxx.xxxxxx.jp
notice: Removing file Puppet::SSL::CertificateRequest puppet-
server.xxxx.xxxxxx.jp at '/etc/puppet/ssl/ca/requests/puppet-
server.xxxx.xxxxxx.jp.pem'
notice: Removing file Puppet::SSL::CertificateRequest puppet-
server.xxxx.xxxxxx.jp at '/etc/puppet/ssl/certificate_requests/puppet-
server.xxxx.xxxxxx.jp.pem'
notice: Starting Puppet master version 2.6.9
info: Inserting default '~ ^/catalog/([^/]+)$'(auth) ACL because /etc/
puppet/auth.conf doesn't exist
info: Inserting default '/file'(non-auth) ACL because /etc/puppet/
auth.conf doesn't exist
info: Inserting default '/certificate_revocation_list/ca'(auth) ACL
because /etc/puppet/auth.conf doesn't exist
info: Inserting default '/report'(auth) ACL because /etc/puppet/
auth.conf doesn't exist
info: Inserting default '/certificate/ca'(non-auth) ACL because /etc/
puppet/auth.conf doesn't exist
info: Inserting default '/certificate/'(non-auth) ACL because /etc/
puppet/auth.conf doesn't exist
info: Inserting default '/certificate_request'(non-auth) ACL because /
etc/puppet/auth.conf doesn't exist
info: Inserting default '/status'(auth) ACL because /etc/puppet/
auth.conf doesn't exist
info: Could not find certificate for 'puppet-node-001'
info: Could not find certificate_request for 'puppet-node-001'
notice: puppet-node-001 has a waiting certificate request
info: Could not find certificate for 'puppet-node-001'
info: Could not find certificate for 'puppet-node-001'
info: Expiring the node cache of puppet-node-001
info: Not using expired node for puppet-node-001 from cache; expired
at Mon Sep 05 11:08:28 +0900 2011
info: Caching node for puppet-node-001
notice: Compiled catalog for puppet-node-001 in environment production
in 0.81 seconds
info: Could not find certificate for 'puppet-node-002'
info: Could not find certificate_request for 'puppet-node-002'
notice: puppet-node-002 has a waiting certificate request
info: Could not find certificate for 'puppet-node-002'
info: Could not find certificate for 'puppet-node-002'
info: Expiring the node cache of puppet-node-002
info: Not using expired node for puppet-node-002 from cache; expired
at Mon Sep 05 11:19:34 +0900 2011
info: Caching node for puppet-node-002
err: Could not find default node or by name with 'puppet-node-002,
puppet-node-002.xxxx.xxxx.jp, puppet-node-002.xxxx.xxxx, puppet-
node-002.xxxx' on node puppet-node-002
err: Could not find default node or by name with 'puppet-node-002,
puppet-node-002.xxxx.xxxx.jp, puppet-node-002.xxxx.xxxx, puppet-
node-002.xxxx' on node puppet-node-002
■Client hostname
puppet-node-001 ~]# hostname
puppet-node-001
puppet-node-001 ~]# cat /etc/puppet/puppet.conf
[agent]
report = true
[main]
certname = puppet-node-001
puppet-node-002 ~]# hostname
puppet-node-002
puppet-node-002 ~]# cat /etc/puppet/puppet.conf
[agent]
report = true
[main]
certname = puppet-node-002
■manifests
# cat /etc/puppet/manifests/site.pp
import "modules/*"
import "nodes/*"
# cat /etc/puppet/manifests/nodes/puppet-node-001.pp
node puppet-node-001 {
include 'mysql'
include 'apache'
}
node 'puppet-node-001.xxxx.xxxx.jp' {
include 'mysql'
include 'apache'
}
# cat /etc/puppet/manifests/nodes/puppet-node-002.pp
node puppet-node-002 {
include 'mysql'
}
node 'puppet-node-002.xxxx.xxxx.jp' {
include 'mysql'
}
=================================
puppet-node-001 successed to run manifest.
but puppet-node-002 failed to run manifest.
Then, after restarting the PuppetMasterd, puppet-node-002 was
successfully executed.
The current situation is like this.
On 9月3日, 午前1:30, Daniel Pittman <dan...@puppetlabs.com> wrote:
> On Fri, Sep 2, 2011 at 09:19, Nan Liu <n...@puppetlabs.com> wrote:
> > On Fri, Sep 2, 2011 at 6:14 AM, Ryohei Suzuki <ryohei.suz...@progmind.jp>
> > wrote:
> >> I have one question.
> >> I changed the manifest of a Puppet.
> >> Then, if you do not restart the Puppetmasterd, manifest did not run.
> >> What's the functional movements are correct?
>
> > You should not have to restart the puppet master. Try running puppet
> > agent again and see if it updates.
>
> > Check and see if it's related to this open issue regarding passenger
> > and caching:http://projects.puppetlabs.com/issues/5318.
>
> That issue has been closed for a couple of months; as long as you have
> one of the release versions of 2.6 or 2.7 mentioned, you shouldn't hit
> it. I think that is 2.7.1 and 2.6.9, but off hand have not checked.
>
> Daniel
> --
> ⎋ Puppet Labs Developer –http://puppetlabs.com
> ♲ Made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
