On Tue, Apr 27, 2010 at 1:57 PM, Patrick <kc7...@gmail.com> wrote: > > On Apr 27, 2010, at 10:51 AM, Charles Johnson wrote: > > 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). > > I'll try these suggestions after getting --debug output from a hung client.
> 3. Are you using 0.25.X > > Yes. The puppetmaster is 0.25.4 and the client is 0.25.3. > > 4. On one of your nodes try puppetd --debug and see if there are telling > details there. > > Done. We'll see what comes up. > 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 > > With the exception of the puppetmaster's Puppet install, yes. Puppetmaster - FreeBSD 8.0 i386 with Ruby 1.8.7.248,1, Passenger 2.2.9, Apache 2.2.14_5 all from packages and Puppet 0.25.4 from gems. Puppetclient - FreeBSD 8.0 x64 with Ruby 1.8.7.248,1 and Puppet 0.25.3 from packages. > I second all that. Also, did you try sending a SIGTERM to the clients and > waiting a couple minutes? Sometimes puppetd can take a very long time to > stop. > A cronned client hung last night and hadn't stopped even three hours after I sent it a SIGTERM. kill -9 seems to be the only. -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. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.