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 when it has no proxy proxy response.
I modified 'home_server_pool my_auth_failover' in /etc/raddb/proxy.conf in this way:
home_server_pool my_auth_failover {
home_server = raddb1
home_server = raddb2
type = fail-over
...
home_server raddb1 is another radiusd server. When raddb1 is down, it should be marked as zombie->dead and radiusd should switch to raddb2.
But radiusd hang when raddb1 should be marked as zombie
Version-Release number of selected component (if applicable):
freeradius-3.0.1-6.el7
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Problem occures only if snmp traps are enabled. I will add reproducer later.
Comment 6Nikolai Kondrashov
2014-07-16 11:49:58 UTC
David, the radiusd output you cite ends with "Aborted", probably due to a talloc issue. Does the server actually hang, or does it abort? Or does it abort *after* you signal it to terminate?
Thank you.
Server aborts as you can see in the output. Server aborts when raddb1 goes down and server triggers this change and tries send snmp trap.
If I do the same test without snmp traps conguration then server doesn't abort. So abort is probably caused by some snmp traps code.
Comment 9Nikolai Kondrashov
2014-08-07 12:39:02 UTC
Reproduced locally.
Comment 10Nikolai Kondrashov
2014-09-29 11:44:35 UTC
This reproduces on 3.0.4 as well.
Comment 11Nikolai Kondrashov
2014-09-29 14:15:38 UTC
The problem could be home_trigger function allocating a dummy REQUEST on the stack and the xlat functions expecting it to be a valid talloc context.
Comment 12Nikolai Kondrashov
2014-09-29 15:18:58 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 when it has no proxy proxy response. I modified 'home_server_pool my_auth_failover' in /etc/raddb/proxy.conf in this way: home_server_pool my_auth_failover { home_server = raddb1 home_server = raddb2 type = fail-over ... home_server raddb1 is another radiusd server. When raddb1 is down, it should be marked as zombie->dead and radiusd should switch to raddb2. But radiusd hang when raddb1 should be marked as zombie Version-Release number of selected component (if applicable): freeradius-3.0.1-6.el7 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: