Hi,
further
Just filtered my node from the masterhttp.logs and come across this
"transaction_uuid=f189dce8-d424-4736-8bbc-3dd4da655275&fail_on_404=true"
msg below. Investigating further au advise welcome.
2015-08-27 06:40:07] - -> /production/report/chat.client.com
DNS:chat.client.com, DNS:puppet, DNS:puppet.master.com
[2015-08-27 06:43:48] 172.18.1.204 - - [27/Aug/2015:06:43:48 BST] "GET
/production/node/chat.client.com?transaction_uuid=a4e4515f-ce5e-439d-b662-b92bf136346a&fail_on_404=true
HTTP/1.1" 200 4094
[2015-08-27 06:43:48] - ->
/production/node/chat.client.com?transaction_uuid=a4e4515f-ce5e-439d-b662-b92bf136346a&fail_on_404=true
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/a666a04a-ab5d-4351-8f95-70c2652d7931%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
