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 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/1b28887c-8f0e-4d5a-b8b3-18678ef6e000%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
