On 06/19/2012 04:48 AM, Eric Shamow wrote:
> Jo,
>
> Let's not make this personal. You don't know how old I am or what
> infrastructures I've managed.
>
> You don't need to use Hiera. You can use any data lookup tool you like
> to do the same thing.
>
> What you are seeing is not an official s
I'm not sure if he wants to monitor the puppet runs on the clients.
Maybe he wants to monitor if the the puppetmaster is available or not, so
/usr/lib/nagios/plugins/check_tcp -H YOURPUPPETMASTER -p 8140
TCP OK - 0.000 second response time on port
8140|time=0.000464s;;;0.00;10.00
or
/usr/
This might give another starting point:
* http://www.bernd-adamowicz.de/180/monitoring-puppet-part-3/
*
http://www.bernd-adamowicz.de/85/synchronizing-puppet-generated-icinga-configuration/
Essentially the first link might be helpful.
Bernd
Von: puppet-users@googlegroups.com
>
> nagios_command {
>
"check_puppetmaster_https":
command_line => '$USER1$/check_http -SI $HOSTNAME$ -p 8140 -u
/production/status/puppetclient --header="Accept: yaml"';
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view
where does the paramter locate which specify how often the clients
update with the server?
--
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 unsubscribe from this group, send e
Hi folks, I'm scratching my head with a problem with system load.
When Puppet checks in every hour, runs through all our checks, then exits
having confirmed that everything is indeed as expected, the vast majority
of the time no changes are made. But we still load our systems with this
work ev
Not working for me.
Stages generate cycles.
Your solution tells me it cannot find the pre class:
Tue Jun 19 05:20:23 -0400 2012 Puppet (err): Failed to apply catalog: Could
not find dependency Class[Fw::Pre] for Firewall[100 accept http
connections] at
It definitely does not like:
Firewall {
how about this: nagios_command {
"check_puppetmaster_https":
command_line => '$USER1$/check_http -SI $HOSTNAME$ -p 8140 -u
/production/status/puppetclient --header="Accept: yaml"';
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
Due to the documentation not being specifically clear with regards to node
level variables and scoping. In 2.7 node variables they are local scope.
Therefore in your templates you call the ldap_server variable NOT
::ldap_server as it is not a top scope variable.
As I say, the document is not s
Right now I'm referencing the variable as "<%= ldap_server %>" and puppet
is complaining on startup about dynamic scoping and telling me this will
break. So clearly this isn't the way to go otherwise I wouldn't have the
warning.
On Tue, Jun 19, 2012 at 7:06 AM, earthgecko wrote:
> Due to the doc
- Original Message -
> From: "Jon Schewe"
> To: puppet-users@googlegroups.com
> Sent: Tuesday, June 19, 2012 1:13:09 PM
> Subject: Re: [Puppet Users] Re: Correct way to handle node-specific variable
> values in puppet 2.7
>
> Right now I'm referencing the variable as "<%= ldap_server %
Hai a écrit :
where does the paramter locate which specify how often the clients
update with the server?
puppet agent --genconf | vim -
gives me
# How often puppet agent applies the client configuration; in seconds.
# Note that a runinterval of 0 means "run continuously" rather than
On Tuesday, 19 June 2012 03:26:14 UTC+10, Steve Traylen wrote:
>
>
> On Monday, 18 June 2012 13:02:33 UTC+2, Peter wrote:
>>
>> Hi Puppet Users,
>>
>> Essentially I would like to define a hiera.yaml file (just the hierarchy
>> and puppet datasource location) within my module and use it to clearly
On Tuesday, June 19, 2012 5:23:42 AM UTC-5, Duncan wrote:
>
> Hi folks, I'm scratching my head with a problem with system load.
>
> When Puppet checks in every hour, runs through all our checks, then exits
> having confirmed that everything is indeed as expected, the vast majority
> of the time
On Tuesday, June 19, 2012 4:30:38 AM UTC-5, Ioannis wrote:
[...]
Stages generate cycles.
>
Yes, stages are prone to that.
Your solution tells me it cannot find the pre class:
>
No, *your application* of Ken's example tells you that.
Tue Jun 19 05:20:23 -0400 2012 Puppet (err): Failed to appl
There actually is a way to do this, though you may find it to be more
painful to work with.
Imagine, if you will, two environments: production and maintenance.
The production environment is the one you're running right now, for
production. It fully manages everything and ensures that your system
Hello,
Thanks for the reply. I hope this is really not something related to
an incompatibility with puppet 2.7. Did anyone get this working using
puppet 2.7?
I have tried this with stages and I get the cyclic dependency problem.
Then I tried this solution using require => Class["fw::pre"] and
bef
On Mon, Jun 18, 2012 at 10:27 PM, Kinzel, David wrote:
>
> >On Mon, Jun 18, 2012 at 10:02:10PM +0300, Ohad Levy wrote:
> >> On Mon, Jun 18, 2012 at 9:32 PM, Forrie wrote:
> >>
> >> > What is the status of compatibility with Puppet 2.7.16+ and Ruby
> >> > 1.9? I searched through this group and f
I have this working in our environment as a module, which I will attempt to
describe.
module: casfirewall
init.pp
class casfirewall {
include casfirewall::default, casfirewall::fwpre, casfirewall::fwpost
file {"/etc/iptables":
ensure => "directory",
owner => "root",
group => "ro
On Tuesday, June 19, 2012 7:20:47 AM UTC-5, R.I. Pienaar wrote:
> > Right now I'm referencing the variable as "<%= ldap_server %>" and
> > puppet is complaining on startup about dynamic scoping and telling
> > me this will break. So clearly this isn't the way to go otherwise I
> > wouldn't ha
Thanks a lot for the example. I managed to make it work. Turns out
that in fw::post my firewall rules need to have the parameter before
=> undef in order to work.
On Tue, Jun 19, 2012 at 4:18 PM, Christian McHugh
wrote:
> I have this working in our environment as a module, which I will attempt to
From: puppet-users@googlegroups.com
[mailto:puppet-users@googlegroups.com] On Behalf Of Ohad Levy
Sent: Tuesday, June 19, 2012 8:13 AM
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] Puppet and Ruby 1.9
Do you know which version of puppet solv
I've created a set of functions that exposes the PuppetDB query API
from inside puppet. Feel free to give them a spin and get back to me
with any bugs or feedback.
https://github.com/dalen/puppet-puppetdbquery
They require ruby-restclient, ruby-json and the puppetdb-terminus.
To give you an exam
On 19.06.2012 16:48, Erik Dalén wrote:
I've created a set of functions that exposes the PuppetDB query API
from inside puppet. Feel free to give them a spin and get back to me
with any bugs or feedback.
https://github.com/dalen/puppet-puppetdbquery
They require ruby-restclient, ruby-json and th
Hello everyone,
everytime I run on a puppet host:
#puppet agent --test
I see this commet:
info: Applying configuration version '01'
then lets say I deploy a new package from my local repository, from
which I would get a different configuration version.
#puppet agent --test
info: Applying co
Hi All,
I'm trying to get a feel for the puppetlabs-openstack module by
deploying the openstack::all class using the example in the readme.
Puppet master using puppet 2.7.14 on Debian Squeeze, client node
2.7.11 on Ubuntu 12.04. Using module and dependencies from the forge.
I get this:
err: Cou
On 19 June 2012 16:55, David Schmitt wrote:
> On 19.06.2012 16:48, Erik Dalén wrote:
>>
>> I've created a set of functions that exposes the PuppetDB query API
>> from inside puppet. Feel free to give them a spin and get back to me
>> with any bugs or feedback.
>>
>> https://github.com/dalen/puppet
On Monday, June 18, 2012 4:53:23 AM UTC-5, Javi wrote:
>
> Scenario: install SNMP (agent and daemon), change config file and restart
> of service.
>
> What's wrong? The logs showed that AFTER the new config file is applied,
> the service (snmpd) is restarted, but looks like this is not true.
>
Is there any trick to getting Geppetto to work with Ruby DSL defined types?
The code validates and works, but Geppetto highlights uses of the resource
as an error.
Thanks,
Adam
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this dis
On Tue, Jun 19, 2012 at 9:55 AM, David Schmitt wrote:
> On 19.06.2012 16:48, Erik Dalén wrote:
>
>> I've created a set of functions that exposes the PuppetDB query API
>> from inside puppet. Feel free to give them a spin and get back to me
>> with any bugs or feedback.
>>
>> https://github.com/da
On Tue, Jun 19, 2012 at 9:48 AM, Erik Dalén wrote:
> I've created a set of functions that exposes the PuppetDB query API
> from inside puppet. Feel free to give them a spin and get back to me
> with any bugs or feedback.
>
> https://github.com/dalen/puppet-puppetdbquery
>
> They require ruby-restc
This may be an obvious question, but I'd rather ask than guess at it.
Do the actual file names have any meaning to puppet or facter ?
Seems to me that as long as the facts are syntactically correct and do not
conflict with facts in any other file,
the file names are only important to the human m
That looks like the issue then. We're using augeas 0.10 (default with
ubuntu 10.04) and puppet 2.7.3. I'll look at upgrading puppet and see how
that goes.
Thanks all,
Guy
On Saturday, June 16, 2012 12:45:54 AM UTC-7, Dominic Cleal wrote:
>
> On 15/06/12 22:42, Guy Knights wrote:
> > Ok, thanks
As this came up in #puppet today (and nobody seemed to know about it) I
thought I'd spam the list to mention that there's a Puppetcamp in
Cambridge, MA, this friday. The details are at
http://puppetcampboston.eventbrite.com/ for anyone that didn't know about
this and can wrangle a day off work to
On Tuesday, June 19, 2012 10:01:42 AM UTC-5, MrTeleBird wrote:
>
> Hello everyone,
>
> everytime I run on a puppet host:
> #puppet agent --test
>
> I see this commet:
> info: Applying configuration version '01'
>
> then lets say I deploy a new package from my local repository, from
> wh
Thanks everyone for your replies. I've been waiting to upgrade our
infrastructure to 1.9.
We don't do any esoterica, it's just a simple puppet setup (for the
time being) - not even marionette.
I switched our config to use an NFS mount for puppet and ruby (configs
stored locally on each machine,
On Tuesday, June 19, 2012 8:27:55 AM UTC-5, Peter wrote:
>
> On Tuesday, 19 June 2012 03:26:14 UTC+10, Steve Traylen wrote:
>>
>>
>> On Monday, 18 June 2012 13:02:33 UTC+2, Peter wrote:
>>>
>>> Hi Puppet Users,
>>>
>>> Essentially I would like to define a hiera.yaml file (just the hierarchy
>>>
On Tue, Jun 19, 2012 at 9:56 AM, Ashley Penney wrote:
> As this came up in #puppet today (and nobody seemed to know about it) I
> thought I'd spam the list to mention that there's a Puppetcamp in
> Cambridge, MA, this friday. The details are at
> http://puppetcampboston.eventbrite.com/ for anyon
On Tue, Jun 19, 2012 at 7:20 AM, R.I.Pienaar wrote:
>
>
> - Original Message -
> > From: "Jon Schewe"
> > To: puppet-users@googlegroups.com
> > Sent: Tuesday, June 19, 2012 1:13:09 PM
> > Subject: Re: [Puppet Users] Re: Correct way to handle node-specific
> variable values in puppet 2.7
On Tue, Jun 19, 2012 at 9:19 AM, jcbollinger wrote:
>
>
> On Tuesday, June 19, 2012 7:20:47 AM UTC-5, R.I. Pienaar wrote:
>
>> > Right now I'm referencing the variable as "<%= ldap_server %>" and
>> > puppet is complaining on startup about dynamic scoping and telling
>> > me this will break. So cl
On Tue, Jun 19, 2012 at 5:37 PM, Kinzel, David wrote:
>From: puppet-users@googlegroups.com [mailto:
> puppet-users@googlegroups.com] On Behalf Of Ohad Levy
>Sent: Tuesday, June 19, 2012 8:13 AM
>To: puppet-users@googlegroups.com
>Subject: Re: [Puppet Users] Puppet a
On Tuesday, June 19, 2012 11:02:55 AM UTC-7, Jon Schewe wrote:
>
>
> Am I getting this right that instead of just leaving the functionality in
> puppet I should now call out to another application to have node-specific
> variables? This seems like a step in the wrong direction. It's really nice
Sorry, never mind this. I discovered that the source version of puppet was
install in /usr/local/libs/site_ruby while the repository version appears
to have been installed in /usr/lib/ruby1.8.
On Tue, Jun 19, 2012 at 12:41 PM, Guy Knights
wrote:
> Hi again,
>
> I attempted to upgrade puppet from
Hi again,
I attempted to upgrade puppet from the office Puppet apt repository today,
previously it had been installed from source. I just installed the package
over the top, thinking it would overwrite the existing files. However, when
I run puppet --version it still spits out 2.7.3. I looked a
On Tue, Jun 19, 2012 at 8:56 AM, Dan White wrote:
> This may be an obvious question, but I'd rather ask than guess at it.
>
> Do the actual file names have any meaning to puppet or facter ?
>
They used to matter with Facter, but they don't since 1.5.8.
You can see this by running `facter uptime
On Tue, Jun 19, 2012 at 2:43 PM, Nick Fagerlund <
nick.fagerl...@puppetlabs.com> wrote:
>
>
> On Tuesday, June 19, 2012 11:02:55 AM UTC-7, Jon Schewe wrote:
>>
>>
>> Am I getting this right that instead of just leaving the functionality in
>> puppet I should now call out to another application to
The official word from us is documented here:
http://docs.puppetlabs.com/guides/platforms.html#ruby-versions
Basically: you should try to stick with 1.8.7 through the 2.7 series, but
3.0 (which is in RC now) and higher will fully and unconditionally support
1.9.3.
- To my knowledge, the whole
On Tuesday, June 19, 2012 1:24:42 PM UTC-7, Jon Schewe wrote:
>
>
> So what I'm currently doing is perfectly valid and should continue to work
> with 2.8, I've just got a version that's giving me extra warnings. Correct?
>
>
Yup! ...sorry about that. Implementing those warnings correctly turned
On Tue, Jun 19, 2012 at 3:41 PM, Nick Fagerlund <
nick.fagerl...@puppetlabs.com> wrote:
>
>
> On Tuesday, June 19, 2012 1:24:42 PM UTC-7, Jon Schewe wrote:
>>
>>
>> So what I'm currently doing is perfectly valid and should continue to
>> work with 2.8, I've just got a version that's giving me extr
Before I start hacking away does anybody have or know of an existing
script / project for publishing modules to PuppetForge via the CLI? I'd
like to utilize Jenkins and automate this as much as possible.
If not, I have no problems starting from scratch.
--
Paul Belanger | PolyBeacon, Inc.
Jab
On Tue, Jun 19, 2012 at 1:54 PM, Paul Belanger wrote:
> Before I start hacking away does anybody have or know of an existing
> script / project for publishing modules to PuppetForge via the CLI? I'd
> like to utilize Jenkins and automate this as much as possible.
>
> If not, I have no problems s
I can now confirm that Dominic was correct. I'm upgraded to puppet 2.7.16
now and the augeas resources are working. One thing I can also confirm is
that Alan's observation about the context not working and to use the full
path in the set command was also correct, at least for the sudoers config
On Tuesday, June 19, 2012 7:19:20 AM UTC-7, jcbollinger wrote:
>
>
> Have I missed a change in plan for node variables, so that in Puppet 3
> they remain accessible outside node declarations? Does that form of
> dynamic scoping live on?
>
>
Yeah, they're effectively a tiny island of dynamic sc
Hello all. Kelsey Hightower has an outstanding pull request to add Rackspace
support for the Puppet Labs Cloud Provisioner product. However, we need people
to test it. If you're interested in trying it out, the branch is located on
github here:
https://github.com/kelseyhightower/puppetlabs-c
Amazing!
Many thanks, I will check all your suggestions, but I use similar
modules for other services (such as puppet, ssh, ntp...) On debian
nodes (all of them are clones) smoothly, but SNMP init script can be
buggy.
Thanks again
On 19/06/2012, jcbollinger wrote:
>
>
> On Monday, June 18, 2012
Yep, pretty much exactly what I proposed in
https://projects.puppetlabs.com/issues/14998
That said, someone offline made a fair argument for it not being another
directive, but perhaps an attribute of the notify or subscribe directive. I
would totally support that idea.
On Jun 18, 2012, at 5:2
On 12-06-19 05:00 PM, Pieter van de Bruggen wrote:
On Tue, Jun 19, 2012 at 1:54 PM, Paul Belanger
wrote:
Before I start hacking away does anybody have or know of an existing
script / project for publishing modules to PuppetForge via the CLI? I'd
like to utilize Jenkins and automate this as mu
I've used 2.7.13 and higher with Ruby 1.9.3. The only real problem I
remember having was around reports. I wasn't doing anything super
complicated though.
Mike
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email
Thanks for the response, Jeff.
On Jun 19, 2012, at 4:03 PM, Jeff McCune wrote:
> On Tue, Jun 19, 2012 at 8:56 AM, Dan White wrote:
> This may be an obvious question, but I'd rather ask than guess at it.
>
> Do the actual file names have any meaning to puppet or facter ?
>
> They used to matter
There's a generic problem that I suspect that many people are bumping into, but
I suspect it will surprise others. RIP's concat module includes a facter plugin
which is required for the catalog to compile. This requires pluginsync to be
enabled.
Problem is when you have a brand new client, they
On Jun 18, 2012, at 7:48 PM, Eric Shamow wrote:
> You don't need to use Hiera. You can use any data lookup tool you like to do
> the same thing.
You are suggesting to create an external data reference for something which
should be 100% expressed within the puppet policies. There is no other ne
- Original Message -
> From: "Jo Rhett"
> To: puppet-users@googlegroups.com
> Cc: r...@devco.net
> Sent: Wednesday, June 20, 2012 12:05:47 AM
> Subject: facter plugin requires cause catalog failure, prevent setting up new
> clients
>
> There's a generic problem that I suspect that many
On Jun 19, 2012, at 4:13 PM, R.I.Pienaar wrote:
> Just enable pluginsync from your bootstrap, its not hard and really everyone
> else manages just fine,
Um, the bootstrap won't run if the catalog doesn't compile. That's the problem.
> AFAIK its also on by default now.
Nope. If it was we wou
- Original Message -
> From: "Jo Rhett"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, June 20, 2012 12:26:48 AM
> Subject: Re: [Puppet Users] facter plugin requires cause catalog failure,
> prevent setting up new clients
>
>
>
> On Jun 19, 2012, at 4:13 PM, R.I.Pienaar wrote
On Jun 19, 2012, at 4:30 PM, R.I.Pienaar wrote:
> catalog compile happens *after* pluginsync so if you enable it, it will
> fetch the plugins then request catalog with the new fact attached.
But not if the bootstrapping is done via puppet.
> by bootstrap i mean kickstart or whatever, ie. before y
Puppet 2.7.17 is a maintenance release for Puppet in the 2.7.x series.
It contains a fix for the ubuntu service regression in 2.7.16 (#15027,
#15028, #15029).
Downloads are available at:
* Source https://downloads.puppetlabs.com/puppet/puppet-2.7.17.tar.gz
Windows package is available at
https:/
66 matches
Mail list logo
