As far as disabling modules is concerned. The way I've organized my
manifests allows me to quickly comment out the various "include
someclass" entries per system role or hostgroup. The following works
for my environment and is not necessarily considered best practice.
For example, I might have a "generic role" that has numerous "include
someclass" entries like so:
node generic {
include autofs
include puppet
include crontab
include ntp
...
}
a typical node might look like:
node 'typical-node' inherits generic {
}
The above configuration allows me to quickly comment out modules for
my nodes.
Mark
On Mar 8, 1:55 am, Matt <mattmora...@gmail.com> wrote:
> Out of interest Mark, how did you go about disabling all modules bar puppet?
>
> Matt
>
> On 8 March 2010 02:07, Mark Christian <supertr...@gmail.com> wrote:
>
> > Thanks for the suggestion. I've set storeconfigs = false, it's been a
> > couple hours and I've yet to see any "too many connections" errors.
>
> > On Mar 7, 5:47 pm, Ohad Levy <ohadl...@gmail.com> wrote:
> > > Hi Mark,
>
> > > Are you using storeconfigs? I've seen the too many connections error in
> > > relationship to activerecord versions (and the lack of mysql gem
> > existence).
>
> > > In general, I would expect the load on your mongrels to be lower than
> > > 0.24.x
> > > cheers,
> > > Ohad
>
> > > On Mon, Mar 8, 2010 at 3:46 AM, Mark Christian <supertr...@gmail.com>
> > wrote:
> > > > I have updated the 1100 clients that prior to the update used to
> > > > connect to the master just fine. Now after about 30 minutes of
> > > > running, puppetmasterd starts to complain "puppetmasterd[6875]: Too
> > > > many connections", and from that point forward will stop compiling
> > > > catalogs. Puppetmaster is configured using the Mongrel Apache
> > > > configuration as described here:
> > > >http://reductivelabs.com/trac/puppet/wiki/UsingMongrel
>
> > > > In addition I've disabled all modules except for the "puppet" module
> > > > which helped push the client upgrade as well as configure the
> > > > "runinterval" from the pre-upgrade 1 hour run to a 4 hour run
> > > > interval. At this point there might be a couple dozen 24.8 clients
> > > > still attempting to connect.
>
> > > > I guess I'm wondering if I need to scrap the Mongrel config with 5
> > > > "Mongrel instances" that used to handle 1100+ clients all which had
> > > > significant configurations, or if someone has an idea outside of
> > > > implementing more puppetmasters.
>
> > > > Thank you for any insight.
>
> > > > Mark
>
> > > > --
> > > > 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>
> > <puppet-users%2bunsubscr...@googlegroups.com<puppet-users%252bunsubscr...@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<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.
