supportconfig for Linux

supportconfig for Linux

Description


Table of Contents

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. Click here for the SLES10 repository.

  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_hostname_date_time.tbz.

Reporting Bugs


Updates to Supportconfig Version 3.0-40:

  • Fixed X and SYSFS looping issue with /sys/class/drm

  • Added kGraft detection in updates.txt

  • Updated xen.txt with SLE12 grub2 and systemd information

  • Fixed plugin detection

  • Added journalctl to boot.txt

  • Added /proc/device-tree under ppc64 directory

  • Added perl-Bootloader log to y2log.txt


Updates to Supportconfig Version 3.0-26:

  • Support for the upcoming SLE12 added

  • Limited mcelog to VAR_OPTION_LINE_COUNT

  • Removed schealth, use the SCA Appliance

  • Fixed LVM processing

  • Added OPTION_OES to activate other OES components

  • Fixed ipv6 flush permission error

  • Env gets sysctl config files

  • Fixed duplicate snapshot listings

  • Scanning base_reachable_time excluded

  • Corrected man page headers

  • Fixed drm configuration commands

  • novell-nss.txt captures VolumeInfo.xml file

  • Added novell-ncs-resource*.txt files

  • Included NCS parsed log information

  • Compatible with SLE10-SLE12

Attachments

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments
Would be nice if this could be included in the normal OES/Linux software selection and the rug channels...
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!
It seems that supportconfig needs the sysstat package to include some CPU statistics. But there is no warning if sysstat is not installed.

Walter
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 the differences in a current config file from a "baseline" config file.
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.
Great tool but
it seems that it always scans the whole / in the File System List Section. This is pretty useless for troubleshooting a fileserver.
The option -L seems to be always set.
This option is not set by default, and must have been changed.

The following switches will enable a full file listing: -ALe -or- /etc/supportconfig.conf has been modified with either of the following:
ADD_OPTION_FSLIST=1
ADD_OPTION_EDIR_SEARCH=1

You can force supportconfig to run with it's default settings using -D, which will not set ADD_OPTION_FSLIST.
As of today, October 10. The link to download.opensuse.org appears to be down.
We contacted them, and they said they are having outages that should be solved by tomorrow. Sorry for the inconvenience!
supportutils is included in the base install for SLE11.
AS NON Technical user several times tried send tarball error data to SUPPORT only to find it changes in size...

Asked to send the Support Utilities - Supportconfig
Script Version: 2.25-82
Script Date: 2008 12 04

The tarball reports created when logged in as SU

The Siebel eService am logged in as username, not SU.

When loading the tar file from /var/log

it appears to be 889.9 KB

However after load it shows as 65 (bytes ?? ) and they can not read it.

IF am wrongly sending it as user-self and NOT SU, how do I change it so can load them or send them as SU not username ?
You have mentioned several issues. I'm not exactly sure what your question is. However, I will answer the question about root verses non-root user. The supportconfig script forces you to run as root. If you use startup options to upload to support, that too will be as the root user, but the tarball will be uploaded using the anonymous user on the ftp server. Hope that helps.
There's no mention above about the option to install on download automatically. The file ends up in /sbin with root as owner, but I found it and ran it with sudo.

Also not mentioned is the option for a command line entry that tells the app to ftp the tarball. The instruction shows up at the end of the test. If you enter the command to ftp, it performs the entire test again--not very efficient. Could supportconfig check for the presence of a recent tarball to ftp before making another?
The supportutils package is not included in the SLE10 distribution, but will be included for SLE11. We are currently looking at possibly adding it to SLE10 SP3, which would make it installable from yast. I presume this is what you mean by "automatic" install on download.

The whole point is to gather current information. I could add an option to upload a specific tar ball, but then again you could just ftp the file yourself. So the only time supportconfig cares about uploading, is after it's gathered the current information.

You could use the -d and -f options in connection with one another. -d will gather the information and not compress it. The -f will then compress that directory into a tar ball. If you combine -f with -u, it would compress the nts_* directory created by -d and upload it to the upload target. Refer to supportconfig(8).
Hey there,

Was just wondering if there is planned options for some more upload options? We are upgrading our server, and we are not placing FTP services on it, so we cannot FTP the files to a central store in readiness for raising any SR's

Is it possible to get the software extended to add SCP or RSYNC support? or is only FTP and http methods supported?
supportconfig currently supports http,https,scp and ftp, see supportconfig(8). I will consider adding rsync. For example,

supportconfig -U 'scp://user@server.domain.com/directory/to/upload' will upload the tarball using scp and the specified user login. If the server is a trusted host, no password will be requested. Otherwise, you're prompted for the password.
I cannot turn this option off. Tried the -x FSLIST flag with the command line, tried the -D, and its still performing the file system list....

how can I turn this off???

I have a couple of servers which have smb mounts to other servers and its genreating gb text files.

how can I force it to STOP scanning file system list.....

Using supportutils-1.20-15.1
Sounds /sbin/supportconfig has been modified. It should contain ADD_OPTION_FSLIST=0
and not ADD_OPTION_FSLIST=1. You should also run rpm -V supportutils to see if the files have been modified. If that doesn't help, report a bug against supportconfig in bugzilla.novell.com and attached a supportconfig to it so I can take a look.
[no-glossary]When supportconfig is collecting eDirectory information, it attempts to bind to each configured instance's LDAP interface. But it looks like it is assuming that LDAP will be listening on either localhost or 0.0.0.0.

Novell eDirectory... Please Wait... 6 ldap_bind: Can't contact LDAP server
5 ldap_bind: Can't contact LDAP server
4 ldap_bind: Can't contact LDAP server
3 ldap_bind: Can't contact LDAP server
2 ldap_bind: Can't contact LDAP server
1 ldap_bind: Can't contact LDAP server
Done

While the default for eDirectory is to listen on 0.0.0.0, in a multi-instance configuration this doesn't work. eDirectory can be configured (ldapinterfaces attribute) to listen only on a specified IP address and port so that the instances don't conflict with each other. It would be nice if supportconfig could identify this and act appropriately.
[/no-glossary]
A bug report has been opened. I will be looking into this issue.
Hmm nice find 😃
Can someone post an example basic-health-check.txt ? I don't seem to find it in my SUSE box :S

ejma:~ # schealth
###############################################
Supportconfig Health Check Report Tool v1.00-5
Date Checked: 03/16/11 16:31:44
###############################################

Health Check Files [ ERROR ]
ERROR: File not found, /root/basic-health-check.txt


###############################################
Status: ERROR
Checked: /root/basic-health-check.txt
Report: /root/basic-health-report.txt
###############################################

Thanks
The basic-health-check.txt needs to be in the current directory to work. If you run a supportconfig, extract it, and look in the directory, the schealth output will be basic-health-report.txt. It looks like this:
##################################################################
Supportconfig Health Check Report Tool v1.00-5
Date Checked: 03/17/11 09:45:56
##################################################################

Health Check Files [ Green ]
Processes Waiting for Run Queue [ Green ]
Kernel Taint Status [ Green ]
CPU Utilization [ Green ]
Interrupts Per Second [ Green ]
Context Switches Per Second [ Green ]
Free Memory and Disk Swapping [ Green ]
Used Disk Space [ Green ]
Uninterruptible Processes [ Green ]
Zombie Processes [ Green ]

##################################################################
Status: Healthy
Checked: /mnt/nts_node_110317_0922/basic-health-check.txt
Report: /mnt/nts_node_110317_0922/basic-health-report.txt
##################################################################
I have installed supportutils-1.01-45.13.4.noarch.rpm on a SELS 10 SP2

I executed the command:
ejma:~ # supportconfig

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

ejma:~ # ls -l /var/log/nts*
-rw------- 1 root root 33 Mar 16 10:49 /var/log/nts_ejma_110316_1044.tbz.md5
-rw------- 1 root root 930068 Mar 16 10:49 /var/log/nts_ejma_110316_1044.tbz

Can you please printout your basic-health-check.txt ?
# cat /mnt/nts_node_110317_0922/basic-health-check.txt

Thanks
I printed my output above in my post. The archive is tarred and compressed. Run the following:
1. cd /var/log
2. tar jxvf nts_ejma_110316_1044.tbz
3. cd nts_ejma_110316_1044
4. cat basic-health-check.txt

NOTE: You are running a old version of supportconfig. Please update per the instructions above and retest.
Perfect, that did the trick 😉 Many thanks
Sweet! You certainly manage to get these fixed fast!
supportconfig, chkbin, schealth

These seem now part of supportutils in sle11 🙂

BTW self is one of the "Technically Challenged" !



localhost:/home/paulparker # zypper se supportconfig
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...
No packages found.

localhost:/home/paulparker # zypper se supportutils
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...

S | Name | Summary | Type
--+----------------------+----------------------------------+-----------
i | sledsp1-supportutils | Security update for supportutils | patch
i | supportutils | Support Troubleshooting Tools | package
| supportutils | Support Troubleshooting Tools | srcpackage
localhost:/home/paulparker #



http://www.novell.com/documentation/sled11/sled11_admin/?page=/documentation/sled11/sled11_admin/data/sled11_admin.html

In this document find : Administration Guide
open, then find : Support and Common Tasks
open, then find : Gathering System Information for Support
open, then find : Using Supportconfig



Current details from my system:

localhost:/home/paulparker # zypper info supportutils
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...


Information for package supportutils:

Repository: SLED11-SP1-Updates
Name: supportutils
Version: 1.20-0.10.1
Arch: noarch
Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Support Level: Level 3
Installed: Yes
Status: up-to-date
Installed Size: 198.0 KiB
Summary: Support Troubleshooting Tools
Description:
A package containing troubleshooting tools. This package contains the
following: supportconfig, chkbin, schealth
localhost:/home/paulparker #
localhost:/home/paulparker # supportconfig --help

=============================================================================
Support Utilities - Supportconfig
Script Version: 2.25-237
Script Date: 2010 10 25
=============================================================================

----deleted----
localhost:/home/paulparker # chkbin --help

####################################################################
Binary Check Tool, v1.01-25
Date: 07/15/11, 17:21:21
Kernel: 2.6.32.36-0.5-default, Hardware: x86_64
####################################################################
----deleted----
localhost:/home/paulparker # schealth --help
----deleted----
####################################################
Supportconfig Health Check Report Tool v1.00-5
Date Checked: 07/15/11 17:22:01
####################################################
----deleted----




Paul.
That is the current distributed version. I will be starting the patch process soon to update all the distributions with the current supportutils package available on Cool Solutions.
This is very useful tool for data collection. we have found this very useful for database administration, when database hits with problem of operating system we use this tool for data collection.
Some servers don't like newer version, they don't output correctly. Once uninstalling older version can't go back. Can we have a ZIP download that includes older versions?

Example, update.txt:

echo $$ > /var/log/nts_SERVER1_120426_1150/updates.txt.zypp-query-pool.1335434122.SEMAPHORE.pid
/usr/lib/zypp/zypp-query-pool products >> /var/log/nts_SERVER1_120426_1150/updates.txt.zypp-query-pool.1335434122.SEMAPHORE.out 2>&1
echo $? > /var/log/nts_SERVER1_120426_1150/updates.txt.zypp-query-pool.1335434122.SEMAPHORE.returncode
if [ -e /var/log/nts_SERVER1_120426_1150/updates.txt ]; then
sed -i -e "$(grep -n /var/log/nts_SERVER1_120426_1150/updates.txt.zypp-query-pool.1335434122.SEMAPHORE.out /var/log/nts_SERVER1_120426_1150/updates.txt | cut -d: -f1)r /var/log/nts_SERVER1_120426_1150/updates.txt.zypp-query-pool.1335434122.SEMAPHORE.out" /var/log/nts_SERVER1_120426_1150/updates.txt 2>/dev/null
sed -i -e "/$(basename /var/log/nts_SERVER1_120426_1150/updates.txt.zypp-query-pool.1335434122.SEMAPHORE.out)/d" /var/log/nts_SERVER1_120426_1150/updates.txt 2>/dev/null
rm -f /var/log/nts_SERVER1_120426_1150/updates.txt.zypp-query-pool.1335434122.SEMAPHORE.out
fi
rm -f /var/log/nts_SERVER1_120426_1150/updates.txt.zypp-query-pool.1335434122.SEMAPHORE
Is proxy authentication supported? Our server is behind a squid proxy with eDirectory authentication.
No, just run supportconfig with the -r and it will save locally. Copy the supportconfig off and upload it manually to ftp.novell.com or anywhere else.
SR numbers are now 12 digits long and supportconfig can no longer transmit them to Micro Focus.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-03-25 16:53
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.