Some errors not captured in Module-Failure-Message

[Alan DeKok]

On Jan 9, 2017, at 10:34 AM, Adam Bishop <Adam.Bishop at jisc.ac.uk> wrote:
> 
> I have a fairly standard line log stanza, which records module-failure-message:
> 
>  ... MODULE_MESSAGE=%{%{%{request:Module-Failure-Message}:-%{session-state:Module-Failure-Message}}:-NONE} ...
> 
> There are some failures it does not record. For example (taken from radius.log):
>    Tue Jan  3 11:16:20 2017 : Info: (125679) eap_peap:   The users session was previously rejected: returning reject (again.)
>    Mon Jan  9 10:06:53 2017 : Error: rlm_eap (EAP): No EAP session matching state 0xe679227be27f3b1e
>    Mon Jan  9 10:03:19 2017 : ERROR: (165330) eap: ERROR: Malformed EAP Message: Malformed EAP packet.  Length in packet header does not match actual length
> 
> I can correlate the entries by time manually, but this makes things rather tedious; is there any way I can capture these in using linelog?

  Submit a patch to make EAP / PEAP use Module-Failure-Message. :)

  Alan DeKok.