For a node I know has been updated, I get (just listing the timestamps): "facts_timestamp" : "2016-08-17T17:52:33.899Z",
"report_timestamp" : "2016-08-16T21:15:22.376Z", "catalog_timestamp" : "2016-08-16T21:14:24.444Z", So it seems that facts are being stored, but reports & catalogs aren't. The puppet.conf file on this (and all other clients) contains: reports = puppetdb Is there something else I need to have set? I don't think we changed config this morning.... On Wednesday, August 17, 2016 at 1:50:58 PM UTC-4, Wyatt Alt wrote: > > I'd check the timestamps in the output of > > curl -X GET http://localhost:8080/pdb/query/v4/nodes/fs1603.our.net > > (with a real certname if that one is fake). These will tell you when the > last report/facts/catalog for the node were stored. > > Nothing about the log output you've posted indicates an issue storing > data, so I'm wondering if the problem is with what puppet > explorer/puppetboard are considering an "update". For example maybe reports > got switched off and only reports are considered in that determination (I > have no idea if this is true). > > Wyatt > > On Wed, Aug 17, 2016 at 9:39 AM, Bret Wortman <[email protected] > <javascript:>> wrote: > >> Versions: >> >> >> # rpm -qa | grep puppet >> puppetserver-2.4.0-1.el7.noarch >> puppetdb-4.2.0-1.el7.noarch >> puppetexplorer-2.0.0-1.noarch >> puppetdb-termini-4.2.0-1.el7.noarch >> puppet-agent-1.6.0-1.el7.x86_64 >> # rpm -qa | grep postgres >> postgresql95-libs-9.5.4-1PGDG.rhel7.x86_64 >> postgresql95-9.5.4-IPGDG.rhel7.x86_64 >> postgresql95-server-9.5.4-IPGDG.rhel7.x86_64 >> postgresql95-contrib-9.5.4-IPGDG.rhel7.x86_64 >> # >> >> >> On Wednesday, August 17, 2016 at 12:37:12 PM UTC-4, Bret Wortman wrote: >>> >>> My puppetdb instance is up and running but hasn't stored any updates of >>> any kind in the past 7 hours, according to both Puppet Explorer and >>> Puppetboard. >>> >>> The process is running and so is postgres. Puppet configs haven't >>> changed in that time. /var/log/puppetlabs/puppetdb/puppetdb.log shows >>> plenty of updates coming in: >>> >>> 2016-08-17 16:31:48,887 INFO [p.p.command] [-UUID-] [replace facts] >>> branfile1.our.net >>> 2016-08-17 16:31:59,136 INFO [p.p.command] [-UUID-] [replace facts] >>> zs311.our.net >>> 2016-08-17 16:32:11,347 INFO [p.p.command] [-UUID-] [replace facts] >>> gs1205.our.net >>> 2016-08-17 16:32:12,982 WARN [p.p.q.engine] The event-counts entity is >>> experimental and may be altered or removed in the future. >>> 2016-08-17 16:32:15,237 INFO [p.p.command] [-UUID-] [replace facts] >>> fs1603.our.net >>> >>> >>> and so on. >>> >>> There's nothing obviously wrong when Puppetdb starts up in the logfile, >>> either. What should I be looking at to see why it's accepting these updates >>> but (apparently) not storing them? Does anyone know postgres better than I >>> do who could give me some way to directly query the database to see if one >>> of the above updates (or any other, for that matter) exists? >>> >>> Thanks! >>> >>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/8a76426c-1da9-4d24-9ffe-ffc9d8cae59b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/puppet-users/8a76426c-1da9-4d24-9ffe-ffc9d8cae59b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/dc8966c1-7740-4334-91e5-2283c55842b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
