Bug 19677

Summary:	Guessing: /etc/sysctl.d/* not being read by systemd to enable core file generation
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Colin Guthrie <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	doktor5000, marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	systemd-230-12.mga6	CVE:
Status comment:

Description Bit Twister 2016-10-28 23:16:53 CEST

Description of problem: 6_rc0:

Guessing:
  /etc/sysctl.d/* not being read by systemd to enable core file generation

Result; no core file generated upon segfault.

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


How reproducible: Always


Steps to Reproduce:
The following are all performed in root terminals

1. Create /etc/sysctl.d/xx_enable_core.conf with the following:
kernel.core_uses_pid=0
kernel.core_pattern="/var/tmp/%e_%p_%s.core"

2. Reboot and verify values are set with the following:
   sysctl kernel.core_uses_pid
   sysctl kernel.core_pattern

   They should match contents seen/set in step 1.

3. Monitor journal for core-dump entry with
   xterm -e journalctl -fa --no-pager &

4. Create a segfault and see if core file generated.
   pkill -SIGILL -f irqbalance
   ls -al /var/tmp/*core
   systemctl start irqbalance

   Note no core entry in the journalctl terminal or /var/tmp

5. Now set values again interactively and re-test with the following:
   sysctl -w kernel.core_uses_pid=0
   sysctl -w kernel.core_pattern="/var/tmp/%e_%t_%s_uid%u.core"

   pkill -SIGILL -f irqbalance
   ls -al /var/tmp/*core
   systemctl start irqbalance

   Note core-dump entry in journalctl terminal and core file /var/tmp

Comment 1 Bit Twister 2016-10-29 02:47:51 CEST

Workaround:   create a local service to run 
   sysctl --system --quiet

Example snippet from mine:
  sysctl --system > /var/tmp/local.rc.log  2>&1

Comment 2 Marja Van Waes 2016-10-29 18:18:03 CEST

Assigning to systemd maintainer.

CC: (none) => marja11
Assignee: bugsquad => mageia

Bit Twister 2017-01-24 09:35:28 CET

Source RPM: systemd-230-5.mga6.src.rpm => systemd-230-8.mga6.src.rpm
Status comment: (none) => 6_s2
Summary: 6_rc0: Guessing: /etc/sysctl.d/* not being read by systemd to enable core file generation => Guessing: /etc/sysctl.d/* not being read by systemd to enable core file generation

Bit Twister 2017-01-31 18:36:49 CET

Keywords: (none) => 6sta2
Status comment: 6_s2 => (none)

Comment 3 Florian Hubold 2017-08-08 21:47:33 CEST

systemd-sysctl.service is enabled ? It's static and it should be, but would like to be sure.

CC: (none) => doktor5000

Comment 4 Bit Twister 2017-08-09 00:41:07 CEST

(In reply to Florian Hubold from comment #3)
> systemd-sysctl.service is enabled ? 

Was enabled during install, still is after reboot.


$ systemctl status systemd-sysctl
  systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static; vendor preset: enabled)
   Active: active (exited) since Tue 2017-08-08 08:58:25 CDT; 8h ago

Source RPM: systemd-230-8.mga6.src.rpm => systemd-230-12.mga6
Version: Cauldron => 6
Keywords: 6sta2 => (none)

Comment 5 Aurelien Oudelet 2020-08-05 15:02:33 CEST

This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD