On 24 April 2013 06:18, Mike Power dodts...@gmail.com wrote:
In git they set recurse to true. Compound that with a resource default up
the declaration stack and you have puppet spending a long time uselessly
changing the ownership and permission on a ton a files when they get
checked out.
You get also this error when puppet master server is disabled or
unresponsive (there is no response to the client and you get error)
Make sure that your puppet master server is running by command:
ps -aux
If process is running and you still get this error message, kill this
process (kill
On 04/24/2013 02:34 PM, Przemek wrote:
ps -aux
That should just be ps aux, no dash, actually.
On 04/24/2013 12:24 AM, martp...@gmail.com wrote:
I am able to ssh to both host. Am now getting the error: [Could not
request certificate: Connection refused]
This error is different to the
On Tuesday, April 23, 2013 4:52:11 PM UTC-5, Mike Power wrote:
I have been backed into a corner, by they way puppet works, but some third
party module.
Basically I have two resources defined:
a {$somevar:}
b::b {$somrvar:}
both have code that looks something like this:
if
On Tuesday, April 23, 2013 12:02:49 PM UTC-5, Smashed wrote:
It looks like when you use composition you can't redefine a class:
https://gist.github.com/anonymous/5445418 IE.. you can't redefine a
resource that was included.
That is correct. It is also a different case from the one in
I appreciate the reply but I think the thrust of my point is getting missed.
Any other solution is far more cryptic, some reader coming and reading the
code will not understand the code nearly as well.
The fact that puppet has a dimension (parse order) that is so convoluted
that its behavior
Any suggestion of a fix would be appreciated.
I had the same error while using the PE installer (v2.8.1) on AWS and
CentOS 6.3 64bit.
Yet it worked fine on Amazon Linux AMI.
Cheers.
On Friday, 1 February 2013 05:47:48 UTC, Mike Beauchamp wrote:
Would love to know what the fix was, having the
Hello Puppeteers,
please consider the following scenario: Puppet is supposed to set up similar
(but not necessarily identical) groups of hosts for a range of customers. For
each customer a dedicated filesystem tree needs to be established on host A.
This should not be difficult using
Thanks Ken. Bug 20392 is now created for this.
On Wed, Apr 24, 2013 at 12:46 PM, Ken Barber k...@puppetlabs.com wrote:
Hiya,
So at the moment there is no way to do this with the /v2/nodes API -
you can query particular nodes that are deactivated but you can't
filter around the deactivated
I keep running into the following upgrade pattern.
Previous Puppet run declared:
file { my_jar.1.2.3.jar: ... }
New puppet run declares:
file {my_jar.2.4.6.jar: ... }
But the new puppet run doesn't delete the older versions of this jar file.
Is there a standard puppet pattern for
I am trying to use puppetlabs apache module on CentOS to install mod php
package.
class {'apache::mod::php': }
It returns error Error: Could not find dependency Package[httpd] for
A2mod[php5]. I am using Puppet 3.1 version.
Do I need to call class{'apache': } explicitly to get mod-php
I updated some of my gems, and I think it may be the reason I am getting
the following error when the agents try to retrieve a catalog.
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
The single-table inheritance mechanism failed to locate the subclass:
Ubuntu 12.04 has Puppet v2.7.11.
These
http://docs.puppetlabs.com/puppet/2.7/reference/modules_installing.html docs
talk about 2.7.14 and later. Specifically, the puppet module commands.
So, is there a PPA, or another method (other than compiling from source),
to update Puppet?
FYI, I did
On 4/24/2013 4:26 PM, David Reagan wrote:
Ubuntu 12.04 has Puppet v2.7.11.
These
http://docs.puppetlabs.com/puppet/2.7/reference/modules_installing.html docs
talk about 2.7.14 and later. Specifically, the puppet module commands.
So, is there a PPA, or another method (other than compiling from
See http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html
Duh.
Note that just upgrading didn't work to go from 2.7 to 3.1. Nor did
dist-upgrade. I had to run apt-get purge puppet, then apt-get install
puppet to get it installed correctly.
On Wednesday, April 24, 2013 4:26:11
Just declare or include apache without the chaining syntax. Should work
fine.
include apache
class {'apache::mod::php': }
On Wednesday, April 24, 2013 4:22:21 PM UTC-6, jmar...@gmail.com wrote:
I am trying to use puppetlabs apache module on CentOS to install mod php
package.
class
16 matches
Mail list logo
