Insufficient Space to Store Pair string
Hi All, I am probably doing something wrong but, we have a requirement to log all Input and output attributes following post auth. So we configured a linelog module and added %{pairs:&request:} & %{pairs:&reply:} Worked a treat with EAP-PEAP, however we enabled EAP-TLS and all the attributes from the certificate is causing some out of memory condition and get a error saying insufficient space to store pair string, needed 2390 bytes available 2048 bytes. Any other more efficient way of dealing with this so I can capture the entire value pair. Many Thanks Arnab
On Oct 8, 2017, at 6:10 PM, Arnab Roy <arnabroy@mail.com> wrote:
I am probably doing something wrong but, we have a requirement to log all Input and output attributes following post auth. So we configured a linelog module and added
%{pairs:&request:} & %{pairs:&reply:}
Worked a treat with EAP-PEAP, however we enabled EAP-TLS and all the attributes from the certificate is causing some out of memory condition and get a error saying insufficient space to store pair string, needed 2390 bytes available 2048 bytes.
The linelog module has a hard-coded buffer of 2K. If you need more, either edit the source, or change your requirements.
Any other more efficient way of dealing with this so I can capture the entire value pair.
Don't log EAP-Message. It's all encrypted SSL stuff, and has zero value to anyone. i.e. if your political requirements conflict with the technical limitations, reality should win. Alan DeKok.
I am probably doing something wrong but, we have a requirement to log all Input and output attributes following post auth. So we configured a linelog module and added
%{pairs:&request:} & %{pairs:&reply:}
Worked a treat with EAP-PEAP, however we enabled EAP-TLS and all the attributes from the certificate is causing some out of memory condition and get a error saying insufficient space to store pair string, needed 2390 bytes available 2048 bytes. The linelog module has a hard-coded buffer of 2K. If you need more, either edit the source, or change your requirements. Any other more efficient way of dealing with this so I can capture the entire value pair. Don't log EAP-Message. It's all encrypted SSL stuff, and has zero value to anyone. i.e. if your political requirements conflict with the technical limitations, reality should win. Alan DeKok.
Hi Alan, I was thinking the same "Don't log EAP-Message" , but not sure how I remove that attribute before logging , can I delete the EAP-Message attribute from linelog module somehow and log everything else. I think that will solve the problem. Many Thanks Arnab Sent: Monday, October 09, 2017 at 1:08 PM From: "Alan DeKok" <aland@deployingradius.com> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: Insufficient Space to Store Pair string On Oct 8, 2017, at 6:10 PM, Arnab Roy <arnabroy@mail.com> wrote: - List info/subscribe/unsubscribe? See [1]http://www.freeradius.org/list/users.html References 1. http://www.freeradius.org/list/users.html
On Oct 9, 2017, at 10:24 AM, Arnab Roy <arnabroy@mail.com> wrote:
I was thinking the same "Don't log EAP-Message" , but not sure how I remove that attribute before logging , can I delete the EAP-Message attribute from linelog module somehow and log everything else. I think that will solve the problem.
There's not really an easy way to do that unfortunately. The better solution is to just log the attributes you need. Or, if you want to log all of the attributes, use the detail file. Alan DeKok.
participants (2)
-
Alan DeKok -
Arnab Roy