Not all host reports in PuppetDB

[Jim Miller]

Hello everyone,

I hadn't noticed until recently but a large % of host reports are not getting into PuppetDB and I looking for ways to determine what the cause is.  I could see an all or nothing but not this.  I'm not worried about the data for those hosts but I'm un-sure what steps to take.  I sure hope this is an easy fix. 

For example in the puppetdb.log file, I'm seeing for some hosts where reports are getting stored and facts and catalogs are getting replaced.  For other hosts just replacing facts and catalogs are getting replaced.

I don't understand enough of the internals to know what to do here and I'm not sure how to peer into the database.  I did upgrade from an pretty old version of PuppetDB (1.x something to 2.3.3) and I can't help but feel that could be the cause but I'm just guessing.

We did use Puppetboard but now use Puppetboard.

Here's the relevant config values for puppet.conf -- just the master section
[master]
    certname = puppet.ourdomain.com
    report = true
    # reports log, store for non-dashboard or puppetdb
    # reports = log,store
    reports = http,puppetdb,rrdgraph
    reporturl = http://puppet.centric.com:3000/reports/upload  # Broke and no longer processing
   # removed by Jim 5/8/2015
   #  ### CONFIGS FOR PUPPET-DASHBOARD
   #  node_terminus = exec
   #  external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://puppet.centric.com:3000 /usr/share/puppet-dashboard/bin/external_node
    ### CONFIGS FOR PUPPETDB
    storeconfigs = true
    storeconfigs_backend = puppetdb
    ssldir = $vardir/ssl

We're running
Puppet Server 3.7.5
PuppetDB and PuppetDB-Terminus 2.3.3

[Wyatt Alt]

Hey Jim,

Do you see anything in your puppetserver log you can correlate to this? Also curious if your "Broke and no longer processing" comment is in relation to this issue or preexisting.

One interesting, possibly unrelated thing to know is that the report processors in "reports" attribute in your config file are parsed and applied in order, so if there were intermittent problems with your reporturl that somehow caused the run to bail uncompleted, that could prevent reports from making it to PuppetDB and would match with what you're seeing. Just a theory though -- I don't know what would cause that and I've been unsuccessful demonstrating it locally.

Wyatt

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b9581bf2-e372-46e9-b06d-c75e193554cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.