On Thu, Jun 24, 2010 at 10:48 PM, Douglas Garstang
wrote:
> On Thu, Jun 24, 2010 at 6:20 PM, Gary Larizza wrote:
>> Yep - I narrowed it down to Rack and Passenger, but haven't tested for
>> exactly which one was the problem since I fixed it. I should have
>> probably submitted a bug. We were usi
Hi all,
Is it possible to override the behaviour of all instances of a
resource from a module?
I would like to have my "apt" module add a requirement for Exec["apt-
get update"] to all Package resources.
putting
Package { require => Exec["apt-get update"] }
in the module itself won't work, since
On Thu, Jun 24, 2010 at 6:20 PM, Gary Larizza wrote:
> Yep - I narrowed it down to Rack and Passenger, but haven't tested for
> exactly which one was the problem since I fixed it. I should have
> probably submitted a bug. We were using OS X 10.6.4 Server, BTW.
>
> On Thursday, June 24, 2010, Silv
Yep - I narrowed it down to Rack and Passenger, but haven't tested for
exactly which one was the problem since I fixed it. I should have
probably submitted a bug. We were using OS X 10.6.4 Server, BTW.
On Thursday, June 24, 2010, Silviu Paragina wrote:
> Also check the rack version, and the requ
Also check the rack version, and the requirements for your version of
passenger. It smells like an incompatibility between the passenger
version and the rack version.
Aka what Gary said should be perfectly valid.
Silviu
On 25.06.2010 02:50, Douglas Garstang wrote:
I have a freshly installed
On 23.06.2010 17:19, zu...@puzzle.ch wrote:
Hello
I use puppet for a while now and try to configure as much as possible with
puppet (some old configurations are still not 'puppetized'). The more we
configure with puppet the more complex the manifests get. They are filled
with functionality and c
Check Passenger version. Had this problem, rolled back to 2.2.9
(IIRC), removed the most recent Gem (2.2.11, I think), and all was
well.
On Thursday, June 24, 2010, Douglas Garstang wrote:
> I have a freshly installed and updated CentOS 5.4 system running
> puppet 0.25.5. I followed the passenger
I have a freshly installed and updated CentOS 5.4 system running
puppet 0.25.5. I followed the passenger docs here:
http://projects.puppetlabs.com/projects/puppet/wiki/Using_Passenger
Upon starting the client, the following appears in the apache error log.
[Thu Jun 24 10:48:40 2010] [error] [cli
This is kind of a meta-puppet question. If you are keeping your puppet modules
-- manifests + templates + files -- in revision control (and you are, right?),
how do you manage releasing out to the world? Let me start out with our setup
and if other folks can follow up in a similar format perhaps
Has anyone tried using this puppet forge module with a certificate?
(puppetlabs/vcsrepo) Any ideas on how to specify via command line to git
what certificate to use?
The only way that I know to tell git to use a specific certificate is to
use the GIT_SSH env variable and specify a script which
> -Original Message-
> From: puppet-users@googlegroups.com [mailto:puppet-
> us...@googlegroups.com] On Behalf Of Daniel Pittman
> Sent: Wednesday, June 02, 2010 1:36 AM
> To: puppet-users@googlegroups.com
> Subject: Re: [Puppet Users] do X if package Y is installed?
>
> Bill Weiss writes
Some days I wonder why I even bother with puppet.
---
classes:
- datacentre::new_york
- role::appserver
- elements::tfel0
environment: production:
parameters:
< set key/value pairs here >
class ldap {
< do some stuff that behaves slightly differently between different
data centers >
}
cl
We have an environment that depends largely on a series of NFS mounts
on our application systems. Sometimes NFS mounts go away, things stop
working.
In the past, I've had problems with autofs (rpc storms) when things go
badly, and we're just beginning to get int Puppet (read: I'm learning
it).
thanks Brice,
that's a very good point and I am going to investigate it. the master is
running as a virtual machine with limited resources so this can be really the
issue.
thanks, Antony.
From: Brice Figureau
To: puppet-users@googlegroups.com
Sent: Thu, 24 J
Maybe it's just me stumbling with object inheritance, but here's a
simple example of some of the issues I can't quite get my head around
with puppet.
Lets say nodes might be either physical or virtual, and each requires
slightly different stuff to be installed. Lets also say that we have
applicati
On 24/06/10 14:51, Antony Mayi wrote:
> [snip]
> In about 10% of all runs Puppet randomly fails on some (random) File
> resource either with this error:
>
> Thu Jun 24 02:40:03 + 2010 ///File[]
> (err): Failed to generate additional resources using 'eval_generate':
>
> or this error:
>
> Wed
Hello Fellows,
I am running into an odd bug trying to setup External Nodes with
Puppet Dashboard. I have a presentation to give to my clients by
12:00PM. I was hoping to show them how to manage classes and nodes
using the DB. Many thanks if the solution jumps out at anyone and they
can help me bef
Hi,
I thing this issue has been mentioned several times in this list but I
can't see any conclusion.
In about 10% of all runs Puppet randomly fails on some (random) File
resource either with this error:
Thu Jun 24 02:40:03 + 2010 ///File[]
(err): Failed to generate additional resources using
I'd like to broaden the concept a little. What do you guys suggest I
can do to realize all virtual users and all virtual groups outlined in
their respective classes, ensuring that the groups get realized before
the users do? Collection or realize method? Syntax suggestions?
Thanks,
On Jun 23
Problem solved. The ruby-shadow rpm I had obtained wasn't delivering
the appropriate libraries to the x64 system. I recompiled the source
rpm, and that did the trick. Everything works again.
Thanks for the feedback.
Cheers,
On Jun 23, 7:46 pm, "Kinzel, David" wrote:
> >Hello,
>
> > I ha
my node definitions look like this:
node basenode {
$utility_network = x.x.x.x
[...]
}
node 'mcp.c42' inherits basenode {
$my_local_network = $utility_network
$my_default_gateway = $utility_default_gateway
$my_netmask = $utility_netmask
$my_eth1_default_gateway = $
21 matches
Mail list logo