Puppet node does not pull changes from master's catalogs in site.pp or node.pp ?

Chuck Amadi

unread,

Aug 26, 2015, 10:22:05 PM8/26/15

to Puppet Users

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

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,

Rich Burroughs

unread,

Aug 26, 2015, 10:45:40 PM8/26/15

to Puppet Users

Hi Chuck,

If the communication is all working fine and the agent is getting the catalog back from the master, and nothing is changing, that likely means the agent just doesn't have any changes to make.

If there are files that you think should be created but aren't, then it's possible there is a problem with node classification. It would probably help folks to see your site.pp and node.pp file to see what the logic is there, or you might examine them yourself. Mask any sensitive data you don't want to share if you post them.

If you've used Gist that would be a good place to stick this sort of thing.

The resources are possibly being applied to the master but not to the other host in your code. If you hook an agent up to a master and it doesn't have any classes or resources being applied to it, then the agent will run and just not make any changes.

Rich

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c75e0221-54a8-4cf6-b5aa-2ee0691ff0a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Message has been deleted

Chuck Amadi

unread,

Aug 26, 2015, 11:17:19 PM8/26/15

to Puppet Users

On the Puppet Master this occurred when I tweaked the site.pp file, but no joy on the Node Agent ?

I run the following command on the node "chat.client.com".

chat.client.com# puppet agent --test on the node agent.

puppet-master # puppet apply site.pp

Notice: Compiled catalog for puppet.master.com in environment production in 0.26 seconds

Notice: /Stage[main]/Main/File[/tmp/test_example-ip]/ensure: created

Notice: Finished catalog run in 0.16 seconds

# cat /tmp/test_example-ip

Here is my Public IP Address: 172.18.x.xxx.

puppet-master # vi /etc/puppet/manifest/site.pp

node 'chat.client.com' {

file { '/tmp/hello_puppet':

content => "Hello, Puppet\n",

}

file {'/tmp/test_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

}

node default { }

<-- EOF -->

I tried this below but failed miserable in my site.pp file.

node 'chat.client.com' {

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

}

Cheers,

Rich Burroughs

unread,

Aug 27, 2015, 12:11:08 AM8/27/15

to puppet...@googlegroups.com

Hi Chuck,

I'm not seeing anything wrong with your code glancing at it, but it could be I'm missing something. But if it was an issue with the syntax I'd expect you to get an actual failure, as opposed to the agent running but just making no changes.

You connected with the agent once and signed the cert for it on the master? I'd check and make sure the cert on the master has the same hostname that you're using in your site.pp. You'll want those to match, like if the cert has the FQDN then you want the same thing in site.pp.

Like I said, if you are connecting fine and the agent is running with no errors but nothing is happening, that sounds like a node classification problem to me. Like the master doesn't think that node should be given that resource in its catalog.

Rich

--

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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ab996036-649b-4891-82ba-923bad9d5f3a%40googlegroups.com.

Chuck Amadi

unread,

Aug 27, 2015, 1:35:06 AM8/27/15

to Puppet Users

Very weird indeed.

Yes, I have signed the cert and all that jazz, double checked /etc/hosts and puppet.conf. Stummed.

puppet.master# puppet cert --list --all

+ "chat.client.com" (SHA256) 71:6E:52:19:F0:D4:4F:6C:1B:CC:29:70:DC:93:36:F5:5E:E8:45:9B:66:2C:13:FC:5E:9B:AF:D1:DD:8E:55:11

+ "puppet.master.com" (SHA256) E5:22:C4:F5:29:72:D3:98:F1:96:B7:50:99:6D:01:16:7A:82:FF:52:0D:83:A8:3F:9D:CF:1D:B3:33:C1:5E:3C (alt names: "DNS:chat.client.com", "DNS:puppet", "DNS:puppet.master.com")

chat.client]# puppet agent --fingerprint

(SHA256) 71:6E:52:19:F0:D4:4F:6C:1B:CC:29:70:DC:93:36:F5:5E:E8:45:9B:66:2C:13:FC:5E:9B:AF:D1:DD:8E:55:11

# node.pp file:

