Hi, On Thu, Aug 19, 2010 at 6:39 PM, Tim <tkedwa...@fastmail.com.au> wrote: > puppetd[7303]: (//munin/Config-file[muninnode]/File[/etc/m > unin/munin-node.conf]) Failed to retrieve current state of resource:
Are you using the built-in webrick server that comes with Puppet or have you switched to either Mongrel or Passenger? If you're using the built-in server, you may be hitting the single threaded nature of that server, i.e. it can only respond to one request at a time. So, if more than one puppet client connects at the same time, you'll see some of them throw this (and other similar) errors as their requests time out. If you have a low number of clients (<100), you should be able to get away with using the --splay command-line parameter (or splay=true in puppet.conf) to spread the load out on the client side. If you have more clients, you should look at switching to Mongrel or Passenger instead. Hope that helps, Avi -- 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.
