Ken / Deepak, first of all thanks a ton for the great help.
It seems there is some issue with the "puppet facts upload" command" I already have the certname & server configuration directives declared in the puppet.conf but for some reason the same are not being recognized by the puppet facts command When I am trying to run *# puppet facts upload* ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) *Error: getaddrinfo: Name or service not knownError: Try 'puppet help facts upload' for usage* But when I try to run *# puppet facts upload --server="puppet_master_server" --certname="agent_certname"*ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) *Notice: Uploaded facts for 'agent_certname'* Also I tried to use the postrun_command within the puppet.conf on the client node but I end up getting the same error. Please let me know if there is something that I am missing, as I am planning to either use "puppet facts upload" within my manifest or in the postrun command. Awaiting your reply. Thanks & Regards, Rakesh K. On Wed, Jun 11, 2014 at 8:21 PM, Ken Barber <[email protected]> wrote: > My colleague Deepak just brought to my attention another mechanism > which works like option #3 without the hard work: > > puppet facts upload > > But you'll need to ensure your auth.conf on your puppet master has a > snippet like the following: > > path ~ ^/facts/([^/]+)$ > method save > allow $1 > > Without it, you'll get a permission denied error. > > ken. > > On Wed, Jun 11, 2014 at 2:22 PM, Ken Barber <[email protected]> wrote: > >> Sorry for re-opening a old thread but I am still struggling on related > >> topic.. > >> > >> Step 1: I am copying some .rb files to the > >> /usr/lib/ruby/site_ruby/ruby/1.8/facter/ folder > >> Step 2: A facter command gives me the values for all new custom / > external > >> facts > >> > >> But the values for new facts will not get into puppetdb untill a next > agent > >> run... > >> > >> Is there a way to run puppet from within a manifest or any other way to > >> force "replace facts" remotely on the agent ??? > > > > * You could run things in noop mode potentially, which would force a > > fact submission. > > * You could run puppet apply, and use a masterless way of submitting > > facts also (setup would be required: > > http://docs.puppetlabs.com/puppetdb/2.0/connect_puppet_apply.html). > > * You could submit a POST request in a script for your facts against > > the master, throwing away the catalog (saves on the noop processing) > > * You could sumibt the facts manually to PuppetDB yourself, here is a > > rough script I use for testing which you could modify to match your > > needs: https://gist.github.com/kbarber/6190c64335613111c9df > > > > Each one has its own pros and cons. In particular some of these > > require direct communication between the node and the PDB instance > > which might not be desirable in some cases. > > > > None of these things have common solutions today that we (the PDB > > maintainers) "maintain" ourselves, but a few people have done things > > like the above in the past in their own bespoke way. > > > > ken. > > -- > 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/CAE4bNTne8zw%3DcZDHg4cdBhK6T0EcC5axvWKQs7ALxcX6WB4aig%40mail.gmail.com > . > 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/CAEJrXMXuu5A5ETD0QbR28TY259kGgE-YQpwHYJCwCBbh5964Gg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
