|
Patch 2369 : Availmon 2.1 for IRIX 6.2 : [IRIX 6.2]
INDEX
RELATIONS
RELEASE NOTES
1. Patch SG0002369 Release Note
This release note describes patch SG0002369 to IRIX OS
version 6.2.
Patch SG0002369 replaces patches SG0002003, SG0002306.
1.1 Supported Hardware Platforms
This patch contains bug fixes for all hardware platforms
supported by IRIX OS at revision 6.2.
1.2 Supported Software Platforms
This patch contains bug fixes for IRIX 6.2. The software
cannot be installed on other configurations.
1.3 Bugs Fixed by Patch SG0002369
Descriptions of fixes in this patch include bug numbers from
Silicon Graphics bug tracking system for reference.
The following bug fixes in IRIX 6.2 are included in this
patch.
o Availmon 2.1 generates a correction report if a System
Serial Number or Hostname change is detected. This
generated report is sent to configured e-mail addresses
to notify them of change in Serial Number or Hostname.
Availmon, before sending this report, should check
whether automatic reporting is turned on. This check
is missing resulting in the correction report sent to
the configured addresses even if availmon reporting is
off (bug 516080).
The following bug fixes are included from patch SG0002307.
o Minor bug fixes to /sbin/init (bugs 453524 and 466570)
where init under heavy stress could miss signals. Over
time this resulted in all process slots being filled
with defunct processes and ultimately with a system
panic. The precise symptom is: "PANIC: init died (why
= 2, what = 0x9)" This specific symptom ("init died")
identifies the difference between this patch and patch
2003. Bug 466570 refers to a performance issue in
high stress situations in the Irix 6.4 OS release of
init from which this edition of init is derived.
The following bug fixes are included from patch SG0002003.
o Added the capability to send a "status update" report,
at a configurable period (in days), indicating that the
system is still up and running. See amconfig(1M)
"statusinterval". The default is statusinterval = 60
(days) for high end systems, and statusinterval = 0 for
low end systems, which disables sending such reports
(rfe 269570).
o Several errors by the init.d availmon script showed up
in abnormal cases, including instances of corrupted
saved information. Those errors are fixed (bugs
318047, 326347, 333777, 335887).
o Amregister could hang when it was invoked with an
invalid argument, such as "root@localhost". In such
cases, amregister now properly gives an error (bug
321958).
o Certain incomplete or unexpected message formats in
SYSLOG could cause the amsyslog command to crash.
Amsyslog is run while producing an Availmon report.
The correctness and format of every message in SYSLOG
is now checked (bugs 336199, 338326, 340193, 485937).
o Amsysinfo did not return the machine readable system
serial number for IP28 systems, since IP28 systems were
not yet released when IRIX 6.2 was released. Amsysinfo
now handles IP28 systems (bug 459861).
o Added a new "pager" report capability. This supports
sending a concise report intended for a "chatty pager",
identifying the hostname, a brief description of the
event reason, and the summary (if present). See
amconfig(1M) "autoemail.list" (rfe 463973, 463983).
The following are known problems.
o If a system is taken down to single user mode and while
in single user mode a reboot is requested, availmon
will generate a single user report followed by a reboot
report after coming back up to multi user mode. The
re-start time for the single user report, and the start
time for the reboot report are the same, the event time
of the reboot request. However, when the system is
reset while in single user mode, availmon is not able
to correctly determine the time of the reset event.
This will cause amreport to incorrectly display the
re-start time for the single user report and the start
time for the reset report (as Dec 31, 1969 or Jan 1,
1970). This will also cause computed downtime to be
incorrect in such a case.
o On older platforms which doesn't have a machine
readable serial number and which have been registered
to send availmon reports, running 'amconfig
autoemail.list' to add e-mail addresses will cause a
spurious error message to be printed out saying that
'this platform, does not have a machine-readable serial
number. Please use '-s' option'. Consequently, no
Registration Report is mailed out. The recommended
practice for older platforms (which doesn't have a
machine-readable serial number) is to add all the e-
mail addresses initially while registering.
1.4 Availmon Overview
This patch provides bug fixes for prior Availmon 2.1
patches. The functionality provided is no different from
the patch SG0002003. Patch SG0002003 provides enhanced
Availmon functionality as well as bug fixes for previous
Availmon versions. It is identified as Availmon version
2.1. Reports sent by Availmon include a field identifying
the 2.1 version. See amreport(1M) for how to verify the
installed Availmon version.
Patches SG0002368, SG0002369 and SG0002370 provide Availmon
2.1 functionality for IRIX releases 5.3, 6.2 and 6.4
respectively.
1.4.1 Availmon 2.1 Features
New features which were incorporated in patch SG0002003 of
Availmon 2.1 include the following.
System serial numbers: machine readable serial numbers are
strictly enforced. The first time Availmon 2.1 boots on a
system, if the saved serial number is not correct (that is,
if it is different from the machine readable serial number),
a special "ID correction" report will be sent, notifying of
the the corrected serial number. Thereafter, only the
correct machine readable serial number will ever be used.
Only very old hardware platforms do not provide a machine
readable system serial number.
Single-user handling: taking a system down to single-user
and then back up to multi-user will be treated as downtime,
and an availmon report will be generated. A shutdown reason
prompt will be given (if configured). From single-user, a
full reboot or a crash will be handled as a second event.
In the case of a full reboot, a second shutdown reason
prompt will be given (if configured).
Resending prior reports: amreport supports marking historic
events and resending them, by default to configured email
addresses, but allowing change of addresses for the purpose
of the resend. Availability data can always be resent.
Diagnostic information can be resent only if the appropriate
files have not been removed from the dump directory. In any
case, the resend request will always be accepted and
whatever data is available will be resent.
Amreport is significantly upgraded. In addition to the
ability to resend historic data, amreport can display all
information interactively or as a report written to standard
output. It offers an improved metrics summary that breaks
down events by categories and shows availability overall and
per category. Amreport also adds -f <timestamp> and/or -t
<timestamp> allowing "from" and/or "to" time specifications
for either interactive operation or for generated reports.
It accepts <timestamp>s in the same form as touch(1). See
amreport(1M).
Panic analysis: panics are now distinguished as one of three
kinds: panics known to be due to hardware or known to be
due to software, or panics due to unknown causes. In prior
Availmon versions, the last two panic categories were
grouped together (e.g. two categories: "hardware" and "not
hardware"). The three-valued distinction is important on
high-end platforms IP19, IP21, IP25 and IP27, where built-in
analysis of hardware error state provides the distinction of
known hardware or known software or inconclusive state.
Pager report: a simple, concise pager report is added,
designed to be sent to a chatty pager. This includes the
hostname, a brief event description, and the summary (if
available). See amconfig(1M) for how to configure sending
pager reports.
1.4.2 Registering Availmon
On reboot, Availmon 2.1 can send a report via Internet email
to SGI in Mountain View or other destinations as desired.
Information in such reports is strictly related to system
availability, and optionally may contain diagnostic
information related to the causes of the reboot.
The email addresses and other availmon actions are
configurable via the utility "amconfig" (see availmon(5) and
amconfig(1M)). It is necessary to enable sending email
reports by "registering" after installing this patch. The
default configuration will send a diagnostic report on each
reboot to "availmon@csd.sgi.com", once registered.
Follow these steps to enable Availmon sending reports:
1. After installing patchSG0002369 and rebooting the
system, run amconfig if any configuration change is
desired (see amconfig(1M)).
2. To "register" availmon and enable sending reports, run
/usr/etc/amregister -r
unless running on an old hardware platform, which can
not return a machine readable system serial number.
In that case, run
/usr/etc/amregister -r -s <serial_number>
In the event the system does not have email access,
refer to availmon(5) for configuration examples.
Generally, a reboot is required to complete the
installation. If the system is running critical
applications that can not afford the extra reboot, after
installing patchSG0002369, run
/etc/init.d/availmon start
o Note : Before running the above command, please make
sure that the process amtickerd(1M) is not running.
This process can be stopped by running
/etc/init.d/availmon stop
Then follow step 2. above to enable availmon.
1.5 Subsystems Included in Patch SG0002369
This patch release includes these subsystems:
o patchSG0002369.eoe_sw.unix
o patchSG0002369.eoe_man.unix
1.6 Installation Instructions
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed
in this patch (see Section 1.3), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 and 1.2 of these release
notes, you are unsure whether your hardware and software
meet the requirements for installing a particular patch, run
inst. The inst program does not allow you to install
patches that are incompatible with your hardware or
software.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your Software
Installation Administrator's Guide to bring up the miniroot
form of the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst> prompt, type
install patchSGxxxxxxx
where xxxxxxx is the patch number.
2. Initiate the installation sequence. Type
Inst> go
3. You may find that two patches have been marked as
incompatible. (The installation tools reject an
installation request if an incompatibility is
detected.) If this occurs, you must deselect one of
the patches.
Inst> keep patchSGxxxxxxx
where xxxxxxx is the patch number.
4. After completing the installation process, exit the
inst program by typing
Inst> quit
1.7 Patch Removal Instructions
To remove this patch, donot use the versions remove command
as you would for any other software subsystem. Instead,
removal of this patch should be done from the interactive
version of 'inst'. The removal process reinstates the
original version of software unless you have specifically
removed the patch history from your system.
1. At the Inst> prompt, type
remove patchSGxxxxxxx
where xxxxxxx is the patch number.
2. Initiate the removal sequence. Type
Inst> go
3. After completing the removal process, exit the inst
program by typing
Inst> quit
To keep a patch but increase your disk space, use the
versions removehist command to remove the patch history.
versions removehist patchSGxxxxxxx
where xxxxxxx is the patch number.
1.8 Known Problems INST SUBSYSTEM REQUIREMENTS No Requirements Information Available. INST SUBSYSTEM CHECKSUMS These checksums help to provide a 'signature' for the patch inst image which can be used to authenticate other inst images. You can obtain this kind of output by running sum -r on the image (from the command line): 34719 2 patchSG0002369 45530 67 patchSG0002369.eoe_man 15785 713 patchSG0002369.eoe_sw 34454 18 patchSG0002369.idb INST SUBSYSTEM FILE LISTINGS The following lists the files which get installed from each subsystem in the patch:
DOWNLOAD PATCH
|
||||||||||||||||||||||||||||||||||||
Document Id: 20021117070030-IRIXPatch-1130
|
||||||||||||||||||||||||||||||||||||