Issue #21214 has been updated by Charlie Sharpsteen. Status changed from Unreviewed to Needs More Information Assignee set to Mohit Chawla
Hi Mohit, Could you provide a minimal example of a report processor that isn't logging correctly? This will help us diagnose the problem. ---------------------------------------- Bug #21214: Logging is broken unless --debug enabled https://projects.puppetlabs.com/issues/21214#change-92974 * Author: Mohit Chawla * Status: Needs More Information * Priority: Normal * Assignee: Mohit Chawla * Category: * Target version: * Affected Puppet version: 2.7.20 * Keywords: logs, logging * Branch: ---------------------------------------- I was able to reproduce this behaviour on Puppet 2.7.20 on Ubuntu Precise 32 bit and CentOS 6.4 64 bit. If I use Puppet.info or Puppet.notice or Puppet.err statements in puppet code, specifically tested from report processors code, they are not logged until I enable --debug in puppet master startup options. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
