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 file descriptor and your kernel logs doesn't have much or no error at all, the only way the red hat support could analyze your problem is through crash dump and above is the only way. or if you are having problem with your applications and your kernel couldn't tell.
Hello All,
I am new joiner of this forum.I am new to Linux shell scripting.
At present I have identified 1 application which stalls very frequently (PID is say xyz) and I am not having much information in its application log to identify the root cause of stalling. I need to take the core dump... (19 Replies)
Hi guys,
What is the best server for media streaming over network, when I googled some stuff I found that most of these articles talk about VLC, and according to what I know that is VLC is a third party application, and I don't know actually if there any standard linux streaming server. ... (2 Replies)
Hi,
I need to increase the FS on a vxfs on red hat ent 4. I need to get familiar with it by giving me how to query it if there's a free space. And then increase it, if there's any.
Can it be increase on the fly? I mean, no unmount and just increase it online.
I think the FS is also on... (4 Replies)
hi
i need to put the full path of every executable i need to put on my script. on the testing you don't need it but if it's running from cron you need to put the full path of the executable or another script.
what's the work around for this?
Thanks. (1 Reply)
Hi All,
Does installing sysstat on Red Hat Ent 4 will make the system unreliable or it's ok? Is it going to make the OS slow, I mean even if the utilities are not being used?
Any advise will be highly appreciated, thanks. (1 Reply)
Hi All,
If red hat 4 crash. How do I find out the error info or the last log info? I tried dmesg and /var/log/messages, it's not there.
Thanks in advance. (2 Replies)
Hi All,
I configured during the installation my red hat 5 ent with dhcp enable. Now I modified to static on ../ifcfg-eth0. It won't change when network is restarted with ../network restart command. I need to do ifdown eth0 and ifup eth0. And when rebooted, it will go back to dhcp.
Here's... (1 Reply)
I have a 500mhz K6 that I'm running Red Hat 8 on. I use xmms for all my music media playing purposes, but There seems to be an issue between xmms and volume control. Every now and then when I adjust the volume through aumix xmms freezes up and sends the sound into a runaway loop that I cant seem... (2 Replies)
hi I was successful in installing redhat 7.2 with no problems or error =) (first try) and It took me about 40 minutes to install it on a p233 mmx. It's running Gnome. I have some issues which I'm unsure of how to deal with.
1.How do I install an apache server, or is there one simular that... (11 Replies)
crashutil(1M)crashutil(1M)NAME
crashutil - manipulate crash dump data
SYNOPSIS
version] source [destination]
DESCRIPTION
copies and preserves crash dump data, and performs format conversions on it. Common uses of include:
o Copying portions of a dump that still reside on a raw dump device into a crash dump directory.
o Converting between different formats of crash dumps.
o Copying crash dumps from one directory, or medium, to another.
will write to its destination the crash dump it reads from its source. The crash dump format used to write the destination is specified
with if is not specified, the destination will have the same format as the source. If no destination is specified, source is used; the
format conversion will be done in place in the source, without copying. When completes successfully, the entire contents of the crash dump
will exist at destination; any portions that had still been on raw dump devices will have been copied to destination.
There are three known dump formats:
(Version 0) This format, used up through HP-UX 10.01, consists of a single file containing the physical memory image, with a 1-to-1 cor-
respondence between file offset and memory address. Normally there is an associated file containing the kernel image.
sources or destinations of this type must be specified as two pathnames to plain files, separated by whitespace; the first is
the core image file and the second is the kernel image file.
(Version 1) This format, used in HP-UX 10.10, 10.20, and 10.30, consists of a directory containing an file, the kernel file, and numerous
files, which contain portions of the physical memory image. sources or destinations of this type should be specified as the
pathname to a core directory.
(Version 2) This format, used in HP-UX 11.00 and later, consists of a directory containing an file, the kernel and all dynamically loaded
kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing
which memory pages were dumped and which were not. sources or destinations of this type should be specified as the pathname
to a crash directory.
(Version 3) This format is used in HP-UX Release 11i Version 1.0 and later. It is very similar in structure to the format in that it
consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files,
each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which
were not. In addition to the primary file, there are auxiliary index files, that contain metadata describing the image files
containing the memory pages. This format will be used when the dump is compressed. See crashconf(1M).
Other formats, for example tape archival formats, may be added in the future.
When the source and destination are different types of files -- for example, when source is a directory and destination is a pair of plain
files -- both must be specified.
Options
(Quiet) Disables the printing of progress messages.
Warning and error messages are still printed.
Specifies the version of the destination format.
Allowed values are 0, 1, 2 or 3. Also allowed is the keyword which specifies that the destination format should be the same as
the current source format. is the default if is not specified. If the destination format is then the source format should
also be Conversion to from older formats is not supported.
RETURN VALUE
Upon exit, returns the following values:
0 The operation was successful.
1 The operation failed, and an appropriate error message was printed.
EXAMPLES
An HP-UX 11.00 crash dump was saved by savecrash(1M) to The flag was specified to savecrash, specifying that only those portions of the
dump which were endangered by swap activity should be saved; the rest are still resident in the raw dump devices. To save the remainder of
the dump into the crash dump directory, use:
If preferred, the completed crash dump directory could be in a different location -- perhaps on another machine via NFS:
To debug this crash dump using tools which do not understand the most current crash dump format, convert it to the older core directory
format:
or the even older "core file and kernel" format:
AUTHOR
was developed by HP.
SEE ALSO savecrash(1M), crashconf(1M).
crashutil(1M)