Sponsored Content
Operating Systems Linux Red Hat Process does not dump any core files when crashed even if coredumpsize is unlimited Post 302467803 by fpmurphy on Sunday 31st of October 2010 11:06:29 AM
Old 10-31-2010
What version of redhat are you using?

What is the output of:
Code:
cat /proc/sys/kernel/core_pattern


Last edited by fpmurphy; 10-31-2010 at 12:11 PM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies

2. Programming

about core dump

MY friends: my program under sco unix have a problem? it create a core dump file on the path when execute program , but i can't find the error of the C program ,i don't know how to see the error about my program use core, please help me or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies

3. Shell Programming and Scripting

Restarting a Crashed Process

Hello, I host a couple of Call of Duty gameing servers. There are some hackers who love the crash them. When they crash them it simply causes a segmentaion fault and kills the PID. I was wondering it you could help me write a script to simply restart the program after it has been crashed. The... (9 Replies)
Discussion started by: Phobos
9 Replies

4. UNIX for Dummies Questions & Answers

Core dump in HP-UX..

Hi All I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies

5. UNIX for Dummies Questions & Answers

How to force core dump of a process

We have an application that terminates with segmentation violation errors in the logs. No source code is available since this is a third party software that is way past its maintenance life cycle. Under these circumstances is there a way to force a core dump of the process for further analysis?? ... (3 Replies)
Discussion started by: Un1xNewb1e
3 Replies

6. AIX

Core dump

Hi , I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information. ux201p3:e46123> dbx capsWrkstnMgr core Type 'help' for help. reading symbolic information ... Segmentation fault in malloc_common.extend_brk at... (1 Reply)
Discussion started by: rps
1 Replies

7. Linux

Find out process that crashed the server

Hi everybody, I want to find out all the processes that ran before a server crashed. Is that possible? I've looked in /var/log/messages and found out that the system was out of memory. A user probably wrote a script (in Perl or Python) that used up all available memory and crashed the... (11 Replies)
Discussion started by: z1dane
11 Replies

8. UNIX for Dummies Questions & Answers

identifying core dump files.

I have come into a business environtment problem and had been 10+ years since the last time I did any unix admin work. A long time ago some mainframe person created an app that talked to a mainframe on UNIX and wrote a c program with "core" in the file name to indicate that the file was the... (2 Replies)
Discussion started by: pcooke2002
2 Replies

9. Red Hat

Core Dump of a process in Red Hat Linux 5.9

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)
Discussion started by: Anjan Ganguly
19 Replies
savecore(8)						      System Manager's Manual						       savecore(8)

Name
       savecore - save a core dump of the operating system

Syntax
       /etc/savecore [ options ] dirname [ system ] [ corename ]

Description
       The  command  is  meant	to  be called near the end of the file.  The command saves the core dump of the system (assuming one was made) and
       writes a reboot message in the shutdown log.

       The command checks the core dump to be certain it corresponds with the current running ULTRIX.  If it does, it saves the core image in  the
       file  dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n.  The trailing .n in the pathnames is replaced by a number which
       increments each time is run in that directory.

       After saving the core and namelist images, will save the error logger buffer into a predetermined file.	The error logger  buffer  contains
       information about why the crash occurred.  After completes, the daemon will extract the error logger file and translate its contents into a
       form familiar to the program.

       Before writes out a core image, it reads a number from the file dirname/minfree.  If there are fewer free blocks  on  the  filesystem  that
       contains  dirname  than the number obtained from the file, a core dump is not done.  If the file does not exist, savecore always writes out
       the core file (assuming that a core dump was taken).

       The command also writes a reboot message in the shut down log.  If the system crashed as a result of a panic, also records the panic string
       in the shut down log.

       For  partial  crash  dumps,  creates  a	sparse	core image file in dirname/vmcore.n.  If this sparse core image file is copied or moved to
       another location, the file expands to its true size which can take too much file system space.  Hence, to copy or move  sparse  core  image
       files, you must use the command. The command has a conversion option to create sparse output files.

Options
       -c   Clears  the core dump.  This option is useful when the core dump is corrupted in a way that will not allow to save it safely.  Use the
	    option with caution, because once it clears the core dump, the core dump cannot be retrieved.

       -d dumpdev dumplo
	    Specifies the dump device and the dump offset when running on a system image other than the currently running system image.  The  pro-
	    gram  assumes  that  the running system image is and it reads the dump device and dump device offset are different in the system image
	    that crashed, the option provides the correct dump device and dump device offset.

       -e   Saves only the error logger buffer into a file.  If used, core or namelist images are not saved.

       -f corename
	    Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device.   This  option
	    is used only for diskless workstations.

       If  the	core  dump was from a system other than /vmunix, the name of that system must be supplied as system.  The program assumes that the
       running image is

       After successful completion, the core dump is cleared.  Also, a message is written in the file which tells whether the  dump  succeeded	or
       failed.

Files
       Shut down log

       Current running ULTRIX system

See Also
       dd(1), uerf(8)

																       savecore(8)
All times are GMT -4. The time now is 02:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy