Softpanorama

May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Suse supportconfig

News

Suse Troubleshooting

Recommended Books Recommended Links Baseliners Suse config files
Suse Log Files /proc and /sys Filesystems RC scripts Network configuration Suse config files Cool solutions
SLES Documentation Suse Tips Sysadmin Horror Stories Suse Tips

Humor

Etc

Supportconfig is a huge shell script used Novell to simply Suse troubleshooting. It belongs to a class of support scripts called Baseliners:

... servers are typically in a constant state of change as the result of patches and changes in environment as well as possible hardware changes . So baseline configuration changes with time and we can say about series of snapshots into a state of the system over time. Creation of  a baseline is an important step toward establishing Configuration Management (CM) infrastructure, which is a collection of activities focused on establishing and maintaining the integrity of products and systems via control of the processes for changing, and monitoring the those changes. Existence of baseline configuration is the cornerstone of configuration management.

It is used by Novell support to troubleshoot problems with Suse but can be used by any sysadmin too. It all not very Suse specific and can be adapted to other distributions.

It can also be used as a simple configuration management system as it contains all major configuration files in Suse and most files can be restored from the listing. Recently Novell added the updateSupportutils  command compares the current versions of supportutils and its plugins to those installed on your server.

Generally you should consider supportconfig reports to be a unique and important part of Suse logs and run periodically (monthly or weekly) from cron. The easiest was to use  is to run it from cron monthly, for example:

  0      1       1       *       * /sbin/supportconfig

Different generations of suportconfig can be diffed to find changes. In any case they represent an important baseline and as such simplify troubleshooting.

Here is a relevant information from Novell User Communities (version information is incorrect as program is updated pretty often):

download url:

http://download.opensuse.org/repositories/Novell:/NTS/SLE_10/noarch/

license:

GPLv2

home page url:

http://en.opensuse.org/Supportutils

Description

The updateSupportutils command compares the current versions of supportutils and its plugins to those installed on your server. Those that are outdated or missing are automatically downloaded and installed. Only those plugins that apply to your server are installed. The command supports creating a weekly or monthly cron entry to automatically check and update the supportutils package :and its plugins. Click here to see a list of the current supportutils and plugin packages. The updateSupportutils command help screen follows:

################################################################
# Supportutils Auto Update Client
################################################################

Usage: updateSupportutils [OPTION]

Description
  Makes sure the supportutils and supportutils plugin packages are
  installed and current.

Options
  -m  Install a monthly cron for updateSupportutils
  -w  Install a weekly cron for updateSupportutils
  -d  Delete all installed cron entries for updateSupportutils
  -l  List all cron entries for updateSupportutils
  -u  Force RPM update on applicable packages
  -p  Exclude supportutils plugin packages
  -v  Verbose mode
  -h  This screen

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 supportconfig(8) man page to see these options.

Update Instructions

Run updateSupportutils as root.

If you do not already have the supportutils-plugin-updater package installed, refer to the Installation Instructions below. If your server does not have network connectivity to http://download.opensuse.org, then install using the Option B (Manual) method.

Installation Instructions

Option A (Automated)

  1. Download the supportutils-plugin-updater
  2. Login as root
  3. Install the updater package
    # rpm -Uvh supportutils-plugin-updater-*.noarch.rpm
  4. Run updateSupportutils as root
    # updateSupportutils

Option B (Manual)

  1. Download the supportutils and any applicable supportutils plugin packages for your server.
  2. Login as root
  3. Install the supportutils-X.XX-XX.XX.noarch.rpm
    # rpm -Uvh supportutils-X.XX-XX.XX.noarch.rpm
  4. Install the supportutils-plugin-*-X.X-X.X.norarch.rpm packages you want
    # rpm -Uvh supportutils-plugin-*-X.X-X.X.norarch.rpm

Using Supportconfig

To upload a supportconfig to Novell, run

supportconfig -ur $srnum
; where $srnum is your 11 digit service request number. You can also just run supportconfig for local use. By default, supportconfig saves its information in /var/log/nts_date_time.tbz.

Consider using the Novell Support Advisor to perform an initial analysis of your servers. It will generate an HTML report that links you to Technical Information Documents that directly relate to any server issues identified.

Reporting Bugs

Updates to Supportconfig Version 2.25-314:

Updates to Supportconfig Version 2.25-301:

Attachment Size
supportutils-1.20-56.1.noarch.rpm 96.5 KB
supportutils-plugin-updater-1.0-19.1.noarch.rpm 6.99 KB

Disclaimer:

As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.

Here is an example of a protocol:

=============================================================================
Support Utilities - Supportconfig
Script Version: 2.25-136
Script Date: 2009 08 07
=============================================================================

Gathering system information

Basic Server Health Check... Done
RPM Database... Done
Basic Environment... Done
Basic Health Report... Done
System Modules... Done
Memory Details... Done
Disk I/O... Done
System Logs... Done
YaST Files... Done
File System List... Skipped
Crash Info... Skipped
NTP... Done
PROC... Done
Boot Files... Done
SLERT... Skipped
Updates... Done
Updates Daemon... Done
SMT... Skipped
Novell eDirectory... Please Wait... Skipped
Novell LUM... Skipped
Novell NCP... Skipped
Novell NSS... Skipped
Novell SMS... Skipped
Novell NCS... Skipped
Novell AFP... Skipped
Novell CIFS... Skipped
HA Cluster... Skipped
OCFS2... Skipped
PAM... Done
LDAP... Done
CIMOM... Skipped
Open Files... Done
Environment... Done
ETC... Done
SYSCONFIG... Done
SYSFS... Done
System Daemons... Done
CRON... Done
AT... Done
UDEV... Done
LVM... Please Wait... Base Detail Done
EVMS... Done
Software Raid... Done
Multipathing... Done
Networking... Done
Web... Skipped
InfiniBand... Skipped
DNS... Skipped
SLP... Done
SSH... Done
iSCSI... Done
Samba... Done
NFS... Done
AUTOFS... Done
SAR Files... Skipped
AppArmor... Done
Xen... Skipped
X... Done
Printing... Done
SMART Disks... Excluded
Hardware... Please Wait...

Top Visited
Switchboard
Latest
Past week
Past month

NEWS CONTENTS

Old News ;-)

[Apr 19, 2012] Novell Doc Administration Guide - Using Supportconfig

Using Supportconfig

The following sections describe how to use supportconfig with YaST, with the command line and what other options you have.

2.2.1 Using YaST to Collect Information

To use YaST to gather your system information, proceed as follows:

  1. Open the URL http://www.novell.com/center/eservice and create a service request number.

  2. Start YaST.

  3. Open the Support module.

  4. Click on Create report tarball.

  5. Select an option from the radio button list. If you want to test it first, use Only gather a minimum amount of info. Proceed with Next.

  6. Enter your contact information. Use your service request number from Step 1 and enter it into the text field labeled Novell 11 digit service request number. Proceed with Next.

  7. The information gathering begins. After the process is finished, continue with Next.

  8. Review the data collection. Continue with Next.

  9. Save your tarball. If you want to upload to the Novell customer center, make sure Upload log files tarball into URL is activated. Finish the operation with Next.

2.2.2 Using Supportconfig Directly to Collect Information

To use supportconfig from the commandline, proceed as follows:

  1. Open a shell and become root.

  2. Run supportconfig without any options. This gathers the default system information.

  3. Wait for the tool to complete the operation.

  4. The default archive location is /var/log with the filename format nts_HOST_DATE_TIME.tbz

2.2.3 Common Supportconfig Options

The supportconfig utility is usually called without any options. Display a list of all options with supportconfig -h or refer to the man page. The following list gives a brief overview of the more common cases:

Supportconfig Health Check Report Tool by jrecord

15 October 2008 | Novell User Communities

The Supportconfig Health Check Report Tool (schealth) parses and evaluates the basic-health-check.txt file generated by supportconfig. The tool is based on the concepts outlined in the article, "A Basic Server Health Check with Supportconfig". The schealth output will be most effective to you if you have read and understand the concepts documented in the article.

Installation Instructions

  1. schealth is included in the supportutils package along with supportconfig.

Usage

schealth [-hqv]

  1. Get a supportconfig tar ball from the server.
  2. Extract the supportconfig tar ball.
  3. Change to the directory where the basic-health-check.txt file is located.
  4. schealth requires the basic-health-check.txt file be in the current working directory.
  5. Run schealth.
  6. Observe the output. The output is also stored in the basic-health-report.txt file in the current directory.
  7. Use the supportconfig output to troubleshoot in more detail any red or yellow flags reported by schealth.

Sample Output

######################################################
Supportconfig Health Check Report Tool v0.95.3
######################################################

Health Check Files                         [  Green  ]
Processes Waiting for Run Queue            [ Yellow  ]
 Last 1 and 15 minutes: 6 > 5 && 6 > 5

Kernel Taint Status                        [  Green  ]
CPU Utilization                            [   Red   ]
 95% meets or exceeds 90%

Interrupts Per Second                      [ Yellow  ]
 8852 meets or exceeds 8000

Context Switches Per Second                [   Red   ]
 16546 meets or exceeds 10000

Free Memory and Disk Swapping              [ Yellow  ]
 Observed: 3 MB <= 4 MB, Swapping: No

Used Disk Space                            [   Red   ]
 Some meet or exceed limits

Red Flags
/var                 96% >= 90%
/boot                93% >= 90%

Yellow Flags
/dev                 81% >= 80%

Uninterruptible Processes                  [ Yellow  ]
 3 meets or exceeds 3

Zombie Processes                           [  Green  ]

######################################################
Status:   Red Flag
Checked:  /var/log/nts_jrecord1_080711_0953/basic-health-check.txt
Report:   /var/log/nts_jrecord1_080711_0953/basic-health-report.txt
######################################################

Recommended Links

Google matched content

Softpanorama Recommended

Top articles

Sites



Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D


Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019