12-09-2009
If the system crashes, and produces a dump then read these
http://wdb1.sco.com/kb/tasearch.results and enter "crash dump" in the search text, and select Unixware 7 in the product.
If the system just reboots without a dump, then start looking for a defective piece of hardware.
10 More Discussions You Might Find Interesting
1. SCO
Dear sir,
I am using sco open server 5.06.How we can reboot the system without using root password? Whar are the permision need to change to do this.
Thanks,
Mostafizur Rahman (3 Replies)
Discussion started by: rahmanm
3 Replies
2. SCO
Hello,
How do a schedule a reboot of a SCO 5.0 box like every wednesday at 3:30 am. Doesn't have a /etc/crontab file like our Suse boxes have. Thanks for any help. (6 Replies)
Discussion started by: benefactr
6 Replies
3. HP-UX
Hi,
Whenever I reboot this server remotely by using the command 'shutdown -r now' or 'reboot'. The server does not return to normal multi-user mode. It boots in single user mode.
To bring back the server, someone is required to connect via console and fire 'init 3'.
Please suggest on what... (1 Reply)
Discussion started by: mystition
1 Replies
4. Solaris
One of my X4600 server had a power loss and rebooted and now its giving me a strange problem servers internal disk controller naming has changed by itself ... the after failsafe boot md.conf file shows following c3txdx but shows internal disk at c4txdx ... what could be the reason for this and... (1 Reply)
Discussion started by: fugitive
1 Replies
5. SCO
I am haveing a problem with my VMware ESXi 4.1 server and a virtual SCO UnixWare 7.1.4 server that I need for a legacy application for my company. The problem seems simple but I can't find a solution. The UnixWare (UW) server is a clean install and patched as SCO recommends. I am able to telnet to... (1 Reply)
Discussion started by: DudeCrush
1 Replies
6. SCO
I recently installed the Java Communications API (v2.0Aa) on SCO and I'm having some issues running the SerialDemo application that comes with it.
I can open a connection and send text from SCO to a toy windows app I wrote - that works fine. However, when I try and close the connection, I get... (2 Replies)
Discussion started by: jdsnatl
2 Replies
7. Solaris
Hi ,
Everytime after reboot when user tries to start vnc below error is thrown
$ vncserver :5
Couldn't start Xvnc; trying default font path.
Please set correct fontPath in the vncserver script.
Couldn't start Xvnc process.
_XSERVTransSocketCreateListener: failed to bind listener... (7 Replies)
Discussion started by: chidori
7 Replies
8. Shell Programming and Scripting
Hi guys
I am troubleshooting a script that informs me when a system has rebooted.
The script is placed in /etc/rc3.d folder under root.
The script is as follows:
. /opt/scripts/function.sh
PATH=/usr/bin
EMAIL_ADD=<email address> ... (2 Replies)
Discussion started by: Junaid Subhani
2 Replies
9. IP Networking
I'm trying to figure out what circumstances would cause an Open Solaris 11.2 host to switch itself from a static to a DHCP ip address upon reboot. This has only happened once but is a cause for some concern as this machine will be part of a web server pool.
Nothing has changed on the LAN that... (2 Replies)
Discussion started by: SmokeyJoe
2 Replies
10. Linux
Respected Members,
We encountered an issue during node reboot when eth1 and eth5 of bond1 were behaving unusual(both eth1 and eth5 were in unknown states and ifdown and ifup were used to rectify). Please find the messages and configuration files as below and please let me know for any other... (0 Replies)
Discussion started by: Mudit Bansal
0 Replies
LEARN ABOUT OSF1
expand_dump
expand_dump(8) System Manager's Manual expand_dump(8)
NAME
expand_dump - Produces a non-compressed kernel crash dump file
SYNOPSIS
/usr/sbin/expand_dump input-file output-file
DESCRIPTION
By default, kernel crash dump files (vmzcore.#) are compressed during the crash dump. Compressed core files can be examined by the latest
versions of debugging tools that have been recompiled to support compressed crash dump files. However, not all debugging tools may be
upgraded on a given system, or you may want to examine a crash dump from a remote system using an older version of a tool. The expand_dump
utility produces a file that can be read by tools that have not been upgraded to support compressed crash dump files. This non-compressed
version can also be read by any upgraded tool.
This utility can only be used with compressed crash dump files, and does not support any other form of compressed file. You cannot use
other decompression tools such as compress, gzip, or zip on a compressed crash dump file.
Note that the non-compressed file will require significantly more disk storage space as it is possible to achieve compression ratios of up
to 60:1. Check the available disk space before running expand_dump and estimate the size of the non-compressed file as follows: Run tests
by halting your system and forcing a crash as described in the Kernel Debugging manual. Use an upgraded debugger to determine the value of
the variable dumpsize. Multiply this vale by the 8Kb page size to approximate the required disk space of the non-compressed crash-dump.
Run expand_dump and pipe the output file to /dev/null, noting the size of the file that is printed when expand_dump completes its task.
RETURN VALUES
Successful completion of the decompression. The user did not supply the correct number of command line arguments. The input file could
not be read. The input file is not a compressed dump, or is corrupted. The output file could not be created or opened for writing and
truncated. There was some problem writing to the output file (probably a full disk). The input file is not formated consistantly. It is
probably corrupted. The input file could not be correctly decompressed. It is probably corrupted.
EXAMPLES
expand_dump vmzcore.4 vmcore.4
SEE ALSO
Commands: dbx(1), kdbx(8), ladebug(1), savecore(8)
Kernel Debugging
System Administration
expand_dump(8)