On Tue, Sep 13, 2011 at 12:41 AM, Justin Lambert
jlamb...@localmatters.com wrote:
Thanks for the response. We're using Posrgres, and the catalog build seems
a bit slow, but nothing compared to the client runtime which is where I've
been focusing. Your assessment is correct, it is just the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We're at about the 100 hosts, but have closer to 1500 services - maybe we
have exceeded what storeconfigs can do then. If that is the case, is there
a recommended alternative that isn't manually maintaining config files?
Just to be clear: After
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The good thing with this method is that you can manage the module
directory (where the different config file excerpts are stored) with
'purge = true' so that only exported resources are present in the final
nagios configuration (something that
I had a similar problem with my nagios server where the catalog run
took about 500seconds for about 100 nodes with about 1000 services,
most of which were generated with exported resources/stored config. We
use the Naginator-resources in puppet.
However, the main speed issue was not with the
And as an additional note, there is a related bug/feature open for it:
http://projects.puppetlabs.com/issues/5650
On Sep 13, 9:49 am, Bart Descamps barty.desca...@gmail.com wrote:
I had a similar problem with my nagios server where the catalog run
took about 500seconds for about 100 nodes
Yes, I was simply missing the worker process.
Thanks, Craig and Michael!
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Craig White
Gesendet: Montag, 12. September 2011 22:00
An: puppet-users@googlegroups.com
Err, what is that 0.25-5 doc folder and what RPM owns it?
rpm -qf /usr/share/doc/puppet-0.25.5
If nothing owns it, you've pretty much proved your system has old
Puppet artefacts lying around. Personally I wouldn't trust any of the
content in /usr/lib/ruby now. Is this a production system?
I don't know what pbcopy is locate can't find it. Never heard of
it,
Yeah never mind - its a convenient Mac OS X tool for copying something
into the clipboard. Not critical.
but, after removing the rpm and wiping /var/lib/puppet and running
'locate puppet', I get:
(you really should use
On Mon, Sep 12, 2011 at 3:39 PM, Vlad v...@vladgh.com wrote:
Are there any plans to get the latest puppet and facter into
apt.puppetlabs.com?
Of course. I started with yum simply because it was asked for more
loudly, and I know rpm a bit better than the debian packaging. I
welcome any help,
I have set up puppet on Ubuntu/Debian servers with no problem. I am trying
to get puppet working in a RHEL environment. I have the client installed and
the certificate is signed so I know the two are talking but for some reason
I can not get puppet to push the file on to the client.
What am I
Sorry, forgot to include the puppet command output...:
# puppet agent --test --verbose
info: Caching catalog for client
info: Applying configuration version '1315910859'
notice: Finished catalog run in 0.02 seconds
John Kennedy
On Tue, Sep 13, 2011 at 12:13, John Kennedy skeb...@gmail.com
Try this:
node client {
file { /home/admin/puppet/jck.txt:
owner = admin,
group = admin,
mode = 0744,
source = puppet:///test/jck.txt,
}
Beware the colon and the commas. (Didn't you get any error messages in your log
On Tue, Sep 13, 2011 at 12:27, Bernd Adamowicz
bernd.adamow...@esailors.dewrote:
Try this:
** **
node client {
file { /home/admin/puppet/jck.txt:
owner = admin,
group = admin,
mode = 0744,
source =
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von John Kennedy
Gesendet: Dienstag, 13. September 2011 13:43
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users] Re: Puppet not pushing file
On Tue, Sep 13, 2011 at 12:27, Bernd Adamowicz
I know it's not directly related to Puppet but I didn't find any
better place to ask about this either.
Since sometimes, there is no value for 'fqdn' in facter on the puppet
agents.
[root@disk10 ~]# facter hostname
disk10
#
[root@disk10 ~]# facter fqdn date
Tue Sep 13 13:26:54 BST 2011
#
What version of facter are you running btw?
You already answered that - never-mind :-).
ken.
--
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,
I'm guessing you get nothing when you try:
facter domain
?
What version of facter are you running btw?
Can you show the results of the following commands:
hostname
dnsdomainname
cat /etc/resolv.conf
Cheers.
ken.
On Tue, Sep 13, 2011 at 1:33 PM, Sans r.santanu@gmail.com wrote:
I know
Hullo
I'd like to add the various rpmfusion repos to my puppet manifests. Is
it possible to use yum/rpm to do this directly from the rpmfusion
site, using the downloadable rpm (from the rpmfusion web site):
yum localinstall --nogpgcheck
On Tue, Sep 13, 2011 at 12:52, Bernd Adamowicz
bernd.adamow...@esailors.dewrote:
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com]
Im Auftrag von John Kennedy
Gesendet: Dienstag, 13. September 2011 13:43
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users]
Nope, facter domain doesn't return anything either.
[root@disk10 ~]# facter domain date
Tue Sep 13 14:44:21 BST 2011
hostname, dnsdomainname and resolv.conf are just fine, like
this:
[root@disk10 ~]# hostname
disk10
[root@disk10 ~]# dnsdomainname
hep.xxx.xxx.ac.uk
[root@disk10 ~]# cat
Yep - that looks like a bug. The change was here:
https://github.com/puppetlabs/facter/commit/f7daae300d5c993052dd6c49b1b5e1f3501eaa10
Basically the domain =~ part is _not_ returning true even though
dnsdomainname is returning something, and not falling through as it
used to to find the answer
I could be wrong about the cause actually ... I think its still a bug
though :-).
Let me take a closer look at the code and see if I can work it out.
ken.
On Tue, Sep 13, 2011 at 3:29 PM, Ken Barber k...@puppetlabs.com wrote:
Yep - that looks like a bug. The change was here:
On 09/13/2011 09:47 AM, Tim Coote wrote:
Hullo
I'd like to add the various rpmfusion repos to my puppet manifests. Is
it possible to use yum/rpm to do this directly from the rpmfusion
site, using the downloadable rpm (from the rpmfusion web site):
yum localinstall --nogpgcheck
Hi all,
I'm trying to install Puppet Dashboard 1.2.0 and having some troubles, I'm
aware that it's probably something wrong with my ruby/rails environment but
I really can't seem to figure out why this happens..
My environment is:
ruby 1.8.7
rake 0.9.2
gem 1.8.10
When I try to create the DB
Yep, the creates makes exec know that the command given will create that
file and won't run once it exists. This is similar to using onlyif/unless w/
something like test -e /etc/yum.repo.d/blah.repo.
I have the requires setup on the package resources like that so the -release
RPMs are installed,
I'm trying to load balance multiple puppetmasters using apache and
passenger as described in James's book.
Was able to get a single passenger server installation to work
correctly. When I configure the frontend load balancer and backend
workers, the backend workers does not authenticate even
Since this is urgent and we are in RC, I've raised a bug for you Sans:
http://projects.puppetlabs.com/issues/9457
ken.
On Tue, Sep 13, 2011 at 3:43 PM, Ken Barber k...@puppetlabs.com wrote:
Yeah okay I was close though :-).
if name = Facter::Util::Resolution.exec('hostname')
...
fpm ;)
On Tue, Sep 13, 2011 at 12:35 AM, Michael Stahnke stah...@puppetlabs.comwrote:
On Mon, Sep 12, 2011 at 3:39 PM, Vlad v...@vladgh.com wrote:
Are there any plans to get the latest puppet and facter into
apt.puppetlabs.com?
Of course. I started with yum simply because it was asked
On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum luke.bi...@lmax.com wrote:
Err, what is that 0.25-5 doc folder and what RPM owns it?
rpm -qf /usr/share/doc/puppet-0.25.5
If nothing owns it, you've pretty much proved your system has old
Puppet artefacts lying around. Personally I wouldn't trust
- Original Message -
On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum luke.bi...@lmax.com
wrote:
Err, what is that 0.25-5 doc folder and what RPM owns it?
rpm -qf /usr/share/doc/puppet-0.25.5
If nothing owns it, you've pretty much proved your system has old
Puppet artefacts
Yeah this doesn't seem to be old versions of Puppet.
So from my other email ... can you show us the code where you are
doing your comparison for $puppetversion? I have a feeling I might
know what it is ... although I'm probably wrong ...
In fact - grep for 'puppetversion' in all of your puppet
If that were true the job of QA would be much easier
On Sep 13, 2011 10:48 AM, Douglas Garstang doug.garst...@gmail.com
wrote:
On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum luke.bi...@lmax.com
Just a stab in the dark, here... but looks like you might need an older
version of rack installed? The key line might be:
*can't activate rack-1.1.0, already activated rack-1.1.2*
On Tue, Sep 13, 2011 at 8:33 AM, Galed Friedmann
galed.friedm...@onavo.comwrote:
Hi all,
I'm trying to install
This is a maintenance release candidate of Puppet Dashboard.
This release candidate (rc2) fixes a broken init script on redhat
systems (issues #9101 and #9423).
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well
Did you yuse rubygems-1.3.7 as documented in the install procedure ?
I did try with rubygems-1.8.10 (the latest one) and got failures as
well, like yours.
--
Bruno
On 11-09-13 02:55 PM, Russell Van Tassell wrote:
Just a stab in the dark, here... but looks like you might need an
older
On Sep 13, 2011, at 10:48 AM, Douglas Garstang wrote:
On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum luke.bi...@lmax.com
wrote:
Err, what is that 0.25-5 doc folder and what RPM owns it?
rpm
On Tue, Sep 13, 2011 at 12:25 PM, Craig White craig.wh...@ttiltd.com wrote:
On Sep 13, 2011, at 10:48 AM, Douglas Garstang wrote:
On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum luke.bi...@lmax.com
On Tue, Sep 13, 2011 at 11:01 AM, Ken Barber k...@puppetlabs.com wrote:
Yeah this doesn't seem to be old versions of Puppet.
So from my other email ... can you show us the code where you are
doing your comparison for $puppetversion? I have a feeling I might
know what it is ... although I'm
So that is the only case where you are using the variable throughout
your entire code? I mean - ALL your code ... not just the one line you
are printing to the screen ...
ken.
On Tue, Sep 13, 2011 at 8:30 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Sep 13, 2011 at 11:01 AM, Ken
On Sep 13, 2011, at 12:28 PM, Douglas Garstang wrote:
On Tue, Sep 13, 2011 at 12:25 PM, Craig White craig.wh...@ttiltd.com wrote:
I'm thinking that he has puppet 0.25.5 gem installed and all of the rpm -e /
yum remove isn't going to solve that.
try 'gem list --local'
Craig, I posted
The reason why I say this - is because I can replicate this problem myself with:
node default {
$puppetversion = 0.25.5
notice($puppetversion)
}
In fact its the only way I can think of to replicate the issue -
besides all the other ways we have already ruled out. *shrug*.
ken.
On Tue, Sep
I know this has come up on the list numerous times before but I
thought it would be a good time to see if the state of the art has
advanced for this kind of thing. I wanted to know how people are
handling higher level deployment of applications - things that have to
be done repeatedly but not all
Even using:
notify{${::puppetversion} on ${::fqdn}:}
Instead would be of interest ...
ken.
On Tue, Sep 13, 2011 at 8:46 PM, Ken Barber k...@puppetlabs.com wrote:
The reason why I say this - is because I can replicate this problem myself
with:
node default {
$puppetversion = 0.25.5
On Tue, Sep 13, 2011 at 12:46 PM, Ken Barber k...@puppetlabs.com wrote:
The reason why I say this - is because I can replicate this problem myself
with:
node default {
$puppetversion = 0.25.5
notice($puppetversion)
}
In fact its the only way I can think of to replicate the issue -
Hmm ... well can you try using ${::puppetversion} ...?
Also - I notice you are using an ENC ... can you disable that and just
use node entries? Yet another place where we might be getting vars we
don't expect. In fact - setup a site.pp that is really blank - and
only contains that notify
If you want something simple and don't need a GUI, many folks are using
either Capistrano (Ruby) or the very similar Fabric (Python) for deployment.
You can populate hostlists via Foreman queries. That said, I am not sure
what sort of integration with Puppet/Foreman you are looking for.
Cheers,
Yeah - try this copy instead if you can:
https://raw.github.com/puppetlabs/facter/master/lib/facter/domain.rb
ken.
On Tue, Sep 13, 2011 at 9:21 PM, Sans r.santanu@gmail.com wrote:
Thanks Ken!
Back home an hr. or so ago and saw you reply. Is it the /usr/lib/ruby/
Thanks for everyone's comments - I finally found where the large chunk of
client time was going. Client runs are still slow, but 5 mins is a lot
better than 20 minutes. The issue in our case was having the directory that
contained the nagios config files managed by puppet (purge = true, recurse
Done!!
Work like a charm. thanks.
-Santanu
On Sep 13, 9:25 pm, Ken Barber k...@puppetlabs.com wrote:
Yeah - try this copy instead if you can:
https://raw.github.com/puppetlabs/facter/master/lib/facter/domain.rb
ken.
--
You received this message because you are subscribed to the Google
Good to hear. That fix should be in the next rc.
ken.
On Tue, Sep 13, 2011 at 10:46 PM, Sans r.santanu@gmail.com wrote:
Done!!
Work like a charm. thanks.
-Santanu
On Sep 13, 9:25 pm, Ken Barber k...@puppetlabs.com wrote:
Yeah - try this copy instead if you can:
On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber k...@puppetlabs.com wrote:
Hmm ... well can you try using ${::puppetversion} ...?
Adding this:
notify{xxx = ${::puppetversion} ...:}
to the manifest gives this on the server:
Sep 13 15:14:43 sv2admin1 puppet-master[22452]:
The kind of thing I was thinking of was selecting where to run jobs by
puppet class, or even requiring that certain classes are assigned to certain
nodes (requiring a pre-req class before you actually send over a job to
build). In my mind I envisioned extensions to something like Foreman where
On Tue, Sep 13, 2011 at 3:21 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber k...@puppetlabs.com wrote:
Hmm ... well can you try using ${::puppetversion} ...?
Adding this:
notify{xxx = ${::puppetversion} ...:}
to the manifest gives this on
This is a maintenance release candidate of Puppet. This rc rolls in
several commits that were targeted by Puppet Labs for 2.7.4 and
omitted.
This release is available for download at:
http://downloads.puppetlabs.com/puppet/
See the Verifying Puppet Download section at:
On Tue, Sep 13, 2011 at 4:01 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Sep 13, 2011 at 3:21 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber k...@puppetlabs.com wrote:
Hmm ... well can you try using ${::puppetversion} ...?
You could always do one of your crazy greps :-).
Out of curiosity - what do your /var/lib/puppet/yaml/facts/*.yaml
files show you on your server?
ken.
On Wed, Sep 14, 2011 at 12:16 AM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Sep 13, 2011 at 4:01 PM, Douglas Garstang
On Tue, Sep 13, 2011 at 4:43 PM, Ken Barber k...@puppetlabs.com wrote:
How are you running your puppet master?
Can you try it with just:
puppet master --debug --no-daemonize
Just there was a thread I recall about Mongrel - it may not be related:
I think this may be totally related. We're using mongrel... AND,
running the puppet master in standalone mode as you suggested yields
this now on the client:
Sep 13 16:49:06 hproxy11 puppet-agent[27311]:
(/Stage[main]/Puppet::Setup/Notify[xxx = 2.7.3 ...]/message) defined
'message' as 'xxx
On Tue, Sep 13, 2011 at 5:12 PM, Ken Barber k...@puppetlabs.com wrote:
I think this may be totally related. We're using mongrel... AND,
running the puppet master in standalone mode as you suggested yields
this now on the client:
Sep 13 16:49:06 hproxy11 puppet-agent[27311]:
On Tue, Sep 13, 2011 at 5:16 PM, Douglas Garstang
doug.garst...@gmail.comwrote:
I wonder if the performance of the puppet master in 2.7.3 has
increased to the point where passenger/mongrel aren't really required
anymore? I'm running puppet in standalone debug right now, and forced
40 or so
Thanks for your help. Unfortunately, I can't tell you much about the
setup. I've only ever done this with passenger as well, and the person
who did set it up has
left the company.
I'm not really sure if you should raise a new ticket on this one - or
add an addendum to this:
I'm looking for a bit of best-practices here. Our puppet environment
up-until-today has been owned and operated by IT Operations only. We've had a
single 'production' environment and our code has been managed in a local
GitHub::FI install. We have ~14,000 lines of code in our PP files. We're
On Sep 1, 4:47 am, Daniel Maher dma...@milestonelab.com wrote:
On 09/01/2011 04:32 AM, col yte wrote:
Hi folks,
I was curious if anyone would be willing to share how they organize
their puppet implementation. Perhaps something similar to what you'll
find
63 matches
Mail list logo