node 'chat.client.com' {

file { '/tmp/hello Testing':

content => "Hello, world\n",

}

node 'puppet.master.com' {

file { '/tmp/hello Testing':

content => "Hello, world\n",

}

puppet.master]# puppet apply node.pp

Notice: Compiled catalog for puppet.master.com in environment production in 0.16 seconds

Notice: /Stage[main]/Main/Node[puppet.master.com]/File[/tmp/hello Testing]/ensure: defined content as '{md5}a7966bf58e23583c9a5a4059383ff850'

Notice: Finished catalog run in 0.11 seconds

Will not pick up the Node Agent (chat.client).

On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:

Chuck Amadi

unread,

Aug 27, 2015, 2:31:18 AM8/27/15

to Puppet Users

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:

Rich Burroughs

unread,

Aug 27, 2015, 2:45:32 AM8/27/15

to Puppet Users

I'm not that familiar with that log file but it looks like it did a GET and got a 200 back, so I wouldn't guess that indicates a problem.

I saw you have that definition for the node in your node.pp file. What does your site.pp look like?

I'm assuming you've double/triple checked that the file in /tmp does not exist already on the chat node? Because if it got created once with the right content, you'd get the exact behavior you're describing on the following configuration runs.

Rich

--

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...@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.

Chuck Amadi

unread,

Aug 27, 2015, 3:01:06 AM8/27/15

to Puppet Users

Hi Rich,

Yes I got a 200 as well lol. Then realised it's not mine or my Comapnies FQDN.

# wget "http://chat.client.com?transaction_uuid=a4e4515f-ce5e-439d-b662-b92bf136346a"

--2015-08-27 07:22:37-- http://chat.client.com/?transaction_uuid=a4e4515f-ce5e-439d-b662-b92bf136346a

Resolving chat.client.com... 69.172.201.208

Connecting to chat.client.com|69.172.201.208|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/html]

Saving to: `index.html?transaction_uuid=a4e4515f-ce5e-439d-b662-b92bf136346a'

[ <=> ] 1,559 --.-K/s in 0.01s

2015-08-27 07:22:37 (148 KB/s) - `index.html?transaction_uuid=a4e4515f-ce5e-439d-b662-b92bf136346a' saved [1559]

Thanks anyway. Will continue to work it out.

Cheers

On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:

Chuck Amadi

unread,

Aug 27, 2015, 3:18:07 AM8/27/15

to Puppet Users

My site.pp file below:

This file /tmp/mytest_example-ip was created on the Puppet Master.

node 'chat.client.com', 'puppet.master.com' {

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

}

Cheers,

On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:

jcbollinger

unread,

Aug 27, 2015, 10:16:26 AM8/27/15

to Puppet Users

On Wednesday, August 26, 2015 at 9:22:05 PM UTC-5, 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.

You don't necessarily need to disable SELinux to use Puppet, though you may need to add appropriate SELinux policy. In any case, if SELinux were interfering with Puppet then you would see failure diagnostics in Puppet's log / console output.

Also, it is atypical for one site to use both 'puppet apply' and 'puppet master' / 'puppet agent' to obtain and apply catalogs. If you are going to operate a puppet master, then it is more usual to run the agent service on the master than to use 'puppet apply' there.

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.

Perhaps you are confused about the nature of the master / agent setup. Since you keep bringing up the 'apply' face, I wonder whether you are under the impression that the agent serves to synchronize Puppet manifests (.pp files), which could later be used with 'puppet apply'. This is not the case. In an agent / master setup, the master is responsible for compiling digested "catalogs" for each agent based on manifest files and data residing on the master and node-specific facts provided by each agent. The agent receives these catalogs from the master and applies them.

In contrast, 'puppet apply' compiles catalogs from local manifests, data, and facts, and applies the result. The 'apply' and 'agent' faces are alternatives, not complements.

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.

It appears that the catalog received by the agent contains no out-of-sync resources. Given the timing, it may contain no resources at all.

If you changed the site manifests after starting the master, then you may be experiencing a caching issue. Restart the master after making manifest changes to ensure that the new version of the manifest is used.

Also, consider providing a 'default' node block with distinctive resources / behavior. That could help you verify that you are getting the right node block. And consider declaring Notify resources at strategic places in your manifests, such as at top scope and within each node block. Applying these emits the specified message into the agent's log output, so they can serve in Puppet's version of debugging via print statements.

