Redhat Linux 4 crashed

Operating Systems Linux Red Hat Redhat Linux 4 crashed

09-24-2010

Registered User

23, 0

Join Date: Mar 2010

Last Activity: 3 December 2010, 5:41 AM EST

Posts: 23

Thanks Given: 4

Thanked 0 Times in 0 Posts

Redhat Linux 4 crashed

Hi,

I am having redhat enterprise linux 4 machine with kernel version 2.6.9-39.EL.Whenever I ran some java applications related to mechanical the system got crashed and powered off.

last output is as shown below.

reboot system boot 2.6.9-39.EL Fri Sep 24 15:23 (01:43)
user1 pts/1 :0.0 Fri Sep 24 14:32 - crash (00:50)
user1 :0 Fri Sep 24 14:32 - crash (00:50)

Could some one please help me on it.

ktrimu

View Public Profile for ktrimu

Find all posts by ktrimu

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Difference Redhat Linux/RH Enterprise Linux

what is the difference between Redhat Linux and Redhat Enterprise Linux. whereas Redhat linux have Server installation options too.

2. Red Hat

DNS for linux RedHat

Dear members, I am trying to set up a simple DNS but the problem is that when I ping the name of the IP address in the Reverse file, it does not recognise it. My code are as follows: Note that my IP address is 172.22.45.237. In my /etc/named.conf file, I have added the following lines ...

3. UNIX and Linux Applications

Redhat Linux 5

Can anyone help me outwith the post installation script.I'm newbie to scripting! i need to customize the post installation script using kickstart..here are the requirements to be set set permissions /etc/crontab =400 /etc/securetty=400 /etc/sysctl.conf=600 and following services to be set OFF...

4. Linux

Suse Linux System Crashed

Friends please let me know. How we can check the reason why system restarted automatically or rebooted. Suggest me some way other than messag log. Thankx Bryan

5. UNIX for Dummies Questions & Answers

Redhat Linux?

I seen a pool that said Linux was the most popular Unix download. I then seen Redhat Linux is the most popular Linux download. Is there a difference? Is it the better program/s?

6. HP-UX

rsh from Redhat Linux AS 3.0 to hp-ux 11.11

Dear Friends, I am unable to do rsh from Redhat Linux AS 3.0 to HP-UX 11.11. It takes lot of time request times out. What could be the reason. regards Rajendra More

7. Slackware

Redhat Linux?

Hi, I use linux and it is a great OS, I use Redhat Linux 9 and I was wondering are they going to update 9 or they'll be leaving that to the fedora project? I would like a stable linux distro. Thanks -n

8. UNIX for Dummies Questions & Answers

Linux RedHat. Help please.

I from russia. install rus Linux RedHat. When i load linux it ask me for user name and pass... and up of ask form label: Welcome to localhost... dont remember... what i want write in it? (sorry, bad english..:( )..

9. UNIX Desktop Questions & Answers

RedHat Linux Cd

I am wondering if anyone has copies (or can burn me a copy) of RedHat Linux. I will pay shipping charges... I don't have a CD burner and i dont want to run it off of my hard drive... please email me at: empireinfo623@yahoo.com or baldwitm@muc.edu

10. UNIX for Dummies Questions & Answers

redhat linux 7.3

hi, just installed redhat linux 7.3 on my server, and put it in gnome gui. Does anyone know what software i need to run a web server??? and what software i need to set up a proxy to secure it? also, if these are free to download, can you give me the links. Thanx

LEARN ABOUT CENTOS

trace-cmd-restore

TRACE-CMD-RESTORE(1)													      TRACE-CMD-RESTORE(1)

NAME

       trace-cmd-restore - restore a failed trace record

SYNOPSIS

       trace-cmd restore [OPTIONS] [command] cpu-file [cpu-file ...]

DESCRIPTION

       The trace-cmd(1) restore command will restore a crashed trace-cmd-record(1) file. If for some reason a trace-cmd record fails, it will
       leave a the per-cpu data files and not create the final trace.dat file. The trace-cmd restore will append the files to create a working
       trace.dat file that can be read with trace-cmd-report(1).

       When trace-cmd record runs, it spawns off a process per CPU and writes to a per cpu file usually called trace.dat.cpuX, where X represents
       the CPU number that it is tracing. If the -o option was used in the trace-cmd record, then the CPU data files will have that name instead
       of the trace.dat name. If a unexpected crash occurs before the tracing is finished, then the per CPU files will still exist but there will
       not be any trace.dat file to read from. trace-cmd restore will allow you to create a trace.dat file with the existing data files.

OPTIONS

       -c
	   Create a partial trace.dat file from the machine, to be used with a full trace-cmd restore at another time. This option is useful for
	   embedded devices. If a server contains the cpu files of a crashed trace-cmd record (or trace-cmd listen), trace-cmd restore can be
	   executed on the embedded device with the -c option to get all the stored information of that embedded device. Then the file created
	   could be copied to the server to run the trace-cmd restore there with the cpu files.

	       If *-o* is not specified, then the file created will be called
	       'trace-partial.dat'. This is because the file is not a full version
	       of something that trace-cmd-report(1) could use.

       -t tracing_dir
	   Used with -c, it overrides the location to read the events from. By default, tracing information is read from the debugfs/tracing
	   directory.  -t will use that location instead. This can be useful if the trace.dat file to create is from another machine. Just tar
	   -cvf events.tar debugfs/tracing and copy and untar that file locally, and use that directory instead.

       -k kallsyms
	   Used with -c, it overrides where to read the kallsyms file from. By default, /proc/kallsyms is used.  -k will override the file to read
	   the kallsyms from. This can be useful if the trace.dat file to create is from another machine. Just copy the /proc/kallsyms file
	   locally, and use -k to point to that file.

       -o output'
	   By default, trace-cmd restore will create a trace.dat file (or trace-partial.dat if -c is specified). You can specify a different file
	   to write to with the -o option.

       -i input
	   By default, trace-cmd restore will read the information of the current system to create the initial data stored in the trace.dat file.
	   If the crash was on another machine, then that machine should have the trace-cmd restore run with the -c option to create the trace.dat
	   partial file. Then that file can be copied to the current machine where trace-cmd restore will use -i to load that file instead of
	   reading from the current system.

EXAMPLES

       If a crash happened on another box, you could run:

	   $ trace-cmd restore -c -o box-partial.dat

       Then on the server that has the cpu files:

	   $ trace-cmd restore -i box-partial.dat trace.dat.cpu0 trace.dat.cpu1

       This would create a trace.dat file for the embedded box.

SEE ALSO

       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1),
       trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1)

AUTHOR

       Written by Steven Rostedt, <rostedt@goodmis.org[1]>

RESOURCES

       git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

COPYING

       Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).

NOTES

	1. rostedt@goodmis.org
	   mailto:rostedt@goodmis.org

								    06/11/2014						      TRACE-CMD-RESTORE(1)

Red Hat