Welcome to Cool Solutions
supportconfig for Linux
Installation Instructions
- Uninstall the supportconfig and chkbin RPM packages
- Download ntsutils-1.00-66.1.noarch.rpm
- Install the RPM
- Run the supportconfig command as root; use -h or man page to see more options.
- To view the information files, assuming the tarball filename is: /var/log/nts_host1_080509_1300.tbz
cd /var/log
tar jxf nts_host1_080509_1300.tbz
cd nts_host1_080509_1300
ls -l - Perform a Basic Server Health Check with Supportconfig
rpm -e supportconfig chkbin
rpm -Uvh ntsutils-1.00-66.1.noarch.rpm
supportconfig
If you have difficulties installing the RPM, do the following:
- Change to the root of the file system
- Download ntsutils-1.00-66.1.noarch.rpm
- Extract the RPM files
- The preferred method is to install the RPM using the rpm command, not rpm2cpio.
cd /
rpm2cpio ntsutils-1.00-66.1.noarch.rpm | cpio -ivd
Updates to Version 2.19-58:
- Added the ntsutils package to the openSUSE Build Service
- Supports all types of plugins, just make sure it has execute permissions.
- Enhanced the plugin diplay and output order.
- Added lsscsi -g to mpio.txt
- Added udevinfo to udev.txt
Updates to Version 2.19-46:
- Supportconfig can now automatically upload it's tar ball to ftp.novell.com using the -u switch. The -u switch is the same as -r, but -u also uploads the tar ball. See supportconfig(1) for more details.
- Added plugin ability to allow custom scripts to be added to supportconfig, see supportconfig(1) PLUGINS for more details.
- Added -r and contact information to be included in the basic-environment.txt. See supportconfig(1) and supportconfig.conf(5) for more details.
- MPIO checks for repackaged multipath-tools
- Added rpm --last to rpm.txt
- Created supportconfig.conf(5) man page and updated existing man pages
- Added dmsetup and udevinfo commands to mpio, lvm and evms
- Added netstat -as to network.txt
Note: Detailed system information and logs are collected and organized in a manner that helps reduce service request resolution times. Private system information can be disclosed when using this tool. If this is a concern, please prune private data from the log files. Several startup options are available to exclude more sensitive information. Refer to the man page to see these options.
- To leave a comment you need to Login or Register
- 14539 reads
Print
Email
RSS
Digg
Slashdot
Why not include it?
Would be nice if this could be included in the normal OES/Linux software selection and the rug channels...
Including the suportconfig
We are working at including the supportconfig in the distribution. There is a lot involved in adding it, in addition to getting approval. Thanks for the suggestion!
Sysstat package
It seems that supportconfig needs the sysstat package to include some CPU statistics. But there is no warning if sysstat is not installed.
Walter
Sysstat package
Supportconfig will use iostat, mpstat and sar if the sysstat package is installed, otherwise it skips that data. Supportconfig is intended to have as little dependencies as possible. This way it gathers what information it can, regardless of the packages installed.
How about an option to show
How about an option to show the differences in a current config file from a "baseline" config file.
Baseline diff
I've thought about this before, but there are already some excellent tools to compare files (kdiff3, vimdiff, kompare). So, I really haven't felt a need to go beyond what is already there.