search for: livegam

...ssl directory on the client: [root@app03 puppet]# service puppet stop Stopping puppet: [ OK ] [root@app03 puppet]# rm -fR /var/lib/puppet/ssl [root@app03 puppet]# I then go and clean the certificate on the server. prov01 ~:# puppetca --clean app03.pax.livegamer.com notice: Revoked certificate with serial 114 notice: Removing file Puppet::SSL::Certificate app03.pax.livegamer.com at ''/var/lib/puppet/ssl/ca/signed/app03.pax.livegamer.com.pem'' notice: Removing file Puppet::SSL::Certificate app03.pax.livegamer.com at ''/var/lib/pupp...

...uby/1.8/puppet/application.rb:301:in `run'' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:398:in `exit_on_fail'' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:301:in `run'' /usr/sbin/puppetmasterd:4 err: Could not find default node or by name with ''app01.pax.livegamer.com, app01.pax.livegamer, app01.pax, app01'' on node app01.pax.livegamer.com -- 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, s...

I just upgraded puppet from 0.25.5 to 0.26, and I''m getting this: (/Stage[main]/Repo::Livegamer_software_base/Yumrepo[Livegamer-Software-Base]) Could not evaluate: File /etc/yum.conf does not contain a main section However, my /etc/yum.conf contains this. What''s wrong with that? Is puppet smoking crack? [main] cachedir=/var/cache/yum keepcache=0 debuglevel=2 logfile=/var/log/yum....

...ass { amodule::afunc: version => "1.0" } } /etc/puppet/modules/amodule/manifests/afunc.pp: class amodule::afunc ( $version ) { file { "/tmp/foo": ensure => directory; } } This causes the following error to be displayed on the client: Jul 30 03:48:45 s_sys@name01.pax.livegamer.com puppet-agent[15475]: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Syntax error at ''amodule::afunc''; expected ''}'' at /etc/puppet/manifests/nodes/pax/name01.pax.xxx.com.pp:9 on node name01.pax...

I don''t know what it is with puppet''s certificates, but once again, they are behaving strangely. Client is reporting: debug: Using cached certificate for auth01.fre.livegamer.com /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:166:in `certificate'' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:227:in `wait_for_cert'' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:194:in `setup_host'' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent...

All, I have --confdir=/etc/puppet/common in my /etc/init.d/puppetmaster and /etc/init.d/puppet files, vardir set to /var/lib/puppet in /etc/puppet/common/puppet.conf, and yet, every time I run puppetca it creates /etc/puppet/ssl. Anyone know why? Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email

I have this: class foo::foobar ($version) { } which is called like this: class facility::sanjose inherits facility::common { class { foo::foobar: version => "1.3.13" } } puppet complains with this on the client: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find parent resource type ''facility::sanjose'' of type hostclass in