linux:abrtd_linux_rac
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
linux:abrtd_linux_rac [2015/03/19 20:47] – [Dump Verhalten optimieren] gpipperr | linux:abrtd_linux_rac [2015/03/19 21:10] (aktuell) – [Dump Verhalten optimieren] gpipperr | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
+ | =====Abrtd - Red Hat Automatic Bug Reporting Tool - Kernel Dumps - RedHat Linux 6 ===== | ||
+ | |||
+ | |||
+ | Über ein Problem unter einem RAC Cluster auf diese Linux Dämon unter RedHat Linux 6 gestoßen: | ||
+ | |||
+ | <code bash> | ||
+ | |||
+ | Mar 05 15:37:00 racdb01 abrt[83534]: | ||
+ | Mar 05 15:37:00 racdb01 abrtd: Directory ' | ||
+ | Mar 05 15:37:00 racdb01 abrtd: Executable '/ | ||
+ | Mar 05 15:37:00 racdb01 abrtd: ' | ||
+ | Mar 05 15:37:00 racdb01 abrtd: Corrupted or bad directory / | ||
+ | Mar 05 15:37:01 racdb01 abrt[83604]: | ||
+ | Mar 05 15:37:02 racdb01 abrt[83661]: | ||
+ | </ | ||
+ | |||
+ | Warum wird nun der Dump nicht geschrieben? | ||
+ | |||
+ | Wichtig ist die Zeile " | ||
+ | |||
+ | |||
+ | |||
+ | Lösung: | ||
+ | |||
+ | <code bash> | ||
+ | vi / | ||
+ | |||
+ | # auf yes setzen | ||
+ | ProcessUnpackaged = yes | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | Support Node zu diesen Thema: | ||
+ | |||
+ | * Abrtd Daemon Delete Recently Created Application Core Dumps- Corrupted or Bad Dump / | ||
+ | |||
+ | |||
+ | == Wo wird der Core abgelegt?== | ||
+ | |||
+ | <code bash> | ||
+ | |||
+ | sysctl -a|grep core_pattern | ||
+ | |||
+ | kernel.core_pattern = |/ | ||
+ | |||
+ | </ | ||
+ | ==== Oracle Linux 7 ==== | ||
+ | |||
+ | |||
+ | Aus der Oracle Dokumentation => http:// | ||
+ | |||
+ | ... | ||
+ | the daemons and features provided by the Red Hat Automatic Bug Reporting Tool (ABRT) <fc # | ||
+ | ... | ||
+ | |||
+ | ===== Infos zur Core Dumps ===== | ||
+ | |||
+ | |||
+ | === Dump Verhalten optimieren === | ||
+ | |||
+ | Zentrales Verzeichniss für Dumps einrichten wie / | ||
+ | |||
+ | <code bash> | ||
+ | |||
+ | mkdir / | ||
+ | chmod 777 / | ||
+ | |||
+ | |||
+ | vi / | ||
+ | |||
+ | kernel.core_uses_pid=1 | ||
+ | kernel.panic_on_oops = 1 | ||
+ | kernel.core_pattern = / | ||
+ | |||
+ | fs.suid_dumpable=1 | ||
+ | |||
+ | |||
+ | sysctl -p | ||
+ | |||
+ | </ | ||
+ | |||
+ | Core File Parameter: | ||
+ | |||
+ | * %p: pid | ||
+ | * %%: output one ' | ||
+ | * %u: uid - user id | ||
+ | * %g: gid - group id | ||
+ | * %s: signal number | ||
+ | * %t: UNIX time of dump | ||
+ | * %h: hostname | ||
+ | * %e: executable filename | ||
+ | * %E: pathname of executable | ||
+ | * %h: hostname | ||
+ | |||
+ | |||
+ | |||
+ | fs.suid_dumpable | ||
+ | |||
+ | * 0 - (default) - traditional behaviour. Any process which has changed | ||
+ | * 1 - (debug) - all processes dump core when possible. The core dump is owned by the current user and no security is applied. This is intended for system debugging situations only. | ||
+ | * 2 - (suidsafe) - any binary which normally not be dumped is dumped readable by root only. This allows the end user to remove such a dump but not access it directly. For securityreasons core dumps in this mode will not overwrite one another or other files. This mode is appropriate when adminstrators are attempting to debug problems in a normal environment. | ||
+ | |||
+ | |||
+ | Auf die aktuellen Limit Einstellungen achten, falls " | ||
+ | |||
+ | ==testen== | ||
+ | |||
+ | Als Oracle User anmelden und Dump verursachen, | ||
+ | <code bash> | ||
+ | |||
+ | su - oracle | ||
+ | |||
+ | #ulimit | ||
+ | ulimit -c | ||
+ | |||
+ | unlimited => beliebig gross | ||
+ | |||
+ | #Core dump der Bash Session erzeugen | ||
+ | |||
+ | kill -s SIGSEGV $$ | ||
+ | |||
+ | Segmentation fault (core dumped) | ||
+ | |||
+ | |||
+ | #nun wieder root und testen: | ||
+ | |||
+ | cd / | ||
+ | |||
+ | ls | ||
+ | |||
+ | coredump_racdb01.pipperr.local_.11.1100.1100_1426632616_!usr!bin!bash_bash.2779 | ||
+ | |||
+ | |||
+ | #Datum aus dem Core anzeigen mit: | ||
+ | |||
+ | date -d @1426632616 | ||
+ | |||
+ | Tue Mar 17 23:50:16 CET 2015 | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | # auswerten mit gdb ( gdb < | ||
+ | |||
+ | <code bash> | ||
+ | |||
+ | gdb / | ||
+ | |||
+ | </ | ||
+ | |||
+ | siehe => http:// | ||
+ | |||
+ | ==Kdump zur Analyse== | ||
+ | |||
+ | siehe | ||
+ | * https:// | ||
+ | |||
+ | |||
linux/abrtd_linux_rac.txt · Zuletzt geändert: 2015/03/19 21:10 von gpipperr