Hi Mike, glad to hear I'm not the only one with the headaches :) We are planning on upgrading everything across the board from puppet server, puppet agent and puppet db. At least now I can get back to planning that!
Our catalog/resource duplication is zero after about 5 hours of running. I need to look at this as well but suspect each agent run has different data or catalog compile. I need to look into those more just like you do when time permits. Command queue has peeked at 5 max and command processing/sec is 1.93. Let me know if you have any questions. On Wednesday, June 28, 2017 at 12:25:57 PM UTC-4, Peter Krawetzky wrote: > > Last Sunday we hit a wall on our 3.0.2 puppetdb server. The cpu spiked > and the KahaDB logs started to grow eventually almost filling a > filesystem. I stopped the service, removed the mq directory per a > troubleshooting guide, and restarted. After several minutes the same > symptoms began again and I have not been able to come up with a puppetdb or > postgresql config to fix this. > > We tried turning off storeconfig in the puppet.conf file on our puppet > master servers but that doesn't appear to have resolved the problem. I > also can't find a good explanation as to what this parameter really does or > does not do even in the puppet server documentation. Anyone have a better > insight into this? > > Also is there a way to just turn off puppetdb? > > I've attached a file that is a snapshot of the puppetdb dashboard. > > Anyone experience anything like this? > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1b82f569-81b0-4bbf-8f49-f2e94a799e21%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
