# AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: Fedora Deployment Guide\n" "POT-Creation-Date: 2011-02-22T00:51:16\n" "PO-Revision-Date: 2011-08-21 10:04+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: Greek \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: el\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" #. Tag: title #, no-c-format msgid "" "The kdump Crash Recovery Service" msgstr "" #. Tag: para #, no-c-format msgid "" "kdump is an advanced crash " "dumping mechanism. When enabled, the system is booted from the context of " "another kernel. This second kernel reserves a small amount of memory, and " "its only purpose is to capture the core dump image in case the system " "crashes. Since being able to analyze the core dump helps significantly to " "determine the exact cause of the system failure, it is strongly recommended " "to have this feature enabled." msgstr "" #. Tag: para #, no-c-format msgid "" "This chapter explains how to configure, test, and use the kdump service in &MAJOROS;, and provides a " "brief overview of how to analyze the resulting core dump using the " "crash debugging utility." msgstr "" #. Tag: title #, no-c-format msgid "Configuring the kdump Service" msgstr "" #. Tag: para #, no-c-format msgid "" "This section covers three common means of configuring the kdump service: at the first boot, using the " "Kernel Dump Configuration graphical utility, and " "doing so manually on the command line. It also describes how to test the " "configuration to verify that everything works as expected." msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "system requirements" msgstr "" #. Tag: title #, no-c-format msgid "Note: Make Sure You Have kexec-tools Installed" msgstr "" #. Tag: para #, no-c-format msgid "" "To use the kdump service, you " "must have the kexec-tools package installed. Refer to " " for more information on how to install " "new packages in &MAJOROS;." msgstr "" #. Tag: title #, no-c-format msgid "" "Configuring the kdump at First " "Boot" msgstr "" #. Tag: para #, no-c-format msgid "" "When the system boots for the first time, the " "firstboot application is launched to guide a user" " through the initial configuration of the freshly installed system. To " "configure kdump, navigate to the " "Kdump section, and follow the instructions below." msgstr "" #. Tag: title #, no-c-format msgid "Important: Make Sure the System Has Enough Memory" msgstr "" #. Tag: para #, no-c-format msgid "" "Unless the system has enough memory, this option will not be available. For " "the information on minimum memory requirements, refer to the Required minimums section of the Red Hat Enterprise Linux comparison " "chart. Note that when the kdump crash recovery is enabled, the minimum " "memory requirements increase by the amount of memory reserved for it. This " "value is determined by a user, and defaults to 128 MB." msgstr "" #. Tag: title #, no-c-format msgid "Enabling the Service" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "enabling the service" msgstr "" #. Tag: para #, no-c-format msgid "" "To start the kdump daemon at boot" " time, select the Enable kdump? check box. This will " "enable the service for runlevels 2, 3," " 4, and 5, and start it for the " "current session. Similarly, unselecting the check box will disable it for " "all runlevels and stop the service immediately." msgstr "" #. Tag: title #, no-c-format msgid "Configuring the Memory Usage" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "configuring the service memory " "usage" msgstr "" #. Tag: para #, no-c-format msgid "" "To configure the amount of memory that is reserved for the " "kdump kernel, click the up and down arrow buttons " "next to the Kdump Memory field to increase or decrease " "the value. Notice that the Usable System Memory field " "changes accordingly showing you the remaining memory that will be available " "to the system." msgstr "" #. Tag: title #, no-c-format msgid "Using the Kernel Dump Configuration Utility" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "Kernel Dump Configuration " "kdump" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "system-config-kdump kdump" msgstr "" #. Tag: para #, no-c-format msgid "" "To start the Kernel Dump Configuration utility, " "select " "SystemAdministrationKernel" " crash dumps from the panel, or type system-config-kdump at a shell prompt (for example, " "xterm or GNOME Terminal). You will" " be presented with a window as shown in ." msgstr "" #. Tag: para #, no-c-format msgid "" "The utility allows you to configure kdump as well as to enable or disable " "starting the service at boot time. When you are done, click " "Apply to save the changes. The system reboot will be " "requested, and unless you are already authenticated, you will be prompted to" " enter the superuser password." msgstr "" #. Tag: para #, no-c-format msgid "" "Unless the system has enough memory, the utility will not start, and you " "will be presented with the following error message:" msgstr "" #. Tag: para #, no-c-format msgid "The not enough memory error" msgstr "" #. Tag: para #, no-c-format msgid "" "For the information on minimum memory requirements, refer to the Required minimums section of the Red Hat Enterprise Linux comparison " "chart. Note that when the kdump crash recovery is enabled, the minimum " "memory requirements increase by the amount of memory reserved for it. This " "value is determined by a user, and defaults to 128 MB." msgstr "" #. Tag: para #, no-c-format msgid "" "To start the kdump daemon at boot" " time, click the Apply button on the toolbar. This " "will enable the service for runlevels 2, " "3, 4, and 5, and " "start it for the current session. Similarly, clicking the " "Disable button will disable it for all runlevels and " "stop the service immediately." msgstr "" #. Tag: para #, no-c-format msgid "" "For more information on runlevels and configuring services in general, refer" " to ." msgstr "" #. Tag: title #, no-c-format msgid "The Basic Settings Tab" msgstr "" #. Tag: para #, no-c-format msgid "" "The Basic Settings tab enables you to configure the " "amount of memory that is reserved for the kdump " "kernel. To do so, select the Manual kdump memory " "settings radio button, and click the up and down arrow buttons " "next to the New kdump Memory field to increase or " "decrease the value. Notice that the Usable Memory field" " changes accordingly showing you the remaining memory that will be available" " to the system." msgstr "" #. Tag: title #, no-c-format msgid "Basic Settings" msgstr "" #. Tag: title #, no-c-format msgid "The Target Settings Tab" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "configuring the service target " "location" msgstr "" #. Tag: para #, no-c-format msgid "" "The Target Settings tab enables you to specify the " "target location for the vmcore dump. It can be either " "stored as a file in a local file system, written directly to a device, or " "sent over a network using the NFS (Network File System) or SSH (Secure " "Shell) protocol." msgstr "" #. Tag: title #, no-c-format msgid "Target Settings" msgstr "" #. Tag: para #, no-c-format msgid "" "To save the dump to the local file system, select the Local " "filesystem radio button. Optionally, you can customize the " "settings by choosing a different partition from the " "Partition, and a target directory from the " "Path pulldown lists." msgstr "" #. Tag: para #, no-c-format msgid "" "To write the dump directly to a device, select the Raw " "device radio button, and choose the desired target device from " "the pulldown list next to it." msgstr "" #. Tag: para #, no-c-format msgid "" "To store the dump to a remote machine, select the " "Network radio button. To use the NFS protocol, select " "the NFS radio button, and fill the Server " "name and Path to directory fields. To use " "the SSH protocol, select the SSH radio button, and fill" " the Server name, Path to " "directory, and User name fields with the " "remote server address, target directory, and a valid remote user name " "respectively." msgstr "" #. Tag: para #, no-c-format msgid "" "Refer to for information on how to configure" " an SSH server, and how to set up a key-based authentication." msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "known issues hpsa driver" msgstr "" #. Tag: title #, no-c-format msgid "" "Important: Using the hpsa Driver" " for a Storage" msgstr "" #. Tag: para #, no-c-format msgid "" "Due to known issue with the hpsa" " driver, kdump is unable to save " "the dump to a storage that uses this driver for HP Smart Array Controllers. " "If this applies to your machine, it is advised that you save the dump to a " "remote system using the NFS or SSH protocol instead." msgstr "" #. Tag: title #, no-c-format msgid "The Filtering Settings Tab" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "configuring the service filtering " "level" msgstr "" #. Tag: para #, no-c-format msgid "" "The Filtering Settings tab enables you to select the " "filtering level for the vmcore dump." msgstr "" #. Tag: title #, no-c-format msgid "Filtering Settings" msgstr "" #. Tag: para #, no-c-format msgid "" "To exclude the zero page, cache " "page, cache private, user " "data, or free page from the dump, select the" " check box next to the appropriate label." msgstr "" #. Tag: title #, no-c-format msgid "The Expert Settings Tab" msgstr "" #. Tag: para #, no-c-format msgid "" "The Expert Settings tab enables you to choose which " "kernel and initial RAM disk to use, as well as to customize the options that" " are passed to the kernel and the core collector program." msgstr "" #. Tag: title #, no-c-format msgid "Expert Settings" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "configuring the service initial RAM " "disk" msgstr "" #. Tag: para #, no-c-format msgid "" "To use a different initial RAM disk, select the Custom " "initrd radio button, and choose the desired RAM disk from the " "pulldown list next to it." msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "configuring the service kernel " "image" msgstr "" #. Tag: para #, no-c-format msgid "" "To capture a different kernel, select the Custom kernel" " radio button, and choose the desired kernel image from the pulldown list on" " the right." msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "configuring the service kernel " "options" msgstr "" #. Tag: para #, no-c-format msgid "" "To adjust the list of options that are passed to the kernel at boot time, " "edit the content of the Edited text field. Note that " "you can always revert your changes by clicking the " "Refresh button." msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "configuring the service default " "action" msgstr "" #. Tag: para #, no-c-format msgid "" "To choose what steps should be taken when the kernel crash is captured, " "select the appropriate option from the Default action " "pulldown list. Available options are mount rootfs and run " "/sbin/init (the default action), " "reboot (to reboot the system), " "shell (to present a user with an interactive " "shell prompt), halt (to halt the system), and " "poweroff (to power the system off)." msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "configuring the service dump image " "compression" msgstr "" #. Tag: para #, no-c-format msgid "" "To customize the options that are passed to the " "makedumpfile core collector, edit the Core " "collector text field; see for more information." msgstr "" #. Tag: title #, no-c-format msgid "" "Configuring kdump on the Command " "Line" msgstr "" #. Tag: para #, no-c-format msgid "" "To perform actions described in this section, you have to be logged in as a " "superuser:" msgstr "" #. Tag: screen #, no-c-format msgid "" "~]$ su -\n" "Password:" msgstr "" #. Tag: para #, no-c-format msgid "" "To configure the amount of memory that is reserved for the " "kdump kernel, open the " "/boot/grub/grub.conf file in a text editor such as " "vi or nano, and add " "the " "parameter to the list of kernel options as shown in ." msgstr "" #. Tag: title #, no-c-format msgid "A sample /boot/grub/grub.conf file" msgstr "" #. Tag: screen #, no-c-format msgid "" "# grub.conf generated by anaconda\n" "#\n" "# Note that you do not have to rerun grub after making changes to this file\n" "# NOTICE: You have a /boot partition. This means that\n" "# all kernel and initrd paths are relative to /boot/, eg.\n" "# root (hd0,0)\n" "# kernel /vmlinuz-version ro root=/dev/sda3\n" "# initrd /initrd\n" "#boot=/dev/sda\n" "default=0\n" "timeout=5\n" "splashimage=(hd0,0)/grub/splash.xpm.gz\n" "hiddenmenu\n" "title Red Hat Enterprise Linux (2.6.32-54.el6.i686)\n" " root (hd0,0)\n" " kernel /boot/vmlinuz-2.6.32-54.el6.i686 root=/dev/sda3 ro crashkernel=128M\n" " initrd /initramfs-2.6.32-54.el6.i686.img\n" msgstr "" #. Tag: para #, no-c-format msgid "" "When the kdump crash recovery is " "enabled, the minimum memory requirements increase by the amount of memory " "reserved for it. This value is determined by a user, and defaults to 128 MB," " as lower values proved to be unreliable. For more information on minimum " "memory requirements for &MAJOROSVER;, refer to the Required minimums section of the Red Hat Enterprise Linux " "comparison chart." msgstr "" #. Tag: title #, no-c-format msgid "Configuring the Target Type" msgstr "" #. Tag: para #, no-c-format msgid "" "When a kernel crash is captured, the core dump can be either stored as a " "file in a local file system, written directly to a device, or sent over a " "network using the NFS (Network File System) or SSH (Secure Shell) protocol. " "Note that only one of these options can be set at the moment. The default " "option is to store the vmcore file in the /var/crash/ directory of the local file " "system. To change this, open the /etc/kdump.conf " "configuration file in a text editor such as vi or" " nano, and edit the options as described below." msgstr "" #. Tag: para #, no-c-format msgid "" "To change the local directory in which the core dump is to be saved, remove " "the hash sign (#) from the beginning of the #path " "/var/crash line, and replace the value with a desired directory " "path. Optionally, if you wish to write the file to a different partition, " "follow the same procedure with the #ext4 /dev/sda3 line " "as well, and change both the file system type and the device (a device name," " a file system label, and UUID are all supported) accordingly. For example:" msgstr "" #. Tag: screen #, no-c-format msgid "" "ext3 /dev/sda4\n" "path /usr/local/cores" msgstr "" #. Tag: para #, no-c-format msgid "" "To write the dump directly to a device, remove the hash sign " "(#) from the beginning of the #raw " "/dev/sda5 line, and replace the value with a desired device name. " "For example:" msgstr "" #. Tag: screen #, no-c-format msgid "raw /dev/sdb1" msgstr "" #. Tag: para #, no-c-format msgid "" "To store the dump to a remote machine using the NFS protocol, remove the " "hash sign (#) from the beginning of the #net " "my.server.com:/export/tmp line, and replace the value with a valid" " hostname and directory path. For example:" msgstr "" #. Tag: screen #, no-c-format msgid "net penguin.example.com:/export/cores" msgstr "" #. Tag: para #, no-c-format msgid "" "To store the dump to a remote machine using the SSH protocol, remove the " "hash sign (#) from the beginning of the #net " "user@my.server.com line, and replace the value with a valid " "username and hostname. For example:" msgstr "" #. Tag: screen #, no-c-format msgid "net john@penguin.example.com" msgstr "" #. Tag: title #, no-c-format msgid "Configuring the Core Collector" msgstr "" #. Tag: para #, no-c-format msgid "" "To reduce the size of the vmcore dump file, kdump allows you to specify an external " "application (that is, a core collector) to compress the data, and optionally" " leave out all irrelevant information. Currently, the only fully supported " "core collector is makedumpfile." msgstr "" #. Tag: para #, no-c-format msgid "" "To enable the core collector, open the /etc/kdump.conf " "configuration file in a text editor such as vi or" " nano, remove the hash sign (#) " "from the beginning of the #core_collector makedumpfile -c " "--message-level 1 -d 31 line, and edit the command line options as" " described below." msgstr "" #. Tag: para #, no-c-format msgid "" "To enable the dump file compression, add the parameter. " "For example:" msgstr "" #. Tag: screen #, no-c-format msgid "core_collector makedumpfile -c" msgstr "" #. Tag: para #, no-c-format msgid "" "To remove certain pages from the dump, add the parameter, where " "value is a sum of values of pages you want to " "omit as described in . For example, to remove both zero and free " "pages, use the following:" msgstr "" #. Tag: screen #, no-c-format msgid "core_collector makedumpfile -d 17 -c" msgstr "" #. Tag: para #, no-c-format msgid "" "Refer to the manual page for makedumpfile for a complete " "list of available options." msgstr "" #. Tag: title #, no-c-format msgid "Supported filtering levels" msgstr "" #. Tag: entry #, no-c-format msgid "Option" msgstr "" #. Tag: entry #, no-c-format msgid "Description" msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "Zero pages" msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "Cache pages" msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "Cache private" msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "User pages" msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "Free pages" msgstr "" #. Tag: title #, no-c-format msgid "Changing the Default Action" msgstr "" #. Tag: para #, no-c-format msgid "" "By default, when the kernel crash is captured, the root file system is " "mounted, and /sbin/init is run. To change this behavior, " "open the /etc/kdump.conf configuration file in a text " "editor such as vi or " "nano, remove the hash sign (#) " "from the beginning of the #default shell line, and " "replace the value with a desired action as described in . For example:" msgstr "" #. Tag: screen #, no-c-format msgid "default halt" msgstr "" #. Tag: title #, no-c-format msgid "Supported actions" msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "Reboot the system, losing the core in the process." msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "" "After attempting to capture a core, halt the system no matter if it " "succeeded." msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "Power off the system." msgstr "" #. Tag: entry #, no-c-format msgid "" msgstr "" #. Tag: entry #, no-c-format msgid "" "Run the msh session from within the initramfs, " "allowing a user to record the core manually." msgstr "" #. Tag: para #, no-c-format msgid "" "To start the kdump daemon at boot" " time, type the following at a shell prompt:" msgstr "" #. Tag: screen #, no-c-format msgid "~]# chkconfig kdump on" msgstr "" #. Tag: para #, no-c-format msgid "" "This will enable the service for runlevels 2, " "3, 4, and 5. " "Similarly, typing chkconfig kdump off will disable it for" " all runlevels. To start the service in the current session, use the " "following command:" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "running the service" msgstr "" #. Tag: screen #, no-c-format msgid "" "~]# service kdump start\n" "No kdump initial ramdisk found. [WARNING]\n" "Rebuilding /boot/initrd-2.6.32-54.el6.i686kdump.img\n" "Starting kdump: [ OK ]" msgstr "" #. Tag: title #, no-c-format msgid "Testing the Configuration" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "testing the configuration" msgstr "" #. Tag: title #, no-c-format msgid "Caution: Be Careful When Using These Commands" msgstr "" #. Tag: para #, no-c-format msgid "" "The commands below will cause the kernel to crash. Use caution when " "following these steps, and by no means use them on a production machine." msgstr "" #. Tag: para #, no-c-format msgid "" "To test the configuration, reboot the system with kdump enabled, and make sure that the service" " is running (refer to for more " "information on how to run a service in &MAJOROS;):" msgstr "" #. Tag: screen #, no-c-format msgid "" "~]# service kdump status\n" "Kdump is operational" msgstr "" #. Tag: para #, no-c-format msgid "Then type the following commands at a shell prompt:" msgstr "" #. Tag: screen #, no-c-format msgid "" "~]# echo 1 > /proc/sys/kernel/sysrq\n" "~]# echo c > /proc/sysrq-trigger" msgstr "" #. Tag: para #, no-c-format msgid "" "This will force the Linux kernel to crash, and the " "address-YYYY-MM-" "DD-HH:MM:SS/vmcore file " "will be copied to the location you have selected in the configuration (that " "is, to /var/crash/ by default)." msgstr "" #. Tag: title #, no-c-format msgid "" "Listing a content of /var/crash/ " "after a crash" msgstr "" #. Tag: screen #, no-c-format msgid "" "~]# tree --charset=ascii /var/crash\n" "/var/crash\n" "`-- 127.0.0.1-2010-08-25-08:45:02\n" " `-- vmcore\n" "\n" "1 directory, 1 file" msgstr "" #. Tag: title #, no-c-format msgid "Analyzing the Core Dump" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "analyzing the dump " "crash" msgstr "" #. Tag: para #, no-c-format msgid "" "To determine the cause of the system crash, you can use the " "crash utility. This utility allows you to " "interactively analyze a running Linux system as well as a core dump created " "by netdump, diskdump, " "xendump, or kdump. When " "started, it presents you with an interactive prompt very similar to the GNU " "Debugger (GDB)." msgstr "" #. Tag: indexterm #, no-c-format msgid "" "crash system " "requirements" msgstr "" #. Tag: title #, no-c-format msgid "Note: Make Sure You Have Relevant Packages Installed" msgstr "" #. Tag: para #, no-c-format msgid "" "To analyze the vmcore dump file, you must have the " "crash and kernel-debuginfo packages " "installed. To do so, type the following at a shell prompt:" msgstr "" #. Tag: screen #, no-c-format msgid "" "~]# yum install --enablerepo=fedora-debuginfo crash kernel-" "debuginfo" msgstr "" #. Tag: para #, no-c-format msgid "" "Refer to for more information on how to " "install new packages in &MAJOROS;." msgstr "" #. Tag: indexterm #, no-c-format msgid "" "crash opening the " "dump image" msgstr "" #. Tag: para #, no-c-format msgid "" "To start the utility, type the command in the following form at a shell " "prompt:" msgstr "" #. Tag: screen #, no-c-format msgid "" "crash /var/crash/timestamp/vmcore " "/usr/lib/debug/lib/modules/kernel/vmlinux" msgstr "" #. Tag: para #, no-c-format msgid "" "Note that the kernel version should be the same " "that was captured by kdump. To " "find out which kernel you are currently running, use the uname " "-r command." msgstr "" #. Tag: title #, no-c-format msgid "Running the crash utility" msgstr "" #. Tag: screen #, no-c-format msgid "" "~]# crash /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux \\\n" "/var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore\n" "\n" "crash 5.0.0-23.el6\n" "Copyright (C) 2002-2010 Red Hat, Inc.\n" "Copyright (C) 2004, 2005, 2006 IBM Corporation\n" "Copyright (C) 1999-2006 Hewlett-Packard Co\n" "Copyright (C) 2005, 2006 Fujitsu Limited\n" "Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.\n" "Copyright (C) 2005 NEC Corporation\n" "Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.\n" "Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.\n" "This program is free software, covered by the GNU General Public License,\n" "and you are welcome to change it and/or distribute copies of it under\n" "certain conditions. Enter \"help copying\" to see the conditions.\n" "This program has absolutely no warranty. Enter \"help warranty\" for details.\n" "\n" "GNU gdb (GDB) 7.0\n" "Copyright (C) 2009 Free Software Foundation, Inc.\n" "License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\n" "This is free software: you are free to change and redistribute it.\n" "There is NO WARRANTY, to the extent permitted by law. Type \"show copying\"\n" "and \"show warranty\" for details.\n" "This GDB was configured as \"i686-pc-linux-gnu\"...\n" "\n" " KERNEL: /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux\n" " DUMPFILE: /var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore [PARTIAL DUMP]\n" " CPUS: 4\n" " DATE: Wed Aug 25 08:44:47 2010\n" " UPTIME: 00:09:02\n" "LOAD AVERAGE: 0.00, 0.01, 0.00\n" " TASKS: 140\n" " NODENAME: hp-dl320g5-02.lab.bos.redhat.com\n" " RELEASE: 2.6.32-69.el6.i686\n" " VERSION: #1 SMP Tue Aug 24 10:31:45 EDT 2010\n" " MACHINE: i686 (2394 Mhz)\n" " MEMORY: 8 GB\n" " PANIC: \"Oops: 0002 [#1] SMP \" (check log for details)\n" " PID: 5591\n" " COMMAND: \"bash\"\n" " TASK: f196d560 [THREAD_INFO: ef4da000]\n" " CPU: 2\n" " STATE: TASK_RUNNING (PANIC)\n" "\n" "crash>" msgstr "" #. Tag: para #, no-c-format msgid "" "To exit the interactive prompt and terminate " "crash, type exit." msgstr "" #. Tag: title #, no-c-format msgid "Displaying the Message Buffer" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "crash analyzing the" " dump message buffer" msgstr "" #. Tag: para #, no-c-format msgid "" "To display the kernel message buffer, type the log " "command at the interactive prompt." msgstr "" #. Tag: title #, no-c-format msgid "Displaying the kernel message buffer" msgstr "" #. Tag: screen #, no-c-format msgid "" "crash> log\n" "... several lines omitted ...\n" "EIP: 0060:[<c068124f>] EFLAGS: 00010096 CPU: 2\n" "EIP is at sysrq_handle_crash+0xf/0x20\n" "EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000\n" "ESI: c0a09ca0 EDI: 00000286 EBP: 00000000 ESP: ef4dbf24\n" " DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068\n" "Process bash (pid: 5591, ti=ef4da000 task=f196d560 task.ti=ef4da000)\n" "Stack:\n" " c068146b c0960891 c0968653 00000003 00000000 00000002 efade5c0 c06814d0\n" "<0> fffffffb c068150f b7776000 f2600c40 c0569ec4 ef4dbf9c 00000002 b7776000\n" "<0> efade5c0 00000002 b7776000 c0569e60 c051de50 ef4dbf9c f196d560 ef4dbfb4\n" "Call Trace:\n" " [<c068146b>] ? __handle_sysrq+0xfb/0x160\n" " [<c06814d0>] ? write_sysrq_trigger+0x0/0x50\n" " [<c068150f>] ? write_sysrq_trigger+0x3f/0x50\n" " [<c0569ec4>] ? proc_reg_write+0x64/0xa0\n" " [<c0569e60>] ? proc_reg_write+0x0/0xa0\n" " [<c051de50>] ? vfs_write+0xa0/0x190\n" " [<c051e8d1>] ? sys_write+0x41/0x70\n" " [<c0409adc>] ? syscall_call+0x7/0xb\n" "Code: a0 c0 01 0f b6 41 03 19 d2 f7 d2 83 e2 03 83 e0 cf c1 e2 04 09 d0 88 41 03 f3 c3 90 c7 05 c8 1b 9e c0 01 00 00 00 0f ae f8 89 f6 <c6> 05 00 00 00 00 01 c3 89 f6 8d bc 27 00 00 00 00 8d 50 d0 83\n" "EIP: [<c068124f>] sysrq_handle_crash+0xf/0x20 SS:ESP 0068:ef4dbf24\n" "CR2: 0000000000000000" msgstr "" #. Tag: para #, no-c-format msgid "" "Type help log for more information on the command usage." msgstr "" #. Tag: title #, no-c-format msgid "Displaying a Backtrace" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "crash analyzing the" " dump stack trace" msgstr "" #. Tag: para #, no-c-format msgid "" "To display the kernel stack trace, type the bt command at" " the interactive prompt. You can use bt " "pid to display the backtrace of the " "selected process." msgstr "" #. Tag: title #, no-c-format msgid "Displaying the kernel stack trace" msgstr "" #. Tag: screen #, no-c-format msgid "" "crash> bt\n" "PID: 5591 TASK: f196d560 CPU: 2 COMMAND: \"bash\"\n" " #0 [ef4dbdcc] crash_kexec at c0494922\n" " #1 [ef4dbe20] oops_end at c080e402\n" " #2 [ef4dbe34] no_context at c043089d\n" " #3 [ef4dbe58] bad_area at c0430b26\n" " #4 [ef4dbe6c] do_page_fault at c080fb9b\n" " #5 [ef4dbee4] error_code (via page_fault) at c080d809\n" " EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000 EBP: 00000000\n" " DS: 007b ESI: c0a09ca0 ES: 007b EDI: 00000286 GS: 00e0\n" " CS: 0060 EIP: c068124f ERR: ffffffff EFLAGS: 00010096\n" " #6 [ef4dbf18] sysrq_handle_crash at c068124f\n" " #7 [ef4dbf24] __handle_sysrq at c0681469\n" " #8 [ef4dbf48] write_sysrq_trigger at c068150a\n" " #9 [ef4dbf54] proc_reg_write at c0569ec2\n" "#10 [ef4dbf74] vfs_write at c051de4e\n" "#11 [ef4dbf94] sys_write at c051e8cc\n" "#12 [ef4dbfb0] system_call at c0409ad5\n" " EAX: ffffffda EBX: 00000001 ECX: b7776000 EDX: 00000002\n" " DS: 007b ESI: 00000002 ES: 007b EDI: b7776000\n" " SS: 007b ESP: bfcb2088 EBP: bfcb20b4 GS: 0033\n" " CS: 0073 EIP: 00edc416 ERR: 00000004 EFLAGS: 00000246" msgstr "" #. Tag: para #, no-c-format msgid "" "Type help bt for more information on the command usage." msgstr "" #. Tag: title #, no-c-format msgid "Displaying a Process Status" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "crash analyzing the" " dump processes" msgstr "" #. Tag: para #, no-c-format msgid "" "To display status of processes in the system, type the ps" " command at the interactive prompt. You can use ps " "pid to display the status of the " "selected process." msgstr "" #. Tag: title #, no-c-format msgid "Displaying status of processes in the system" msgstr "" #. Tag: screen #, no-c-format msgid "" "crash> ps\n" " PID PPID CPU TASK ST %MEM VSZ RSS COMM\n" "> 0 0 0 c09dc560 RU 0.0 0 0 [swapper]\n" "> 0 0 1 f7072030 RU 0.0 0 0 [swapper]\n" " 0 0 2 f70a3a90 RU 0.0 0 0 [swapper]\n" "> 0 0 3 f70ac560 RU 0.0 0 0 [swapper]\n" " 1 0 1 f705ba90 IN 0.0 2828 1424 init\n" "... several lines omitted ...\n" " 5566 1 1 f2592560 IN 0.0 12876 784 auditd\n" " 5567 1 2 ef427560 IN 0.0 12876 784 auditd\n" " 5587 5132 0 f196d030 IN 0.0 11064 3184 sshd\n" "> 5591 5587 2 f196d560 RU 0.0 5084 1648 bash" msgstr "" #. Tag: para #, no-c-format msgid "" "Type help ps for more information on the command usage." msgstr "" #. Tag: title #, no-c-format msgid "Displaying Virtual Memory Information" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "crash analyzing the" " dump virtual memory" msgstr "" #. Tag: para #, no-c-format msgid "" "To display basic virtual memory information, type the vm " "command at the interactive prompt. You can use vm " "pid to display information on the " "selected process." msgstr "" #. Tag: title #, no-c-format msgid "Displaying virtual memory information of the current context" msgstr "" #. Tag: screen #, no-c-format msgid "" "crash> vm\n" "PID: 5591 TASK: f196d560 CPU: 2 COMMAND: \"bash\"\n" " MM PGD RSS TOTAL_VM\n" "f19b5900 ef9c6000 1648k 5084k\n" " VMA START END FLAGS FILE\n" "f1bb0310 242000 260000 8000875 /lib/ld-2.12.so\n" "f26af0b8 260000 261000 8100871 /lib/ld-2.12.so\n" "efbc275c 261000 262000 8100873 /lib/ld-2.12.so\n" "efbc2a18 268000 3ed000 8000075 /lib/libc-2.12.so\n" "efbc23d8 3ed000 3ee000 8000070 /lib/libc-2.12.so\n" "efbc2888 3ee000 3f0000 8100071 /lib/libc-2.12.so\n" "efbc2cd4 3f0000 3f1000 8100073 /lib/libc-2.12.so\n" "efbc243c 3f1000 3f4000 100073\n" "efbc28ec 3f6000 3f9000 8000075 /lib/libdl-2.12.so\n" "efbc2568 3f9000 3fa000 8100071 /lib/libdl-2.12.so\n" "efbc2f2c 3fa000 3fb000 8100073 /lib/libdl-2.12.so\n" "f26af888 7e6000 7fc000 8000075 /lib/libtinfo.so.5.7\n" "f26aff2c 7fc000 7ff000 8100073 /lib/libtinfo.so.5.7\n" "efbc211c d83000 d8f000 8000075 /lib/libnss_files-2.12.so\n" "efbc2504 d8f000 d90000 8100071 /lib/libnss_files-2.12.so\n" "efbc2950 d90000 d91000 8100073 /lib/libnss_files-2.12.so\n" "f26afe00 edc000 edd000 4040075\n" "f1bb0a18 8047000 8118000 8001875 /bin/bash\n" "f1bb01e4 8118000 811d000 8101873 /bin/bash\n" "f1bb0c70 811d000 8122000 100073\n" "f26afae0 9fd9000 9ffa000 100073\n" "... several lines omitted ..." msgstr "" #. Tag: para #, no-c-format msgid "" "Type help vm for more information on the command usage." msgstr "" #. Tag: title #, no-c-format msgid "Displaying Open Files" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "crash analyzing the" " dump open files" msgstr "" #. Tag: para #, no-c-format msgid "" "To display information about open files, type the files " "command at the interactive prompt. You can use files " "pid to display files opened by the " "selected process." msgstr "" #. Tag: title #, no-c-format msgid "Displaying information about open files of the current context" msgstr "" #. Tag: screen #, no-c-format msgid "" "crash> files\n" "PID: 5591 TASK: f196d560 CPU: 2 COMMAND: \"bash\"\n" "ROOT: / CWD: /root\n" " FD FILE DENTRY INODE TYPE PATH\n" " 0 f734f640 eedc2c6c eecd6048 CHR /pts/0\n" " 1 efade5c0 eee14090 f00431d4 REG /proc/sysrq-trigger\n" " 2 f734f640 eedc2c6c eecd6048 CHR /pts/0\n" " 10 f734f640 eedc2c6c eecd6048 CHR /pts/0\n" "255 f734f640 eedc2c6c eecd6048 CHR /pts/0" msgstr "" #. Tag: para #, no-c-format msgid "" "Type help files for more information on the command " "usage." msgstr "" #. Tag: title #, no-c-format msgid "Additional Resources" msgstr "" #. Tag: title #, no-c-format msgid "Installed Documentation" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "additional resources manual " "pages" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "additional resources installed " "documents" msgstr "" #. Tag: term #, no-c-format msgid "man kdump.conf" msgstr "" #. Tag: para #, no-c-format msgid "" "The manual page for the /etc/kdump.conf configuration " "file containing the full documentation of available options." msgstr "" #. Tag: term #, no-c-format msgid "man makedumpfile" msgstr "" #. Tag: para #, no-c-format msgid "" "The manual page for the makedumpfile core collector " "containing the full documentation on its usage." msgstr "" #. Tag: term #, no-c-format msgid "man kexec" msgstr "" #. Tag: para #, no-c-format msgid "" "The manual page for kexec containing the full " "documentation on its usage." msgstr "" #. Tag: term #, no-c-format msgid "man crash" msgstr "" #. Tag: para #, no-c-format msgid "" "The manual page for the crash utility containing " "the full documentation on its usage." msgstr "" #. Tag: term #, no-c-format msgid "" "/usr/share/doc/kexec-tools-version/kexec-kdump-howto.txt" msgstr "" #. Tag: para #, no-c-format msgid "" "An overview of the kdump and " "kexec installation and usage." msgstr "" #. Tag: title #, no-c-format msgid "Useful Websites" msgstr "" #. Tag: indexterm #, no-c-format msgid "" "kdump " "additional resources websites" msgstr "" #. Tag: term #, no-c-format msgid "" msgstr "" #. Tag: para #, no-c-format msgid "" "The Red Hat Knowledgebase article about the kexec and " "kdump configuration." msgstr "" #. Tag: term #, no-c-format msgid "" msgstr "" #. Tag: para #, no-c-format msgid "The crash utility homepage." msgstr ""