Hi Chuck, I'm not seeing anything wrong with your code glancing at it, but it could be I'm missing something. But if it was an issue with the syntax I'd expect you to get an actual failure, as opposed to the agent running but just making no changes.
You connected with the agent once and signed the cert for it on the master? I'd check and make sure the cert on the master has the same hostname that you're using in your site.pp. You'll want those to match, like if the cert has the FQDN then you want the same thing in site.pp. Like I said, if you are connecting fine and the agent is running with no errors but nothing is happening, that sounds like a node classification problem to me. Like the master doesn't think that node should be given that resource in its catalog. Rich On Wed, Aug 26, 2015 at 8:17 PM Chuck Amadi <amadi.ch...@gmail.com> wrote: > On the Puppet Master this occurred when I tweaked the site.pp file, but no > joy on the Node Agent ? > > I run the following command on the node "chat.client.com". > > chat.client.com# > <http://www.google.com/url?q=http%3A%2F%2Fchat.client.com%23&sa=D&sntz=1&usg=AFQjCNHP_7aE8GU-Qrv7HdVdRpxKs_TueA> > puppet > agent --test on the node agent. > > puppet-master # puppet apply site.pp > Notice: Compiled catalog for puppet.master.com in environment production > in 0.26 seconds > Notice: /Stage[main]/Main/File[/tmp/test_example-ip]/ensure: created > Notice: Finished catalog run in 0.16 seconds > # cat /tmp/test_example-ip > Here is my Public IP Address: 172.18.x.xxx. > > puppet-master # vi /etc/puppet/manifest/site.pp > > node 'chat.client.com' { > file { '/tmp/hello_puppet': > content => "Hello, Puppet\n", > } > } > > file {'/tmp/test_example-ip': # > resource type file and filename > ensure => present, # make > sure it exists > mode => 0644, # > file permissions > content => "Here is my Public IP Address: ${ipaddress_eth0}.\n", # note > the ipaddress_eth0 fact > } > > node default { } > > <-- EOF --> > > I tried this below but failed miserable in my site.pp file. > > node 'chat.client.com <http://chat.noc.velocix.com/>' { > file {'/tmp/mytest_example-ip': > # resource type file and filename > ensure => present, > # make sure it exists > mode => 0644, > # file permissions > content => "Here is my Public IP Address: > ${ipaddress_eth0}.\n", # note the ipaddress_eth0 fact > } > } > > > Cheers, > > On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote: > >> Hi I Setup a Open Source Puppet Master and a Puppet Agent client on Linux >> CentOS release 6.6, Puppet 3.8.1 on two separate servers. >> >> Have successfully setup communications between both servers (cert >> list/sign/fingerprint etc etc and telnet 8140, disabled SELinux and added >> iptables 8140 rule) and I have created and run "puppet apply site.pp" >> node.pp and a init.pp/class no errors. >> >> Thus run "puppet master --verbose --no-daemonize" on the PM and "puppet >> agent -t --debug" on the client and I do not receive any errors when I run >> # puppet apply site.pp or node.pp etc or see any issues when I run tail on >> the masterhttp.log file. >> >> Test files specified in site.pp and node.pp are created on the Puppet >> Master but do not replicate to the Node ? >> >> Puppet node does not pick any changes from master's catalogs when I >> forcibly restart puppet client or run puppet agent instead of waiting 30 >> mins, even though the "Info: Applying configuration version '1440626773'" >> number changes accordingly. Further information below: >> >> # puppet master --verbose --no-daemonize >> >> Info: access[/file_metadata]: adding authentication any >> Info: Inserting default '/status' (auth true) ACL >> Info: Caching node for chat.client.com >> Info: Caching node for chat.client.com >> Notice: Compiled catalog for chat.client.com in environment production >> in 0.04 seconds >> >> # puppet agent -t --debug >> >> Debug: Creating default schedules >> Debug: Loaded state in 0.00 seconds >> Info: Applying configuration version '1440626773' < changes > >> Debug: Finishing transaction 69904202860300 >> Debug: Storing state >> Debug: Stored state in 0.03 seconds >> Notice: Finished catalog run in 0.13 seconds >> Debug: Using cached connection for https://puppet.master.com:8140 >> Debug: Caching connection for https://puppet.master.com:8140 >> Debug: Closing connection for https://puppet.master.com:8140 >> >> Any help or advice to troubleshoot on why Puppet node does not pull any >> changes from master's site.pp and node.pp manifest. I'm ignoring the Module >> classes I have created for now. >> >> Cheers, >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/ab996036-649b-4891-82ba-923bad9d5f3a%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/ab996036-649b-4891-82ba-923bad9d5f3a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAPGcbtCMer4bW858KA5SznWS_5C_Rw%3D9c6WBiJtCNvO2855Apw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
