[Resolved]Re: freeradius down every Sun Dec 30 06:50:40 2012 : Error: ASSERT FAILED modcall.c[106]: (p->type > MOD_SINGLE) && (p->type <= MOD_POLICY)

2012-12-30 Thread EasyHorpak.com

On 30/12/2555 13:47, Fajar A. Nugraha wrote:

On Sun, Dec 30, 2012 at 9:41 AM, 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 
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



Dear Fajar

I have check in file /etc/logrotate.d/freeradius
it 's show
/var/log/freeradius/*.log {
weekly
rotate 52
compress
delaycompress
notifempty
missingok
postrotate
/etc/init.d/freeradius reload > /dev/null
endscript
}

so when I try on /etc/init.d/freeradius reload
freeradius is stopped
so I change to /etc/init.d/freeradius restart
everything works fine

Thank you so much for your advice.


Regards
Chuan Chudabut
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Freeradius Attribute For HotSpot Users

2012-12-30 Thread Alan Buxey
Use expiration . Once a user has logged in for the first time then set the 
expiration for that account to the required valueor set it when the counter 
is reached. Et voila, next time they try to login they can't (then you can do 
fancy extra stuff like telling them that their account has expired on the login 
window etc)


alan

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: freeradius down every Sun Dec 30 06:50:40 2012 : Error: ASSERT FAILED modcall.c[106]: (p->type > MOD_SINGLE) && (p->type <= MOD_POLICY)

2012-12-30 Thread Alan Buxey
This fails without fail every Sunday? In that case check what happens... eg if 
that HUP'ING of the freeradius is a weekly crontab then investigate what else 
is going on at that time ...eg there appear to be mysql errors - ate you using 
mysql? If so, its not good having errors with that module (and can be the cause 
if the problem...) I wouldn't say just stop that jobit has a purpose...but 
see if you are also eg dealing with mysql logrotating at the same time and if 
you are, don't.

I would advise doing a restart of the daemon rather than a HUP and contact your 
distro maintainers to get latest version. 2.1.10 is really really old.

alan

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Freeradius Attribute For HotSpot Users

2012-12-30 Thread Prabhpal S. Mavi

Dear List Members,

i have working setup of FreeRadius 2x (freeradius-2.1.12-4.el6_3.x86_64)
including "rlm_sqlcounter" (Max-Daily-Session). User are logged off
alright when "Max Session Timeout" is reached. But users can re login to
gain access.

The username and passwords are for hotspot. We do not want the username
and password to work again once it has been used.

For example: prepaid voucher (MySQL username & password) has 1 hour
access. User should be able to use sum of one hour, either continuously
once they are logged in or in parts (30min today & 30min tomorrow so on)
username &
password must never work for more than 1 hour to access our network.

i am bit confuse attribute to use, i would grateful if someone can advice
the correct attribute to use for the purpose.


Thanks





-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html