(puppet 3.1.1, hiera 1.2.1, redhat 6.x) My puppetmaster is filling up it''s logs filesystem every other day because of hiera debug logging that I cannot seem to get rid of. I have a pretty large hierarchy (18 levels) and about 30 modules that I deploy out to 1900 servers. Every time I have an agent run the master logs thousands of lines such as: Jul 31 12:55:21 rv-mg-xppm-08 puppet-master[17966]: (Scope(Class[Samba::Params])) Could not look up qualified variable ''data::osfamily/Solaris/10_u8/samba::samba::params::service''; class data::osfamily/Solaris/10_u8/samba::samba::params could not be found Basically one for every permutation of module and hierarchy level where I don''t define values for that module. This comes out to thousands and thousands of lines a minute. According to the hiera docs, I should be able to put ":logging: noop" in the /etc/hiera.yaml file but then puppet automatically sets it to "puppet" no matter what I put. Is there some way I can shut down this logging?? Right now I have had to stop ALL puppet master logging by changing the rack configuration (putting "--logdest /dev/null" in my config.ru file) Thanks Bill -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Hi all, I''m seeing exactly the same issue. Is there some config setting that can prevent this? I''d rather not just redirect all master logging to /dev/null. This is with Puppet 3.3.0 and Hiera 1.2.1 on RHEL6. J On Wednesday, 31 July 2013 18:50:19 UTC+1, Bill Sirinek wrote:> > > (puppet 3.1.1, hiera 1.2.1, redhat 6.x) > > My puppetmaster is filling up it''s logs filesystem every other day because > of hiera debug logging that I cannot seem to get rid of. I have a pretty > large hierarchy (18 levels) and about 30 modules that I deploy out to 1900 > servers. > > Every time I have an agent run the master logs thousands of lines such as: > > Jul 31 12:55:21 rv-mg-xppm-08 puppet-master[17966]: (Scope(Class[Samba::Params])) Could not look up qualified variable ''data::osfamily/Solaris/10_u8/samba::samba::params::service''; class data::osfamily/Solaris/10_u8/samba::samba::params could not be found > > Basically one for every permutation of module and hierarchy level where I don''t define values for that module. This comes out to thousands and thousands of lines a minute. > > According to the hiera docs, I should be able to put ":logging: noop" in the /etc/hiera.yaml file but then puppet automatically sets it to "puppet" no matter what I put. Is there some way I can shut down this logging?? > > Right now I have had to stop ALL puppet master logging by changing the rack configuration (putting "--logdest /dev/null" in my config.ru file) > > Thanks > > Bill > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
This is amusing to me, because I spent an hour or so the other day trying to turn hiera logging *on*. If you are using a syslog facility, the hiera debug stuff does not seem to go to the log (actually gets logged at level :info, rather than :debug). I had to add the --logdest option in rack to have it log directly to a file to see it. Maybe if you use syslog it will help? - Chad On Fri, Sep 27, 2013 at 11:16 AM, jamese <james.eckersall@gmail.com> wrote:> Hi all, > > I''m seeing exactly the same issue. Is there some config setting that can > prevent this? I''d rather not just redirect all master logging to /dev/null. > This is with Puppet 3.3.0 and Hiera 1.2.1 on RHEL6. > > J > > > On Wednesday, 31 July 2013 18:50:19 UTC+1, Bill Sirinek wrote: >> >> >> (puppet 3.1.1, hiera 1.2.1, redhat 6.x) >> >> My puppetmaster is filling up it''s logs filesystem every other day because >> of hiera debug logging that I cannot seem to get rid of. I have a pretty >> large hierarchy (18 levels) and about 30 modules that I deploy out to 1900 >> servers. >> >> Every time I have an agent run the master logs thousands of lines such as: >> >> Jul 31 12:55:21 rv-mg-xppm-08 puppet-master[17966]: >> (Scope(Class[Samba::Params])) Could not look up qualified variable >> ''data::osfamily/Solaris/10_u8/samba::samba::params::service''; class >> data::osfamily/Solaris/10_u8/samba::samba::params could not be found >> >> >> Basically one for every permutation of module and hierarchy level where I >> don''t define values for that module. This comes out to thousands and >> thousands of lines a minute. >> >> >> According to the hiera docs, I should be able to put ":logging: noop" in >> the /etc/hiera.yaml file but then puppet automatically sets it to "puppet" >> no matter what I put. Is there some way I can shut down this logging?? >> >> >> Right now I have had to stop ALL puppet master logging by changing the >> rack configuration (putting "--logdest /dev/null" in my config.ru file) >> >> Thanks >> >> >> Bill >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out.-- Chad M. Huneycutt -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.