It may also be that the master is not looking for its manifest files in the same place that 'apply' did when run on the same machine, especially if you ran 'apply' as an unprivileged user.

John

Chuck Amadi

unread,

Aug 27, 2015, 4:47:44 PM8/27/15

to Puppet Users

Hi Folks,

OK, so I digested node classification documentation to ensure my nodes attempts can be classified using the correct node definitions as below:

puppet.master # vi /etc/puppet/manifests/site.pp

# site.pp file.

-- sof --

node default {

}

node 'chat.client.com', 'puppet.master.com' { # applies to puppet-client and puppet-master nodes

file {'/tmp/dns': # resource type file and filename

ensure => present, # make sure it exists

mode => 0644,

content => "Only DNS servers get this file.\n",

}

-- eof --

Then restarted the Puppet Master and run "puppet master --verbose --no-daemonize". Even tried this "puppet master --compile chat.client.com", still nothing triggers catalogs for my node "chat.client.com".

puppet.master # puppet apply site.pp --noop

Notice: Compiled catalog for puppet.master.com in environment production in 0.16 seconds << no joy >>

Notice: /Stage[main]/Main/Node[puppet]/File[/tmp/dns]/ensure: current_value absent, should be present (noop)

Notice: Node[puppet]: Would have triggered 'refresh' from 1 events

Notice: Class[Main]: Would have triggered 'refresh' from 1 events

Notice: Stage[main]: Would have triggered 'refresh' from 1 events

Notice: Finished catalog run in 0.09 seconds

puppet.master # puppet apply site.pp

Notice: Compiled catalog for puppet.master.com in environment production in 0.17 seconds

Notice: /Stage[main]/Main/Node[puppet]/File[/tmp/dns]/ensure: created

Notice: Finished catalog run in 0.13 seconds

puppet.master # cat /tmp/dns

Only DNS servers get this file.

puppet.master # vi /etc/puppet/manifests/site.pp

Why does this only trigger on the master if I have two nodes declared ? in the site.pp file. Is there method to force a creation for nodes catalogs.

I tried this on the master but nothing of interest below:

# puppet master --compile chat.client.com

{

"document_type": "Catalog",

"data": {

"resources": [

{

"tags": ["stage"],

"type": "Stage",

"parameters": {

"name": "main"

},

"exported": false,

"title": "main"

},

{

"tags": ["class","settings"],

"type": "Class",

"exported": false,

"title": "Settings"

},

{

"tags": ["class"],

"type": "Class",

"parameters": {

"name": "main"

},

"exported": false,

"title": "main"

}

],

"tags": ["settings"],

"classes": [

"settings"

],

"version": 1440708265,

"edges": [

{

"target": "Class[Settings]",

"source": "Stage[main]"

},

{

"target": "Class[main]",

"source": "Stage[main]"

}

],

"environment": "production",

"name": "chat.client.com"

},

"metadata": {

"api_version": 1

}

TIA.

On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:

Chuck Amadi

unread,

Aug 28, 2015, 2:35:38 AM8/28/15

to Puppet Users

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:

jcbollinger

unread,

Aug 28, 2015, 9:54:46 AM8/28/15

to Puppet Users

On Thursday, August 27, 2015 at 3:47:44 PM UTC-5, Chuck Amadi wrote:

Hi Folks,

OK, so I digested node classification documentation to ensure my nodes attempts can be classified using the correct node definitions as below:

puppet.master # vi /etc/puppet/manifests/site.pp

# site.pp file.

-- sof --

node default {
}

node 'chat.client.com', 'puppet.master.com' { # applies to puppet-client and puppet-master nodes
file {'/tmp/dns': # resource type file and filename
ensure => present, # make sure it exists
mode => 0644,
content => "Only DNS servers get this file.\n",
}
}

-- eof --

Then restarted the Puppet Master and run "puppet master --verbose --no-daemonize". Even tried this "puppet master --compile chat.client.com", still nothing triggers catalogs for my node "chat.client.com".

I'm not sure what you mean be nothing "triggers" catalogs.

puppet.master # puppet apply site.pp --noop
Notice: Compiled catalog for puppet.master.com in environment production in 0.16 seconds << no joy >>
Notice: /Stage[main]/Main/Node[puppet]/File[/tmp/dns]/ensure: current_value absent, should be present (noop)
Notice: Node[puppet]: Would have triggered 'refresh' from 1 events
Notice: Class[Main]: Would have triggered 'refresh' from 1 events
Notice: Stage[main]: Would have triggered 'refresh' from 1 events
Notice: Finished catalog run in 0.09 seconds

What "no joy"? What did you hope would happen that didn't happen?

puppet.master # puppet apply site.pp
Notice: Compiled catalog for puppet.master.com in environment production in 0.17 seconds
Notice: /Stage[main]/Main/Node[puppet]/File[/tmp/dns]/ensure: created
Notice: Finished catalog run in 0.13 seconds
puppet.master # cat /tmp/dns
Only DNS servers get this file.
puppet.master # vi /etc/puppet/manifests/site.pp

Why does this only trigger on the master if I have two nodes declared ? in the site.pp file.

What triggers only if you have two nodes declared? The two "puppet apply" commands you just gave differ in that one uses "--noop". Their results are consistent with each other. I don't see the basis for your claim that behavior differs depending on how many nodes you have declared.

In any event, if your intention is to use a master / agent setup, then I urge you to stop messing around with "puppet apply". It will not give you reliable information about how the master will respond to catalog requests from agents. If you want the master to manage itself, then run the agent there.

Is there method to force a creation for nodes catalogs.

The problem is not your agent failing to obtain a catalog from the master. The agent would complain if it could not retrieve a catalog, and it is not emitting such a complaint. The problem, therefore, is with the contents of the catalog it does receive.

In any event, yes, but you already know "puppet master --compile". Also, restarting the master, as I previously suggested, will ensure that each node's catalog is compiled freshly on the next request.

And that is an empty catalog, or as empty as they come, at least. It does not correspond to the site manifest you presented, so either you have a caching issue on the master, or the master is not consulting the given site manifest at all. The latter might be the case if you are using directory environments, depending on the configuration of environment "production" (the default environment, and the one to which your node is assigned per the above catalog), or if you have configured a different site manifest or site manifest directory in your puppet.conf.

Note also that Puppet looks for configuration in different places depending on its process UID and on command-line options. In part for that reason, it is usually best to start the master via the appropriate service control tool. On CentOS 6, that would probably mean "service puppetmaster start". Supposing that you installed via a PL-provided RPM, it should have installed and registered the necessary initscript.

John

Chuck Amadi

unread,

Aug 28, 2015, 12:47:53 PM8/28/15

to Puppet Users

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:

Christopher Wood

unread,

Aug 28, 2015, 1:14:35 PM8/28/15

to puppet...@googlegroups.com

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.

> 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...@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...@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

Rich Burroughs

unread,

Aug 28, 2015, 2:38:51 PM8/28/15

to puppet...@googlegroups.com

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

To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20150828171410.GA8646%40iniquitous.heresiarch.ca.

Christopher Wood

unread,

Aug 28, 2015, 2:59:45 PM8/28/15

to puppet...@googlegroups.com

True at that, my mail filters had moved much of the thread before I got to this part.

I did see "/etc/puppet/manifest/site.pp" -- manifest not manifests plural -- but I doubt that's what's up here.

Chuck, in your place I might:

1) check the configuration of master and agent, look for where the environment is and where things like manifest dir and module dir are

puppet config print

2) edit any test files like your items in /tmp

