2008/11/12 Mark D. Nagel <[EMAIL PROTECTED]> > > We've been having a huge number of problems with puppetmaster seizing up > on CentOS 4. We started with 0.23.2 and it worked, but the clients were > leaking memory and we hoped upgrading to 0.24.5 would help. Since then > we've had far worse problems, primarily that puppetmaster gets into a > state where it simply stops doing anything and any already connected > client similarly freezes. Part of the troubleshooting involved > upgrading ruby, first to a hand-built RPM, then to the RubyWorks RPMs, > but nothing really improved. I finally decided to revert to 0.23.2 and > we're still seeing the lockups. I believe replacing ruby with the > original OS RPM might get us back, but I am also looking at building a > dedicated VM. Since I have the option to install any OS I want, I was > hoping folks might have some suggestions on which have been found to > work best for running puppetmaster in terms of just making sure all the > parts work properly together as well as simplifying implementation of > the scalability options (this was painful on CentOS 4). I'm leaning > toward Debian Etch, but I'm open to anything at this point -- > suggestions welcome! > > Thanks, > Mark > > > Debian etch here with 16 real hosts, and 48 Xen hosts, No problems as yet.
This is a test env, hopefully puppet will be production soon with apporx 250 hosts. so we'll see how that go's :) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
