On 1 August 2011 15:47, Nikolay Sturm goo...@erisiandiscord.de wrote:
* Lars Kellogg-Stedman [2011-07-29]:
I am trying to place some sanity checks (currently as git pre-commit
hooks) in our configuration repository to avoid committing invalid
Puppet configurations.
This is exactly the
You can indeed use Exported resources.
See the first example in this documentation:
http://docs.puppetlabs.com/guides/exported_resources.html
The example shows how to have every host export its SSH public key,
and then collect every host’s key and install it in the
ssh_known_hosts file (which
The Fact will get downloaded ahead of the manifest being compiled.
You just need to add a require = Service[myservice] to the config
file.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
Hi,
I am bringing back a topic that I started a month ago. Summer holidays
prevented me from following up on it back then, but they didn't make the
problem go away, unfortunately ;-)
Having installed Puppet 2.7.1 on my testserver yesterday, I am now bugged
by log messages, that tell me not to
On Jul 29, 7:55 am, Oliver Beattie oli...@obeattie.com wrote:
Hi,
I need to use the output of a script to set the value of a variable. I
understand the only way to do this is to use a custom Facter fact.
However, this script will only run when (naturally) it's been installed,
which is
On Jul 29, 11:17 am, Paul Morgan jumanji...@gmail.com wrote:
On Jul 29, 2011 9:25 AM, Oliver Beattie oli...@obeattie.com wrote:
I need it to run at a specified point during the manifest though. The
value of the fact depends on a package being installed. And my config files
depend on the
HI Doug,
I am also facing the same issue after following the steps from the
book. I tried with nginx and passenger and i mentioned it on the
following post.
http://groups.google.com/group/puppet-users/browse_thread/thread/44bc89455ccc311a#
Regards,
Kevin
Douglas Garstang wrote:
prep for 2.8: scopes and variables: nodes are not classes
I have been preparing for 2.8 by
experimenting with 2.7.X and seeing
what it takes to get rid of the
warnings. I would like to share my
results in a number of upcoming posts.
Begin with the simple question of
hard-wiring scopes. the
On Mon, Aug 1, 2011 at 8:03 AM, linuxbsdfreak linuxbsdfr...@gmail.comwrote:
HI Doug,
I am also facing the same issue after following the steps from the
book. I tried with nginx and passenger and i mentioned it on the
following post.
Hi, I'm quite new to Puppet.. I'm wondering if someone could point me
in the right direction regarding the best way to manage a temporary
requirement within Puppet?
The scenario is, every server in our estate of Debian machines
requires some monitoring software which is not provided as a Debian
Seeing exactly the same, nearly the same setup (using $environment instead
of hardcoding production/development, trying to use my own extension).
Running puppet 2.6.9 on CentOS 5.6 (both master and agent). I did not see
any issue about this yet, but since I'm just starting with puppet it might
Hi,
I'm trying to use stored configs with puppet 2.7.1
But I get the following error once puppet agent connects to the
master:
err: !!! Outdated mysql gem. Upgrade to 2.8.1 or later. In your
Gemfile: gem 'mysql', '2.8.1'. Or use gem 'mysql2'
This seems to be activerecord (3.0.9) check - BUT I've
We just started testing CentOS 6.0 here, and I'm using Facter 1.6.0
If I run this command from my CentOS 5.x test machine:
[root@puppetclient.nj1:~]# facter --version
1.6.0
[root@puppetclient.nj1:~]# facter | grep lsb
lsbdistcodename = Final
lsbdistdescription = CentOS release 5.3 (Final)
Hi,
I'm trying to retrieve a configuration value from a local file in a
custom fact. I'm having some problems with this though. I hope,
someone can point me to the right direction.
My configuration file looks something like this:
cat /tmp/example.properties
On 30/07/11 05:26, Derek J. Balling wrote:
We just started testing CentOS 6.0 here, and I'm using Facter 1.6.0
If I run this command from my CentOS 5.x test machine:
[root@puppetclient.nj1:~]# facter --version
1.6.0
[root@puppetclient.nj1:~]# facter | grep lsb
lsbdistcodename = Final
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is this a known issue? Is there any work-around? It's really breaking my
CentOS 6 servers' ability to find their REPOs. :-)
You need to have the lsb_release command installed for the lsb* results
to appear.
Fedora/Redhat have it in the
On 08/01/2011 06:40 AM, David wrote:
The scenario is, every server in our estate of Debian machines
requires some monitoring software which is not provided as a Debian
package.
You should make your own debian package(s) for the monitoring software
instead of installing from source on every
Is the redhat-lsb package installed? IIRC it provides the necessary info
for the lsb facts.
On Aug 1, 2011 8:27 AM, Derek J. Balling dr...@megacity.org wrote:
We just started testing CentOS 6.0 here, and I'm using Facter 1.6.0
If I run this command from my CentOS 5.x test machine:
Peter Meier wrote :
Is this a known issue? Is there any work-around? It's really breaking my
CentOS 6 servers' ability to find their REPOs. :-)
You need to have the lsb_release command installed for the lsb* results
to appear.
Fedora/Redhat have it in the redhat-lsb package, so
On Thu, Jul 21, 2011 at 7:37 AM, Peter Meier peter.me...@immerda.ch wrote:
I'm still not getting my error() messages in the report yaml ... why?
Probably, because functions are evaluated on the master, while the
report is created on the client when the catalog is applied. So these
messages
Is anyone having success with #includedir option in sudo? I have a
module that uses a definition to create files in /etc/sudoers.d/ which
is referenced in the main suders file as #includedir /etc/sudoers,
but these entries are not getting referenced when sudo is used.
I'm running CentOS 5 and 6,
Yup. This is totally the right way to do that.
If you don't want to, I would suggest that you compile once, tar up
the content, and just untar it on the machine.
If you really, really want to go through installing the compiler,
building, then removing it, you can: write your script to use apt
I want to start out with an apache class that will disable all modules
except for a pre-defined list, thus establishing a baseline of active
modules.
Then as needed, other classes could enable a module that they require
that would have been disabled by the baseline state.
Its possible several
Take a look at Jordan Sissel's FPM software if you want a cheap way of
making a deb.
Ken.
On Aug 1, 2011 7:10 PM, Daniel Pittman dan...@puppetlabs.com wrote:
Yup. This is totally the right way to do that.
If you don't want to, I would suggest that you compile once, tar up
the content, and
Hello all,
I've recently installed a puppet PKI as detailed in the Multiple
Certificate Authorities document. However, when I try to list the
signed certificates using puppet cert list --all, I get the following
output:
- bnjpuppet02.mydomain.com
It's working here for RHEL 5 6. Check the owner and perms of sudoers.d,
that's probably not your problem, but it's the only one we've had.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
It is not listed in the command details on this page?
http://docs.puppetlabs.com/man/agent.html
But it is cited as an example of a valid puppet agent command at the
very bottom of the page.
Kinda confusing.
--
You received this message because you are subscribed to the Google Groups
Puppet
Hi there. Can somebody help me diagnose an error?
On the Puppet Master node, we've started the Puppet Master with:
ubuntu@domU-12-31-39-09-x-x:~$ sudo puppet master
Then from a node where we want to apply updates, I ran:
ubuntu@ip-10-72-x-x:~$ sudo puppet agent --server domU-12-31-39-x-x-
On Mon, Aug 1, 2011 at 1:50 PM, Blueplastic sam...@blueplastic.com wrote:
It is not listed in the command details on this page?
http://docs.puppetlabs.com/man/agent.html
But it is cited as an example of a valid puppet agent command at the
very bottom of the page.
Kinda confusing.
--
I'm currently using Puppet (2.7.1) to manage a single site. I'm in the
process of bringing up a second data center which of course will be
managed by Puppet. The number of managed sites will grow to at least 7
in the near future. How is everyone else handling multiple sites
within puppet?
Here's
Thanks for the replies.
I did start off down the route of distributing binaries but was having
problems getting them to run on the different architectures involved
and ended up with multiple packages - and every time I needed to tweak
the build config I was having to rebuild multiple times.
It
On Aug 1, 6:37 am, Martijn Grendelman mart...@iphion.nl wrote:
[...]
In classes that have been defined in the top scope (imported in site.pp),
I can use the fully qualified names ($::somevar). That results in the
correct value, and it doesn't generate any warnings about dynamic scoping.
From the sudoer docs it mentioned making the files in /etc/sudoers.d
be 440, but what about the folder? Here's the perms on /etc/sudoers.d
drwxr-xr-x 2 root root 4096 Jul 26 19:16 .
drwxr-xr-x. 64 root root 4096 Jul 26 19:16 ..
-r--r- 1 root root 53 Jul 26 19:16 zabbix-puppet
- Trey
These are the perms we're using for that functionality:
dr-xr-x--- 2 root root 4096 Jul 7 18:09 /etc/sudoers.d
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Mon, Aug 1, 2011 at 2:49 PM, treydock treyd...@gmail.com wrote:
From the sudoer
On 08/01/2011 01:41 PM, treydock wrote:
#includedir /etc/sudoers.d
Maybe without the quotation marks?
--
vagn
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To
Cool, thanks for the clarification Gary.
On Aug 1, 2:02 pm, Gary Larizza ccsh...@gmail.com wrote:
On Mon, Aug 1, 2011 at 1:50 PM, Blueplastic sam...@blueplastic.com wrote:
It is not listed in the command details on this page?
http://docs.puppetlabs.com/man/agent.html
But it is cited as
Just wanted to say this turned out to be an Amazon problem.
The Amazon EC2 console showed the private DNS for the PuppetMaster
node to be X. But SSHing into server X and running 'hostname' to get
the name showed Y. There was a mismatch between what Amazon console
thought the DNS was and what the
Ok , so this was actually two problems...
The first , can't have quotes around the folder location in
#includedir...
Second is the way I was populating those files...
Here's the sudo module definition...
define sudo::directive (
$ensure=present,
$content=,
$source=
) {
# sudo skipping
On 08/01/2011 05:04 PM, Jared Curtis wrote:
* Central Dashboard instance
* Central CA
Would it be a problem if your central
CA and dashboard became unavailable?
-v
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this
I recommend taking a look at R I Pienaar's alternative extlookup
implementation. It supports YAML in addition to csv which allows for the
full range of available variable types to be pulled in from external
sources. I've combined this with a YAML-based ENC to put all variables for
a single node
40 matches
Mail list logo
