On Mon, 2013-03-04 at 06:09 -0800, jcbollinger wrote:
>
>
> On Sunday, March 3, 2013 3:53:29 AM UTC-6, Brice Figureau wrote:
> On 01/03/13 22:24, r.yeo wrote:
> > Passenger settings are currently -
> >
> &g
file service (use a vhost for instance).
File resource are theorically much shorter in time (especially metadata)
than compilation requests. Separating both would allow for a smarter
queueing at the master level.
[snip]
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this mes
ike if you have 30 agents trying to access the master at the same time,
but you can accomodate only 25, the other 5 will have to wait for every
request they're sending to your master VM.
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received
les/path/to/file",
> but it seems like there might be a better solution.
You could also setup a puppetmaster only for the purpose of serving
files to your servers, and use:
puppet://fileserver.domain.com/files/path/to/file
kind of url.
It's still masterless for compilation purpos
t;path value is: #{@resource[:path]}.")
> end
>
> end
>
>
> However I'm not having any success with the above.
Well, what kind of error or output do you get?
> Any ideas???
Isn't it better to use a defaultto, like this:
defa
ilable as a Forge module, which should even more help using
it.
It produces a report that lists the differences between catalogs
(old/new resources, and differences between changed resources).
It is specifically useful when upgrading a puppet master to a new
version to spot differences in behavior
hat
it's a complex stuff. Last time I tried to fiddle with the checksumming,
I never quite got anywhere :)
As I said in the preamble, feel free to chime in puppet-dev to talk
about this, and check the various redmine tickets regarding those issues.
--
Brice Figureau
My Blog: http://www.mas
the fact that we
> were trying to import a big dump(2GB seems ok to me but who knows) and
> puppet just died because they are not streaming the file but it is
> *fully* loaded into memory.
This assertion is not true anymore since at least 2.6.0.
Also, for big files you can activate http co
derstood something.
> Should this option instead be placed in the client's configuration to
> make them export only the @@-resources?
No, it's a master option.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed to the Goo
reconfigs'
> directive without 'storeconfigs=true'?
You just need:
thin_storeconfigs = true
It will automatically enable storeconfigs for you.
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message because you are subs
ft on the agent (ie
manual modifications for instance)
* you run the agent on demand when you need a change
This can be done with something like MCollective where you can decide to
remotely launch some puppet runs as you see fit.
Now you need to have a way to map from manifest modification to a s
On 01/06/12 12:41, Matthew Burgess wrote:
> On Thu, May 31, 2012 at 6:07 PM, Brice Figureau
> wrote:
>
>> I'll run a test over the week-end to see if I can reproduce the issue
>> with 2.7.14. It's possible something changed in the puppet codebase and
>> pu
On 31/05/12 18:34, Matthew Burgess wrote:
> On Thu, May 31, 2012 at 4:31 PM, Brice Figureau
> wrote:
>
>> That's perfect!
>>
>> Apparently the client_version fact is not correct (it contains an
>> array).
>> One thing you might want to do, is to modify
On Thu, 2012-05-31 at 15:57 +0100, Matthew Burgess wrote:
> On Thu, May 31, 2012 at 2:09 PM, Brice Figureau
> wrote:
>
> > Can you run your master on the console (add --no-daemonize to the
> > command-line)?
> >
> > Because due to how Puppet reports er
On Thu, 2012-05-31 at 10:38 +0100, Matthew Burgess wrote:
> On Wed, May 30, 2012 at 6:58 PM, Brice Figureau
> wrote:
>
> > Probably that the stacktrace you'll get with --trace will be enough for
> > the moment. Also if you can cat the facts file (feel free to obfuscat
On 30/05/12 19:10, Matthew Burgess wrote:
> On Wed, May 30, 2012 at 5:11 PM, Brice Figureau
> wrote:
>> Hi Matthew,
>>
>> As the original author of puppet-load (and the aforementioned blog
>> post), I'm sorry to answer so late to this thread.
>>
>
on node master.domain.com
Where do you get this error?
Is it from puppet-load or your current master stack?
Is there any stack trace printed?
Can you add --debug and --trace to the puppet-load command line?
This should print more information to the console and we'll certainly be
able to fin
hosted
> offerings (such as Heroku) was a reasonable compromise.
I didn't had a look to the code itself, but is the postgresql code
isolated in its own module?
If yes, then that'd definitely help if someone (not saying I'm
volunteering :) wants to port the code to MySQL.
On a s
;t final, but I would like to get opinions on the
> idea. I welcome feedback until Friday, April 13.
What would be utterly awesome would be better pull request e-mails flow
on this commit (or on the dev) list:
* no close e-mail
* more readable inlined patches (syntax coloring?, broken in differen
with the minimal manifest,
and then file a bug report as detailed as possible.
This way I'd be able to reproduce it and potentially fix the problem.
Alternatively you might try Puppet 2.7.10, maybe the bug was fixed.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received t
ith thin_storeconfigs instead of the
full one if you can.
You might also want to check that your server is not swapping.
> Does the compiled time scale with the module number? Do I have to make
> sure I don't cross a certain limit?
--
Brice Figureau
Follow the latest Puppet Community e
nu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/
> 0.6.5"
>
> That's a request from another server. Here are the Apache configs:
>
> http://pastebin.com/rDKPSjjy
>
>
> Thanks everyone!
> Ryan Bowlby
>
--
Brice Figureau
My Blog: http://www.mas
#x27;m definitely looking see if there's interest and whether the model
> above fits people usage of EC2.
Based on discussions I had at the last PuppetConf with a lot of people,
I'm sure this would be a terriffic feature.
Imagine all what you can do, including setting up notificatio
conf::Generic/Exec[newaliases]: Would have
> triggered 'refresh' from 1 events
The problem is that in 2.7.x '-' is a valid character in variable names.
So your "postfixconf/$hostname-aliases" string was interpolated to
"postfixconf/" which is a directory.
s still present and we are basically stuck on an outdated
> version.
I believe this was fixed as part of the work in:
https://projects.puppetlabs.com/issues/9109
So it was released in 2.7.8rc1, and should definitely be fixed in 2.7.8.
--
Brice Figureau
Follow the latest Puppet Community ev
On Tue, 2011-12-20 at 08:25 -0800, ollies...@googlemail.com wrote:
>
> On Dec 20, 4:16 pm, Brice Figureau
> wrote:
> > On Tue, 2011-12-20 at 08:02 -0800, ollies...@googlemail.com wrote:
> > > > That's easy: dedicate two host to be CAs only. One is the hot stand
th a new client I get the new cert generated but then the above
> error.
That's expected because when the client connects to one of your
loadbalanced server it receives a certificate that was signed/generated
under the previous CA. You actually need your loadbalanced masters to
get a certificate
event your actual nodes to get a catalog.
I highly recommend you to get a copy of the "Pro Puppet" book. It
contains an extensive chapter on load balancing puppet master (both with
the SPOF and without it).
[1]: http://www.apress.com/9781430230571
--
Brice Figureau
Follow the latest Pup
th a potential to scale horizontally.
The command just complains about the certdnsnames option that has been
removed. You can stil use dns_alt_names to generate clients and/or
server certificates with embedded subjectAltName extension.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You recei
lse" {
}
Because a string when (internally) converted to a boolean is true.
This was discussed 2 days ago (look when the thread changes name):
http://groups.google.com/group/puppet-users/browse_thread/thread/3dfba6566d97880e/c473deea3f302410?#
And this is tracked in the following bug:
http:/
on of true/false (ie the boolean). Any puppet
conditional expression can evaluate to either true or false.
On the other hande "true" is a string containing the word true. "false"
is a string containing the word false. It is not a boolean.
But that's where things get diffic
ore information (especially with -debug).
Also, it might be worth checking on the apache error log.
> I know the time is in sync OK
>
> Certs look the same.
To be really sure compare the certificate fingerprints.
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.p
ocumentation says to use a selector.
> So, what's a recommended puppet way to do something like this? thx in
> advance.
file {
"somefile" :
ensure => $hasfile ? {
"true" => present,
default => absent
},
source => &
text.
But apparently the ca_host configuration tell the server that it will
receive SSL content.
> [snipped]
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&quo
p
[2]: http://www.masterzen.fr/2010/03/21/more-puppet-offloading/
[3]: http://www.masterzen.fr/2010/10/18/benchmarking-puppetmaster-stacks/
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message because you are subscribed to the Google Grou
o you), and
the master doesn't know which facts matters or not (regarding to change
in the compiled catalog, which I believe is an hard problem).
Check the "Optimize Catalog Compilation" section of this blog post for a
workaround:
http://www.masterzen.fr/2010/03/21/more-puppet-offlo
re in puppet cert (like --generateca).
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
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@googlegro
ion
> on how to do it instead.
Puppetca is now called "puppet cert".
> Well other than what's described above that is. But that's not
> feasible in an automated fashion. I'd like to deploy a second puppet
> master.
--
Brice Figureau
Follow the latest Puppet Co
On 22/10/11 18:47, Brice Figureau wrote:
> On 05/10/11 19:46, Steve Snodgrass wrote:
>> While testing puppet 2.7, I found that one of my manifests broke
>> because of the following quoted string:
>>
>> "http://$yumserver/repos/vmware-$esxversion-rhel6-64";
>
nded?
I don't know if it was intended, but there's a ticket open right now:
http://projects.puppetlabs.com/issues/10146
Go watch it to increase the odds of it being fixed :)
I really believe '-' shouldn't be allowed at end of any variable name,
which then should fix your
eometry (\d+x\d
> +)(.*)$/,
> :to_line => proc { |record|
> "VNCSERVERARGS[#{record[:port]}]=\"-geometry
> #{record[:geometry]} #{record[:optional_args]}\""
> }
>
> record_line :parsed_again,
> :joiner =>
parsing of a given record
line happens. It allows to modify was what read, or munge some values...
> 6 What does :pre_gen do?
It allows to run provider specific code before the to_line operation
happens.
> 7 Are there any other "mystery" parameter?
There's at least process,
resorting to using a different port
for CA :)
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
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 th
aster) or when applying
it (ie puppet agent)?
If the later, can you report what --summarize gives you on both host?
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message because you are subscribed to the Google Groups
"Puppet Us
puppet is looking M in the scope of C, but not in the scope of P
anymore.
Can you rewrite it like this and test:
class c inherits p {
P::M["test"] {
message => "overridden",
}
}
I'm confident this will solve your issue, but I don't
Then the 3 other stages would happen in the same
run.
It would also be great to have this stage being optional in subsequent
runs, allowing you to use the bootstrap stage during provisioning (ie
just after a pre-seed or kickstart), but never again. This would help
bootstrap from bare-metal.
--
B
the selector never matches at all
> and throws an error.
There shouldn't be any difference, except there is a known issue with
selectors and arrays:
http://projects.puppetlabs.com/issues/5860
Since you're mentioning an error (which you should have included for
further analysis), I'
think some
users will soon have CA that will expire. I don't think we yet have a
canned solution for this specific issue.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To pos
ke sense?
Having all the data in the database can help write inventory
applications. If you don't have such application, thin storeconfig is
way better. On another hand, if you don't use exported
resources/collection, you really don't care about storeconfigs at all
and you should disable
be a
pionneer and find things by yourself (hint: read the commit messages) :)
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
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@goog
o simplify people's life, make those extra
attributes become metaparameters (but please keep the old syntax):
user { luke: ensure => present, virtual => [boolean] }
That would even allow us to parametrize virtuality/exportability with
the help of an expression (ie selectors, functions
bug :))
> Are others using puppetdoc for their modules? Are there some good
> examples out there? The official documentation is useful but seems
> somewhat limited.
I think Alessandro is using puppetdoc for his own module, check Lab42's
Example42 modules on github:
htt
ct to them).
Note: all this is still experimental, use at your own risk, blah blah.
HTH,
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To po
I think the best practice is to use an ENC[1] (external node classifier)
like the Foreman or Puppet Dashboard, or one of your own.
This way you can program (more easily) the logic of attributions of
modules to your specific nodes.
[1]: http://docs.puppetlabs.com/guides/external_nodes.html
--
Bri
At the
> html's source, I can see the tags describing as iso-8859-1, and
> replacing it for utf-8 would correct for me.
Just use --charset utf-8 on the puppet doc command line. I think this
was added in puppet 2.6.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received thi
you can try:
puppetdoc --all -m rdoc --modulepath modules --manifestdir /path/to/emptydir
The idea is that puppetdoc will parse only the modules.
HTH,
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed to the Google Groups
"Puppet
that puppet has to create many
instances in memory (one per managed file/dir found during the walk).
This in turn expose some scalability issues in the event system and
transaction system of puppet.
> So I hope that the performance issue when recursing directories gets
> attention and get
nt to do,
but that'd be a great opportunity to generalize it :)
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
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 unsu
) but I've been gnawing at this
> one all day and haven't figured it out.
For an unknown reason your local node CA cert is not correct.
You can solve this by overwriting it with the main CA cert, or check
that your server certificate is indeed correctly signed by the CA you
think it wa
ct/H1991ZM/A?fnode=MTY1NDA3NA&mco=MjA1MTA3MzY
> <http://store.apple.com/us/product/H1991ZM/A?fnode=MTY1NDA3NA&mco=MjA1MTA3MzY>)
>
> and a ticket to Puppet
> Camp(http://www.puppetlabs.com/community/puppet-camp/)
>
Can we submit more than one entry?
I have several ones
On 11/02/11 18:06, Jason Wright wrote:
> I've completed rolling out 2.6.3 and it's completely resolved our issues.
That's terriffic!
Thanks for sharing this good news.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscr
On Thu, 2011-02-10 at 15:55 +0100, Udo Waechter wrote:
> Hello,
> I am one of those who have this problem. Some people suggested using Ruby
> Enterprise. I looked at its installation, it looked a little bit
> time-consuming, so I did not try that one out.
> I upgraded to debian squeeze (of course
On Tue, 2011-02-08 at 10:16 +, Nick Moffitt wrote:
> Brice,
>
> Thanks for your helpful answers.
>
> Brice Figureau:
> > > I saw someone say that it was good at finding "README" files, but:
> > > ...was unable to find ./manifests/README or
ur puppet code in
classes and modules, then I think puppetdoc can be a really good tool
(and you don't need the --all parameter in this case).
In any case, what is produced is a bunch of html files, which means you
can do whatever post-processing you want to them. If you just need to
in
of the high CPU usage.
That'd be great if one of the people having the problem could disable
reports to see if that's the culprit.
And if this is the case, we should at least log how long it takes to
process a report on the master.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
at big).
This way, they'll certainly be able to fix it.
Do we have a redmine ticket to track this issue?
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group
f us have this problem since upgrading means it can be fixed within
> Puppet, rather than Ruby, because it was fine before.
Do you mean puppet 2.6.2 wasn't exhibiting this problem?
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You receive
catalogs or sourced files (or file
metadata). This can dramatically increase the run time.
> Something is weird there... --udo,
Indeed.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gr
On Thu, 2011-01-27 at 15:59 -0800, Jason Wright wrote:
> On Thu, Jan 27, 2011 at 1:46 PM, Brice Figureau
> wrote:
>
> > Regarding the first stacktrace you posted in your first e-mail, I'm sure
> > this is the writelock multiprocess issue we fixed in 2.6 and that I
>
On 27/01/11 20:40, Jason Wright wrote:
> On Thu, Jan 27, 2011 at 1:42 AM, Brice Figureau
> wrote:
>> Which make me think that either you still have 0.24.x clients or I
>> missed some 0.25 client feature that uses XMLRPC file serving.
>
> All of our OS teams upgraded to 0
t it should help move
> forward. Annoyingly, I don't have a super-solid picture of what the
> problem is at this stage, because it looks like it shouldn't be
> possible to hit the situation but, clearly, it is getting there...
Yes, so we're certainly missing something, and in
On Thu, 2011-01-27 at 10:31 +0100, Brice Figureau wrote:
> On Wed, 2011-01-26 at 13:56 -0800, Jason Wright wrote:
> > On Wed, Jan 26, 2011 at 1:17 PM, Daniel Pittman
> > wrote:
> > > For what it is worth I have been looking at this quietly in the
> > > background
in production (especially if it's the filebucket handler).
There are great chances your test environment doesn't change, so the
filebucket is almost never used.
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message becau
_cache_path /var/cache/nginx/cache levels=1:2
keys_zone=puppetcache:50m inactive=300m
The default inactive is 10 minute which is too low for a sleeptime of 60
minutes, and it is possible the cached catalog to be evicted.
--
Brice Figureau
Follow the latest Puppet Community evoluti
On Wed, 2011-01-26 at 10:11 -0500, Micah Anderson wrote:
> Brice Figureau writes:
>
> > On Tue, 2011-01-25 at 17:11 -0500, Micah Anderson wrote:
> >> Brice Figureau writes:
> >>
> >> All four of my mongrels are constantly pegged, doing 40-50% of the CPU
ng?
>
> It wasn't before. Before things start spinning, compilation times are
> between 9 seconds and 60 seconds, usually averaging just shy of 30
> seconds.
Do you use a External Node Classifier?
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpupp
On Tue, 2011-01-25 at 17:11 -0500, Micah Anderson wrote:
> Brice Figureau writes:
>
> > On 15/12/10 19:27, Ashley Penney wrote:
> >> This issue is definitely a problem. I have a support ticket in with
> >> Puppet Labs about the same thing. My CPU remains at 100%
On Tue, 2011-01-25 at 20:26 +0100, Brice Figureau wrote:
> On 25/01/11 20:10, Jason Wright wrote:
> > On Tue, Jan 25, 2011 at 10:48 AM, Brice Figureau
> > wrote:
> >>>> xmlrpc?
> >>>> Do you still have 0.24.x clients?
> >
> > No. W
On 25/01/11 20:10, Jason Wright wrote:
> On Tue, Jan 25, 2011 at 10:48 AM, Brice Figureau
> wrote:
>>>> xmlrpc?
>>>> Do you still have 0.24.x clients?
>
> No. We're 0.25.5 across the board.
>
>>>> You omitted one important piece of inform
On 25/01/11 19:27, Nigel Kersten wrote:
> On Tue, Jan 25, 2011 at 10:25 AM, Brice Figureau
> wrote:
>> On 25/01/11 18:47, Jason Wright wrote:
>>> On Mon, Jan 24, 2011 at 9:24 PM, Daniel Pittman
>>> wrote:
>>>> For the other two exceptions, do you
5:in `dispatch'
> /usr/lib/ruby/1.8/xmlrpc/server.rb:368:in `call_method'
> /usr/lib/ruby/1.8/xmlrpc/server.rb:380:in `handle'
> /usr/lib/ruby/1.8/puppet/network/xmlrpc/processor.rb:44:in `process'
> /usr/lib/ruby/1.8/puppet/network/http/rack/xmlrpc.rb:35:in `process&#x
Notice how the "require" is in the function instead of being outside.
I'd think that ruby would be smart enough to understand the file has
already been "required" and not bother, but apparently it doesn't do
that for you. Can you give us what ruby version and wh
On 18/01/11 18:12, Nigel Kersten wrote:
> On Tue, Jan 18, 2011 at 8:50 AM, Brice Figureau
> mailto:brice-pup...@daysofwonder.com>>
> wrote:
>
> On Mon, 2011-01-17 at 18:38 -0800, Nigel Kersten wrote:
> > I'm trying to get a feel for the actual use cases
et update" only once
per day.
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
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@googlegro
On 07/01/11 20:44, Jeff McCune wrote:
> -Jeff
>
> On Jan 7, 2011, at 6:51 AM, Brice Figureau
> wrote:
>
>> On Fri, 2011-01-07 at 15:33 +0100, Sébastien Barthélémy wrote:
>>> Hello again,
>>>
>>> thank you for your answers. I use puppet 2.6.4.
>
of its time?
We used to have some problems with recursive file resources back in the
0.24/0.25 days that we fixed in the latest 0.25 releases. It is possible
some of them re-surfaced in 2.6...
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received t
duce the hyperlinking so it's possible that a bug there prevents it
to work in some cases. I know that some identifiers valid in puppet for
instance don't produce hyperlink because of that.
> This is using puppet 2.6.4-0.5-el5 and ruby-rdoc 1.8.5-5.el5_4.8 on
> RHEL 5.
they have a site.pp default? Wouldn't be the first time
> someone ran into that.
Or the OP is using puppet 0.25 or 0.24 which didn't support the none
checksum.
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message be
On Wed, 2011-01-05 at 13:25 -0800, Patrick wrote:
>
> On Jan 5, 2011, at 10:13 AM, Brice Figureau wrote:
>
> > On 05/01/11 18:11, Sébastien Barthélémy wrote:
> > > Hello,
> > >
> > > I store camera pictures in a git repository, which became quite
>
tatement.pp"
>
> Well, that was 4 hours ago and since then, ruby is eating 100% of my CPU
> (of one core of my 2.26GHz core 2 duo).
> From the log file, I can tell that puppet is indeed fixing perms, at a
> rate lower than one file per 10 seconds.
>
> I think find, xar
eal way to know is to use
Puppet introspection:
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Introspection
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
You received this message because you are subscribed to the Google Groups
"Puppet
On Wed, 2010-12-15 at 20:15 -0800, Patrick wrote:
> On Dec 15, 2010, at 1:48 PM, Brice Figureau wrote:
>
> > On 15/12/10 12:04, Patrick wrote:
> >> I'm looking for a way to run more than one puppetmaster on the same
> >> server under passenger. Most of the pupp
le requests to stop being blocked by the expensive catalog
> requests and keep the RAM usage low on the file serving processes.
You can use what I called file serving offloading:
http://www.masterzen.fr/2010/03/21/more-puppet-offloading/
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
nly 66% of the 30 minute span,
you'll globally consume 66% of all your CPU available...
Hope that helps,
[1]: http://projects.puppetlabs.com/projects/1/wiki/Puppet_Introspection
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed
On 15/12/10 20:24, Disconnect wrote:
> On Wed, Dec 15, 2010 at 2:14 PM, Brice Figureau
> mailto:brice-pup...@daysofwonder.com>>
> wrote:
>>
>> Note: we were talking about the puppet master taking 100% CPU, but
>> you're apparently looking to the pu
re talking about the puppet master taking 100% CPU, but
you're apparently looking to the puppet agent, which is a different story.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gr
ppears to be going on. This is absolutely not
> normal behavior. Even when I had 1 client checking in I had all cores
> fully used.
I do agree that it's not the correct behavior. I suggest you to strace
or use any other ruby introspection techniques to find what part of the
master i
On Wed, 2010-12-15 at 05:28 -0800, Chris wrote:
>
> On Dec 15, 12:42 pm, Brice Figureau
> wrote:
> > On Tue, 2010-12-14 at 00:24 -0800, Chris wrote:
> > > Hi
> >
> > > I recently upgraded my puppet masters (and clients) from 0.24.8 to
> > > 2.6.4
resource)
> end
> scope.compiler.add_resource(scope, resource)
> scope.compiler.evaluate_classes([resource_title],scope,false)
> if fully_qualified_type == 'class'
> resource
> end
> }.reject { |resource| resource.nil? }
> ---
ng (see one
of my blog post for more information).
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe fro
1 - 100 of 259 matches
Mail list logo
