From 43c171056f826cf08b4155472ad9a6a4d14ba8a9 Mon Sep 17 00:00:00 2001 From: Michael Friedrich Date: Tue, 4 Dec 2018 12:14:01 +0100 Subject: [PATCH] Minor updates for core dumps The main parts are discussed in #6723 --- doc/21-development.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/doc/21-development.md b/doc/21-development.md index 1b43724fe..1d08add4e 100644 --- a/doc/21-development.md +++ b/doc/21-development.md @@ -279,10 +279,11 @@ developers to analyze and fix the problem. This requires setting the core dump file size to `unlimited`. -Example for Systemd: + +##### Systemd ``` -vim /usr/lib/systemd/system/icinga2.service +systemctl edit icinga2.service [Service] ... @@ -293,7 +294,7 @@ systemctl daemon-reload systemctl restart icinga2 ``` -Example for init script: +##### Init Script ``` vim /etc/init.d/icinga2 @@ -303,10 +304,13 @@ ulimit -c unlimited service icinga2 restart ``` +##### Verify + Verify that the Icinga 2 process core file size limit is set to `unlimited`. ``` -cat /proc/`pidof icinga2`/limits +for pid in $(pidof icinga2); do cat /proc/$pid/limits; done + ... Max core file size unlimited unlimited bytes ``` @@ -318,7 +322,7 @@ The Icinga 2 daemon runs with the SUID bit set. Therefore you need to explicitly enable core dumps for SUID on Linux. ``` -sysctl -w fs.suid_dumpable=1 +sysctl -w fs.suid_dumpable=2 ``` Adjust the coredump kernel format and file location on Linux: -- 2.40.0