After an unexpected and unreasonably long hiatus, I've finally returned to
implementing Puppet in my environment.

My puppetmaster: Puppet 0.25.4, Facter 1.5.7, Ruby 1.8.7, and FreeBSD 8.0.

I've got five clients using the puppetmaster so far. After about 24 hours,
I've got three puppetmaster processes running. This number continues to grow
over time. If stored configs are enabled, catalog requests eventually start
failing because they've maxed out my allowed DB connections.

The children processes are in an Idle state. Sending a sigterm to the
children has zero effect. Killing the parent sends it into its stop routine
(which prevents new connections), but never actually terminates the process
(presumably because it's waiting for its idle children to terminate). Kill
-9 does the trick, but I don't like the idea of clobbering an in-progress
transaction.

Is this a known problem?


-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.

Reply via email to