search for: pidlock

Hi, whenever i am starting puppet master after new installation it gives below messages .. /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `initialize'': Permission denied - /var/lib/puppet/run/master.pid (Errno::EACCES) from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `open'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `lock'' from /usr/lib/ruby/...

...ientbucket]/ensure) change from absent to directory failed: Cannot create /var/puppet/clientbucket; parent directory /var/puppet does not exist I had to manually create that directory: $ sudo mkdir /var/puppet $ sudo puppetmasterd --mkusers /usr/lib/ruby/gems/1.8/gems/puppet-0.24.1/lib/puppet/util/pidlock.rb:33:in `initialize'': Permission denied - /var/puppet/run/puppetmasterd.pid (Errno::EACCES) from /usr/lib/ruby/gems/1.8/gems/puppet-0.24.1/lib/puppet/util/pidlock.rb:33:in `open'' from /usr/lib/ruby/gems/1.8/gems/puppet-0.24.1/lib/puppet/util/pidlock.rb:33:in `lock...

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into