07-12-2005
It sounds to me that system might be running out of virtual memory and is performing a core dump which takes some time and space. You may also be running out of disk on the entire box.
If you have the space try and double the virtual memory size or add more disk space.
You may also want to perform the lsps -a or topas commands to watch the memory usage etc while it is running. Check for an application dump.
10 More Discussions You Might Find Interesting
1. Slackware
Anyone else notice Fedora Core 2 (both 2.6.5 and .8 kernels) hang, specifically when running konqueror? I notice a lot of HD activity, but by the time I can switch to a shell to use top it's over. (1 Reply)
Discussion started by: Karma
1 Replies
2. AIX
Hi guys,
Got a tiny bit of a problem on one of our servers here at work. I installed AIX 5.3 on the server and that went fine. Then I upgraded to ML 5300-05-01, but now the system just hangs on boot.
The system starts up and the monitor comes on in few minutes, but a few seconds later when... (6 Replies)
Discussion started by: drchris
6 Replies
3. AIX
To All:
I have this AIX machine (see boot process below). The problem was it hangs at:
The ctrmc Subsystem has been started. Subsystem PID is 11906..
I checked with other forums but their advise were just "strong punches in the air" with no specific explanation.
I really appreciate if... (6 Replies)
Discussion started by: aix_xia
6 Replies
4. Shell Programming and Scripting
Hi,
I have script which is based on TCL and expect. It is written to test my code. It usually runs fine for a while and hangs after sometime.
Code snippet
set l_temp_timeout $timeout
OUTPUT_LOG2 2 >>>$expect_out(buffer)<<<
OUTPUT_LOG2 2... (2 Replies)
Discussion started by: naveenpn
2 Replies
5. Solaris
Hi Guys,
Anyone encontered a problem where when you run your SUN explorer, it hangs at sysconfig? I am having this problem for some of my servers.
rgds, (1 Reply)
Discussion started by: ronny_nch
1 Replies
6. Solaris
Hi,
today when i started the OS Sun Solaris 10 it hangs on initialization. Following was shown in the end of the screen
Initializing system
Please wait....
*
Please help? (3 Replies)
Discussion started by: malikshahid85
3 Replies
7. AIX
Hi all,
We have a old Power4 server with AIX version 5.3 installed. Upon boot up, it hangs right after the AIX welcome screen. On the diagnostic load progress LED indicator, I saw that it stopped at '0c32' then after awhile the LED would be blank. The screen on the monitor will hang at the black... (15 Replies)
Discussion started by: a_sim
15 Replies
8. HP-UX
hi,
bdf command hangs but before it, it lists all the fstab content, so i cannot find the reason...
could anybody give me any clue??
thanks a lot for your attention.
regards
Pablo
i attach syslog
Jan 14 16:30:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d... (7 Replies)
Discussion started by: pabloli150
7 Replies
9. Solaris
I have a Sun-Fire-V210, the Server hangs for sometime and evn console wont be abled to access and after sometime the server comes back active. the messages file shows this , whats causing this ?
# tail -500 messages
Jan 25 07:02:16 xxxxxxxxxxxxx Corrupt label; wrong magic number
Jan 25... (2 Replies)
Discussion started by: Sojourner
2 Replies
10. IP Networking
Ok sftp connects but hangs after I enter the password manually
The ssh version is 1.0
bash-2.05$ ssh -V
SSH Version Sun_SSH_1.0, protocol versions 1.5/2.0.
When I go from solaris 9 to sftp to another server with latest proftpd version it hangs after the password.
proftpd -V
Compile-time... (6 Replies)
Discussion started by: slufoot80
6 Replies
LEARN ABOUT ULTRIX
savecore
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)