Hello, I test freeradius1.0.1 on redhat-AS-3. If I run freeradius in debug mode (radiusd -X) there are no problems (running 15 hours). If I run freeradius in normal mode (radiusd -y) after several hours all rad- access-requests which are processed via pam lead to a timeout:
Wed Feb 2 04:02:07 2005 : Info: Using deprecated naslist file. Support fo s will go away soon. Wed Feb 2 04:02:07 2005 : Info: rlm_exec: Wait=yes but no output defined. Did y ou mean output=none? Wed Feb 2 04:02:07 2005 : Info: rlm_sql (sql): Driver rlm_sql_mysql (module rlm _sql_mysql) loaded and linked Wed Feb 2 04:02:07 2005 : Info: rlm_sql (sql): Attempting to connect to radiusa [EMAIL PROTECTED]:/freeradius Wed Feb 2 04:02:07 2005 : Info: rlm_sql_mysql: Starting connect to MySQL server for #0 Wed Feb 2 04:02:07 2005 : Info: rlm_sql_mysql: Starting connect to MySQL server for #1 Wed Feb 2 04:02:07 2005 : Info: rlm_sql_mysql: Starting connect to MySQL server for #2 Wed Feb 2 04:02:07 2005 : Info: rlm_sql_mysql: Starting connect to MySQL server for #3 Wed Feb 2 04:02:07 2005 : Info: rlm_sql_mysql: Starting connect to MySQL server 3026 Wed Feb 2 05:02:25 2005 : Error: Killing unresponsive thread for request 23027 Wed Feb 2 05:02:31 2005 : Error: Killing unresponsive thread for request 23028 Wed Feb 2 05:03:08 2005 : Error: Killing unresponsive thread for request 23029 Wed Feb 2 05:03:08 2005 : Error: Killing unresponsive thread for request 23030 Wed Feb 2 05:03:08 2005 : Error: Killing unresponsive thread for request 23031 Wed Feb 2 05:03:08 2005 : Error: Killing unresponsive thread for request 23032 Wed Feb 2 05:03:08 2005 : Error: Killing unresponsive thread for request 23033 Wed Feb 2 05:03:08 2005 : Error: Killing unresponsive thread for request 23034 Wed Feb 2 05:03:08 2005 : Error: Killing unresponsive thread for request 23035 Wed Feb 2 05:03:13 2005 : Error: Killing unresponsive thread for request 23036 Wed Feb 2 05:03:21 2005 : Error: Killing unresponsive thread for request 23037 Wed Feb 2 05:03:29 2005 : Error: Killing unresponsive thread for request 23038 Wed Feb 2 05:03:41 2005 : Error: Killing unresponsive thread for request 23039 This leads to: Wed Feb 2 06:01:49 2005 : Error: Killing unresponsive thread for request 24384 Wed Feb 2 06:01:49 2005 : Error: Killing unresponsive thread for request 24385 Wed Feb 2 06:01:49 2005 : Error: FATAL: Thread create failed: Cannot allocate memory If I configure: max_requests_per_server = 50 in the thread pool section there are no problems for 24 hours and more. I append: radiusd.conf.gz users radiusd-X.gz Grüße Hans-Peter Fuchs Hans-Peter Fuchs - RZKR, Zimmer 20 Zentrum fuer angewandte Informatik - Universitaetsweiter Service RRZK Universität zu Köln - Tel: 0221-470-6972
# # Please read the documentation file ../doc/processing_users_file, # or 'man 5 users' (after installing the server) for more information. # # This file contains authentication security and configuration # information for each user. Accounting requests are NOT processed # through this file. Instead, see 'acct_users', in this directory. # # The first field is the user's name and can be up to # 253 characters in length. This is followed (on the same line) with # the list of authentication requirements for that user. This can # include password, comm server name, comm server port number, protocol # type (perhaps set by the "hints" file), and huntgroup name (set by # the "huntgroups" file). # # If you are not sure why a particular reply is being sent by the # server, then run the server in debugging mode (radiusd -X), and # you will see which entries in this file are matched. # # When an authentication request is received from the comm server, # these values are tested. Only the first match is used unless the # "Fall-Through" variable is set to "Yes". # # A special user named "DEFAULT" matches on all usernames. # You can have several DEFAULT entries. All entries are processed # in the order they appear in this file. The first entry that # matches the login-request will stop processing unless you use # the Fall-Through variable. # # If you use the database support to turn this file into a .db or .dbm # file, the DEFAULT entries _have_ to be at the end of this file and # you can't have multiple entries for one username. # # You don't need to specify a password if you set Auth-Type += System # on the list of authentication requirements. The RADIUS server # will then check the system password file. # # Indented (with the tab character) lines following the first # line indicate the configuration values to be passed back to # the comm server to allow the initiation of a user session. # This can include things like the PPP configuration values # or the host to log the user onto. # # You can include another `users' file with `$INCLUDE users.other' # # # For a list of RADIUS attributes, and links to their definitions, # see: # # http://www.freeradius.org/rfc/attributes.html # # # Deny access for a specific user. Note that this entry MUST # be before any other 'Auth-Type' attribute which results in the user # being authenticated. # # Note that there is NO 'Fall-Through' attribute, so the user will not # be given any additional resources. # #lameuser Auth-Type := Reject # Reply-Message = "Your account has been disabled." # # Deny access for a group of users. # # Note that there is NO 'Fall-Through' attribute, so the user will not # be given any additional resources. # #DEFAULT Group == "disabled", Auth-Type := Reject # Reply-Message = "Your account has been disabled." # # # This is a complete entry for "steve". Note that there is no Fall-Through # entry so that no DEFAULT entry will be used, and the user will NOT # get any attributes in addition to the ones listed here. # #steve Auth-Type := Local, User-Password == "testing" # Service-Type = Framed-User, # Framed-Protocol = PPP, # Framed-IP-Address = 172.16.3.33, # Framed-IP-Netmask = 255.255.255.0, # Framed-Routing = Broadcast-Listen, # Framed-Filter-Id = "std.ppp", # Framed-MTU = 1500, # Framed-Compression = Van-Jacobsen-TCP-IP # # This is an entry for a user with a space in their name. # Note the double quotes surrounding the name. # #"John Doe" Auth-Type := Local, User-Password == "hello" # Reply-Message = "Hello, %u" # # Dial user back and telnet to the default host for that port # #Deg Auth-Type := Local, User-Password == "ge55ged" # Service-Type = Callback-Login-User, # Login-IP-Host = 0.0.0.0, # Callback-Number = "9,5551212", # Login-Service = Telnet, # Login-TCP-Port = Telnet # # Another complete entry. After the user "dialbk" has logged in, the # connection will be broken and the user will be dialed back after which # he will get a connection to the host "timeshare1". # #dialbk Auth-Type := Local, User-Password == "callme" # Service-Type = Callback-Login-User, # Login-IP-Host = timeshare1, # Login-Service = PortMaster, # Callback-Number = "9,1-800-555-1212" # # user "swilson" will only get a static IP number if he logs in with # a framed protocol on a terminal server in Alphen (see the huntgroups file). # # Note that by setting "Fall-Through", other attributes will be added from # the following DEFAULT entries # #swilson Service-Type == Framed-User, Huntgroup-Name == "alphen" # Framed-IP-Address = 192.168.1.65, # Fall-Through = Yes # # If the user logs in as 'username.shell', then authenticate them # against the system database, give them shell access, and stop processing # the rest of the file. # #DEFAULT Suffix == ".shell", Auth-Type := System # Service-Type = Login-User, # Login-Service = Telnet, # Login-IP-Host = your.shell.machine # # The rest of this file contains the several DEFAULT entries. # DEFAULT entries match with all login names. # Note that DEFAULT entries can also Fall-Through (see first entry). # A name-value pair from a DEFAULT entry will _NEVER_ override # an already existing name-value pair. # #DEFAULT Auth-Type = Local # Fall-Through = yes #Unprotected Auth-Type := Accept # Service-Type = Authenticate-Only pohlig-gw Password == "xxxxxx",Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Port-Limit = 2, Framed-IP-Address = 134.95.125.3 messe-gw Password == "xxxxxx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.7 euradbackup-gw Password == "xxxxxxx", Framed-Protocol == PPP, NAS-IP-Address ==134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.8 uni77-gw Password == "xxx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.8 ufg-gw Password == "xxx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.9 krings-gw Password == "xx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.10 sozial-gw Password == "xx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.11 kath-gw Password == "ddd", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.12 nlphil-gw Password == "xx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.13 bfeilbackup-gw Password == "xxx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.14 seismobackup-gw Password == "xxx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.15 sozrecht-gw Password == "xxx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.16 wiwabackup-gw Password == "xxx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.17 Duerener56-gw Password == "x", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.18 FstAfrika-gw Password == "xxx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.19 gks1-gw Password == "xx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.20 nomad-gw Password == "xx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.250 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.227 fuchs-gw Password == "xx", Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251 Service-Type = Framed, Framed-Protocol = PPP, Framed-IP-Address = 134.95.125.40 cc001 Framed-Protocol == PPP, NAS-IP-Address == 134.95.127.251, Auth-Type := Pam Framed-IP-Address = 134.95.125.67, Port-Limit = 2 tvreimer NAS-IP-Address == 134.95.4.86, Auth-Type = Pam Framed-IP-Address = 134.95.83.254 vislab Password == "xxxx", NAS-IP-Address == 134.95.4.86 Framed-IP-Address = 134.95.83.253 test Password == "xxxxx", Auth-Type = Local Reply-Message = "Hallo %u!", Framed-Ip-Address = "134.95.128.30", Service-Type = Framed-User smokeping Password == "xxx" DEFAULT Auth-Type = Pam Nomadix-Bw-Up = 128, Fall-Through = yes #DEFAULT Suffix = "@uni-koeln.de.dt" # Service-Type = Framed-User # #DEFAULT Suffix = "@smail.uni-koeln.de" # Service-Type = Framed-User # #DEFAULT Suffix = "@smail.uni-koeln.de.dt" # Service-Type = Framed-User # #DEFAULT Suffix = "@uni-koeln.de" # Service-Type = Framed-User # #DEFAULT Auth-Type := Pam # Service-Type = Framed-User
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any another MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: radiusd-X.gz
Date: 2 Feb 2005, 10:35
Size: 6424 bytes.
Type: Unknown
radiusd-X.gz
Description: Binary data
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any another MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: radiusd.conf.gz
Date: 3 Feb 2005, 11:13
Size: 19705 bytes.
Type: Unknown
radiusd.conf.gz
Description: Binary data
