I had a bad manifest at one point which told puppetd to --recurse on a massive directory that I didn't actually want it to manage. I reverted the config. Ever since then however, the nodes that once applied that --recurse take a much longer time to update themselves.
What I see is this: debug: Storing state debug: Stored state in 59.66 seconds On a fresh node this takes less than five seconds. While "Storing state" is running the puppetd Ruby process is at 100% CPU. Is there any way I can get the affected nodes to forget about that old config? Or is there any way I can get more information about what state is being stored to make sure this is the issue? Ubuntu 9.10/ puppetd --version => 0.24.8 thanks! hernan -- 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.
