I am pulling in the ''client'' intended version of puppet.conf on my puppetmaster system - probably because I had a package that required a class it shouldn''t have and I have fixed that (I think - hard to test) but even after killing off all puppetd processes, clearing out /var/lib/puppet/client_yaml/* and /var/lib/puppet/state/* and restarting puppetd they just seem to reload the specific mod_puppet classes that it shouldn''t. Perhaps it is a stored config and I''ve tried running puppetstoredconfigclean.rb without any success (user stupidity for not knowing what this host file is supposed to look like). How can I get a fresh start with a client so it operates only on the classes it is configured to use? Craig -- Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
What problem do you have with puppetstoreconfigclean.rb? The problem I usually have is that I forget it has to be run as root on the puppetmaster, I keep thinking I need to run it on the client machine. -- Nathan Clemons http://www.livemocha.com The worlds largest online language learning community On Thu, Jun 30, 2011 at 9:59 AM, Craig White <craig.white@ttiltd.com> wrote:> I am pulling in the ''client'' intended version of puppet.conf on my > puppetmaster system - probably because I had a package that required a class > it shouldn''t have and I have fixed that (I think - hard to test) but even > after killing off all puppetd processes, clearing out > /var/lib/puppet/client_yaml/* and /var/lib/puppet/state/* and restarting > puppetd they just seem to reload the specific mod_puppet classes that it > shouldn''t. Perhaps it is a stored config and I''ve tried running > puppetstoredconfigclean.rb without any success (user stupidity for not > knowing what this host file is supposed to look like). > > How can I get a fresh start with a client so it operates only on the > classes it is configured to use? > > Craig > > -- > Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com > 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com > > Need help communicating between generations at work to achieve your desired > success? Let us help! > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Jun 30, 2011, at 8:21 PM, Nathan Clemons wrote:> What problem do you have with puppetstoreconfigclean.rb? The problem I usually have is that I forget it has to be run as root on the puppetmaster, I keep thinking I need to run it on the client machine.---- The other issue I fixed... PEBKAC naturally # ruby puppetstoredconfigclean.rb ubuntu.ttinet puppetstoredconfigclean.rb:54:in `require'': no such file to load -- puppet/rails (LoadError) from puppetstoredconfigclean.rb:54 root@ubuntu:/etc/puppet# which ruby /usr/local/bin/ruby root@ubuntu:/etc/puppet# gem list --local *** LOCAL GEMS *** abstract (1.0.0) actionmailer (3.0.4) actionpack (3.0.4) activeldap (1.2.4) activemodel (3.0.4) activerecord (3.0.4, 2.3.12) activeresource (3.0.4) activesupport (3.0.4, 2.3.12) arel (2.0.8) builder (2.1.2) bundler (1.0.10) daemon_controller (0.2.6) erubis (2.6.6) facter (1.5.9) fast_gettext (0.5.8) fastthread (1.0.7) file-tail (1.0.5) gettext_i18n_rails (0.2.2) i18n (0.5.0) json (1.5.2) locale (2.0.5) mail (2.2.15) mime-types (1.16) mysql (2.8.1) passenger (3.0.7) polyglot (0.3.1) puppet (2.6.8) rack (1.2.1) rack-mount (0.6.13) rack-test (0.5.7) rails (3.0.4) railties (3.0.4) rake (0.8.7) ruby-ldap (0.9.11) spruz (0.2.5) thor (0.14.6) treetop (1.4.9) tzinfo (0.3.24) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.