search for: async_storeconfigs

Hi all, I currently am using puppet with storeconfigs and am quite happy with the results. I also see that there is now the option of having async_storeconfigs. What I''m wondering about is the following: 1. What benefit is there to running async_storeconfigs over storeconfigs? 2. In what scenario''s would async provide a benefit to standard storeconfigs? 3. What are the typical things to look out for when running async_storeconfigs? Than...

So we are trying to use async_storeconfigs. It seems when I get it all up and running the hosts.ip for an agent gets its hosts.ip entry in the DB set to the puppetmaster that it got its catalog from instead of its own IP. If I turn async_storeconfigs off and re-run puppet agent on the node that had its IP updated incorrectly it then updat...

# cat /etc/redhat-release CentOS release 6.4 (Final) # puppet --version 3.2.3 # rpm -q puppetdb puppetdb-1.3.2-1.el6.noarch I am now receiving "Not collecting exported resources without storeconfigs" for my opsview module. It was working fine on puppet 2.7 with Activerecord/MySQL. I am still new to puppetdb so maybe I am missing something. This is from puppet.conf: storeconfigs

...They connect to their PM in site B just fine, but then the site B PM needs to connect to the storeconfigs DB in site A. This connection usually takes too long. So we end up with about 50% error rate in site B while having a 0% error rate in site A. I''ve tried to address this by using async_storeconfigs which seemed to help a lot but ran into https://projects.puppetlabs.com/issues/12140 which was a dealbreaker. Something else I''ve tried is just having agents in site B use the PMs in site A (so no more PM in site B). This helps a lot, but we still get errors. The 50% error rate drop...

...D files are kept. # The default value is ''$vardir/run''. rundir = /var/run/puppet dns_alt_names = devops.XXXXX.com,devops confdir = /etc/puppet vardir = /var/lib/puppet storeconfigs = true storeconfigs_backend = puppetdb thin_storeconfigs = false async_storeconfigs = false ssl_client_header = SSL_CLIENT_S_D ssl_client_verify_header = SSL_CLIENT_VERIFY # Where SSL certificates are kept. # The default value is ''$confdir/ssl''. ssldir = $vardir/ssl any ideas where am I going wrong? I checkthe directory permissions; /usr/sh...

Hello, I have configured puppet and puppetdb (storeconfig) with postgresql and the service run and the collecting are good for example: I can make query with the next command and responds ok . [.........................] [root@master]# curl -X GET -H ''Accept: application/json'' http://127.0.0.1:8080/v2/facts --data-urlencode ''query=["=", "name",

...Using cached certificate for ca debug: Using cached certificate for vusion-production debug: Using cached ce ..............* it works* ## User mode config root@vusion-production:~# puppet config print all --mode user allow_duplicate_certs = false archive_file_server = puppet archive_files = false async_storeconfigs = false authconfig = /etc/puppet/namespaceauth.conf autoflush = false autosign = /etc/puppet/autosign.conf bindaddress = "" bucketdir = /var/lib/puppet/bucket ca = true ca_days = "" ca_md = md5 ca_name = Puppet CA: vusion-production ca_port = 8140 ca_server = puppet ca_ttl = 5y...

...e following set: root@puppet:/etc/puppet# grep storeconfig puppet.conf # Boolean; wether storeconfigs store in the database only the facts and exported resources. # If true, then storeconfigs performance will be higher and still allow exported/collected thin_storeconfigs = false # async_storeconfigs = false # You can adjust the backend using the storeconfigs_backend setting. storeconfigs = true storeconfigs_backend = active_record root@puppet:/etc/puppet# grep foreman puppet.conf external_nodes = /usr/share/foreman/extras/puppet/foreman/files/ external_node.rb reports...