Hmm, I had thought these were one in the same. I don't have a 3 environment to look at anymore. Good luck.
On Wednesday, June 28, 2017 at 2:37:35 PM UTC-5, Peter Krawetzky wrote: > > I looked at both documents and the second one references the scheduler log > files filling up. Mine are actually in the KahaDB directory. > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/06d2078d-120e-46b7-8f60-006582a39d47%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
