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), and the problem persists.

Thus I did some tests:

1. got ruby from "Ubuntu Meercat":
libruby1.8                                1.8.7.299-2
ruby1.8                                   1.8.7.299-2
ruby1.8-dev                               1.8.7.299-2

Same Problem (debian is 1.8.7.302 I think), with ruby from ubuntu lucid 
(1.8.7.249) the problem is the same. I guess we can rule out debian's ruby here.

2. I reported that after stopping apache, stray master process remain and do 
100% cpu. I did an strace on those processes and they do this (whatever that 
means):

$ strace -p 1231
Process 1231 attached - interrupt to quit
brk(0xa49a000)                          = 0xa49a000
brk(0xbf51000)                          = 0xbf51000
brk(0xda09000)                          = 0xda09000
brk(0xa49a000)                          = 0xa49a000
brk(0xbf52000)                          = 0xbf52000
brk(0xda09000)                          = 0xda09000
brk(0xa49a000)                          = 0xa49a000
brk(0xbf52000)                          = 0xbf52000
brk(0xda09000)                          = 0xda09000
^CProcess 1231 detached

3. I have now disabled reports, lets see what happens.

Thanks for the effort and have a nice day.
udo.


On 07.02.2011, at 19:56, Brice Figureau wrote:

> On 07/02/11 17:23, Ashley Penney wrote:
>> Because I like to live dangerously I upgraded to 2.6.5 and it seems like
>> this has resolved the CPU problem completely for me.
> 
> Did you upgrade the master or the master and all the nodes?
> 
> I had a discussion about this issue with Nigel during the week-end, and
> he said something really interesting I didn't thought about:
> it might be possible that the reports generated by 2.6.3 were larger
> than what they were in previous versions.
> 
> It is then possible that the CPU time taken to unserialize and process
> those larger reports is the root cause 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/
> 
> -- 
> 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 email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 

-- 
:: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1"
:: genuine input for your ears: http://auriculabovinari.de 
::                          your eyes: http://ezag.zoide.net
::                          your brain: http://zoide.net




-- 
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 email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to