Are you using custom facts?
If so, you should check to see if any of them are unintentionally doing Bad
Things, e.g., modifying global state like environment variables.
-Josh
On Sep 24, 2011, at 7:22 AM, treydock wrote:
>
>
> On Sep 23, 5:42 pm, Brian Gupta wrote:
>> Over the years many sho
Hi Lars,
Take a look at virtual resources:
http://projects.puppetlabs.com/projects/1/wiki/Virtual_Resources
-Josh
On Nov 18, 2010, at 3:28 PM, Lars Francke wrote:
> Hi,
>
> I'm trying to manage our Hadoop cluster with Puppet but there are a
> few challenges. The one I'm facing now is managing
I'm afraid that I couldn't reproduce this on a Debian VM with Kai's example.
Here's my attempt:
j...@debian:~$ uname -a
Linux debian 2.6.18.8-x86_64-linode10 #1 SMP Tue Nov 10 16:29:17 UTC 2009
x86_64 GNU/Linux
j...@debian:~$ ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]
j...@deb
On Feb 9, 2010, at 11:12 AM, Tim Stoop wrote:
> file { "/tmp": mode => 1777 }
I think you're seeing odd behavior because Puppet doesn't know that /tmp is
supposed to be a directory.
Try this instead:
file { "/tmp": ensure => directory, mode => 1777 }
-Josh
--
You received this message becau
Adding --logdest /path/to/your/log to your config.ru file should work. Here's
what I'm using with 0.25.1 and Passenger 2.2.7:
# a config.ru, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.
# if puppet is not i
Nevermind, I fooled myself.
Initially, I had set checksum => mtime on my test file (to try to
avoid the disk I/O of checksumming a 30MB file). I didn't realize that
using the source parameter forced an MD5 checksum, and that was why I
saw the file content being read in truss.
I did find a
Hi all,
I'm testing fileserving performance under 0.25 and I noticed that
processing large files seems to take much longer than it should.
Here's what I've got:
class filetest {
file { "/var/tmp/test.tar":
source => "puppet:///filetest/test.tar",
backup
> Been racking my brain and I don't think there is a way to do it so I
> come to the experts. I have a puppet server and a client. Pretty
> simple - so here is the problem. I have a job that runs on the CLIENT
> and creates a file. I want puppet to notice when this file changes on
> the CLIENT and
On Mar 17, 2009, at 7:45 AM, Ivo van der Meer wrote:
> Is my syntax wrong or isn't it possible yet to use the "ensure"
> statement
> like this ?
>
>
>"sym_ldap.conf":
> path => $operatingsystem ? {
>"FreeBSD" => "/usr/local/etc/ldap.conf",
>"Debian" => "/etc/ldap.conf"
Having to work around defining parent directories multiple times is
kind of annoying. It'd be nice to be able to say something like:
file { "/usr/local/something":
ensure => directory,
createparent => true
}
This would be the equivalent of doing a mkdir -p. The parent directory
(or dir
Hi, Daniel.
> So, we have these machine configurations:
>
> NTP master: fetch from an upstream server, serve local subnet
> NTP client: fetch from local server, serve no one
>
> We need, for each host, to configure it as either an NTP master or
> client, talking to the appropriate servers — and
Case statements don't work inside of resource definitions. There are
three ways I can think of do what you're doing:
1. Use multiple inline selectors. (Very long and ugly.)
2. Write four different definitions of the NTP service and wrap them
in a case statement (Not as long, but still ugly.)
You have to run facter with the "-p" argument if you want to see facts
distributed by Puppet.
-Josh
On Mar 9, 2009, at 1:50 PM, Steve Wray wrote:
>
> Hi there,
>
> I'm trying to use a fact to tell whether the machine is virtualised.
>
> I found this and, in testing, its been ok:
> http://redu
That's rather odd. I just tested it with 0.24.7 on my workstation, and
the "ensure => [link target]" syntax works for me. Do you see anything
odd in the logs?
-Josh
On Mar 9, 2009, at 1:10 PM, Steve Wray wrote:
>
> Based on the documentation I had thought that this:
>
> file { "/var/puppe
On Mar 2, 2009, at 6:18 AM, Arnau Bria wrote:
> So, when all hosts connect, I get 100 connections per daemon, more or
> less. (When I started I did it with 3 puppetmasters and I got too many
> connections, and I got " Connection timeout calling
> puppetmaster.getconfig" many times, now it happens
Hi, everyone.
I'm trying to set up multiple CAs as described on the wiki at
http://reductivelabs.com/trac/puppet/wiki/MultipleCertificateAuthorities
, but I've run into an annoying problem.
I followed the instructions on the page exactly and openssl s_client/
s_server is able to verify the cer
16 matches
Mail list logo
