- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Urgant: crash dump does not created
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 03:48 AM
тАО12-29-2010 03:48 AM
Urgant: crash dump does not created
i have SLES11 OS running on DL585 G6 server , the server running oracle RAC with another nodes , i have the system crash , i try to create the crash dump file using atl+sys rq+c , but it soes not work and the system still hang what should i do.
BR;
fadia Almarei
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 07:21 AM
тАО12-29-2010 07:21 AM
Re: Urgant: crash dump does not created
Please check the setting for sysrq
Refer the below article "Set up magic SysRq (recommended)"
http://www.novell.com/support/viewContent.do?externalId=3374462
Hope this helps
Chhaya
I am an HP employee.
Was this post useful? - You may click the KUDOS! star to say thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 11:42 PM
тАО12-29-2010 11:42 PM
Re: Urgant: crash dump does not created
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2010 01:45 AM
тАО12-30-2010 01:45 AM
Re: Urgant: crash dump does not created
"i have the system crash , i try to create the crash dump file using atl+sys rq+c ,"
The above statement says that you had a server crash. Was it a kernel panic, hung, oops or badly hung that it didnot even take keyboard strokes?
A vmcore is generated only under these 5 conditions:
1>die()
2>panic()
3>├в Alt-SYSRQ-c├в keyboard interrupt is received (sysrq key combination must be enabled)
4>Character ├в c├в is echoed to /proc/sysrq-trigger (sysrq key combination must be enabled)
5>NMI issued via iLO on HP Proliant Servers
3 and 4 Manually calls kdump & generates vmcore (e.g. when the system is hung or frozen, you can manually crash the server using SYSRQ keys to generate a vmcore).
So if the server was hung and all the setting are correct it should have generated the vmcore.
Hope this recommended setting is also set correctly:
Set up magic SysRq (recommended)
For kernel problems other than a kernel oops or panic, a kernel core dump is not triggered automatically. If the system still responds to keyboard input to some degree, a kernel core dump can be triggered manually through a "magic SysRq" keyboard combination (typically: hold down three keys simultaneously: the left Alt key, the Print Screen / SysRq key and a letter key indicating the command - ' s' for sync, ' c' for core dump), if this feature has been enabled.
For general documentation of the "magic SysRq" feature, please refer to the Documentation/sysrq.txt file in the Linux kernel source.
To enable the magic SysRq feature permanently, edit /etc/sysconfig/sysctl, change the ENABLE_SYSRQ line to ENABLE_SYSRQ="yes". This change becomes active after a reboot. To enable the feature for the running kernel, run
echo 1>/proc/sys/kernel/sysrq
In case it was badly hung that it did not accept the keyboard strokes then you can try the NMI option.
Also was the kdump configuration tested in the past? Have u ever had a vmcore generated in the past?
Chhaya
I am an HP employee.
Was this post useful? - You may click the KUDOS! star to say thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2010 02:46 AM
тАО12-30-2010 02:46 AM
Re: Urgant: crash dump does not created
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2010 09:14 AM
тАО12-30-2010 09:14 AM
Re: Urgant: crash dump does not created
Try to switch to text terminal and then try Alt+sysrq+c.
Try to change to text terminal use ctrl+alt +f1
Chhaya
I am an HP employee.
Was this post useful? - You may click the KUDOS! star to say thank you.