Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
radiusd hang after 'Access-Request' when listens on TCP port.
It doesn't matter if authentication is sucessful or not (e.g. if 'Access-Accept' or 'Access-Reject' is send)
Version-Release number of selected component (if applicable):
freeradius-3.0.1-6.el7
How reproducible:
always
Steps to Reproduce:
1.set 'proto = tcp' to "listen" section in /etc/raddb/sites-enabled/default and /etc/raddb/sites-enabled/inner-tunnel, add tcp to section "home_server localhost" in /etc/raddb/proxy.conf
2.radtest -P tcp clearuser cleartext-pas localhost 0 testing123
3.wait for a while and check if radiusd is running
Actual results:
radiusd hangs
Expected results:
radiusd is running
Additional info:
radiusd -X output:
... new connection request on TCP socket.
Listening on auth from client (127.0.0.1, 32832) -> (*, 1812, virtual-server=default)
Waking up in 0.4 seconds.
rad_recv: Access-Request packet from host 127.0.0.1 port 32832, id=45, length=95
User-Name = 'clearuser'
User-Password = 'cleartext-password'
NAS-IP-Address = 192.168.100.144
NAS-Port = 0
Message-Authenticator = 0x0cd0d533990ce9d207ee24f22cc5159e
(0) # Executing section authorize from file /etc/raddb/sites-enabled/default
(0) authorize {
(0) filter_username filter_username {
(0) ? if (User-Name != "%{tolower:%{User-Name}}")
(0) expand: "%{tolower:%{User-Name}}" -> 'clearuser'
(0) ? if (User-Name != "%{tolower:%{User-Name}}") -> FALSE
(0) ? if (User-Name =~ / /)
(0) ? if (User-Name =~ / /) -> FALSE
(0) ? if (User-Name =~ /@.*@/ )
(0) ? if (User-Name =~ /@.*@/ ) -> FALSE
(0) ? if (User-Name =~ /\\.\\./ )
(0) ? if (User-Name =~ /\\.\\./ ) -> FALSE
(0) ? if ((User-Name =~ /@/) && (User-Name !~ /@(.+)\\.(.+)$/))
(0) ? if ((User-Name =~ /@/) && (User-Name !~ /@(.+)\\.(.+)$/)) -> FALSE
(0) ? if (User-Name =~ /\\.$/)
(0) ? if (User-Name =~ /\\.$/) -> FALSE
(0) ? if (User-Name =~ /@\\./)
(0) ? if (User-Name =~ /@\\./) -> FALSE
(0) } # filter_username filter_username = notfound
(0) [preprocess] = ok
(0) [chap] = noop
(0) [mschap] = noop
(0) [digest] = noop
(0) suffix : No '@' in User-Name = "clearuser", looking up realm NULL
(0) suffix : No such realm "NULL"
(0) [suffix] = noop
(0) eap : No EAP-Message, not doing EAP
(0) [eap] = noop
(0) files : users: Matched entry clearuser at line 213
(0) [files] = ok
(0) [expiration] = noop
(0) [logintime] = noop
(0) [pap] = updated
(0) } # authorize = updated
(0) Found Auth-Type = PAP
(0) # Executing group from file /etc/raddb/sites-enabled/default
(0) Auth-Type PAP {
(0) pap : login attempt with password "cleartext-password"
(0) pap : Using clear text password "cleartext-password"
(0) pap : User authenticated successfully
(0) [pap] = ok
(0) } # Auth-Type PAP = ok
(0) # Executing section post-auth from file /etc/raddb/sites-enabled/default
(0) post-auth {
(0) [exec] = noop
(0) remove_reply_message_if_eap remove_reply_message_if_eap {
(0) ? if (reply:EAP-Message && reply:Reply-Message)
(0) ? if (reply:EAP-Message && reply:Reply-Message) -> FALSE
(0) else else {
(0) [noop] = noop
(0) } # else else = noop
(0) } # remove_reply_message_if_eap remove_reply_message_if_eap = noop
(0) } # post-auth = noop
Sending Access-Accept of id 45 from 0.0.0.0 port 1812 to 127.0.0.1 port 32832
(0) Finished request 0.
Waking up in 0.3 seconds.
Client has closed connection
... closing socket auth from client (127.0.0.1, 32832) -> (*, 1812, virtual-server=default)
Waking up in 0.3 seconds.
WARNING: Socket was closed while processing request 0: Stopping it.
(0) Cleaning up request packet ID 45 with timestamp +8
talloc: access after free error - first free may be at src/main/listen.c:3287
Bad talloc magic value - access after free
Aborted
Comment 1Nikolai Kondrashov
2014-07-16 12:07:46 UTC
David, the radiusd output you cite ends with an "Abort", meaning the server has terminated (likely due to the talloc error output right above it). Does the server actually hang, or does it abort? Or does it abort after you signal it to terminate?
Thank you.
Sorry for misleading bug name, server aborts. I doesn't send signal to terminate. Server is running and listening on TCP ports. Then I start communication over TCP with radtest and then server aborts.
Comment 3Nikolai Kondrashov
2014-07-16 12:35:30 UTC
Ah, thank you.
Comment 5Nikolai Kondrashov
2014-08-01 16:00:15 UTC
Reproduced locally.
Comment 6Nikolai Kondrashov
2014-08-04 11:54:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-0438.html
Description of problem: radiusd hang after 'Access-Request' when listens on TCP port. It doesn't matter if authentication is sucessful or not (e.g. if 'Access-Accept' or 'Access-Reject' is send) Version-Release number of selected component (if applicable): freeradius-3.0.1-6.el7 How reproducible: always Steps to Reproduce: 1.set 'proto = tcp' to "listen" section in /etc/raddb/sites-enabled/default and /etc/raddb/sites-enabled/inner-tunnel, add tcp to section "home_server localhost" in /etc/raddb/proxy.conf 2.radtest -P tcp clearuser cleartext-pas localhost 0 testing123 3.wait for a while and check if radiusd is running Actual results: radiusd hangs Expected results: radiusd is running Additional info: radiusd -X output: ... new connection request on TCP socket. Listening on auth from client (127.0.0.1, 32832) -> (*, 1812, virtual-server=default) Waking up in 0.4 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 32832, id=45, length=95 User-Name = 'clearuser' User-Password = 'cleartext-password' NAS-IP-Address = 192.168.100.144 NAS-Port = 0 Message-Authenticator = 0x0cd0d533990ce9d207ee24f22cc5159e (0) # Executing section authorize from file /etc/raddb/sites-enabled/default (0) authorize { (0) filter_username filter_username { (0) ? if (User-Name != "%{tolower:%{User-Name}}") (0) expand: "%{tolower:%{User-Name}}" -> 'clearuser' (0) ? if (User-Name != "%{tolower:%{User-Name}}") -> FALSE (0) ? if (User-Name =~ / /) (0) ? if (User-Name =~ / /) -> FALSE (0) ? if (User-Name =~ /@.*@/ ) (0) ? if (User-Name =~ /@.*@/ ) -> FALSE (0) ? if (User-Name =~ /\\.\\./ ) (0) ? if (User-Name =~ /\\.\\./ ) -> FALSE (0) ? if ((User-Name =~ /@/) && (User-Name !~ /@(.+)\\.(.+)$/)) (0) ? if ((User-Name =~ /@/) && (User-Name !~ /@(.+)\\.(.+)$/)) -> FALSE (0) ? if (User-Name =~ /\\.$/) (0) ? if (User-Name =~ /\\.$/) -> FALSE (0) ? if (User-Name =~ /@\\./) (0) ? if (User-Name =~ /@\\./) -> FALSE (0) } # filter_username filter_username = notfound (0) [preprocess] = ok (0) [chap] = noop (0) [mschap] = noop (0) [digest] = noop (0) suffix : No '@' in User-Name = "clearuser", looking up realm NULL (0) suffix : No such realm "NULL" (0) [suffix] = noop (0) eap : No EAP-Message, not doing EAP (0) [eap] = noop (0) files : users: Matched entry clearuser at line 213 (0) [files] = ok (0) [expiration] = noop (0) [logintime] = noop (0) [pap] = updated (0) } # authorize = updated (0) Found Auth-Type = PAP (0) # Executing group from file /etc/raddb/sites-enabled/default (0) Auth-Type PAP { (0) pap : login attempt with password "cleartext-password" (0) pap : Using clear text password "cleartext-password" (0) pap : User authenticated successfully (0) [pap] = ok (0) } # Auth-Type PAP = ok (0) # Executing section post-auth from file /etc/raddb/sites-enabled/default (0) post-auth { (0) [exec] = noop (0) remove_reply_message_if_eap remove_reply_message_if_eap { (0) ? if (reply:EAP-Message && reply:Reply-Message) (0) ? if (reply:EAP-Message && reply:Reply-Message) -> FALSE (0) else else { (0) [noop] = noop (0) } # else else = noop (0) } # remove_reply_message_if_eap remove_reply_message_if_eap = noop (0) } # post-auth = noop Sending Access-Accept of id 45 from 0.0.0.0 port 1812 to 127.0.0.1 port 32832 (0) Finished request 0. Waking up in 0.3 seconds. Client has closed connection ... closing socket auth from client (127.0.0.1, 32832) -> (*, 1812, virtual-server=default) Waking up in 0.3 seconds. WARNING: Socket was closed while processing request 0: Stopping it. (0) Cleaning up request packet ID 45 with timestamp +8 talloc: access after free error - first free may be at src/main/listen.c:3287 Bad talloc magic value - access after free Aborted