Bug 25918 - Unterstützung für crash dump kernel
Unterstützung für crash dump kernel
Status: RESOLVED WORKSFORME
Product: UCS
Classification: Unclassified
Component: Kernel
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks: 45407
  Show dependency treegraph
 
Reported: 2012-01-25 09:08 CET by Philipp Hahn
Modified: 2020-07-04 16:41 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016092221002158,2016091621002544,2017112821000348
Bug group (optional): Troubleshooting
Max CVSS v3 score:


Attachments
UCS kdump (4.83 KB, text/plain)
2016-03-15 16:25 CET, Philipp Hahn
Details
UCS kdump v2 (4.88 KB, text/plain)
2016-09-28 12:35 CEST, Philipp Hahn
Details
UCS kdump v3 (4.95 KB, text/plain)
2016-09-28 16:48 CEST, Philipp Hahn
Details
UCS kdump v4 (5.05 KB, application/x-shellscript)
2016-09-28 17:32 CEST, Philipp Hahn
Details
UCS kdump v5 (6.99 KB, application/x-shellscript)
2016-09-29 16:32 CEST, Philipp Hahn
Details
UCS kdump v6 (7.36 KB, text/plain)
2017-09-18 17:22 CEST, Philipp Hahn
Details
UCS kdump v7 (7.94 KB, text/plain)
2017-11-28 12:17 CET, Philipp Hahn
Details
UCS kdump v8 (8.85 KB, text/plain)
2017-12-05 07:15 CET, Philipp Hahn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2012-01-25 09:08:06 CET
Für die Fehlersuche beim Kunden (insbesondere 26) wäre es hilfreich, wenn in unseren Kernel die Option CONFIG_CRASH_DUMP=y aktiviert wäre. Dies erlaubt es einen sog. "Crash-Dump-Kernel" in den Speicher zu laden, der im Falle eines Kernel-Crashes die Kontrolle über das System übernimmt und dann zur Fehlerdiagnose genutzt werden kann, z.B. in dem dieser den Zustand des gecrashten Systems auf die Platte sichert.
<http://www.kernel.org/doc/Documentation/kdump/kdump.txt>

CONFIG_KEXEC=y # bereits aktiviert
CONFIG_SYSFS=y # bereits aktiviert
CONFIG_DEBUG_INFO=Y # bereits aktiviert
CONFIG_CRASH_DUMP=y # neu
CONFIG_PROC_VMCORE=y # neu
CONFIG_RELOCATABLE=y # bereits aktiviert
Comment 1 Philipp Hahn univentionstaff 2016-03-15 16:24:00 CET
# egrep -H '^CONFIG_(KEXEC|SYSFS|DEBUG_INFO|CRASH_DUMP|PROC_VMCORE|RELOCATABLE)\>' /boot/config-`uname -r`
/boot/config-4.1.0-ucs153-amd64:CONFIG_KEXEC=y
/boot/config-4.1.0-ucs153-amd64:CONFIG_CRASH_DUMP=y
/boot/config-4.1.0-ucs153-amd64:CONFIG_RELOCATABLE=y
/boot/config-4.1.0-ucs153-amd64:CONFIG_PROC_VMCORE=y
/boot/config-4.1.0-ucs153-amd64:CONFIG_SYSFS=y
/boot/config-4.1.0-ucs153-amd64:CONFIG_DEBUG_INFO=y

# egrep -H '^CONFIG_(KEXEC|SYSFS|DEBUG_INFO|CRASH_DUMP|PROC_VMCORE|RELOCATABLE)\>' /boot/config-`uname -r`
/boot/config-3.16.0-ucs189-amd64:CONFIG_KEXEC=y
/boot/config-3.16.0-ucs189-amd64:CONFIG_CRASH_DUMP=y
/boot/config-3.16.0-ucs189-amd64:CONFIG_RELOCATABLE=y
/boot/config-3.16.0-ucs189-amd64:CONFIG_PROC_VMCORE=y
/boot/config-3.16.0-ucs189-amd64:CONFIG_SYSFS=y
/boot/config-3.16.0-ucs189-amd64:CONFIG_DEBUG_INFO=y

SDB-Article <http://sdb.univention.de/1362>

Also see <https://wiki.ubuntu.com/Kernel/CrashdumpRecipe>
Comment 2 Philipp Hahn univentionstaff 2016-03-15 16:25:19 CET
Created attachment 7535 [details]
UCS kdump

Setup crash dump kernel and collector:
 ./25918_kexec-crash "collector.$(dnsdomainname)"
Comment 3 Philipp Hahn univentionstaff 2016-09-28 12:35:34 CEST
Created attachment 8041 [details]
UCS kdump v2

Setup crash dump kernel and collector:
 ./25918_kexec-crash "collector.$(dnsdomainname)"
Comment 4 Philipp Hahn univentionstaff 2016-09-28 16:48:55 CEST
Created attachment 8047 [details]
UCS kdump v3

Don't load next kernel by default
Fix `date +%%s`
Comment 5 Philipp Hahn univentionstaff 2016-09-28 17:32:32 CEST
Created attachment 8048 [details]
UCS kdump v4

After kexec-reboot the VGA console is broken because the VESA-mode is not saved/restored correctly. You should disable the VESA-FB for Linux:
 ucr unset grub/gfxmode grub/gfxpayload
Comment 6 Philipp Hahn univentionstaff 2016-09-29 16:32:40 CEST
Created attachment 8055 [details]
UCS kdump v5

Add options to specify
 --interface,--driver in case auto-detect fails (bridge,bonding,...)
 --size in case 128 MiB is not enough - lots of kernel modules?
Tries all interfaces to reach crash collect server
Output debug info on console.
Fixes sysctl syntax.
Comment 7 Stefan Gohmann univentionstaff 2017-06-16 20:37:35 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 8 Florian Best univentionstaff 2017-06-28 14:52:21 CEST
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Comment 9 Philipp Hahn univentionstaff 2017-09-18 17:22:12 CEST
Created attachment 9219 [details]
UCS kdump v6

Fix $output in collector.sh not being expanded.
Detect Xen hypervisor.
Comment 10 Philipp Hahn univentionstaff 2017-11-28 12:17:45 CET
Created attachment 9289 [details]
UCS kdump v7

Add bridge detection
Comment 11 Philipp Hahn univentionstaff 2017-12-05 07:15:33 CET
Created attachment 9298 [details]
UCS kdump v8

Fix IP detection
Add --force option
Ignore more kernel command line arguments
Comment 12 Ingo Steuwer univentionstaff 2020-07-03 20:54:22 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
Comment 13 Philipp Hahn univentionstaff 2020-07-04 16:41:16 CEST
We switched to upstream Debian kernels, which have it enabled by default:

$ grep CONFIG_CRASH_DUMP /boot/config-4.19.0-9-amd64 
CONFIG_CRASH_DUMP=y