Well he has actually been posting that stuff, he's posted his site.pp a few times in the thread. But it has been a bit confusing. He was trying to manage a file resource directly in the node definition in site.pp, but then he was also trying it in node.pp too I think?
I do agree that stepping back and going through some of the tutorials for some context could help.. My guess is that John is right, that the site.pp file he was working on is not in the right place, like he is using directory environments and doesn't have it inside his production environment. It seems like the agent/master communication is all working fine, but Puppet doesn't think there are any resources to manage on the client node. Rich On Fri, Aug 28, 2015 at 10:14 AM Christopher Wood < christopher_w...@pobox.com> wrote: > It sounds like you may need to back up a little and focus on the basics, > these will help: > > https://learn.puppetlabs.com/category/self-paced-training > > https://puppetlabs.com/download-learning-vm > > http://docs.puppetlabs.com/ > > More specifically, you'd have to post your test case for us to see what's > happening. For instance, do you have any node definitions in site.pp? Or > any included classes? Or even any resources? Without those the agent will > not have any catalog items to apply. > > On Fri, Aug 28, 2015 at 09:47:53AM -0700, Chuck Amadi wrote: > > OK, > > For my test case, I want to create basic manifest files such as, > site.pp > > and nodes.pp file on the Puppet Master, which will have one or more > node > > agents statements. So when the node agents pulls the catalog from the > > Puppet Master, it will pull the nodes.pp statements and create a > specified > > user (with permissions), files and directories that are specified in > the > > nodes.pp and automate the tasks. > > Would like Puppet Master to manage all manifests and Puppet Node > Agents to > > pull when changes happen. > > Am I supposed to create site.pp and node.pp manifests on the Puppet > Nodes > > ? > > Regards, > > 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 [1]chat.client.com > > Info: Caching node for [2]chat.client.com > > Notice: Compiled catalog for [3]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 [4] > https://puppet.master.com:8140 > > Debug: Caching connection for [5]https://puppet.master.com:8140 > > Debug: Closing connection for [6]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 [7]puppet-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > [8] > https://groups.google.com/d/msgid/puppet-users/1b28887c-8f0e-4d5a-b8b3-18678ef6e000%40googlegroups.com > . > > For more options, visit [9]https://groups.google.com/d/optout. > > > > References > > > > Visible links > > 1. http://chat.client.com/ > > 2. http://chat.client.com/ > > 3. http://chat.client.com/ > > 4. https://puppet.master.com:8140/ > > 5. https://puppet.master.com:8140/ > > 6. https://puppet.master.com:8140/ > > 7. mailto:puppet-users+unsubscr...@googlegroups.com > > 8. > https://groups.google.com/d/msgid/puppet-users/1b28887c-8f0e-4d5a-b8b3-18678ef6e000%40googlegroups.com?utm_medium=email&utm_source=footer > > 9. 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/20150828171410.GA8646%40iniquitous.heresiarch.ca > . > 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/CAPGcbtCxTNq%3DNgfh%2ByMDjn926PfqxA7N_v6%2BHLaZ5u%3DY6Qa18g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
