>  Hmm... that's not good.  I've tested it with that packet, and I
>don't see the problem.  So there's something else going wrong, too.
>
>  Can you provide a backtrace in gdb?  See doc/bugs
>
>  Alan DeKok.

Hi Alan,
 
Below is the backtrace, hope it's useful.
 
  modcall[accounting]: module "sql" returns ok for request 0
modcall: group accounting returns ok for request 0
Sending Accounting-Request of id 0 to 203.xxx.xxx.6:1646
        User-Name = "dapw"
        Acct-Status-Type = Stop
        Acct-Session-Id = "1086884216.23.11198"
        Acct-Session-Time = 2393
        NAS-Identifier = "ap-1-wlg"
        NAS-IP-Address = 203.xxx.xxx.3
        NAS-Port-Type = Virtual
        Service-Type = Framed-User
        Framed-IP-Address = 203.xxx.xxx.34
        Acct-Tunnel-Connection = "1a0020e7h"
        Called-Station-Id = "01195486745623"
        Calling-Station-Id = "42368475"
        Event-Timestamp = "Jun 13 2004 07:09:50 NZST"
        Acct-Input-Octets = 326128
        Acct-Output-Octets = 6536730
        Acct-Input-Packets = 5069
        Acct-Output-Packets = 5177
        Acct-Input-Gigawords = 0
        Acct-Output-Gigawords = 0
        Acct-Terminate-Cause = User-Request
        Acct-Tunnel-Packets-Lost = 0
        Acct-Delay-Time = 0
        Proxy-State = 0x313637
Thread 1 waiting to be assigned a request
rad_recv: Accounting-Response packet from host 203.xxx.xxx.6:1646, id=0,
length=25
Assertion failed in request_list.c, line 213
 
Program received signal SIGABRT, Aborted.
[Switching to Thread 1024 (LWP 29056)]
0x4011e781 in kill () from /lib/libc.so.6
(gdb) bt
#0  0x4011e781 in kill () from /lib/libc.so.6
#1  0x400e9e5e in pthread_kill () from /lib/libpthread.so.0
#2  0x400ea339 in raise () from /lib/libpthread.so.0
#3  0x4011fbe1 in abort () from /lib/libc.so.6
#4  0x0804f6e0 in request_alloc () at util.c:331
#5  0x0805ab04 in proxy_cmp (one=0xbfffe8a8, two=0x81720f0) at
request_list.c:213
#6  0x400538bb in rbtree_find (tree=0x816f618, Data=0xbfffe8a8) at
rbtree.c:432
#7  0x0805b500 in rl_find_proxy (packet=0x8177190) at request_list.c:844
#8  0x0804cc29 in proxy_ok (packet=0x8177190) at radiusd.c:599
#9  0x0804cda5 in request_ok (packet=0x8177190, secret=0x0,
listener=0x8159bb8) at radiusd.c:721
#10 0x0804da30 in main (argc=2, argv=0xbffffb74) at radiusd.c:1434

We running Debian Woody (Stable), we are using freeRadius 0.9.1 in
production with the ldap (Authorization), kerberos (Authentication), sql
(Simultaneous-Use and Accounting) modules plus we forward on accounting
records to another server (freeRADIUS v0.9.1) for logging via the detail
module.
 
Regards
Allister Maguire


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

Reply via email to