# HOSTTAG - Select if hostname of IP address will be used as a prefix to the use kdump-config propagate to send the public key to the # SSH_KEY - Full path of the ssh private key to be used to login to the remote # SSH - username and hostname of the remote server that will receive the dump To enable remote dumps using the SSH protocol, the /etc/default/kdump-tools must be modified in the following manner: #. Remote kernel crash dumps using the SSH protocol Many configuration options exist and are thoroughly documented in the /etc/default/kdump-tools file. Local dumps are configured automatically and will remain in use unless a remote protocol is chosen. In addition to local dump, it is now possible to use the remote dump functionality to send the kernel crash dump to a remote server, using either the SSH or NFS protocols. This tells us that we will find core dumps in /var/crash. sbin/kexec -p -command-line="." -initrd=. This will display something like this: DUMP_MODE: kdump You can view the current status of kdump via the command kdump-config show. If you enable kdump-tools after a reboot, you will only need to issue the kdump-config load command to activate the kdump mechanism. Upon reboot, kdump-tools will be enabled and active. If a reboot has not been done since installation of the linux-crashdump package, a reboot will be required in order to activate the crashkernel= boot parameter. You can also edit /etc/default/kexec and set parameters directly: # Load a kexec kernel (true/false)Īs well, edit /etc/default/kdump-tools to enable kdump by including the following line: USE_KDUMP=1 If you ever need to manually enable the functionality, you can use the dpkg-reconfigure kexec-tools and dpkg-reconfigure kdump-tools commands and answer ‘Yes’ to the questions. ‘Yes’ should be selected here as well, to enable kdump-tools. | Should kdump-tools be enabled be default? | | reboot is still required in order to enable the crashkernel kernel | | If you choose this option, the kdump-tools mechanism will be enabled. Select ‘Yes’ to select kexec-tools for all reboots. | Should kexec-tools handle reboots (sysvinit only)? | | kernel loaded by kexec instead of going through the full system boot | | If you choose this option, a system reboot will trigger a restart into a | Starting with 16.04, the kernel crash dump mechanism is enabled by default.ĭuring the installation, you will be prompted with the following dialogs. The kernel crash dump utility is installed with the following command: sudo apt install linux-crashdump This permits the existing memory area to remain untouched in order to safely copy its contents to storage. When a kernel panic occurs, the kernel relies on the kexec mechanism to quickly reboot a new instance of the kernel in a pre-reserved section of memory that had been allocated when the system booted (see below). The cause can be determined by inspecting the copied memory contents. Whenever one of the above events occurs, it is important to find out the root cause in order to prevent it from happening again. In other situations a manual intervention is required in order to capture the memory. The following events can cause a kernel disruption:įor some of these events (kernel panic, NMI) the kernel will react automatically and trigger the crash dump mechanism through kexec. Multi-node configuration with Docker-Composeĭistributed Replicated Block Device (DRBD)Ī ‘kernel crash dump’ refers to a portion of the contents of volatile memory (RAM) that is copied to disk whenever the execution of the kernel is disrupted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |