IBM Tivoli Monitoring: Unix(R) Log Agent 6.2.3.1-TIV-ITM_UXLOG-IF0004

Downloadable files


Abstract

This fix resolves the APARs and defects listed in the "Problems Fixed" section below.

Download Description

(C) Copyright International Business Machines Corporation 2013.

All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) Log Agent,
Version 6.2.3.1

Component ID: 5724C04LA

Interim Fix 6.2.3.1-TIV-ITM_UXLOG-IF0004

Date: March 15, 2013

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices


1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below.

2.0 Problems fixed
============
The following problems are addressed by this fix.

2.1 APARs
-------------
APAR: IV33926
Abstract: AGENT HANGS WHEN TEP DISPLAYS ERRLOG
Problem Description: On AIX systems, when displaying the ERRLOG
entries in the Tivoli Enterprise Portal, the IBM Tivoli
Monitoring Unix Log (UL) Agent can hang
This problem can be evidenced from the procstack output
for kulagent process. The stack trace will show a lock in the
RAS1 function called by the ErrLogFile::createChildForReport()
function.

APAR: IV35538
Abstract: UNIX LOG CAN SEND OLD EVENTS IF MONITORED LOG FILE IS
MODIFIED WHILE CLOSING AND REOPENING HANDLE ON MONITORED LOG
Problem Description: The Monitoring Agent for UNIX Logs can send old
events if another process modify the monitored log while kulagent
is closing and opening handle on the monitored log.

APAR: IV36445
Abstract: UNIX LOG IS NOT REPORTING ALL LOGS REQUESTED IN KUL_CONFIGFILE
Problem Description: On AIX the Monitoring Agent for UNIX Logs kulagent
process fails to detect and monitor some log files requested in the
kul_configfile. When it happens the following messages appear in the
kulagent log files:

(510832EA.0027-2:validlog.cpp,283,"extractTokens") Field separator
missing after field 3 for log . Skipping rest of line.

2.2 Defects
--------------
None.

2.3 Superseded fixes
-------------------------
6.2.3.1-TIV-ITM_UXLOG-LA0003 (not shipped)
6.2.3.1-TIV-ITM_UXLOG-LA0002 (not shipped)
6.2.3.1-TIV-ITM_UXLOG-LA0001

2.4 Superseded APARs
-------------------------
6.2.3.1-TIV-ITM_UXLOG-LA0001
----------------------------
APAR: IV14925
Abstract: PART OF LOG RECORDS NOT DISPLAYED IF LONGER THAN 2048
Problem Description: In the user-defined logs (with type U in the kul_configfile
configuration file), if a record is longer than 2048 characters, the
Unix Log agent stops processing the file and all the previous records
are not displayed.


APAR: IV14927
Abstract: PART OF LOG RECORDS NOT DISPLAYED IF 10 CONSECUTIVE FORMATTING ERRORS
Problem Description: In the user-defined logs (the type U in the kul_configfile
configuration file), if more than 10 consecutive records do not respect
the formatting rules, the Unix Log agent stops processing the file and
all the previous records are not displayed.
To fix this problem, the maximum value of formatting errors was increased
to 100 (default value).
In addition to that, a new configuration variable KUL_MAX_FORMAT_ERRORS
has been defined for the kul.ini configuration file.
The KUL_MAX_FORMAT_ERRORS variable can contain the maximum number of
consecutive records with formatting errors that can be found before stopping
the processing of the user defined log.


APAR: IV24706
Abstract: UNIX LOG AGENT ON AIX READ THE CONFIG FILE IN WRONG MODE WHEN IS PRESENT
A COMPLEX LOG PROCEDURE
Problem Description: Unix Log Agent on AIX reads the config file in wrong mode when
a complex log procedure is present, due to the use of an not thread-safe
api. For instance a user log file (;u) can be wrongly interpreted as a
system log (;s).


APAR: IV27935
Abstract: ITM UNIX LOG AGENT IS HANGING
Problem Description: Due to a side effect between the fork() and exec() functions
and the trace log file by ITM, the Unix Log agent may hang and it does not
stop when requested. This is happening on AIX systems when situations
monitoring the ERRLOG system log are started.


APAR: IV30645
Abstract: UNIX LOG AGENT CLOSE AND RESCAN FROM THE BEGINNING A LOG FILE
Problem Description: Unix Log Agent close the monitored log file and
starts again to scan it from the beginning.

3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM
Tivoli Monitoring: Monitoring Agent for UNIX Logs User's Guide,
version 6.2.3.1


The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring : Monitoring Agent for UNIX Logs, version 6.2.3.1


4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.3.1-TIV-ITM_UXLOG-IF0004.README - This README file
- 6.2.3.1-TIV-ITM_UXLOG-IF0004.tar - Fix archive .tar format
- 6.2.3.1-TIV-ITM_UXLOG-IF0004.zip - Fix archive .zip format


Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file if
you are working in a Windows(R) environment.

The fix archive file contains the following files:
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_aix523_tema_if0004.tar - Binaries for 32-bit AIX
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_aix526_tema_if0004.tar - Binaries for 64-bit AIX
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_hp116_tema_if0004.tar - Binaries for 64-bit HP-UX
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_hp11_tema_if0004.tar - Binaries for 32-bit HP-UX
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_hpi116_tema_if0004.tar - Binaries for HP-UX on Itanium
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_li6243_tema_if0004.tar - Binaries for 32-bit Linux on Intel®
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_li6263_tema_if0004.tar - Binaries for 32-bit Linux 2.6 on Intel®
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_lia266_tema_if0004.tar - Binaries for Linux on Itanium
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_lpp266_tema_if0004.tar - Binaries for Linux on PowerPC®
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_ls3243_tema_if0004.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_ls3246_tema_if0004.tar - Binaries for 64-bit Linux on zSeries
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/klz_ls3263_tema_if0004.tar - Binaries for 32-bit Linux (2.6 kernels) on zSeries
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/klz_ls3266_tema_if0004.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_lx8266_tema_if0004.tar - Binaries for Linux on AMD
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_sol283_tema_if0004.tar - Binaries for 32-bit Solaris
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_sol286_tema_if0004.tar - Binaries for 64-bit Solaris
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_sol606_tema_if0004.tar - Binaries for Solaris on AMD
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulaix513.dsc - Descriptor file for 32-bit AIX
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulaix516.dsc - Descriptor file for 64-bit AIX
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulhp11.dsc - Descriptor file for 32-bit HP-UX
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulhp116.dsc - Descriptor file for 64-bit HP-UX
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulhpi116.dsc - Descriptor file for HP-UX on Itanium
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulli6243.dsc - Descriptor file for 32-bit Linux on Intel
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulli6263.dsc - Descriptor file for 32-bit Linux 2.6 on Intel
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kullia266.dsc - Descriptor file for Linux on Itanium
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kullpp266.dsc - Descriptor file for Linux on PowerPC
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulls3243.dsc - Descriptor file for 32-bit Linux on zSeries
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulls3246.dsc - Descriptor file for 64-bit Linux on zSeries
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kullx8266.dsc - Descriptor file for Linux on AMD
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulsol283.dsc - Descriptor file for 32-bit solaris
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulsol286.dsc - Descriptor file for 64-bit solaris
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/kulsol606.dsc - Descriptor file for solaris on AMD
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/klzls3263.dsc - Descriptor file for 32-bit Linux on zSeries
- 6.2.3.1-TIV-ITM_UXLOG-IF0004/klzls3266.dsc - Descriptor file for 64-bit Linux on zSeries


Each tar or cab file has updates to the IBM Tivoli Enterprise Monitoring
Server component for a specific platform. The platform that each file
applies to is included in its name.


5.0 Installation instructions
==================

This fix can only be installed over an existing installation. Use
the following steps to install this fix.

5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> points to
the IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Since there is no uninstall utility for this fix, we suggest you
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file (6.2.3.1-TIV-ITM_UXLOG-IF0004.tar
or .zip) to a temporary directory on the system that contains the
agent code to be updated. For the purpose of this README, the
symbol <TEMP> represents the fully qualified path to this
directory. Note: On Windows, this includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Use the itmpatch command to install the fix for the operating
system of that agent. For more information on the itmpatch command,
see section [6.2].

For example:
On a UNIX system, if the fix was expanded to
<TEMP>/6.2.3.1-TIV-ITM_UXLOG-IF0004,
the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.3.1-TIV-ITM_UXLOG-IF0004/kul_xxxxxx_tema_if0004.tar


where:
- xxxxxx corresponds to the value in the first column returned
by the ./cinfo -i command.

In the following example, the file would be kul_li6243_tema_if0004.tar.
> ./cinfo -i
Monitoring Agent for Unix Log
li6243 Version: 06.23.01.00


5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.2.3.1-TIV-ITM_UXLOG-IF0004.tar
or .zip) to a temporary directory on the IBM Tivoli Enterprise
Monitoring Server system. For the purpose of this README, the
symbol <TEMP> represents the fully qualified path to this
directory.

2. Expand the archive file using the tar command on UNIX systems or
an unzip utility on Windows systems. This creates a directory
structure that contains fixes for all of the supported platforms.

