Hi,

...

/usr/local/etc/raddb# radiusd -f ...and nothing happens any more, it just hangs.

radiusd -X not radiusd -x !

Thanks for the idea, but that does not seem to make a difference: segfault. The only clues it gives me are these two errors: Using deprecated naslist file. Support for this will go away soon. rlm_exec: Wait=yes but no output defined. Did you mean output=none? But hey, both doesn't sound that serious?! Any other ideas? Thank you in advance, Jan P.S.: Here the complete output: # radiusd -X Starting - reading configuration files ... reread_config: reading radiusd.conf Config: including file: /usr/local/etc/raddb/proxy.conf Config: including file: /usr/local/etc/raddb/clients.conf Config: including file: /usr/local/etc/raddb/snmp.conf Config: including file: /usr/local/etc/raddb/eap.conf Config: including file: /usr/local/etc/raddb/sql.conf main: prefix = "/usr/local" main: localstatedir = "/usr/local/var" main: logdir = "/usr/local/var/log/radius" main: libdir = "/usr/local/lib" main: radacctdir = "/usr/local/var/log/radius/radacct" main: hostname_lookups = no main: max_request_time = 30 main: cleanup_delay = 5 main: max_requests = 1024 main: delete_blocked_requests = 0 main: port = 0 main: allow_core_dumps = no main: log_stripped_names = no main: log_file = "/usr/local/var/log/radius/radius.log" main: log_auth = no main: log_auth_badpass = no main: log_auth_goodpass = no main: pidfile = "/usr/local/var/run/radiusd/radiusd.pid" main: user = "(null)" main: group = "(null)" main: usercollide = no main: lower_user = "no" main: lower_pass = "no" main: nospace_user = "no" main: nospace_pass = "no" main: checkrad = "/usr/local/sbin/checkrad" main: proxy_requests = yes proxy: retry_delay = 5 proxy: retry_count = 3 proxy: synchronous = no proxy: default_fallback = yes proxy: dead_time = 120 proxy: post_proxy_authorize = no proxy: wake_all_if_all_dead = no security: max_attributes = 200 security: reject_delay = 1 security: status_server = no main: debug_level = 0 read_config_files: reading dictionary read_config_files: reading naslist Using deprecated naslist file. Support for this will go away soon. read_config_files: reading clients read_config_files: reading realms radiusd: entering modules setup Module: Library search path is /usr/local/lib Module: Loaded exec exec: wait = yes exec: program = "(null)" exec: input_pairs = "request" exec: output_pairs = "(null)" exec: packet_type = "(null)" rlm_exec: Wait=yes but no output defined. Did you mean output=none? Module: Instantiated exec (exec) Segmentation fault

After the next login of course. The counter alters the session time field that is pass back to the NAS and hence will terminate the session based on that time. If you change it whilst the user is online the session variable cannot be passed back to the NAS to update that session time limit. Unless of course you are running your own kill scripts. -----Original Message----- From: freeradius-users-bounces+cory=cmi.net.au@lists.freeradius.org [mailto:freeradius-users-bounces+cory=cmi.net.au@lists.freeradius.org] On Behalf Of PD Sent: Wednesday, 7 March 2007 12:31 PM To: FreeRadius users mailing list Subject: 'bout rlm_sqlcounter Very interesting knowing about rlm_counter and the scripts made; such as noresetcounter, dailycounter, monthlycounter, etc. My question, if we do update the values of the above attributes (let say Max-All-Session attribute) while the user still online (on the session), will the update take effect directly or only effect untill the next login / session ? TIA PD - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html __________ NOD32 2086 (20070301) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com

Hi,

Using deprecated naslist file. Support for this will go away soon. rlm_exec: Wait=yes but no output defined. Did you mean output=none?

both not a problem. delete naslist file if you dont use it and edit radiusd.conf to change the exec stanza if you wish. looks like a module/library issue. can you try compiling without shared libraries? alan

Satish Patel wrote:

check process ID #ps aux | grep radiusd

root 17622 89.6 0.0 4388 2248 pts/1 R+ 02:38 0:02 radiusd I also found: # netstat -nlp udp 1580 0 0.0.0.0:1812 0.0.0.0:* 7579/radiusd udp 0 0 0.0.0.0:1813 0.0.0.0:* 7579/radiusd That Local IP 0.0.0.0 can't be a good sign, right?! Could it be that I'm wrong and the whole thing is not broken after all but running just fine only listening to a broken local IP? BUT: - why does using -X or -x break with a segfault? (could be a different problem) - invoking with or without -f just deliver an: Thu Mar 8 01:50:33 2007 : Info: Starting - reading configuration files ... and nothing more. Shouldn't it say something like "service running" and fork to background? - radtest just keeps repeating this request without getting an answer: # radtest steve testing localhost 10 testing123 Sending Access-Request of id 122 to 127.0.0.1 port 1812 User-Name = "steve" User-Password = "testing" NAS-IP-Address = 255.255.255.255 NAS-Port = 10 Shouldn't there be some sort of answer like "password ok" or so? (Could also be a problem of radtest) Could this be because of the "0.0.0.0"-adress? What do you think: Does it run correctly, just with a broken local IP config? What do you think about this? Perhaps the whole thing is actualy working and I just didn't realize. That would be quite embarrassing, wouldn't it? :-) Jan

Hi,

...

...

#ps aux | grep radiusd root 17622 89.6 0.0 4388 2248 pts/1 R+ 02:38 0:02 radiusd

# netstat -nlp udp 1580 0 0.0.0.0:1812 0.0.0.0:* 7579/radiusd udp 0 0 0.0.0.0:1813 0.0.0.0:* 7579/radiusd

That Local IP 0.0.0.0 can't be a good sign, right?!

No, that's fine. [...]

Thanks, didn't know that. But then I really not understand why it does not answer to any requests. Process is running but no responses to radiustest and no entries in the log. Problem ist it runs on UDP so I can't just try with telnet. Actually: /etc/services does define it should also run on 1812/TCP, and radiusd.conf says port = 0 so it really should do as /etc/services says, but it doesn't: no TCP. Little experiment: deleting the line radiusd 1812/udp in /etc/services and setting "port = 1812/tcp" in radiusd.conf and starting by giving definitely the right config dir: # radiusd -d /usr/local/etc/raddb and... -> still: netstat -nlp: udp 0 0 0.0.0.0:1812 0.0.0.0:* 16289/radiusd Now how on earth ist this possible? Could it be radtest tries only on tcp? Please tell me: When you start radiusd, is it supposed to display more than this: # radiusd Thu Mar 8 15:17:28 2007 : Info: Starting - reading configuration files ... or is this all I should get? Is there some other possibility how I could test it wether it's running correctly? Thank you so much for all your help, jan