search for: rajeshwaran

...`new'' from /usr/sbin/puppetd:312 [FAILED] Can someone help me out in this .. my other puppet clients work great. Is there some basic things I have not done in my new servers ?? please throw some ideas about this. Thanks Rajeshwaran -- He also serves Who only stands and waits.... _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

All, Once the puppet clients are installed, is there a option to list the client in the server. mind you I never meant the cert - signing list.. which would be puppetca --list. Thanks for your help -Rajeshwaran -- He also serves Who only stands and waits.... _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

Folks, I have installed puppet my network and it works great .. I have configured it such a way that when I make changes in the server source fiels..it gets updated in teh puppet clients. As the document reads the puppet clients checks for any changes from the server every 30 mins. But is there is any opiton of changing this value to lesser time .. say 15 mins .. or is there opiton for the

Can anyone help me with this error I am having. I am using puppet on Debian Etch, version 0.20.1-1 from apt works OK, but due to one or two problems we want to use the version from testing, 0.23.2-10, but the puppetd just fails upon startup spitting this out: Starting puppet configuration management tool/usr/lib/ruby/1.8/timeout.rb:54:in `open'': execution expired (Timeout::Error)