On Sun, Dec 30, 2012 at 9:41 AM, EasyHorpak.com <i...@easyhorpak.com> wrote: > On 30/12/2555 09:12, EasyHorpak.com wrote: >> >> Dear all >> >> I found freeradius down every Sun Dec 30 06:50:40 2012 : Error: ASSERT >> FAILED modcall.c[106]: (p->type > MOD_SINGLE) && (p->type <= MOD_POLICY)
>> Sun Dec 30 06:50:40 2012 : Info: Received HUP signal. This looks like cron job rotating the log and sending HUP. The easiest workaround for you is to just disable that logrotate job (/etc/logrotate.d/freeradius, I think). >> Sun Dec 30 06:50:40 2012 : Info: Loaded virtual server <default> >> Sun Dec 30 06:50:40 2012 : Error: ASSERT FAILED modcall.c[106]: (p->type > >> MOD_SINGLE) && (p->type <= MOD_POLICY) Do you use fancy entries on policy.conf, perhaps? > More info about OS and freeradius version > > Debian x86_64 bit > > freeradius: FreeRADIUS Version 2.1.10, for host x86_64-pc-linux-gnu, built > on Sep 24 2012 at 17:58:57 In FR terms, this is old. If you're going to stick with old distro-provided versions, then file a bug report to the distro. I didn't get those errors in my environment, so you might also want to try one of these things: - try restoring policy.conf to the stock version. Just in case some changes you made broke it. - upgrade to the latest version, and see if the bug remains. See http://freeradius.org/, http://wiki.freeradius.org/building/Build#Building-Debian-packages, or https://launchpad.net/~freeradius/+archive/stable -- Fajar - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html