Technical article 109555

What information should be gathered to help diagnose why an OpenServer 5.0.x system is experiencing panics and/or hangs?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

I have an SCO OpenServer 5.0.x system that is experiencing panics
(crashes) and/or hangs.  What information needs to be gathered to
assist with determining the cause of the problem?

Solution

What follows is not a full list of items. There will be more information that may need to be gathered (on a case-by-case basis) but the following can serve as a starting point:

- Has anything (software, hardware, configuration) changed between the time the system was running fine and the time it started to panic or hang?

- Is the panic and/or hang random or can it be re-created by following a series of steps?

- What is the make and model of the computer?

- A hardware listing:
# /etc/hwconfig -hc > /tmp/hwconfig.txt

- On OpenServer 5.0.4 and 5.0.5 systems (this command is not on 5.0.0 and 5.0.2 systems):

# /etc/hw -v > /tmp/hw.txt
- A software listing:
# /usr/bin/swconfig > /tmp/swconfig.txt

- Any errors or warning messages that are appearing on the screen.

- Any error/warning messages in the following files:

# /usr/adm/messages
# /usr/adm/syslog
When the system panics, save the dump (if one is created) and
then run the crash utility against it, then send in the output
text file.  For information on saving a crash dump and running the
crash utility against it, see ta105619, "Panic/Crash Analysis if a
dump is available."
For best results, gather 3 crash dumps and run the crash utility
against each one.  Then compare them to see if a consistent reason
for a system crashing can be determined.
NOTES:    As a standard set of steps, check the filesystem integrity and
          check for discrepancies within the operating system.  To check the
          filesystem integrity, perform the following commands in single user
          mode (for a more thorough explanation of this process, see ta105411
          "Filesystem Repair Utilities for SCO OpenServer 5.0.0, 5.0.2, and
          5.0.4."):

IMPORTANT: The following needs to be done in single-user mode.

# /etc/fsck -ofull    <Enter>
# /tcb/bin/integrity -em > /tmp/integ.rpt    <Enter>
# /etc/tcbck    <Enter>
# /tcb/bin/authck -a -v    <Enter>
# /etc/fixmog -v    <Enter>

Once you have completed the above, check the operating system for discrepancies:

# /etc/custom

Once the Software Manager (custom) has started, select "Software" -> "Verify System" -> "Normal System State (Thorough) and then "Continue".

After the software has been checked you will likely be prompted
to fix some discrepancies that were found.  A system restart is
not necessary after this step. However, if you have scripts that
did not start due to file permission problems and so on, and
they were corrected by the System Verification, it would be
advisable to shut down and restart the system.

See also

ta105619, "Panic/Crash Analysis if a dump is available."

ta105411, "Filesystem Repair Utilities for SCO OpenServer 5.0.0, 5.0.2 and 5.0.4"

From the Xinuos technical article database, record 109555. Reproduced with permission. The original is at www.sco.com/ta/109555, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.