It's a custom script I wrote quite a while ago and I forgot about it ;)
On Thu, Sep 12, 2013 at 3:34 AM, Ken Barber wrote:
> > Yes, using postgresql here. It turns out I have another script pushing
> facts
> > (without custom facts) into puppetdb, which messed up with puppetdb query
> > outputs
> Yes, using postgresql here. It turns out I have another script pushing facts
> (without custom facts) into puppetdb, which messed up with puppetdb query
> outputs. After fixing that script, things are ok now here.
Aaah, so it wasn't performance at all. Was that a custom script
someone at your co
Hi Ken,
Yes, using postgresql here. It turns out I have another script pushing
facts (without custom facts) into puppetdb, which messed up with puppetdb
query outputs. After fixing that script, things are ok now here.
Thanks,
On Wed, Sep 11, 2013 at 5:29 AM, Ken Barber wrote:
> > Running pupp
> Running puppet only at around 4am once a day here. And I noticed that
> puppetdb query not working as expected, if using it to query nodes based on
> some custom fact value.
>
> During the days, things are working fine. But if I ran the same query at
> around say 3am (searching nodes based on som
Running puppet only at around 4am once a day here. And I noticed that
puppetdb query not working as expected, if using it to query nodes based on
some custom fact value.
During the days, things are working fine. But if I ran the same query at
around say 3am (searching nodes based on some custom fa
