On 27/06/17 17:24, Matthew Vernon wrote:
> On 26/06/17 17:27, Alejandro Pérez Méndez wrote:
>>
>>
>> El 26/06/17 a las 18:04, Matthew Vernon escribió:
>>> Hi,
>>>
>>> On 23/06/17 19:26, Mark Donnelly wrote:
>>>
>>>> I haven’t looked, however, to see where we get the configuration for
>>>> the Shibboleth logging within mech_eap. Is it loaded off the
>>>> filesystem? Is it hard-coded within mech_eap? Is it not configured
>>>> anywhere, and therefore getting some set of defaults? Does anybody
>>>> happen to know?
>>> I don't know, sorry.
>> https://wiki.moonshot.ja.net/display/TR/Install+a+Trust+Router+on+Debian+7,
>> section 3.2.3,
>> indicates that you can tweak |/etc/shibboleth/console.logger|to control
>> how some aspects of Shib logging are handled. Is that what you were
>> looking for?
>
> I can't speak for Mark (who asked the original question), and I note
> that section is absent from the Debian 8 instructions, but...
>
> The Ubuntu Xenial and Debian 8 versions of
> /etc/shibboleth/console.logger are the same. So I tried that edit (i.e.
> 'log4j.rootCategory=NONE, console' rather than the WARN it's shipped
> with), and it seems to have resolved (worked around?) this issue(!) I
> suspect there's still a bug somewhere, though.
Alas, I spoke too soon. It behaved fine overnight, so this morning I
removed the various debug libraries I'd installed (and the debian
chroot), and restarted everything, and the bug has returned. I have no
explanation for this - I'm sure I wasn't still running the chrooted
Debian version.
Sorry for raising false hope.
Regards,
Matthew
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
|