echo 'bad line' >> $file
# this gives puppet something to manage, there will be no change to file that matches what the puppetmaster is dishing out

3) run the puppet master and agent in debug mode to see what's happening.

a) stop the puppet master and agent from their daemon'y selves

b) as the puppet user (which the puppet master runs as):

puppet master --debug --no-daemonize --color=false 2>&1 | tee /var/tmp/logm1

c) as the root user (which the puppet agent runs as):

puppet agent --debug --no-daemonize --color=false 2>&1 | tee /var/tmp/logc1

4) read the agent catalog to see what the agent received, and see if stuff listed in the json there is the same as the stuff listed in your pp files

/var/lib/puppet/client_data/catalog/${::fqdn}.json

5) read the logs from above (in /var/tmp) to see what the master/agent were doing, what configs they were using, et cetera

On Fri, Aug 28, 2015 at 06:38:33PM +0000, Rich Burroughs wrote:
> 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
> <[1]christop...@pobox.com> wrote:
>
> It sounds like you may need to back up a little and focus on the basics,
> these will help:
>

> [2]https://learn.puppetlabs.com/category/self-paced-training
>
> [3]https://puppetlabs.com/download-learning-vm
>
> [4]http://docs.puppetlabs.com/

> > Info: Caching node for [1][5]chat.client.com
> > Info: Caching node for [2][6]chat.client.com
> > Notice: Compiled catalog for [3][7]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][8]https://puppet.master.com:8140
> > Debug: Caching connection for
> [5][9]https://puppet.master.com:8140
> > Debug: Closing connection for
> [6][10]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][11]puppet-users...@googlegroups.com.

