if you use summarize = true on your client configs, you should get a block
at the end that looks like this:
#puppetd -vt
Changes:
Total: 1
Resources:
Applied: 1
Out of sync: 1
Restarted: 1
Scheduled: 317
Total: 266
Time:
Config retrieva
Thanks guys. I will give both your suggestions a try and see how i get
on.
--~--~-~--~~~---~--~~
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 u
We have quite a bit of puppet clients handled by Mongrel server
(4instance) and off late been noticing performance issues with the
client mostly. It takes almost 2-3mins to complete puppet runs on
clients and takes almost 100%cpus.
I know its hard to know what the problem is unless you see what
Hello,
> We have majority of RHEL5 servers in our environment. I have noticed
> in the process of trying to deploy puppet, that i am getting errors
> when yum is trying to install packages. Most of the time it works
> flawlessly, however sometime the following will be reported:
> [...]
> Does any
Peter,
I made that change in both affected templates late last night. Both
services are still experiencing strange issues (flapping), but it's no
longer as regular as before (now, say, each one will be OK for 4 or 5
cycles and then flap back and forth).
I've confirmed via debugging output to sys
On Wed, Jul 29, 2009 at 12:35 PM, David Schmitt wrote:
>
> Asif Iqbal wrote:
>> On Wed, Jul 29, 2009 at 1:57 AM, David Schmitt wrote:
>>> Asif Iqbal wrote:
So I think I should start small and simple and it may grow to a
solution that will be really useful to others.
Lets start
Asif Iqbal wrote:
> On Wed, Jul 29, 2009 at 1:57 AM, David Schmitt wrote:
>> Asif Iqbal wrote:
>>> So I think I should start small and simple and it may grow to a
>>> solution that will be really useful to others.
>>>
>>> Lets start w/ real basic.
>>>
>>> I have 300 hosts. I like a push a user to
On Wed, Jul 29, 2009 at 1:57 AM, David Schmitt wrote:
>
> Asif Iqbal wrote:
>> So I think I should start small and simple and it may grow to a
>> solution that will be really useful to others.
>>
>> Lets start w/ real basic.
>>
>> I have 300 hosts. I like a push a user to about 100 hosts (dns
>> r
2009/7/29 josbal :
>
> Hi,
>
> We have majority of RHEL5 servers in our environment. I have noticed
> in the process of trying to deploy puppet, that i am getting errors
> when yum is trying to install packages. Most of the time it works
> flawlessly, however sometime the following will be reporte
Hi Dan,
I wasn't planning to include reporting so quickly, but you've inspired me to
push it up a bit.
you'll find some basic info at http://ohadlevy.github.com/gni/
in the code, look in app/model/report.rb and db/migrate/*report*
have fun
Ohad
On Wed, Jul 29, 2009 at 7:40 PM, Dan Bode wrote:
Brice Figureau writes:
> One thing I noticed is the following: I had in two separate places
> (modules) the following pattern:
>
> if ! defined(File["a"]) {
> file { "a":
> ...
> }
> }
>
> Then when a host was coming to get its config in puppetmaster, it could
> get the File[a] defined f
Hi Ohad,
--ah, we extend the schema... :)
Can you say what the reporting schema looks like? And more importantly for
me, are you combining logs and metrics in some way (if so how?)
-thanks,
Dan
--~--~-~--~~~---~--~~
You received this message because you are subs
On Wed, 2009-07-29 at 09:56 +0100, Trevor Hemsley wrote:
> Brice Figureau wrote:
> > What I suggest you is if it happens next time, is to use innotop and
> > have a look to the live running queries. You might find that you have
> > one or more "slow" queries.
> >
> The slow query log might be a
Brice Figureau wrote:
> What I suggest you is if it happens next time, is to use innotop and
> have a look to the live running queries. You might find that you have
> one or more "slow" queries.
>
The slow query log might be a better alternative.
--
Trevor Hemsley
Infrastructure Engineer
...
On Tue, 2009-07-28 at 21:09 -0400, Mark Plaksin wrote:
> Brice Figureau writes:
>
> >> Our mysql questions, com_select and com_insert stats spike first.
> >> com_select and com_update are normally at around 5 and spike to 40;
> >> questions is normally around 150 and spikes to 600. Threads conn
15 matches
Mail list logo
