Hi All,

Still struggling with this.

Have persisted with creating my manifest, classes and init.pp for a LAMP 
stack in dry run phase for now while trying to figure why my Catalogs that 
have been compiled are not reflected on the pulling node agent, as below 
and everything works but only on the Puppet Master.

Output from  puppet master --verbose --no-daemonize --debug 
(puppet.master.com) .
Debug: Evaluating match for Route /.*/
Info: Caching node for chat.client.com
Notice: Compiled catalog for chat.client.com in environment production in 
0.01 seconds
Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing
Debug: catalog supports formats: pson b64_zlib_yaml yaml dot raw

Output from chat.client.com (puppet agent --test --debug).
Info: Applying configuration version '1440738876'
Debug: Finishing transaction 69939182428040
Debug: Storing state
Debug: Stored state in 0.05 seconds
Notice: Finished catalog run in 0.06 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

puppet.master # puppet apply site.pp --noop
Notice: Compiled catalog for puppet.master..com in environment production 
in 1.02 seconds
Notice: /Stage[main]/Lamp/Exec[yum -y update]/returns: current_value 
notrun, should be 0 (noop)
Notice: /Stage[main]/Lamp/Package[php5]/ensure: current_value absent, 
should be present (noop)
Notice: /Stage[main]/Lamp/Service[apache2]/ensure: current_value stopped, 
should be running (noop)
Notice: /Stage[main]/Lamp/Service[mysql]/ensure: current_value stopped, 
should be running (noop)
Notice: /Stage[main]/Lamp/File[/var/tmp/testfile]/ensure: current_value 
absent, should be present (noop)
Notice: /Stage[main]/Lamp/Package[apache2]/ensure: current_value absent, 
should be present (noop)
Notice: /Stage[main]/Lamp/File[/var/www/html/info.php]/ensure: 
current_value absent, should be file (noop)
Notice: Class[Lamp]: Would have triggered 'refresh' from 7 events
Notice: Stage[main]: Would have triggered 'refresh' from 1 events
Notice: Finished catalog run in 1.65 seconds

I have added "node default {}" site.pp and ofc my node agent statement and 
restarted Puppet Master and Puppet Agent "puppet agent --test --debug" 
still no joy.

node default {}

node 'chat.client.com', 'puppet.master.com' {
include lamp
        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
        }
}

Looked at fileserver.conf, puppet.conf and auth.conf files in case I have 
missed something and even Hiera but I think I will leave Hiera that for 
another day (Project).

Any snippets or advise as I can't get my head around how my Node agent is 
supposed to pull the Catalogs containing site.pp data so I can automate 
this across several node clients eventually ? 

TIA

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/afadeaa5-f87a-4698-ba02-df613bc7b1b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to