Your message dated Tue, 25 Oct 2016 19:51:11 +0200
with message-id
<ca+fnjvborcchg7ucroeu-0qjsc0yllmj-rh1p9y0wzi9nht...@mail.gmail.com>
and subject line freeradius: logrotate causes mschap module to fail
has caused the Debian Bug report #709086,
regarding freeradius: logrotate causes mschap module to fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
709086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709086
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: freeradius
Version: 2.1.12+dfsg-1.2
Severity: important
Tags: upstream
Dear Maintainer,
I just spent a few minutes looking at an issue we've been having with a debian-
based FreeRADIUS server we're running.
After some closer investigation, it turned out that the weekly logrotate was
causing the mschap modules to fail in FreeRADIUS.
This effectively breaks authentication for us, as the mschap modules are what
we rely on to make the wireless 802.1x authentication work.
Digging deeper, I found this mailing list post on lists.freeradius.org
(http://lists.freeradius.org/pipermail/freeradius-users/2012-April/060090.html)
which details the issue exactly.
Alan DeKok appears to have fixed this in the source tree as of 2012-04-13,
however, the fix hasn't made it into Debian (squeeze or wheezy).
Could you please consider either making the logrotate command restart
freeradius, not kill -HUP it, or bring commit
d3504e1766ae965c2983f6ea4c8aa17bb840f4a4 in as a patch?
Link to commit in original source is: https://github.com/FreeRADIUS/freeradius-
server/commit/d3504e1766ae965c2983f6ea4c8aa17bb840f4a4
Either of this will fix - and I don't know which one you'd prefer to take. As
it stands, I'm adding a cron job to restart FreeRADIUS at 06:40 each Sunday
morning to ensure it comes back up again after a logrotate.
Thanks in advance.
Regards,
Chris Malton
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Fixed in 2.2.5 as in previous (not spam) comment.
--- End Message ---
