Hi Christopher,
Hi,
I have been reading documentation and troubleshooting my logs from debug
output and masterhttp logs. I will also look at those links you have sent
me thanks.
Yes, I have created resources such as, files, classes and modules to group
tasks together on the Puppet Master, which (--noop dry run 1st) worked and
automated the my site.pp and chat.pp (chat.pp had Puppet Master and Puppet
Node statements) files on the Puppet Master only.
Please could you answer my question, "have I got to create .pp files,
classes and modules on each Puppet Node agent as well ? " as I thought by
adding node statements to the site.pp file as below, to describe a file
resource, so all Node agent's, chat1, chat2... to have a file at
"/tmp/HelloTesting" on the nodes too ? when the Node agent checks in with
the master automatically or forcibly by running "puppet agent --test
--debug" on each node. Thus restart Puppet Master "service puppet restart"
when I edit or create a .pp in the manifest.
# site.pp file.
node {} # applies to nodes that aren't explicitly defined
node 'chat.client.com', 'chat1.client.com', 'chat3.client.com' { # applies
to cha1, chat1 and chat2 nodes
file { '/tmp/HelloTesting':
# applies to ns1 and ns2 nodes
ensure => present,
# make sure it exists
mode => 0644,
# Permissions
content => "Hello, world\n",
# cat /tmp/HelloTesting and check contents.
}
}
I want Puppet to ensure that a file at "/tmp/HelloTesting" will exist on
cha1, chat1 and chat2 nodes.
So have I got to create resources such as, .pp files, classes and modules
on each node agent or can I create these just once on the Puppet Master, in
the manifests ?
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/38bd4c0c-4e8b-4ba6-874b-cf761a5cad28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