> > To view this discussion on the web visit
> >

> [8][12]https://groups.google.com/d/msgid/puppet-users/1b28887c-8f0e-4d5a-b8b3-18678ef6e000%40googlegroups.com.
> > For more options, visit [9][13]https://groups.google.com/d/optout.
> >
> > References
> >
> > Visible links
> > 1. [14]http://chat.client.com/
> > 2. [15]http://chat.client.com/
> > 3. [16]http://chat.client.com/
> > 4. [17]https://puppet.master.com:8140/
> > 5. [18]https://puppet.master.com:8140/
> > 6. [19]https://puppet.master.com:8140/
> > 7. mailto:[20]puppet-users...@googlegroups.com
> > 8.
> [21]https://groups.google.com/d/msgid/puppet-users/1b28887c-8f0e-4d5a-b8b3-18678ef6e000%40googlegroups.com?utm_medium=email&utm_source=footer
> > 9. [22]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 [23]puppet-users...@googlegroups.com.

> To view this discussion on the web visit

> [24]https://groups.google.com/d/msgid/puppet-users/20150828171410.GA8646%40iniquitous.heresiarch.ca.
> For more options, visit [25]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 [26]puppet-users...@googlegroups.com.

> To view this discussion on the web visit

Chuck Amadi

unread,

Aug 28, 2015, 3:42:07 PM8/28/15

to Puppet Users

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:

Christopher Wood

unread,

Aug 28, 2015, 3:59:32 PM8/28/15

to puppet...@googlegroups.com

On Fri, Aug 28, 2015 at 12:42:07PM -0700, Chuck Amadi wrote:
> 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

These files exist on the master and each agent will download a catalog from the master. You do not have to create the pp files on each node.

> 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

This part ("node {}") does not look correct.

https://docs.puppetlabs.com/puppet/latest/reference/lang_node_definitions.html

See the "naming" section. The node needs to have a name, probably "the bare word default".

