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.
Bug 1977572 - radiusd in RHEL8 cannot coredump.
Summary: radiusd in RHEL8 cannot coredump.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: freeradius
Version: 8.3
Hardware: All
OS: Linux
high
high
Target Milestone: beta
: ---
Assignee: Antonio Torres
QA Contact: Filip Dvorak
URL:
Whiteboard:
Depends On:
Blocks: 1977722
TreeView+ depends on / blocked
 
Reported: 2021-06-30 05:50 UTC by kyoneyama
Modified: 2021-11-18 16:08 UTC (History)
7 users (show)

Fixed In Version: freeradius-3.0.20-7.module+el8.5.0+11913+a0aa3fd3
Doc Type: Bug Fix
Doc Text:
.FreeRADIUS no longer fails to create a core dump file Previously, FreeRADIUS did not create a core dump file when `allow_core_dumps` was set to `yes`. Consequently, no core dump files were created if any process failed. With this update, when you set `allow_core_dumps` to `yes`, FreeRADIUS now creates a core dump file if any process fails.
Clone Of:
: 1977722 (view as bug list)
Environment:
Last Closed: 2021-11-09 18:51:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:
antorres: needinfo+
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-6994 0 None None None 2021-10-01 03:03:29 UTC
Red Hat Product Errata RHBA-2021:4317 0 None None None 2021-11-09 18:51:12 UTC

Description kyoneyama 2021-06-30 05:50:41 UTC
Description of problem:

radiusd in RHEL8 canno coredump.


I allowed radiusd coredump in radiusd.conf.

  -- /etc/raddb/radiusd.conf --
        allow_core_dumps = yes

In the systemd configuration, the core rlimit is unlimited.

  -- /etc/systemd/system.conf --
  DefaultLimitCORE=infinity

However, when I checked the rlimit of the process, it was 0 for both soft and hard.

  # systemctl status radiusd
  ● radiusd.service - FreeRADIUS high performance RADIUS server.
     Loaded: loaded (/usr/lib/systemd/system/radiusd.service; enabled; vendor preset: disabled)
     Active: active (running) since Wed 2021-06-30 14:30:21 JST; 4s ago
    Process: 20827 ExecStart=/usr/sbin/radiusd -d /etc/raddb (code=exited, status=0/SUCCESS)
    Process: 20822 ExecStartPre=/usr/sbin/radiusd -C (code=exited, status=0/SUCCESS)
    Process: 20814 ExecStartPre=/bin/sh /etc/raddb/certs/bootstrap (code=exited, status=0/SUCCESS)
    Process: 20813 ExecStartPre=/bin/chown -R radiusd.radiusd /var/run/radiusd (code=exited, status=0/SUCCESS)
   Main PID: 20829 (radiusd)
      Tasks: 6 (limit: 7974)
  ...

  # prlimit -c -p 20829
  RESOURCE DESCRIPTION        SOFT HARD UNITS
  CORE     max core file size    0    0 bytes



Testing to send SIGSEGV to a process did not coredump.

  # kill -11 20829

  # coredumpctl info 20829
             PID: 20829 (radiusd)
             UID: 95 (radiusd)
             GID: 95 (radiusd)
          Signal: 11 (SEGV)
       Timestamp: Wed 2021-06-30 14:31:32 JST (7s ago)
    Command Line: /usr/sbin/radiusd -d /etc/raddb
      Executable: /usr/sbin/radiusd
   Control Group: /system.slice/radiusd.service
            Unit: radiusd.service
           Slice: system.slice
         Boot ID: ee16e7f9d82940d5a402aaab82380bfc
      Machine ID: 0618d47a97964a6e88fedc399ebd3b46
        Hostname: rhel84-minimal2
         Storage: none
         Message: Process 20829 (radiusd) of user 95 dumped core.


I checked it in debug mode, and it throws the following error:

  # radiusd -X
  FreeRADIUS Version 3.0.20
  Copyright (C) 1999-2019 The FreeRADIUS server project and contributors
  ..snip..
  main {
   security {
          user = "radiusd"
          group = "radiusd"
          allow_core_dumps = yes
   }
          name = "radiusd"
          prefix = "/usr"
          localstatedir = "/var"
          logdir = "/var/log/radius"
          run_dir = "/var/run/radiusd"
  }
  Cannot update core dump limit: Operation not permitted
  Core dumps are enabled
  ..snip..


Version-Release number of selected component (if applicable):

- Red Hat Enterprise Linux 8
- freeradius-3.0.20-3.module+el8.3.0+7597+67902674


How reproducible:

- Always

Steps to Reproduce:

1. Edit the following line in /etc/raddb/radiusd.conf

  -- /etc/raddb/radiusd.conf --
        allow_core_dumps = yes

2. Start radiusd service

  # systemctl start radiusd
  
3. Check rlimits with prlimit

  # prlimit -c -p <radiusd's pid>


Actual results:

- radiusd cannot coredump.

Expected results:

- radiusd can coredump.


Additional info:

- radiusd cannot coredump in RHEL8 GA(freeradius-3.0.17-3.module+el8+2746+2e560403)
   through the latest RHEL8.3(freeradius-3.0.20-3.module+el8.3.0+7597+67902674).

Comment 17 errata-xmlrpc 2021-11-09 18:51:07 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 (freeradius bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2021:4317


Note You need to log in before you can comment on or make changes to this bug.