Created On: 24 June 2011
Problem:
A large amount of information is required to form a complete set of Enterprise Server diagnostics. The collation of these can be laborious. Is there an example that can be used?
Resolution:
The attached script (essupport5.2.sh) has been in the public domain for a few years as version 1. This version has been re-engineered and adds support for 64-bit Enterprise Server as and when available. It has been in use for over a year with a low failure rate usually related to other installation issues. Of particular importance when using the script are:
The script uses a temporary work directory which can be modified by changing the first entry $WRKDIR. This directory should exist. The script should be run as the Enterprise Server Administrator and will exit if run as root. If gzip is not available, the script terminates with a message. In this case, the tar file containing the diagnostics can be found in $WRKDIR
A quick way to unpack a trz file is to change the suffix to .Z and gunzip –d to unpack the image to a tar file (which will have no suffix).
The script uses a temporary work directory which can be modified by changing the first entry $WRKDIR. This directory should exist. The script should be run as the Enterprise Server Administrator and will exit if run as root. If gzip is not available, the script terminates with a message. In this case, the tar file containing the diagnostics can be found in $WRKDIR
A quick way to unpack a trz file is to change the suffix to .Z and gunzip –d to unpack the image to a tar file (which will have no suffix).
Attachments
Old KB# 14582
#MFDS
#EnterpriseDeveloper