> node 'chat.client.com', 'chat1.client.com', 'chat3.client.com' { #

This part looks correct.

> 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 ?

If only one of your three puppet agents is creating these files when they do not exist you have something else going on. This iw here the debug logs will come in handy. Given that your nodes are FQDNs, make sure that they are actually using the FQDNs you think they are.

hostname -f

> 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...@googlegroups.com.

> To view this discussion on the web visit

> [8]https://groups.google.com/d/msgid/puppet-users/38bd4c0c-4e8b-4ba6-874b-cf761a5cad28%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...@googlegroups.com
> 8. https://groups.google.com/d/msgid/puppet-users/38bd4c0c-4e8b-4ba6-874b-cf761a5cad28%40googlegroups.com?utm_medium=email&utm_source=footer
> 9. https://groups.google.com/d/optout

Chuck Amadi

unread,

Aug 29, 2015, 3:24:26 PM8/29/15

to Puppet Users

Hi Christopher and all,

Utilised your crib troubleshooting checks and found out the following on the Master. Currently looking at working out these debug messages such as, "Debug: Did not match path", but can you confirm if this is a possible reason for my nodes not pulling the manifests from the master ?

"puppet master --debug --no-daemonize --color=false 2>&1 | tee /var/tmp/logm1" Procedure.

# cat /var/tmp/logm1

Debug: Evaluating match for Route /^\/v2\.0/
Debug: Did not match path ("/production/catalog/chat.client.com")

Debug: Evaluating match for Route /^\/v2\.0/
Debug: Did not match path ("/production/reports/chat.client.com")

Debug: Evaluating match for Route /^\/v2\.0/
Debug: Did not match path ("/production/node/chat.client.com")

Debug: Evaluating match for Route /^\/v2\.0/
Debug: Did not match path ("/production/file_metadatas/pluginfacts")

Data from chat.client.com logsc file.

Debug: Loading external facts from /var/lib/puppet/facts.d
Info: Loading facts
Debug: Loading facts from /var/lib/puppet/lib/facter/puppet_vardir.rb
Debug: Loading facts from /var/lib/puppet/lib/facter/root_home.rb
Debug: Loading facts from /var/lib/puppet/lib/facter/concat_basedir.rb
Debug: Loading facts from /var/lib/puppet/lib/facter/pe_version.rb
Debug: Loading facts from /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts
Debug: Failed to load library 'msgpack' for feature 'msgpack'

Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing
Debug: catalog supports formats: pson b64_zlib_yaml yaml dot raw

Debug: Using cached connection for https://puppet.chat.client.com:8140
Debug: Caching connection for https://puppet.chat.client.com:8140
Info: Caching catalog for chat.client.com

Debug: Creating default schedules
Debug: Loaded state in 0.00 seconds

Info: Applying configuration version '1440873225'
Debug: Finishing transaction 70311483905180
Debug: Storing state
Debug: Stored state in 0.02 seconds
Notice: Finished catalog run in 0.11 seconds
Debug: Using cached connection for https://puppet.chat.client.com:8140
Debug: Caching connection for https://puppet.chat.client.com:8140
Debug: Closing connection for https://puppet.chat.client.com:8140

I have checked the json and it appears that I have not pulled no .pp files from the master.

# cat chat.client.json

{"metadata":{"api_version":1},"document_type":"Catalog","data":{"resources":[{"title":"main","tags":["main","stage"],"type":"Stage","exported":false},{"title":"Settings","tags":["settings","class"],"type":"Class","exported":false},{"title":"Main","tags":["main","class"],"type":"Class","parameters":{"name":"main"},"exported":false}],"tags":["settings"],"environment":"production","version":1440873225,"classes":["settings"],"edges":[{"target":"Class[Settings]","source":"Stage[main]"},{"target":"Class[Main]","source":"Stage[main]"}],"name":"chat.client.json"}}

Master puppet.conf file:

[main]
    # The Puppet log directory.
    # The default value is '$vardir/log'.
    logdir = /var/log/puppet

    # Where Puppet PID files are kept.
    # The default value is '$vardir/run'.
    rundir = /var/run/puppet

    # Where SSL certificates are kept.
    # The default value is '$confdir/ssl'.
    ssldir = $vardir/ssl
    always_cache_features=true
    # Looking at using hiera key/value lookup to to config data for the future.
    hiera_config = $confdir/hiera.yaml

    server = puppet.master.com
    dns_alt_names = puppet, puppet.master.com, chat.client.com
    always_cache_features = true
    environment_timeout = unlimited
    environmentpath = $confdir/environments
    certname = puppet.master.com
    user = puppet
    group = puppet
    archive_files = true
    archive_file_server = puppet.master.com

[master]
    environmentpath = $confdir/environments
    basemodulepath = $confdir/modules

# This section is used by the Puppet agent application.
[agent]
    # The file in which puppetd stores a list of the classes
    # associated with the retrieved configuratiion. Can be loaded in
    # the separate ``puppet`` executable using the ``--loadclasses``
    # option.
    # The default value is '$confdir/classes.txt'.
    report = true
    classfile = $vardir/classes.txt

    # Where puppetd caches the local configuration. An
    # extension indicating the cache format is added automatically.
    # The default value is '$confdir/localconfig'.
    localconfig = $vardir/localconfig
    graph = true
    pluginsync = true
    #pluginsync = false
    #environment = production

chat.client.com puppet.conf file.

[main]
    # The Puppet log directory.
    # The default value is '$vardir/log'.
    logdir = /var/log/puppet
    vardir=/var/lib/puppet
    # Where Puppet PID files are kept.
    # The default value is '$vardir/run'.
    rundir = /var/run/puppet
    #factpath=$vardir/lib/facter
    # Where SSL certificates are kept.
    # The default value is '$confdir/ssl'.
    ssldir = $vardir/ssl
    server = puppet.chat.client.com
    ordering = manifest
    certificate_revocation = false

# This section is used by the Puppet agent application.
[agent]
    # The file in which puppetd stores a list of the classes
    # associated with the retrieved configuratiion. Can be loaded in
    # the separate ``puppet`` executable using the ``--loadclasses``
    # option.
    # The default value is '$confdir/classes.txt'.
    #report = true
    classfile = $vardir/classes.txt

    server=puppet.chat.client.com

    # Where puppetd caches the local configuration. An
    # extension indicating the cache format is added automatically.
    # The default value is '$confdir/localconfig'.
    localconfig = $vardir/localconfig
    #graph = true
    #pluginsync = true
    #pluginsync = false
    # Have tried commenting this out, but nothing happened so kept the commented it for now.
    #environment = production

Thanks for your help and advise.

On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:

Rich Burroughs

unread,

Aug 29, 2015, 3:50:39 PM8/29/15

to Puppet Users

So Chuck, it looks like you are set up to use what's called directory environments. And I think your site.pp is not in the right place for that setup.

This is in your master config:

environmentpath = $confdir/environments

And your agent is using the default environment, production.

So your site.pp should be located at:

$confdir/environments/production/manifests/site.pp

You can see what the value of $confdir is on your master by running:

sudo puppet config print confdir

This issue actually matches up perfectly with the behavior you're seeing. The agent is running fine but there's just nothing for it to do because the code you're testing is not in the site.pp that the master is actually looking at. So when it compiles the catalog it's not including that resource you're trying to test with.

If you add your code to the site.pp in that location I have a feeling it will work.

This stuff around environments is honestly confusing at first. It was set up so people can run their Puppet master against code in different Git branches.

Rich

--

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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cbea94ba-2216-4bae-be61-4456dd4e16ee%40googlegroups.com.

Chuck Amadi

unread,

Aug 29, 2015, 3:50:47 PM8/29/15

to Puppet Users

Hi All,

Just to note I have added

"environment = production" directives to both master and agent puppet.conf file and still seeing those Debug : Did not match path ("/production/*)" messages.

Cheers,

On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:

Rich Burroughs

unread,

Aug 29, 2015, 3:53:24 PM8/29/15

to Puppet Users

production is the default environment. That's what an agent will use unless you override it with something else.

Rich

--

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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/665c7e02-6b8a-44b3-9d05-73549e3ab83a%40googlegroups.com.

Chuck Amadi

unread,

Aug 29, 2015, 9:35:23 PM8/29/15

to Puppet Users

Hi Rich,

Thanks for clarifying that, I was added that directive because of the these Debug messages "Debug: Did not match path *".

I am still going through all the puppet.conf's directives and retracing my steps as a few months ago, my vps worked like a charm on my vps servers, attempting to familiarising before trying deploy a test case at woek , but I have broken that seemingly :(

Something will go ding, hopefully sooner than later.

Cheers,

On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:

Rich Burroughs

unread,

Aug 29, 2015, 9:50:23 PM8/29/15

to puppet...@googlegroups.com

Did you see my other message about how your site.pp is in the wrong place? I think that was maybe the cause of those debug messages.

I think at least that part of it should work if you get the file into the right place. I sent it right before the message you just replied to :)

Rich

--

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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/aa32ea74-c6e3-48dc-931a-3b4d59f2fe76%40googlegroups.com.

Chuck Amadi

unread,

Aug 30, 2015, 1:10:06 AM8/30/15

to Puppet Users

Hi Rich,

Guess what ?

My vps are back in business.

Much appreciated, now I can continue on the Work Project and add a progress report. :)

Rich Burroughs

unread,

Aug 30, 2015, 1:25:56 AM8/30/15

to Puppet Users

Awesome :)

Rich

--

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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/34ae1fa5-714a-49e3-a4e0-2c96348468f1%40googlegroups.com.

Reply all

Reply to author

Forward