Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-15501

Services dying due a deadly signal are not generating core dumps anymore

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • rhel-9.5
    • rhel-9.2.0
    • systemd
    • None
    • systemd-252-33.el9
    • None
    • Moderate
    • rhel-plumbers
    • ssg_core_services
    • 26
    • 8
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • None
    • Enhancement
    • Hide
      .The default value for the `DefaultLimitCore` option in `systemd` has been changed to `unlimited:unlimited`

      Previously, the default was set to `0:infinity`, which meant that all processes started by `systemd` had a soft limit of 0 for core file size, effectively disabling core dumps by default—although individual processes could raise the limit as needed.
      With this update, the new default of `unlimited:unlimited` removes any default restriction on core file size. Core dumps are now allowed by default, and their size is governed by the `systemd-coredump` component, specifically the `MaxUse` and `MaxFileSize` settings in `/etc/systemd/coredump.conf`. By default, the maximum size for an individual core dump is set to 1 GiB. This change enables better debugging of unexpected crashes.

      NOTE: The crash dumps stored by `systemd-coredump` are removed after 14 days if not used.
      Show
      .The default value for the `DefaultLimitCore` option in `systemd` has been changed to `unlimited:unlimited` Previously, the default was set to `0:infinity`, which meant that all processes started by `systemd` had a soft limit of 0 for core file size, effectively disabling core dumps by default—although individual processes could raise the limit as needed. With this update, the new default of `unlimited:unlimited` removes any default restriction on core file size. Core dumps are now allowed by default, and their size is governed by the `systemd-coredump` component, specifically the `MaxUse` and `MaxFileSize` settings in `/etc/systemd/coredump.conf`. By default, the maximum size for an individual core dump is set to 1 GiB. This change enables better debugging of unexpected crashes. NOTE: The crash dumps stored by `systemd-coredump` are removed after 14 days if not used.
    • Done
    • None

      What were you trying to do that didn't work?

      Services dying due to some deadly signal being received or raised do not generate core dumps anymore, this is new to RHEL9.

      This is problematic because it completely prevents getting the root cause for such anomaly.

      Please provide the package NVR for which bug is seen:

      systemd-252

      How reproducible:

      Always

      Steps to reproduce

      1. Kill any system service, e.g. rsyslog, with sending a SEGV

      Expected results

      Coredump being generated

      Actual results

      No coredump

       

      Root cause

      This is due to having the following in /etc/systemd/system.conf:

      DefaultLimitCORE=0:infinity

      This leads to having all services have a Soft CORE limit of 0, which disables dumping cores.

      This setting was commented out on RHEL8, causing "unlimited" Soft limit to be set.

              msekleta@redhat.com Michal Sekletar
              rhn-support-rmetrich Renaud Métrich
              systemd maint mailing list systemd maint mailing list
              Frantisek Sumsal Frantisek Sumsal
              Mugdha Soni Mugdha Soni
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: