Troubleshooting system-level problems

Checking system configuration

System configuration errors can cause a wide range of problems: the system may not link right, processes may fail, or the system may just behave in peculiar ways. If you experience system problems after tuning the kernel or adding new software packages or hardware devices, check the system configuration. All such activities should be noted in a system log book. You can also study the startup statistics that are logged in the /usr/adm/messages file; if the size of the kernel changes between boots, it indicates that the configuration was modified. The operating system includes a number of commands to help you check facets of the system configuration. Some of the more useful of these are:

/etc/conf/cf.d/configure -x | more
value of kernel parameters. You can also view the /etc/conf/cf.d/config.h file directly for this information.

You can use the sar(ADM) command to get performance statistics about how tunable resources are being utilized. The strstat function of the crash(ADM) command or the netstat -m command displays statistics about the configured STREAMS resources, including information about structures that have overflowed since the system was last booted. See the configure(ADM) manual page and the Performance Guide for more information.

current value of some tunable parameters that affect kernel data structures.

/usr/bin/swconfig -p
history and verification of software packages installed and/or removed from the system.

/usr/bin/hwconfig -h
installed drivers. Some memory maps and drivers that are installed in the /etc/rc.d script are excluded. This information can also be viewed in the /dev/string/cfg file.

whether packages are totally or partially installed.

/etc/custom -v quick SCO:Unix:RTS -x
verifies the presence, permissions and ownership of runtime system files. The -x flag specifies that fixes be made (where possible). Most importantly, this command repairs any broken symbolic links that may have rendered files unreachable. The above command only checks the operating system run time package. To check the entire system, use this command:

/etc/custom -V quick -x

custom leaves a copy of the verify output in custom.VerifyReport. There are other verify options available that perform different levels of checking. See the custom(ADM) manual page or ``Verifying software'' for instructions on invoking the Software Manager.

information about software installed with the installpkg(ADM) utilities. Such packages do not show up in the custom(ADM) or swconfig(ADM) reports.

/tcb/bin/fixmog -v
correct system file permissions to match the Authentication database. Use the -i option to run in interactive mode so you are prompted before any inconsistencies are corrected.

/tcb/bin/cps pathname
Similar to fixmog, but only checks the files specified rather than all system files.

Next topic: Generating a system dump image with sysdump(ADM)
Previous topic: Checking system files with error histories

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003