I have an input file for radmin with the following content: debug file /var/log/radius/nw2.log debug condition '(NAS-IP-Address == "172.31.110.147") || (NAS-IP-Address == "172.31.110.149") || (NAS-IP-Address == "149.246.185.169")' When those commands have been executed and some debugging shows up int the logfile, I want to switch to another log. changing the radmin input file to debug file /var/log/radius/nw3.log debug condition '(NAS-IP-Address == "172.31.110.147") || (NAS-IP-Address == "172.31.110.149") || (NAS-IP-Address == "149.246.185.169")' and executing the commands, freeradius in the actual 2.1.1 version dies. This is, what gdb show up: Loaded symbols for /usr/lib64/freeradius/rlm_sql_log.so 0x00002b091e323562 in ?? () from /lib64/libc.so.6 (gdb) cont Continuing. Program received signal SIGABRT, Aborted. [Switching to Thread 47318162851936 (LWP 2820)] 0x00002b091e299b95 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00002b091e299b95 in raise () from /lib64/libc.so.6 #1 0x00002b091e29af90 in abort () from /lib64/libc.so.6 #2 0x00002b091e2d035b in __libc_message () from /lib64/libc.so.6 #3 0x00002b091e2d534e in malloc_printerr () from /lib64/libc.so.6 #4 0x00002b091e2d695c in free () from /lib64/libc.so.6 #5 0x000000000040e748 in command_debug_condition (listener=<value optimized out>, argc=2820, argv=0x6) at command.c:718 #6 0x000000000040ee01 in command_domain_recv (listener=0x726dc0, pfun=<value optimized out>, prequest=<value optimized out>) at command.c:1680 #7 0x000000000041ef10 in event_socket_handler (xel=<value optimized out>, fd=<value optimized out>, ctx=<value optimized out>) at event.c:2666 #8 0x00002b091d7169c0 in fr_event_loop (el=0x70e980) at event.c:400 #9 0x0000000000418bb1 in main (argc=<value optimized out>, argv=0xe) at radiusd.c:394 Norbert Wegener
Norbert Wegener wrote:
I have an input file for radmin with the following content:
debug file /var/log/radius/nw2.log debug condition '(NAS-IP-Address == "172.31.110.147") || (NAS-IP-Address == "172.31.110.149") || (NAS-IP-Address == "149.246.185.169")'
Hmmm... that should work.
When those commands have been executed and some debugging shows up int the logfile, I want to switch to another log. changing the radmin input file to
debug file /var/log/radius/nw3.log debug condition '(NAS-IP-Address == "172.31.110.147") || (NAS-IP-Address == "172.31.110.149") || (NAS-IP-Address == "149.246.185.169")' and executing the commands, freeradius in the actual 2.1.1 version dies.
OK. It may be some race condition in the server core. I'll take a look.
Program received signal SIGABRT, Aborted. [Switching to Thread 47318162851936 (LWP 2820)] 0x00002b091e299b95 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00002b091e299b95 in raise () from /lib64/libc.so.6 #1 0x00002b091e29af90 in abort () from /lib64/libc.so.6 #2 0x00002b091e2d035b in __libc_message () from /lib64/libc.so.6 #3 0x00002b091e2d534e in malloc_printerr () from /lib64/libc.so.6 #4 0x00002b091e2d695c in free () from /lib64/libc.so.6
Yes... the memory was already free'd, most likely. I don't think git head ("stable" tree) has any changes in this area. Alan DeKok.
Norbert Wegener wrote:
When those commands have been executed and some debugging shows up int the logfile, I want to switch to another log. changing the radmin input file to
debug file /var/log/radius/nw3.log debug condition '(NAS-IP-Address == "172.31.110.147") || (NAS-IP-Address == "172.31.110.149") || (NAS-IP-Address == "149.246.185.169")' and executing the commands, freeradius in the actual 2.1.1 version dies.
OK. I've committed a fix, and pushed it to the "master" and "stable" trees. Alan DeKok.
Hello, Using the latest stable git release, I've noticed the following. radmin> debug file /usr/home/tfa/radius.log radmin> debug condition '(User-Name == "bob")'
At that time the file radius.log begins to be written by radiusd, but it seems to log each request without taking care about the condition ?
Then while doing radmin> debug condition radiusd dies Am I using the radmin command properly ? (the server is a little bit loaded about 5 requests/seconds). Thomas Alan DeKok wrote:
Norbert Wegener wrote:
When those commands have been executed and some debugging shows up int the logfile, I want to switch to another log. changing the radmin input file to
debug file /var/log/radius/nw3.log debug condition '(NAS-IP-Address == "172.31.110.147") || (NAS-IP-Address == "172.31.110.149") || (NAS-IP-Address == "149.246.185.169")' and executing the commands, freeradius in the actual 2.1.1 version dies.
OK. I've committed a fix, and pushed it to the "master" and "stable" trees.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Thomas Fagart wrote:
Using the latest stable git release, I've noticed the following.
radmin> debug file /usr/home/tfa/radius.log radmin> debug condition '(User-Name == "bob")'
At that time the file radius.log begins to be written by radiusd, but it seems to log each request without taking care about the condition ?
Hmm... I'm not seeing that.
Then while doing
radmin> debug condition
radiusd dies
Please see doc/bugs. There was an issue with "debug condition", but it was fixed about 3 weeks ago. Please ensure you're using the version with the fix (see "git log" for details). Alan DeKok.
Hello, I am trying to get statistics information from the freeradius 2.1.1. As I understand the attribute "FreeRADIUS-Statistics-Type" represents the type of information wich will given back by the server. The value ist bit oriented. bit 0 = 1 --> give me Auth stats bit 1 = 1 --> give me Acc stats bit 0 = 1 and bit 1= 1 --> give me Auth stats and Acc stats ... bit 5 = 1--> give me client stats (according the to bit 1 and bit 2) IMHO bit 1 =1 and bit 2= 1 and bit 5 =1 --> should give me Auth stats and Acc stats from a specified client like this hostname> echo "Message-Authenticator = 0x00, FreeRADIUS-Statistics-Type = 35, FreeRADIUS-Stats-Client-IP-Address = 10.0.8.2" |/opt/radius/bin/radclient localhost:18120 status adminsecret FreeRADIUS-Stats-Client-IP-Address = 10.0.8.2 FreeRADIUS-Total-Access-Requests = 55 FreeRADIUS-Total-Access-Accepts = 54 FreeRADIUS-Total-Access-Rejects = 1 FreeRADIUS-Total-Access-Challenges = 0 FreeRADIUS-Total-Auth-Responses = 0 FreeRADIUS-Total-Auth-Duplicate-Requests = 0 FreeRADIUS-Total-Auth-Malformed-Requests = 0 FreeRADIUS-Total-Auth-Invalid-Requests = 0 FreeRADIUS-Total-Auth-Dropped-Requests = 0 FreeRADIUS-Total-Auth-Unknown-Types = 0 FreeRADIUS-Total-Proxy-Accounting-Requests = 108 FreeRADIUS-Total-Proxy-Accounting-Responses = 108 FreeRADIUS-Total-Proxy-Acct-Duplicate-Requests = 0 FreeRADIUS-Total-Proxy-Acct-Malformed-Requests = 0 FreeRADIUS-Total-Proxy-Acct-Invalid-Requests = 0 FreeRADIUS-Total-Proxy-Acct-Dropped-Requests = 0 FreeRADIUS-Total-Proxy-Acct-Unknown-Types = 0 (i wonder me why the Acc data are marked as FreeRADIUS-Total-Proxy -Accounting-Requests) but i get the full server stats too. FreeRADIUS-Total-Access-Requests = 56 FreeRADIUS-Total-Access-Accepts = 118 FreeRADIUS-Total-Access-Rejects = 1 FreeRADIUS-Total-Access-Challenges = 0 FreeRADIUS-Total-Auth-Responses = 119 FreeRADIUS-Total-Auth-Duplicate-Requests = 0 FreeRADIUS-Total-Auth-Malformed-Requests = 0 FreeRADIUS-Total-Auth-Invalid-Requests = 0 FreeRADIUS-Total-Auth-Dropped-Requests = 0 FreeRADIUS-Total-Auth-Unknown-Types = 0 FreeRADIUS-Total-Accounting-Requests = 110 FreeRADIUS-Total-Accounting-Responses = 110 FreeRADIUS-Total-Acct-Duplicate-Requests = 0 FreeRADIUS-Total-Acct-Malformed-Requests = 0 FreeRADIUS-Total-Acct-Invalid-Requests = 0 FreeRADIUS-Total-Acct-Dropped-Requests = 0 FreeRADIUS-Total-Acct-Unknown-Types = 0 FreeRADIUS-Stats-Client-IP-Address = 10.0.8.2 FreeRADIUS-Total-Access-Requests = 55 FreeRADIUS-Total-Access-Accepts = 54 FreeRADIUS-Total-Access-Rejects = 1 FreeRADIUS-Total-Access-Challenges = 0 FreeRADIUS-Total-Auth-Responses = 0 FreeRADIUS-Total-Auth-Duplicate-Requests = 0 FreeRADIUS-Total-Auth-Malformed-Requests = 0 FreeRADIUS-Total-Auth-Invalid-Requests = 0 FreeRADIUS-Total-Auth-Dropped-Requests = 0 FreeRADIUS-Total-Auth-Unknown-Types = 0 FreeRADIUS-Total-Proxy-Accounting-Requests = 108 FreeRADIUS-Total-Proxy-Accounting-Responses = 108 FreeRADIUS-Total-Proxy-Acct-Duplicate-Requests = 0 FreeRADIUS-Total-Proxy-Acct-Malformed-Requests = 0 FreeRADIUS-Total-Proxy-Acct-Invalid-Requests = 0 FreeRADIUS-Total-Proxy-Acct-Dropped-Requests = 0 FreeRADIUS-Total-Proxy-Acct-Unknown-Types = 0 Is this a bug or a feature. Is my understanding wrong ? What can i do get only the client specific stats ? www.biotronik.com BIOTRONIK GmbH & Co. KG Woermannkehre 1, 12359 Berlin, Germany Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501 Vertreten durch ihre Komplementärin: BIOTRONIK Mess- und Therapiegeräte GmbH Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 2918 Geschäftsführer: Dr. Max Schaldach, Christoph Böhmer, Dr. Werner Braun, Dr. Lothar Krings This email and the information it contains including attachments are confidential and meant only for use by the intended recipient(s); disclosure or copying is strictly prohibited. If you are not addressed, but in the possession of this email, please notify the sender immediately and delete the document.
thoralf.freitag@biotronik.com wrote:
(i wonder me why the Acc data are marked as FreeRADIUS-Total-*Proxy*-Accounting-Requests)
It's a bug. I'll fix it in the next release. The accounting stats *are* the client statistics. They're just put into the wrong attribute. Alan DeKok.
participants (4)
-
Alan DeKok -
Norbert Wegener -
Thomas Fagart -
thoralf.freitag@biotronik.com