search for: last_run_report

...uthenticated host, an attacker on that host can send a specially crafted Delete request that can cause an arbitrary file deletion on the Puppet master, potentially causing a denial of service attack. Note that this vulnerability does *not* exist in Puppet as configured by default. CVE-2012-3866 last_run_report.yaml is world readable (medium) The most recent Puppet run report is stored on the Puppet master with world-readable permissions. The report file contains the context diffs of any changes to configuration on an agent, which may contain sensitive information that an attacker can then access. The...

...ensure=>:file, :backup=>false, :owner=>"root", :mode=>"640", :path=>"/var/lib/puppet/state/resources.txt", :loglevel=>:debug}'' Debug: Using settings: adding file resource ''lastrunreport'': ''File[/var/lib/puppet/state/last_run_report.yaml]{:links=>:follow, :ensure=>:file, :backup=>false, :mode=>"640", :path=>"/var/lib/puppet/state/last_run_report.yaml", :loglevel=>:debug}'' Debug: Using settings: adding file resource ''confdir'': ''File[/etc/puppet]{:links=&g...

...gt;false, :owner=>"root", :mode=>"640", >> :path=>"/var/lib/puppet/state/resources.txt", :loglevel=>:debug}'' >> Debug: Using settings: adding file resource ''lastrunreport'': >> ''File[/var/lib/puppet/state/last_run_report.yaml]{:links=>:follow, >> :ensure=>:file, :backup=>false, :mode=>"640", >> :path=>"/var/lib/puppet/state/last_run_report.yaml", :loglevel=>:debug}'' >> Debug: Using settings: adding file resource ''confdir'': >> &...

...up=>false, :path=>"C:/Documents and Settings/All Users/Application Data/PuppetLabs/puppet/etc"}'' Debug: Using settings: adding file resource ''lastrunreport'': ''File[C:/Documents and Settings/All Users/Application Data/PuppetLabs/puppet/var/state/last_run_report.yaml]{:loglevel=>:debug, :ensure=>:file, :links=>:follow, :mode=>"640", :backup=>false, :path=>"C:/Documents and Settings/All Users/Application Data/PuppetLabs/puppet/var/state/last_run_report.yaml"}'' Debug: Using settings: adding file resource '...

...File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys/vusion-production.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/ssl/certs/vusion-production.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] *debug: /File[/var/lib/puppet/ssl/private_keys/vusion-production.pem]: Autorequiring File[/va...

...ers/zach/.puppet/var/state/last_run_summary.yaml", :mode=>"644", :ensure=>:file, :loglevel=>:debug, :links=>:follow, :backup=>false}'' Debug: Using settings: adding file resource ''lastrunreport'': ''File[/Users/zach/.puppet/var/state/last_run_report.yaml]{:path=>"/Users/zach/.puppet/var/state/last_run_report.yaml", :mode=>"640", :ensure=>:file, :loglevel=>:debug, :links=>:follow, :backup=>false}'' Debug: Using settings: adding file resource ''graphdir'': ''File[/Users/zac...

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

...r/lib/puppet/state] debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]: Autorequiring Fi...

Hi, i recently updated our windows 2008 r2 servers to puppet 3.3.0 . Im getting the following error* (only on our exchange 2010 db servers)*ever since: LevelMessageSourceFileLineTimeerrCould not retrieve local facts: undefined method `gsub'' for nil:NilClassPuppet13.09.2013 15:12 CESTerrFailed to apply catalog: Could not retrieve local facts: undefined method `gsub'' for

...] debug: /File[/etc/puppet/ssl/certs/puppet.domain.com.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/ssl/private_keys/puppet.domain.com.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/classes.txt]: Autorequir...

...g File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet...

...g File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/state/graphs]:...

For some reason I am unable to run "dry runs" of the puppet client on my puppetmaster server. Running puppetd with the --test, --noop and verbose / debug flags results in nothing for about a minute or two then this output... $ time puppetd --test --noop -v err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''

Does anyone have some examples of using this create_resources function, https://github.com/puppetlabs/puppetlabs-create_resources, ? Based on the README example I can''t figure out exactly how to change from using defines to using this function. Maybe I misunderstand the purpose of create_resources...is it to replace defines, or is it to allow ENCs (for example) to use a define? Below

my base/default includes this ntp manifest # cat modules/ntp/manifests/ntp.pp # ntp.pp class ntp { case $operatingsystem { centos, redhat: { $service_name = ''ntpd'' $conf_file = ''ntp.conf.el'' } debian, ubuntu: { $service_name = ''ntp'' $conf_file = ''ntp.conf.debian'' } } package {

...uests. It''s a separate server because it cannot # and does not need to horizontally scale. # The default value is ''$server''. ca_server = puppet # Where puppet agent stores the last run report in yaml format. # The default value is ''$statedir/last_run_report.yaml''. lastrunreport = /var/lib/puppet/state/last_run_report.yaml # The preferred means of serializing # ruby instances for passing over the wire. This won''t guarantee that all # instances will be serialized using this method, since not all classes # can be g...

whenever i run a test from client it finishes sucessfully but client is not getting any configuration changes from server [root@PROXY-02 tmp]# puppetd --noop --test notice: Ignoring --listen on onetime run info: Caching catalog for proxy-02.carnation.in info: Applying configuration version ''1327091881'' notice: Finished catalog run in 0.02 seconds [root@PROXY-03 modules]# puppet

...t/state/resources.txt]: Autorequiring File[/ var/lib/puppet/state] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/private_keys/node12.localdomain.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/classes.txt]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /Fil...

Greetings. I am trying to set up a test puppet server in my environment to evaluate windows clients. On the server side, I am using puppet 2.7.14 (from the repos). I''m using the 2.7.14 windows 64 bit on the client (windows 2008 R2). I have another puppetmaster already using "puppet" hostname in DNS (running a very old version of puppet - can''t upgrade yet for various