Sponsored Content
Full Discussion: crash dump
Operating Systems Solaris crash dump Post 302264123 by lid-j-one on Wednesday 3rd of December 2008 07:10:44 AM
Old 12-03-2008
thnx every doby
 

10 More Discussions You Might Find Interesting

1. HP-UX

crash dump

hi friends, i know that when there is a crash then that memory image is put into /var/adm/crash but if the system hangs up and if i have access to console of that machine then how can i take the crash dump manully. thanks (2 Replies)
Discussion started by: mxms755
2 Replies

2. Solaris

crash dump

Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies

3. Linux

crash dump server for red hat ent 4

Is it true that you can't have the crash dump server/client on the same server? I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump. if someone is having problem with high... (0 Replies)
Discussion started by: itik
0 Replies

4. UNIX and Linux Applications

Retrieving symbol information from crash dump on Mac OS X

I am initiating the discussion.Hope everyone will add on to this. Whenever any application crashes the system's crash reporter(/System/Library/CoreServices/Crash Reporter.app) creates a crash dump.A crash dump is the image of the state of the kernel that was in physical memory when the system... (0 Replies)
Discussion started by: elizas
0 Replies

5. Solaris

Sparc Solaris 8 crash dump

My sparc solaris 8 server crashed/rebooted yesterday and I have the vmcore files. I have some initial output from SCAT and ACT. I have not included all but any info would be helpful. I can supply more output if necessary. Thanks you. Can I have any information about this ACT and SCAT... (2 Replies)
Discussion started by: csgonan
2 Replies

6. UNIX for Dummies Questions & Answers

analyze linux crash dump

Can anybody let me know the steps how can I produce a crash dump and then analyze it? (4 Replies)
Discussion started by: rupeshkp728
4 Replies

7. Solaris

Solaris 10 zone crash dump file?

Hi, I'm running Solaris 10 with a zone called "testzone" If I do a "reboot -d" on the host, as expected the kernet panics, reboots and creates a crash dump file in /var/crash However no crash file is created in testzone. My question is how can I tell if a zone crashs or shuts down... (4 Replies)
Discussion started by: fastexit
4 Replies

8. Solaris

copy crash dump file

Hi gurus, I will be glad if anyone can help me with this: How do you copy a crash dump file to send to your support provider? Thanks lots guys. (1 Reply)
Discussion started by: cjashu
1 Replies

9. Solaris

dedicated crash dump device

Hello Guys, I need a little help here. I have been studying crash dump and per what I am reading, you can dedicate a slice to use as a dump device. Now when you dedicate this slice, do you have to : 1) create a mount point? 2) add entry in /etc/vfstab? 3) is this slice wu or wm? 4) should... (3 Replies)
Discussion started by: cjashu
3 Replies

10. HP-UX

Prevent crash dump when SG cluster node reboots

Hi Experts, I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node? Thanks in advance. Vaishey (2 Replies)
Discussion started by: Vaishey
2 Replies
savecore(1M)                                              System Administration Commands                                              savecore(1M)

NAME
savecore - save a crash dump of the operating system SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory] DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is invoked by the dumpadm service each time the system boots. savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the pathnames is replaced by a number which grows every time savecore is run in that directory. Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes a minfree value of 1 megabyte. The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic, savecore logs the panic string too. OPTIONS
The following options are supported: -d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on the dump device indicates the dump has already been saved. -f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command. -L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per- formed if you have configured your system to have a dedicated dump device using dumpadm(1M). savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means that live crash dumps are not fully self-consistent. -v Verbose. Enables verbose error messages from savecore. OPERANDS
The following operands are supported: directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump files to the default savecore directory, configured by dumpadm(1M). FILES
directory/vmcore.n directory/unix.n directory/bounds directory/minfree /var/crash/'uname -n' default crash dump directory ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5) NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier: svc:/system/dumpadm:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the crash dump is overwritten by programs currently running. SunOS 5.10 25 Sep 2004 savecore(1M)
All times are GMT -4. The time now is 04:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy