I have a server pmaster-dev that is a puppet client (its master is pmaster). The server pmaster-dev itself acts as a puppet master for several clients.
When pmaster-dev checks in with pmaster it is caching its facts to a local sqlite3 database file
/var/lib/puppet/state/clientconfigs.sqlite. On every subsequent check-in pmaster-dev never updates this local cache. Thus, its facts are always stale. Other clients of pmaster (including pmaster itself) never cache.
How do we either tell it to update the cache or disable caching of the facts? Why is it caching while other clients of pmaster are not?
We are running 2.7.18 on a Debian squeeze system.
Here is the
/etc/puppet/puppet.conf file for pmaster-dev:
[agent] server = pmaster.example.org environment = master configtimeout = 300 logdir = /var/log/puppet vardir = /var/lib/puppet ssldir = /etc/puppet/ssl rundir = /var/run/puppet ca_server = puppetca.example.org ca_port = 8141 graph = true report = true pluginsync = true classfile = $vardir/classes.txt localconfig = $vardir/localconfig diff_args = '-u' show_diff = true [master] certname = pmaster-dev.example.org syslogfacility = local2 logdir = /var/log/puppet vardir = /var/lib/puppet rundir = /var/run/puppet ssldir = /srv/puppetmaster/ssl reports = tagmail,lastcheck,logcache manifest = /srv/puppet/$environment/manifests/site.pp graph = true modulepath = /srv/puppet/$environment/modules:/srv/puppet/$environment/services:/srv/puppet/$environment/clients cacrl = /srv/puppetmaster/ssl/crl.pem ca = false manifestdir = /srv/puppet/$environment/manifests queue_source = stomp://pupqueue-dev.example.org:61613/ async_storeconfigs = true storeconfigs = false dbadapter = mysql dbuser = puppet dbpassword = secret dbserver = pupqueue-dev.example.org dbname = puppet ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY