06-09-2003
Here is a link on
Kernel Panics -
Your system attempted to do a dump of memory into a core file - the space you have allocated for this was not big enough to save it all. You should read the information in the link and then figure out where you might be able to create enough space (different for what OS you are running).
Please post the OS and version and any other information you might have. Once you have the space to save the dumps, you will have to wait until it happens again to get better information on what to do. I don't know if folks on this site can help with reading your core dump but I'm sure they will have more suggestions for you.
Getting your system up to the latest patch level might help.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all,
we have been noticed that few of processes failed with no reason.
when I chcked the log messages, I have got the following error messages writen to ktlog
just a few minutes before!
When the kernel writes such warning meassages?
will the system sends/generates any signals like... (1 Reply)
Discussion started by: reddyb
1 Replies
2. Filesystems, Disks and Memory
Hi all,
I am running 7.3 Redhat Linux, I have Oracle database running on it and I have some problem with the memory. every time I startup the database, the memory was peak up to 630M of Ram out 640M ram on the entire box and I didn't specify that much of memory on my database. Oracle advise me... (2 Replies)
Discussion started by: lapnguyen
2 Replies
3. UNIX for Dummies Questions & Answers
hello all,
as we know that the kernal Schedules tasks with some time slice given to each.
how does the Kernal know that the time of a Task has been elapsed?
does it follow the syatem Clock?or how?
thanks for your time (4 Replies)
Discussion started by: compbug
4 Replies
4. UNIX for Dummies Questions & Answers
Hi friends,
i would like to know the kernal information (semaphores), which command do i use
Thanks (4 Replies)
Discussion started by: shaan_dmp
4 Replies
5. Linux
Hi all,
I am new to redhat/fedora linux.
In fedora linux 6,we created one file system(hda3 - /fs).
in this mount poing we were installed mounta vista os.
while booting we are getting below error messages.
1)
Booting 'mountaVisat(2.6.18_pro 500_pc_target-x86_586 smp)'
root(hd0,1)... (2 Replies)
Discussion started by: arjunreddy3
2 Replies
6. UNIX for Dummies Questions & Answers
:) Firstly Hi all!!, im NEW!! and on here hoping that someone might be able to offer me some help... i have a server that keeps crashing every few days with the error message:
PANIC KERNAL-MODE ADDRESS FAULT ON USER ADDRESS 0X14
KERNAL PAGE FAULT FROM (CS:EIP)=(100:EF71B5BD)
EAX=EF822000... (10 Replies)
Discussion started by: Twix
10 Replies
7. Solaris
hi,
can anybody tell me how to increase the parameters like project.max-shm-ids on solaris10.
i have used prctl, but got reset while server reboot.
thnks and regards
Ajay (1 Reply)
Discussion started by: ajaysahoo
1 Replies
8. SCO
I am trying to restore Unixware 7.1 from a backup using RestoreEdge which is from Microline version 2. The restore is on another machine using the same RAID controller and TBU. We are retiring the other machine.
Anyway, we get to disk #2 and it panics. Here is the Pic.
Can anyone tell me... (13 Replies)
Discussion started by: ccd1977
13 Replies
9. Solaris
Hi,
Can you please let me know about kernal parameters?
Where we can see that kernal parameters?
we are using System = SunOS 5.10.
Please let me know commands to see these kernal parameters file or files. (1 Reply)
Discussion started by: kancherla.sree
1 Replies
10. Red Hat
HI All,
server stopped here, we are suspecting server crash, need install new OS.
Any suggestions on this. kindly help to us.
Thanks
Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies
LEARN ABOUT DEBIAN
savecore
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)