[JIRA] Commented: (SSPCPP-409) Shibboleth2.xml - undefined InProcess/OutOfProcess means no shibd.log/native.log
Scott Cantor (JIRA)
noreply at shibboleth.net
Tue Nov 29 20:06:25 GMT 2011
[ https://issues.shibboleth.net/jira/browse/SSPCPP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722#comment-13722 ]
Scott Cantor commented on SSPCPP-409:
-------------------------------------
The intent was to default the settings. If that's not what it's doing I'm very surprised nobody mentioned it until now.
> Shibboleth2.xml - undefined InProcess/OutOfProcess means no shibd.log/native.log
> --------------------------------------------------------------------------------
>
> Key: SSPCPP-409
> URL: https://issues.shibboleth.net/jira/browse/SSPCPP-409
> Project: Shibboleth SP - C++
> Issue Type: Bug
> Components: Configuration, Logging
> Affects Versions: 2.4.3
> Environment: RedHat 5, x86_64
> Reporter: mthornton at idp.protectnetwork.org
> Assignee: Scott Cantor
> Priority: Minor
>
> Upgraded release and configuration from 2.3.1 to 2.4.3
> Base shibboleth2.xml for 2.3.1 includes fully-qualified InProcess, OutOfProcess XML elements defining default behaviour. Base shibboleth2.xml for 2.4.3 does not define them at all.
> Side-effect: default configuration on 2.4.3 does no logging to shibd.log or native.log, need to define, at a minimum, empty <InProcess /> <OutOfProcess /> elements to turn on logging.
> Spent a fair bit of time trying to figure out why only syslog.logger and console.logger were being used, but not native.logger and shibd.logger, including permissions checks, etc....
> Possible solutions:
> a) logging via shibd.log and native.log turned on by default AND/OR
> b) provide empty <InProcess /> and <OutOfProcess /> definitions in default configuration, with or without logger attribute
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list