search for: puppetconfig

...1.8.4 (2005-12-24) [i486-linux] Aborted www01:/home/cwarden# puppetd --debug --onetime debug: puppetd: Setting logdir to ''/var/log/puppet'' debug: puppetd: Setting vardir to ''/var/lib/puppet'' debug: puppetd: Setting rundir to ''/var/run'' debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml: Autorequiring file /var/lib/puppet/state debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml: subscribes to /var/lib/puppet/state debug: puppetconfig/puppet/file=/etc/puppet/ssl: Autorequiring file /etc/puppet debug: puppetconfig/puppet/fil...

...ml). But I figure someone else may have seen this. Thanks, Andy Delcambre # puppetd -d debug: puppetd: Setting logdir to ''/var/log/puppet'' debug: puppetd: Setting vardir to ''/var/lib/puppet'' debug: puppetd: Setting rundir to ''/var/run'' debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml: Autorequiring file /var/lib/puppet/state debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml: subscribes to /var/lib/puppet/state debug: puppetconfig/puppet/file=/etc/puppet/ssl: Autorequiring file /etc/puppet debug: puppetconfig/puppet/fil...

...5) [i386-linux] # gem list mongrel *** LOCAL GEMS *** mongrel (1.0.1) A small fast HTTP library and server that runs Rails, Camping, Nitro and Iowa apps. # puppetmasterd --verbose --debug debug: Parsing /etc/puppet/puppet.conf info: Starting server for Puppet version 0.23.2 debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/private_keys/util00- hq.int.mediosystems.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ private_keys] debug: /puppetconfig/ca/File[/var/lib/puppet/ssl/ca/inventory.txt]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /puppetconfig/ca/File[/var/lib/puppet/ssl/c...

...9;' debug: puppet: Setting lockdir to ''/var/lock'' debug: puppet: Setting ssldir to ''$vardir/ssl'' debug: puppetd: Setting classfile to ''$vardir/classes.txt'' debug: puppetd: Setting localconfig to ''$vardir/localconfig'' debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml: Autorequiring file /var/lib/puppet debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml: Autorequiring file /var/lib/puppet/state debug: puppetconfig/puppet/file=/var/lib/puppet/state/state.yaml: subscribes to /var/lib/puppet debug: puppe...

...nd ruby''s --debug option shows the following: [root@puppet ~]# puppetmasterd --debug debug: Parsing /etc/puppet/puppet.conf info: Starting server for Puppet version 0.23.2 debug: Finishing transaction -605102028 with 0 changes debug: Finishing transaction -606620098 with 0 changes debug: /puppetconfig/main/File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /puppetconfig/ca/File[/var/lib/puppet/ssl/ca/ca_crt.pem]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /puppetconfig/ca/File[/var/lib/puppet/ssl/ca/private]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /puppetco...

Hi, I am using a template to create an /etc/exports file. I have a template that looks like this (but results in the puppetmasterd dying on the server when the client updates): <% nfsHomeClients.split.each do |host| -%> /nfs <%= host %>(<%= mainshareoptions %>) <% nfspaths.each do |path| -%> <%= path %> <%= host %>(<%= nfsoptions %>) <% end

...ca: Setting ca_ttl to ''5y'' debug: ca: Setting cacert to ''$cadir/ca_crt.pem'' debug: fileserver: Setting fileserverconfig to ''$confdir/fileserver.conf'' debug: filebucket: Setting clientbucketdir to ''$vardir/clientbucket'' debug: /puppetconfig/puppet/File[/var/opt/csw/puppet/state/state.yaml]: Autorequiring File[/var/opt/csw/puppet/state] debug: /puppetconfig/puppet/File[/var/opt/csw/puppet/state/graphs]: Autorequiring File[/var/opt/csw/puppet/state] debug: /puppetconfig/certificates/File[/etc/opt/csw/puppet/ssl/certs]: Autorequiring Fil...

...9; debug: puppetd: Setting classfile to ''$vardir/classes.txt'' debug: puppetd: Setting localconfig to ''$vardir/localconfig'' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:229: warning: Insecure world writable dir /home/INTERNAL, mode 041777 debug: /puppetconfig/puppet/File[/var/lib/puppet/plugins]: Autorequiring File[/var/lib/puppet] debug: /puppetconfig/puppetd/File[/var/lib/puppet/classes.txt]: Autorequiring File[/var/lib/puppet] debug: /puppetconfig/puppet/File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /...

Are exec resources triggered by notify events supposed to be run once for every event received or only run once per run irregardless of the number of resources that notified it? It seems to me that it gets run twice no matter how many resources triggered it. consider the following class: class dhcp { $prefix = "/usr/local/etc/dhcpd" $dhcpd_conf = "$prefix/dhcpd.conf"

Hi, How should I handle the combinatorics when one config file must be built for a combination of possible classes? Take for example the amd automounter''s configuration file, which on Debian is found at /etc/am-utils/amd.conf. This is an INI style file which looks like: [fsname1] param1=foo param2=bar [fsname2] param1=baz param2=quag In my case I have one class of machines

I just updated to 0.22.2 and am running into a strange issue. I''m starting puppetmaster, and seeing this in my error log: err: /puppetconfig/reporting/File[/Library/Puppet/Generated/Server/var/reports]/ensure: change from absent to directory failed: Cannot create /Library/Puppet/Generated/Server/var/reports; parent directory /Library/Puppet/Generated/Server/var does not exist err: /puppetconfig/metrics/File[/Library/Puppet/Generated...

We haven''t been able to use mongrel for testing yet, but in order not to waste time, we did some performance testing with 1, 2 and 4 puppetmasterd/webrick processes. Attached is an HTML page (ripped from our wiki - not pretty, but reasonably readable) which describes the method and results. If someone feels like making some nice graphs, that would be great. If not, I''ll try to

I''ve got about 40 linux/aix machines that I''d like assimilate into config management with puppet. I''ve been reading lots of docs, recipes and best practices. I''m wondering if there''s a guide somewhere that lays out the most efficient way to spread the use of puppet across a quantity of installed machines. I''d like to do first things first,

Hi- Recently starting using puppet while migrating an existing messy group of systems to some nice new hardware. Things are going incredibly well, and puppet''s functioning great. Have a bit of a headache. I''d like to keep myself from duplicating lots of included classes. Lets say I have this (snippet of a) class: class dbserver { file { "/etc/my_${db}.cnf":

...er.run err: Could not call puppetrunner.run: #<RuntimeError: HTTP-Error: 500 Internal Server Error > Host hostname failed: HTTP-Error: 500 Internal Server Error hostname finished with exit code 2 Failed: hostname Puppetd: debug: Parsing /etc/puppet/puppet.conf info: Loading fact drbd debug: /puppetconfig/main/File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] ... debug: Stored state in 0.03 seconds notice: Finished configuration run in 1.43 seconds debug: Creating default schedules notice: Denying unauthenticated client puppetmaster(10.17.4.5) access to puppetrunner.run I have this in...

This has been a much-requested feature, and is now a reality (in svn trunk): There is a new option, --ignoreimport, that will (surprisingly) ignore import statements. This is really only useful when using -- parseonly in a commit hook, and note that you''ll have to add the option to --parseonly, none of the puppet executables will add it for you. You should be able to