Issue #9258 has been reported by Ronald van Zantvoort.

----------------------------------------
Bug #9258: Puppet Master as Rack application ignores (at least) syslogfacility
https://projects.puppetlabs.com/issues/9258

Author: Ronald van Zantvoort
Status: Unreviewed
Priority: Normal
Assignee: 
Category: logging
Target version: 
Affected Puppet version: 2.7.3
Keywords: syslogfacility,rack,passenger
Branch: 


Attempting to define a syslogfacility in the config file (under `[main]` or 
`[master]`, makes no difference) or in `ARGV` in `rack/config.ru` when running 
Puppet as Rack app through Passenger will not apply the setting, and it will 
stubbornly log with the default settings to syslog.

This can be traced back to the fact that both `daemon.rb` and 
`network/server.rb` (during `daemonize`) call `Puppet::Util::Log.reopen`, but 
when using Rack, `network/http/rack.rb` will be used, which never does.

**DISCLAIMER: I ain't no Ruby dev!**

So in my case, this is quite possibly an unacceptable ugly hack, I dunno ;-), I 
simply patched @network/http/rack.rb@:

<pre>
  def initialize(args)
+    Puppet::Util::Log.reopen
    raise ArgumentError, ":protocols must be specified." if !args[:protocols] 
or args[:protocols].empty?
    protocols = args[:protocols]
</pre>

and it started responding to the config option.



-- 
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to