Mine do not look too dissimilar: PassengerUseGlobalQueue on PassengerMaxPoolSize 20 PassengerHighPerformance on PassengerPoolIdleTime 1800 PassengerStatThrottleRate 120 RackAutoDetect Off RailsAutoDetect Off
1, Try using the global queue 2. Try dropping you pool idle time, which should force turnover/restarts of puppet. (300 is the default, IIRC). 3. Are you using 0.25.X 4. On one of your nodes try puppetd --debug and see if there are telling details there. I am running CentOS 5.x (RedHat essentially) with ruby, passenger and and puppet installed by hand in /usr/local rather than using a package system. Ruby 1.8.7, passenger 2.2.11. Apache is the "packaged" version installed with yum. 2.2.3 I assume that you are using the ports collection to get your installs done? Cheers-- Charles On Tue, Apr 27, 2010 at 10:56 AM, S H <shdashb...@gmail.com> wrote: > I also just discovered that some of my clients are locking up and requiring > a SIGKILL to end them. This could be the root cause of the puppetmaster > issues, so I'm going to run the clients as cron jobs for a while and see if > that changes anything. > > > -SH > > -- > 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 from this group, send email to > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- 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 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.
