Hi,
I have just published the module I use to manage POSIX ACLs : fooacl
I don't consider it the cleanest possible approach to the problem, but
it's very efficient and flexible. I would actually call it a hack :-)
There's room for improvement, such as splitting out Execs per managed
path to avoi
Hi,
On our puppet server the puppet environments do not seem to work. This is
our puppet.conf:
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
confdir=/etc/puppet
templatedir=$confdir/templates
modulepath=$confdi
Not certain if this is the issue or not, but there seems to be a bug in the
master regarding when the configuration file is read to override the
default settings. Try doing this:
1) start up your puppet master
2) after it is up and running try running this from the command line *touch
/etc/puppet
Thnaks, i tried but it didn't work. We do not start puppetmaster as a
standalone service so I stopped and started apache. (can that have anything
to do with the problem ?)
On Tuesday, December 17, 2013 3:08:41 PM UTC+1, John Pyeatt wrote:
>
> Not certain if this is the issue or not, but there se
On Tuesday, December 17, 2013 5:10:20 AM UTC-6, Matthias Saou wrote:
>
> Hi,
>
> I have just published the module I use to manage POSIX ACLs : fooacl
>
> I don't consider it the cleanest possible approach to the problem, but
> it's very efficient and flexible. I would actually call it a hack :
Hello,
I'm using the following expression to format a list:
$valid_environments = ['env1', 'env2', 'env3']
$env_message = $valid_environments.reduce |$message, $env| {
"${message}, ${env}" }
It works at run-time (Puppet 3.2.4 standalone with "--parser=future").
However in Eclip
hey,
so i just installed puppetdb on a dedicated server (with pgsql).
I noticed that the puppet master server doesn't load any facts.
root@puppetmaster:~$ puppet agent -t
> Info: Retrieving plugin
> Info: Caching catalog for puppetmaster.local.domain
> Info: 'replace catalog' command for puppet
I'm a bit late to this thread, but I ran into the same problem with the
puppetlabs-mysql module - it's a bug in how the module was written. There
is a fork by the folks at MediaTemple which addressed that issue:
https://github.com/mediatemple/puppetlabs-mysql
I've been using that successfully for
That is very, very disturbing.
On Wednesday, December 11, 2013 2:25:04 PM UTC-8, Stuart Cracraft wrote:
>
>
> I want to recursively descend infinitely through a directory tree in
> regards to ensuring:
>
> (a) owner, group, permission
> (b) existence of the full path, all the leaves, out to t
There is a problem with variable hooks in puppet.conf that is fixed in
the latest 3.4 release candidates (or so sayeth the bugreps).
Can you try explicitly specifying your directories instead of using
$confdir in that puppet.conf, at least to test?
Jeff
On 12/17/2013 09:18 AM, Chantal Rosmul
Have you tried experimenting ?Much of my Puppet savvy is from tinkering.
Try some code. See what works and what does not work. "Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us."Bill Waterson
(Calvin & Hobbes)
--
I don't have time to play hunt-the-wumpus.
> On Dec 17, 2013, at 1:54 PM, y...@comcast.net wrote:
>
> Have you tried experimenting ?
> Much of my Puppet savvy is from tinkering.
>
> Try some code. See what works and what does not work.
>
> "Sometimes I think the surest sign that intelligent
Have you tried a yaml to csv converter like
https://github.com/tokland/yaml2csv ? Note that it seems to require the
csv module syntax from ruby 1.9.3.
Jeff
On 12/16/2013 03:29 PM, Stuart Cracraft wrote:
Is the back-end piece of Puppet Dashboard which implements the
CSV-capability
of the YAML
> > http://christian.hofstaedtler.name/blog/2008/11/puppet-managing-directories-recursively.html
I thought I had understood recursive directory management. It worked
fine until I switched to puppet v3 (Debian 3.3.2-1puppetla to be exact)
Since then, files in subdirs aren't copied anymore.
An exa
This is very interesting Jeff.
I will play with it.
Thanks!
> On Dec 17, 2013, at 2:04 PM, Jeff Bachtel
> wrote:
>
> Have you tried a yaml to csv converter like
> https://github.com/tokland/yaml2csv ? Note that it seems to require the csv
> module syntax from ruby 1.9.3.
>
> Jeff
>
>> O
It looks like Amazon/publishers/authors/etc. have revised the new puppet
book date:
http://www.amazon.com/Pro-Puppet-Spencer-Krum/dp/1430260408/ref=sr_1_3?ie=UTF8&qid=1387318030&sr=8-3&keywords=puppet+3
Fun!
--
You received this message because you are subscribed to the Google Groups
"Puppet
Stuart, googling the rake error you were getting resulted in the following hit:
http://stackoverflow.com/questions/15349869/undefined-method-source-index-for-gemmodule-nomethoderror
Which indicated the version of rubygems is not compatible with the
rails application.
On Mon, Dec 16, 2013 at 10:3
On Dec 17, 2013, at 9:56 AM, cko wrote:
> hey,
>
> so i just installed puppetdb on a dedicated server (with pgsql).
>
> I noticed that the puppet master server doesn't load any facts.
What do you mean "doesn't load any facts"? What is the problem you're seeing?
>
> root@puppetmaster:~$ pupp
All to nought. No change alas.
Confirmation of version:
[root@ca-sna-pm01 puppet-dashboard]# gem list | grep rubygem
rubygems-update (1.8.25)
[root@ca-sna-pm01 puppet-dashboard]#
Retry of Schematization:
[root@ca-sna-pm01 puppet-dashboard]# !1441
rake RAILS_ENV=producti
Alas, it was all for naught.
Anyone know about the uninitialized constant Yaml2csv error?
[root@ca-sna-pm01 bin]# /usr/local/bin/yaml2csv.rb foobar.yml
./yaml2csv.rb:43: uninitialized constant Yaml2csv (NameError)
from
/usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:4
On 2013-17-12 17:23, Igor Berger wrote:
Hello,
I'm using the following expression to format a list:
$valid_environments = ['env1', 'env2', 'env3']
$env_message = $valid_environments.reduce |$message, $env| {
"${message}, ${env}" }
It works at run-time (Puppet 3.2.4 standalone with "--
This is my first attempt with Puppet, and I'm working on FreeBSD 9.2 with
Puppet 3.3.1 and Ruby 2.0. I'm starting with just a very simple example to
get my feet wet:
node 'myhost' {
package { 'devel/jsmin':
ensure => 'installed',
provider => 'ports'
}
}
When I apply this with:
pu
puppet 3.3.2 on RHEL6
If I run puppet on a node:
# sudo puppet agent --test --noop
I get the following error:
*Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Duplicate declaration: Package[bind] is already declared in file
/etc/puppet/modules/site/manifests/dns_te
I'm a first-time Puppet user, working with FreeBSD 9.2, Puppet 3.3.1, and
Ruby 2.0. I'm starting out with a very simple setup to test the waters:
node 'myhost' {
package { 'devel/jsmin':
ensure => 'installed',
provider => 'ports'
}
}
When I run:
puppet apply -v --debug manifests/si
If you override something in a recursive directory, you're overriding
everything. The subdirectories are being managed explicitly by the resource
managing them, not by a combination of it and the parent. Look inline below:
On Tuesday, December 17, 2013 11:12:21 AM UTC-8, Andy Spiegl wrote:
>
> >
>
>
> file { '/var/lib/nagios/plugins':
>> ensure=> directory,
>> recurse => true,
>> mode => '0775',
>> }
>
>
I should also point out that this is unnecessary, as Puppet will
automatically promote read permissions to read & execute permissions for
dir
First, to clarify - do you have pkgng installed on your FreeBSD box?
That is, should you be using /usr/sbin/pkg instead of
/usr/local/bin/pkg_info if you are doing local package management?
If so, the current freebsd provider is not likely to work well for you,
as it's pretty tied into the old
On 12/17/2013 04:31 PM, Patrick Gibson wrote:
> Debug: Executing '/usr/local/sbin/portupgrade -N -M BATCH=yes devel/jsmin'
In short, out-of-the-box, puppet is broken on FreeBSD in regards to package
handling.
Portupgrade doesn't like being run with stdin not being a terminal. You'll
probably find
Do you have use_cached_catalog set on puppet agents or puppetmaster? Are
you using storeconfigs / puppetdb?
Offhand, I'd guess that when you modify mtime of site.pp by saving, that
forces puppet to invalidate the cached catalog and temporarily resolve
the problem.
If necessary, are you able
Facter 1.7.4
---
- Final: Released December 17, 2013
- RC1: December 9, 2013
Facter 1.7.4 Downloads
--
Source: https://downloads.puppetlabs.com/facter/facter-1.7.4.tar.gz
Available in native package format in the pre-
On Mon, Dec 16, 2013 at 8:19 AM, Erik Dalén wrote:
> What is the desired workflow for submitting a pull request for a ticket?
>
>
Charlie wrapped up the documentation for this here:
http://docs.puppetlabs.com/community/puppet_projects_workflow.html If you
find issues or have questions, please let
Hi everyone,
I've been using a traditional model within puppet defining nodes, applying
classes, and some logic within in a pp file. I'm now in the process of moving
everything away from this model as it has grown beyond the manageable size.
I'm looking at using foreman as an enc and at the sam
Every node (except for the master) does something like this when i run
"puppet agent -t":
root@node1:~$ puppet agent -t
> Info: Retrieving plugin
> Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/environment.rb
> Info: Loadi
33 matches
Mail list logo
