Call this function to manually generate a crash report. When crash information is collected, control is returned to the caller. The crGenerateErrorReport doesn't terminate the caller process. The crash report may contain the crash minidump file, crash description file in XML format and additional custom files added with a function like. Some events are only available in the System Event Log from the node that generated the event. Some pages of System Management Homepage that use java applets like the threshold settings may not load correctly when browsing locally on the managed server. This happens when Internet Explorer is configured manually with a proxy server. Apr 17, 2018 The end-user manually generated the crashdump. After you enable the feature, you can generate a memory dump file by holding down the right CTRL key and pressing the SCROLL LOCK key two times. The feature is available for both PS/2 and universal serial bus (USB) keyboards. PS/2 keyboards use the i8042prt.sys driver that is included with the keyboard.
- The End User Manually Generated The Crash Dump
- The End-user Manually Generated The Crash Dump Video
- The End-user Manually Generated The Crash Dump Site
Gathering Blue Screen Information After Memory Dump
Microsoft Knowledge Base Article: 192463 - This article describes how to gather more information about a blue-screen error message. Note that these steps may not always provide conclusive answers and may only be a symptom of another problem.
Microsoft Knowledge Base Article: 192463 - This article describes how to gather more information about a blue-screen error message. Note that these steps may not always provide conclusive answers and may only be a symptom of another problem.
How to Generate a Memory Dump File When a Server Stops Responding (Hangs)
Microsoft Knowledge Base Article: 303021 - If a Windows NT 4.0-based or a Windows 2000-based server stops responding (hangs), you can create a memory dump file to troubleshoot the issue. When you create a memory dump file, it is similar to forcing a bug check or a Stop error on the server. To perform the procedure that is described in this article, you must have second computer called Remote Debugger and a NULL modem cable.
Microsoft Knowledge Base Article: 303021 - If a Windows NT 4.0-based or a Windows 2000-based server stops responding (hangs), you can create a memory dump file to troubleshoot the issue. When you create a memory dump file, it is similar to forcing a bug check or a Stop error on the server. To perform the procedure that is described in this article, you must have second computer called Remote Debugger and a NULL modem cable.
How to Use Dumpchk.exe to Check a Memory Dump File
Microsoft Knowledge Base Article: 156280 Dumpchk is a command-line utility you can use to verify that a memory dump file has been created correctly. Dumpchk does not require access to symbols.
Microsoft Knowledge Base Article: 156280 Dumpchk is a command-line utility you can use to verify that a memory dump file has been created correctly. Dumpchk does not require access to symbols.
How to Use Hot Keys to Capture a Crash Dump of a Process
Microsoft Knowledge Base Article: 282421 - This article describes how to use hot keys to capture a crash dump of a process.
Microsoft Knowledge Base Article: 282421 - This article describes how to use hot keys to capture a crash dump of a process.
First off………what is a kdump?
Kdump is a standard Linux mechanism to dump machine memory content upon the event of kernel crash. Kdump is based on Kexec. Kdump utilizes two kernels: system kernel and dump capture kernel. System kernel is a normal kernel that is booted with special kdump-specific flags.
When the Kdump crash dumping mechanism is 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.
Being able to analyze the core dump significantly helps to determine the exact cause of the system failure, and it is therefore strongly recommended to have this feature enabled
So………..first you will want to configure memory usage
To do this, edit /boot/grub/grub.conf file and add (that’s if it’s not there already)
To do this, edit /boot/grub/grub.conf file and add (that’s if it’s not there already)
crashkernel=<size>M è crashkernel=128M
or
crashkernel=auto => this option only reserves memory if the physical memory of the system is equal or greater than 2GB pm 64bit systems
or
crashkernel=auto => this option only reserves memory if the physical memory of the system is equal or greater than 2GB pm 64bit systems
Kdump crash recovery service must have enough memory to be operational
When kdump service is enabled, the minimum memory requirements increase by the amount reserved for it. But it the auto option is used, it defaults to 128MB plus 64MB for each TB of memory.
When kdump service is enabled, the minimum memory requirements increase by the amount reserved for it. But it the auto option is used, it defaults to 128MB plus 64MB for each TB of memory.
Sample /boot/grub/grub.conf file below.
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda3
# initrd /initrd
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.32-220.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-220.el6.x86_64 ro root=/dev/sda3
crashkernel=128M
initrd /initramfs-2.6.32-220.el6.x86_64.img
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda3
# initrd /initrd
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.32-220.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-220.el6.x86_64 ro root=/dev/sda3
crashkernel=128M
initrd /initramfs-2.6.32-220.el6.x86_64.img
Configuring target type
the default option is to store the vmcore file in the /var/crash directory of the local system.
to change this, then as root
vi /etc/kdump.conf and change the #patch /var/crash line to what you want.
the default option is to store the vmcore file in the /var/crash directory of the local system.
to change this, then as root
vi /etc/kdump.conf and change the #patch /var/crash line to what you want.
I’ll just use the /var/crash in my own case since I just wanted to generate the vmcore and send it to RedHat for analysis.
Also if you want you can edit the /etc/kdump.conf file to compress the output of the kdump by editing the following lines to this. (you do this because the output can get quite voluminous)
The End User Manually Generated The Crash Dump
so change it from
core_collector makedumpfile -c –message-level 1 -d 31
to
core_collector makedumpfile -c
remember to remove the hash in front of the line too.
Next you if you want you can change the default behavior of kdump because if the kdump fails to to create a core dump it will go ahead and mount the root file system and run /sbin/init
to change this edit the /etc/kdump.conf and remove the # from the beginning of the following lines
#default shell
to change this edit the /etc/kdump.conf and remove the # from the beginning of the following lines
#default shell
Now just start the kdump service and chkconfig it
# service kdump start
# chkconfig kdump on
# service kdump start
# chkconfig kdump on
The End-user Manually Generated The Crash Dump Video
Now in my case I had to manually cause my system to crash…
I did so by running
# echo c > /proc/sysrq-trigger (Don’t PANIC …this will trigger a panic and then system will boot into the crash kernel which kdump created and will take a dump of system memory into the directory /var/crash/<date-time>/.
This is the vmcore…
Once done it will boot back into the normal kernel…
The End-user Manually Generated The Crash Dump Site
I then sent file/files to REDHAT.