Hi. I am just reading this thread, and it strikes me that we have the same problems with 2.6.3.
Since upgrading from 2.6.2 to .3 puppetmaster shows the behabiour described in this thread. We have about 160 clients, and puppetmaster (is now) 8 core, 8Gb RAM kvm instance. Had this with 4 cores and 4 gigs RAM, "doublesizing" the VM did not change a thing! We use passenger 2.2.11debian-2 and apache 2.2.16-3, ruby1.8 from squeeze. Puppetmaster works fine after restart, then after about 2-3 hours it becomes pretty unresponsive, catalog runs go upt do 120 seconds and more (the baseline being something about 10 seconds). I need to restart apache/puppetmaster about once a day. When I do that I need to: * stop apache * kill (still running) pupppetmasters (with SIGKILL!), some are always left running with "CPU 100%" * start apache Something is very weird there, and there were no fundamental changes to the manifests/modules. The only thing that really changed is the VM itself. It was XEN (for years), we switched to KVM with kernel 2.6.35 Another strange thing: puppet-clients do run a lot longer nowadays. A machine usually took about 40-50 seconds for one run. When puppetmaster goes crazy it now takes ages (500 seconds and even more). Something is weird there... --udo, -- 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.