3. To add the agent fix bundles into the remote deploy depot, use
the tacmd addBundles command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the tacmd addBundles command, see the IBM Tivoli
Monitoring Command Reference Guide.

On UNIX systems,
if the fix was expanded to <TEMP>/6.2.3.1-TIV-ITM_UXLOG-IF0004:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.3.1-TIV-ITM_UXLOG-IF0004

On a Windows system,
if the fix was expanded to <TEMP>\6.2.3.1-TIV-ITM_UXLOG-IF0004:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.3.1-TIV-ITM_UXLOG-IF0004

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Command Reference Guide.

For example:
On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.

> $CANDLEHOME/bin/tacmd updateAgent -t ul
-n <Managed system name>
-v 06230104

On a Windows system:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t ul
-n <Managed system name>
-v 06230104

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters UL, not three characters KUL.
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.


5.4 Agent support update
----------------------------
There are no agent support updates for the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server or Tivoli
Enterprise Portal Desktop included in this fix or any of the
superseded fixes. No additional installation steps are required.


6.0 Additional installation information
========================

6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.


6.2 Additional information on using itmpatch command
--------------------------------------------------------------
The itmpatch command has the following syntax.

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch.


For example, on UNIX systems:
<CANDLEHOME> points to the IBM Tivoli Monitoring installation directory
<TEMP> points to the temporary directory where the fix is located.

- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows, this must include the drive
letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows, this must include the drive letter.

6.3 Verifying the update
----------------------------
1. To verify the agent was updated correctly, use the tacmd command
to view the agent's current version after the agent is restarted.
You are required to login to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory. The default location is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t UL

On a Windows system, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory. The default location
is 'C:\IBM\ITM'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t UL

When the agent update is successful, the agent version is:
06.23.01.04.

Note:
- The component (-t) for the tacmd listSystems command is specified
as two characters UL, not three characters KUL.



On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

*********** Mon April 30 04:02:21 EDT 2011 ******************
User: root Groups: sys root other bin adm daemon mail lp users
Host name : mybox_dev Installer Lvl:06.23.01.00
CandleHome: /data/rthan/ITM623FP1
******************************************************
...Product inventory

ax IBM Tivoli Monitoring Shared Libraries
hp116 Version: 06.23.01.00

jr Tivoli Enterprise-supplied JRE
hp11 Version: 05.05.00.00

ui Tivoli Enterprise Services User Interface
hp116 Version: 06.23.01.00

ul Monitoring Agent for Unix Log
hp116 Version: 06.23.01.04



7.0 Known problems and workarounds
=========================
None.

8.0 Additional product information
==================================
This Limited Availability/Interim fix is being provided for the IBM Tivoli Monitoring,
Unix Log agent at Version 6.2.3.1. This LA/IF fix is provided as a temporary solution
until the official maintenance release is made generally available.
When performing any code maintenance it is critical that you validate that the
APAR(s)from your LA/IF fix are contained in the maintenance package you are about
to deploy to avoid any code regressions.


9.0 Notices
=======
This information was developed for products and services offered in the United
States. IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for information
on the products and services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

Trademarks and Service Marks
------------------------------------

IBM, the IBM logo, and ibm.com(R) are trademarks or registered
trademarks of International Business Machines Corporation in the
United States, other countries, or both. If these and other IBM
trademarked terms are marked on their first occurrence in this
information with a trademark symbol (R or TM), these symbols
indicate U.S. registered or common law trademarks owned by IBM
at the time this information was published. Such trademarks may
also be registered or common law trademarks in other countries.
A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at
http://www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.

Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Prerequisites

IBM Tivoli Monitoring Version 6.2.3 Fix Pack 1 (6.2.3-TIV-ITM-FP0001)

Installation Instructions

Please refer to the 6.2.3.1-TIV-ITM_UXLOG-IF0004.README contained in the Description section above for general installation instructions.

Download package

Fix Central is a new way to acquire fixes. In the future it will be the only option for downloading fixes, but for now we are including it as an additional download option. The two main differences from the current download options will be the FTP option will be replaced by HTTP and that you will need to use an IBM registered ID. The reason for this, is we can use Fix Central to notify you if there is a problem with the fix. Privacy is maintained.

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.3.1-TIV-ITM_UXLOG-IF0004 15 Mar 2013 English 10620926 FC

Product Alias/Synonym

IBM Tivoli Monitoring Unix Log agent

Problems (APARS) fixed
IV33926 IV35538 IV36445

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Components
ITM Agent UNIX Log Alert V6

Software version:

6.2.3.1

Operating system(s):

AIX, HP-UX, Linux, Solaris

Reference #:

4036844

Modified date:

2014-01-20

Translate my page

Machine Translation

Content navigation