chunk_id stringlengths 3 7 | chunk stringlengths 1 850 | source_url stringclasses 601
values | title stringclasses 1
value | chunk_idx int64 0 433 | chunk_start_char int64 0 178k | chunk_end_char int64 70 178k |
|---|---|---|---|---|---|---|
66_2 | .0 Additional product information
9.0 Copyright and trademark information
10.0 Notices
1.0 General description
===============
This fix pack adds support for a Windows x86-64 bit (WIX64) and PowerPC
little-endian Log File agent. In addition, it resolves the APARs and
defects listed in the "Problems Fixed" section b... | TRAIN_Q066 | 2 | 783 | 1,248 | |
66_3 |
2.1 APARs
-------------
APAR: IV96363
Abstract: AGENT CRASHES ON WINDOWS 2016 WHILE READING LOG
Additional information: The agent crashes when a second file close
attempt follows a successful close of the monitored log.
Any subsequent I/O operations, such as fseek, fgets, fclose,
etc, either on that thread or anothe... | TRAIN_Q066 | 3 | 1,248 | 1,699 | |
66_4 | The failure
sometimes results in an fgetpos failure with "errno 9 'Bad
file descriptor'" and returns with a -1.
This has been seen more prevalently on Windows 2016 but
might occur on other platforms. This is related to IV60331. | TRAIN_Q066 | 4 | 1,699 | 1,929 | |
66_5 |
On the agent system, with a minimum of the following trace:
"ERROR (UNIT:kumpfile ALL) (UNIT:kum0fdp0 ALL)" enabled, the
agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
shows trace points similar to the following:
- - -
...
...:kum0fdp0.c,76,"KUM0_FileClose") IOE 5619070 file handle
7C3AB428 ... | TRAIN_Q066 | 5 | 1,929 | 2,282 | |
66_6 | 0.c,111,"KUM0_FileClose") SEptr 5613548 local file
D:/Log/WAS/AppSrv01/nodeagent/SystemOut.log IOptr 5619070
7C3AB428 closed unsuccessfully
...:kum0fdp0.c,82,"KUM0_FileClose") File close failed for IOE
@5619070, status code -1, errno 0 'No error'
...:kum0fdp0.c,111,"KUM0_File | TRAIN_Q066 | 6 | 2,282 | 2,561 | |
66_7 | Close") SEptr 5613548 local file
D:/Log/WAS/AppSrv01/nodeagent/SystemOut.log IOptr 5619070
7C3AB428 closed unsuccessfully
...
- - -
APAR: IV95005
Abstract: "DETECTED CODEPAGE CP943, USING CP932 INSTEAD TO MAP
BACKSLASH TO U+005C, NOT U+00A5 (YEN SYMBOL)" LOGGED ON
EVERY READ
Additional information: With a locale... | TRAIN_Q066 | 7 | 2,561 | 2,884 | |
66_8 | Ja_JP (Shift-JIS) and
ERROR level trace, when the data is in the local code page,
the following message appears in agent RAS1 log for each
monitored event processed:
"Detected codepage CP943, using CP932 instead to map
backslash to U+005C, no U+00A5 (Yen symbol)".
This occurs on the agent system, with only ERROR tr... | TRAIN_Q066 | 8 | 2,884 | 3,216 | |
66_9 | The agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following:
- - -
...
kum0nget.c,438,"TranslateStringToUTF8") Detected codepage
CP943, using CP932 instead to map backslash to U+005C, not
U+00A5 (Yen symbol)
...
- - -
APAR: IV93401
Abstract: USING ... | TRAIN_Q066 | 9 | 3,216 | 3,568 | |
66_10 | OTE FILE FAILS
WITH FILE NOT FOUND
Additional information: Using RegexLogSources to monitor a remote
file fails with "*** Unable to obtain statistics for file
</LFA_test_logs/test_1.log> errno 2 'No such file or
directory". This occurs right after the file has been found
and matched. (Note: if the monitored file is a... | TRAIN_Q066 | 10 | 3,568 | 4,006 | |
66_11 |
On the agent system, with a minimum of the following trace:
"ERROR (UNIT:kumpdcm2 ALL) (UNIT:kum0dir ALL)" enabled, the
agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
trace points similar to the following:
- - -
...
...:kumpdcm2.c,195,"KUMP_GetNextMember") Directory 7F3B3401C380
/... | TRAIN_Q066 | 11 | 4,006 | 4,378 | |
66_12 | _1.log$>
...:kumpdcm2.c,211,"KUMP_GetNextMember") Directory handle
7F3B3401C380
name /LFA_test_logs successfully matched <test_1.log> to pattern
<^test_1.log$>
...:kumpdcm2.c,217,"KUMP_GetNextMember") Exit: 0x0
...:kumpdcm2.c,301,"KUMP_GetNextMemberDouble") Retcode 0
Directory
/LFA_test_logs Member <test_ | TRAIN_Q066 | 12 | 4,378 | 4,692 | |
66_13 | 1.log> matched ^test_1.log$
...:kumpdcm2.c,330,"KUMP_GetNextMemberDouble") Directory
7F3B3401C380
/LFA_test_logs member successfully matched <test_1.log> pattern
<^test_1.log$>
...:kumpdcm2.c,335,"KUMP_GetNextMemberDouble") Exit: 0x0
...:kum0dir.c,143,"KUM0_stat_withMsgFlag") *** Unable to obtain
statistics for ... | TRAIN_Q066 | 13 | 4,692 | 5,022 | |
66_14 | _test_logs/test_1.log> errno 2 'No such
file or directory'
...:kum0dir.c,192,"KUM0_stat_withMsgFlag") Unsuccessfully stat
file
/LFA_test_logs/test_1.log size=0 access time=0, modification
time=0,
creation time=0
...:kumpdcm2.c,481,"KUMP_DetermineCurrentMonitorFileNameStrict")
File
/LFA_test_logs/test_1.log ski... | TRAIN_Q066 | 14 | 5,022 | 5,390 | |
66_15 |
Abstract: INVALID CHARACTERS SEEN IN THE TRACE "*****Error:
u_strFromUTF8 failed for string ... - <filename> .........,
status 10 <U_INVALID_CHAR_FOUND>"
Additional information: In the agent RAS1 log, the trace points
"*****Error: u_strFromUTF8 failed for string ..... -
<filename> ..., status 10 <U_INVALID_CHAR_FO... | TRAIN_Q066 | 15 | 5,390 | 5,856 | |
66_16 |
Since these messages might occur when the agent is processing
a directory listing in order to determine the current file
to monitor as a result of a wildcard character in the
RegexLogSources parameter, if the <filename> that results
in this error is a file that should be monitored, then events
would be lost as the... | TRAIN_Q066 | 16 | 5,856 | 6,432 | |
66_17 |
On the agent system, with a minimum of the following
trace enabled: "ERROR (UNIT:kum0regx ALL)", the agent RAS1
log <hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
shows trace points similar to the following with some extra
characters added ".lnk":
-----
...:kum0regx.c,286,"KUM0_IsRegExPatternMatch")
****... | TRAIN_Q066 | 17 | 6,432 | 6,820 | |
66_18 | lnkÙl ÙsÙw pRegEx @4D05810 status 10 <U_INVALID_CHAR_FOUND>
---
APAR: IV79204
Abstract: LOGS RE-READ FROM THE BEGINNING WHEN DAYLIGHT SAVING
TIME (DST) ENDS
Additional information: On Windows systems, when daylight saving
time ends, log files might be re-read from the beginning
resulting in old events being re-sent.... | TRAIN_Q066 | 18 | 6,820 | 7,181 | |
66_19 |
The agent falsely detects that the configuration (.conf)
and format (.fmt) file have changed when the system is
configured to "Automatically adjust clock for Daylight
Saving time" and the file timestamps automatically change
triggering an agent reset. When NumEventsToCatchUp is set
to -1, this series of events ca... | TRAIN_Q066 | 19 | 7,181 | 7,726 | |
66_20 |
To resolve this issue you must install and use the Windows
WIX64 (x86-64 bit) agent or specify NumEventsToCatchUp=-2
in the configuration file as a work-around. | TRAIN_Q066 | 20 | 7,726 | 7,889 | |
66_21 |
APAR: IV77403
Abstract: WINDOWS EVENT LOG EVENTS ARRIVED DELAYED WHEN
NUMEVENTSTOCATCHUP IS USED
Additional information: With a large input load (for example,
8004 events on each of 4 threads), Windows Event Log events
arrive with a significant delay when NumEventsToCatchUp=-1
is set in the conf file. The delay in... | TRAIN_Q066 | 21 | 7,889 | 8,303 | |
66_22 | This is a result of the inherent overhead in
maintaing the position (bookmark) in the Windows Event Log
when NumEventsToCatchUp is set to -1 or n.
This is a follow-on to APAR IV63704.
APAR: IV76731
Abstract: UNABLE TO RENAME FILE WHICH IS BEING MONITORED BY ITM
LOG FILE AGENT
Additional information: On Windows sy... | TRAIN_Q066 | 22 | 8,303 | 8,746 | |
66_23 | When new
records are added to the log, the agent opens the log,
reads the log and closes the log. However, when a large
volume of events are written to the log file, the log file
may remain open or in use due to operating system
efficiencies. As a result, an attempt to rename the log
file may fail. This problem occu... | TRAIN_Q066 | 23 | 8,746 | 9,150 | |
66_24 |
To minimize occurrence of this issue, use the Windows (WIX64)
x86-64 bit Log File agent.
APAR: IV60331
Abstract: RESETTING OF MULTIPLE CONF/FORMAT FILES CAUSES A CRASH
Additional information: Updating multiple configuration (.conf)
or format (.fmt) files, usually via a script or a situation
that runs frequently,... | TRAIN_Q066 | 24 | 9,150 | 9,534 | |
66_25 | This also might be more likely
to occur with multiple subnodes to monitor a large number
of files, for example, 100 files. The root cause of the
crash is closing a file which is already closed or no longer
exists.
This has been seen, mainly on Linux, on agent start-up,
shutdown or reset as a result of configuration... | TRAIN_Q066 | 25 | 9,534 | 9,936 | |
66_26 |
The <hostname>_lo_<#########>.log might contain information
similar to the following:
*** glibc detected *** /opt/IBM/ITM/lx8266/lo/bin/kloagent:
double free
or corruption (out): 0x00007f222d727030 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3c158760e6]
/lib64/libc.so.6[0x3c15878c13] | TRAIN_Q066 | 26 | 9,936 | 10,237 | |
66_27 |
/lib64/libc.so.6(fclose+0x14d)[0x3c1586674d]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(kum_fclose+0x97)[0x7f222
42a68db]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_ReleaseIOResources+
0x430)[0x7f2224275444]
| TRAIN_Q066 | 27 | 10,237 | 10,451 | |
66_28 | /opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_ReleaseSourceResour
ce+0xae1)[0x7f22242799d1]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_FileServer+0x7114)[
0x7f2224250f30]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(+0xb9b56)[0x | TRAIN_Q066 | 28 | 10,451 | 10,679 | |
66_29 | 7f222427fb56
]
/lib64/libpthread.so.0[0x3c16007851]
/lib64/libc.so.6(clone+0x6d)[0x3c158e890d]
. . .
2.2 Defects
--------------
None. | TRAIN_Q066 | 29 | 10,679 | 10,818 | |
66_30 |
2.3 Enhancements
----------------------
Enhancement: IV77403, IV76731
Abstract: Add Support for Windows x86-64 bit (WIX64) Agent
Additional Information: Support was added for Windows x86-64 bit
(WIX64) agent. This addresses APARs IV76731 and IV77403. | TRAIN_Q066 | 30 | 10,818 | 11,071 | |
66_31 |
Enhancement: 216440
Abstract: Add Support for PowerPC little-endian (PPCLE)
Additional Information: Support was added for PowerPC little-endian. | TRAIN_Q066 | 31 | 11,071 | 11,217 | |
66_32 |
2.4 Superseded fixes
-------------------------
6.3.0-TIV-ITM_LFA-FP0001
6.3.0-TIV-ITM_LFA-IF0005
6.3.0-TIV-ITM_LFA-IF0004
6.3.0-TIV-ITM_LFA-IF0003
6.3.0-TIV-ITM_LFA-IF0002
6.3.0-TIV-ITM_LFA-IF0001
2. | TRAIN_Q066 | 32 | 11,217 | 11,419 | |
66_33 | 4 APARs and defects included from superseded fixes
---------------------------------------------------------------
6.3.0-TIV-ITM_LFA-FP0001
------------------------
APAR: IV82875
Abstract: WINEVENTLOG REREAD FROM BEGINNING ON AGENT RESTART
Additional information: When monitoring Windows® Event Logs, the
event log is... | TRAIN_Q066 | 33 | 11,419 | 11,831 | |
66_34 | This occurs
on Microsoft Windows 2003 or 2008 systems with the following
settings in the agent configuration file:
- WINEVENTLOGS=<named event logs>
- NumEventsToCatchUp=-2
- UseNewEventLogAPI=n (must be set on Windows 2008 systems)
Note: NumEventsToCatchUp=-2 is not supported for Windows
Event logs. | TRAIN_Q066 | 34 | 11,831 | 12,139 | |
66_35 |
Problem Determination: On the LO agent system, with a
minimum of the following trace specification:
KBB_RAS1: ERROR (UNIT:WinLogQuery ALL)
the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
trace points similar to the following:
- - -
...
...:winlogqueryclass.cpp,2521,"WinLogQuery... | TRAIN_Q066 | 35 | 12,139 | 12,552 | |
66_36 | Starting with oldest instead
...
- - -
APAR: IV82170
Abstract: SOME EVENTS ARE NOT DETECTED WHEN BOTH MULTI-LINE AND
SINGLE-LINE FORMATS ARE USED
Additional information: When using a format file which contains
both multi-line and single line formats, some events might
not be detected and are discarded. In this ca... | TRAIN_Q066 | 36 | 12,552 | 12,972 | |
66_37 | The single lines were discarded
because the number of lines remaining to be processed was
less than or equal to (not greater than) the maximum number
of lines in the multi-line format.
This problem was discovered using errpt, but it can occur
with other pipes such as syslog, or with a monitored file.
It occurs on L... | TRAIN_Q066 | 37 | 12,972 | 13,364 | |
66_38 |
Problem Determination: On the LO agent system, with a
minimum of the following trace specification:
KBB_RAS1: ERROR (UNIT:logmonitor ALL)(UNIT:kumrmfr ALL)(UNIT:kumpfile ALL)
the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
all the lines are read into the buffer properly. | TRAIN_Q066 | 38 | 13,364 | 13,674 | |
66_39 | Records
are processed until the ReadCount is equal to the
AttributeSetCount, and then the next "File Data Record" is
empty, even though more unprocessed data was still in the
buffer. | TRAIN_Q066 | 39 | 13,674 | 13,859 | |
66_40 |
- - -
...
...:kumprmfr.c,449,"KUMP_ReadMonitorFileUnicodeRecord")
<0x1111746D0,0x2FF>
...
...:kumprmfr.c,454,"KUMP_ReadMonitorFileUnicodeRecord") Read
767 bytes :
Elapsed Time: 0.000425 sec CPU Time: 231 usec
...
...
...
...:kumprmfr.c,1112,"KUMP_ReadMonitorFileUnicodeRecord")
| TRAIN_Q066 | 40 | 13,859 | 14,150 | |
66_41 | DlmRecordMode 0 ReadCount 5 DlmRecordDetected 0 PEptr @11103E450
ShutDownPending 0 AttributeSetCount 5 RecordSetWaitCount 0
FileMonitorFrequency 5
...
...:kumprmfr.c,1153,"KUMP_ReadMonitorFileUnicodeRecord")
File EOF switch set
...:kumprmfr.c,1182,"KUMP_ReadMonitorFileUnicodeRecord") Exit:
0x111941E8
...:kumpfil... | TRAIN_Q066 | 41 | 14,150 | 14,479 | |
66_42 | KUMP_FileServer") <0x1111941E8,0x0>
File Data Record:
...
- - -
APAR: IV81364
Abstract: PROCESS PRIORITY CLASS SETTINGS NOT REFLECTED OR SET
FOR LOG FILE AGENT PROCESS
Additional information: After configuring the Process Priority
class value, the agent process running on Red Hat Linux
does not set the correspondi... | TRAIN_Q066 | 42 | 14,479 | 14,906 | |
66_43 |
For example, after configuring the agent and setting the
ProcessPriorityClass in the configuration file or during
configuration to "D":
When the ps command is issued, the priority of the agent
process remains same:
# ps -eo priority,nice,comm,args,pid,time | grep kloagent
20 0 kloagent /opt/IBM/ITMfLFA/lx8266/l... | TRAIN_Q066 | 43 | 14,906 | 15,352 | |
66_44 | _RAS1= ERROR (UNIT:logmonitor ALL) (UNIT:Utilities ALL)
the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
trace points similar to the following:
- - -
...
...:logmonitorqueryclass.cpp,479,"setProcessPriority") New*
conf file = /opt/IBM/ITM/config/test_lo.conf , fmt file =
/opt/IBM/ITM/... | TRAIN_Q066 | 44 | 15,352 | 15,752 | |
66_45 | Priority") New*
ProcessPriorityClass setting D found. | TRAIN_Q066 | 45 | 15,752 | 15,806 | |
66_46 |
...:logmonitorqueryclass.cpp,532,"setProcessPriority") New*
set process priority value -5
...:utilities.cpp,517,"Utilities::setPriority") Active RAS1
Classes: EVERYT EVERYE EVERYU
...:utilities.cpp,517,"Utilities::setPriority") Entry
...:utilities.cpp,540,"Utilities::setPriority") Successfully
set process priori... | TRAIN_Q066 | 46 | 15,806 | 16,225 | |
66_47 | 423
Abstract: Add support for Linux PowerPC (lpp266)
Additional Information: The agent is now supported running on
Linux PowerPC Red Hat 7.1.
Feature: 216820
Abstract: Upgrade to Installer v6.2.3 FP0005
Additional Information: Upgrade to an Installer which contains
installer APAR IV67172 and provisional APAR IV6561... | TRAIN_Q066 | 47 | 16,225 | 16,577 | |
66_48 |
The following error might have been seen when running
install.sh:
================================================
ITM home directory "/opt/IBM/ITM" already exists.
OK to use it [ 1-yes, 2-no; "1" is default ]? 1
cut: fields and positions are numbered from 1
Try 'cut --help' for more information.
install.sh failure:... | TRAIN_Q066 | 48 | 16,577 | 16,952 | |
66_49 |
================================================
6.3.0-TIV-ITM_LFA-IF0005
------------------------
APAR: IV78340
Abstract: EVENT ARRIVAL DELAYED DUE TO CPU THROTTLING
Additional information: After a system reboot which includes
automatic start-up of a Log File Agent instance, events
become increasingly delayed from... | TRAIN_Q066 | 49 | 16,952 | 17,301 | |
66_50 |
The root cause of the delay is the CPU throttling, which
occurs even when the Process maximum CPU percentage is
configured at 100%, the default which indicates no CPU
throttling, because at that point internally the maximum CPU
is reset to zero. This can occur with only a light flow rate
of events.
It was discovered... | TRAIN_Q066 | 50 | 17,301 | 17,707 | |
66_51 |
Problem Determination: With a minimum of the following trace
enabled: "KBB_RAS1=ERROR (UNIT:kumpcpu ALL) (UNIT:kumpscan ALL)
(UNIT:kumpinit ALL)", the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following:
- - -
...
...:kumpcpu.c,634,"KUMP_hpux_get... | TRAIN_Q066 | 51 | 17,707 | 18,070 | |
66_52 | 0 0 i 0 0 u 0 210142401 s 0 50284806 i 0
16652382
...:kumpcpu.c,486,"KUMP_GetCPUTimeDiff") cpu time diff 692698
second 0 277079589; first 0 0
...:kumpcpu.c,486,"KUMP_GetCPUTimeDiff") cpu time diff 692698
second | TRAIN_Q066 | 52 | 18,070 | 18,286 | |
66_53 | 0 277079589; first 0 0
...:kumpcpu.c,486,"KUMP_GetCPUTimeDiff") cpu time diff 2003
second 0 277079589; first 0 276278019
...:kumpcpu.c,332,"KUMP_UpdateProcessTime") Process utilization
0.000000%; Changing the dampening wait from 0 milliseconds to 1
milliseconds
...
- - -
APAR: IV | TRAIN_Q066 | 53 | 18,286 | 18,573 | |
66_54 | 76119
Abstract: REMOVAL OF RC4 CIPHER FROM REMOTE MONITORING
Additional information: The arcfour (RC4) cipher algorithm, as used
in the TLS protocol and SSL protocol, could allow a remote
attacker to obtain sensitive information. Successful
exploitation could allow an attacker to retrieve sensitive
information. This vu... | TRAIN_Q066 | 54 | 18,573 | 19,018 | |
66_55 |
APAR: IV75776
Abstract: UNABLE TO OBTAIN MONITORED FILE STATISTICS ERROR WHEN FILE
NAME CONTAINS DOUBLE-BYTE CHARACTERS
Additional information: When monitoring a file which contains
Japanese or double-byte characters in the filename, the
message "Unable to obtain statistics for file < <filename> >
errno 2 'No such ... | TRAIN_Q066 | 55 | 19,018 | 19,482 | |
66_56 |
This occurs on Log File Agent version 6.3.0 and is platform
independent. | TRAIN_Q066 | 56 | 19,482 | 19,557 | |
66_57 |
Problem Determination: With a minimum of the following trace
enabled: "KBB_RAS1=ERROR (UNIT:kum0dir ALL)", the agent RAS1
log <hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following:
- - -
...
...:kum0dir.c,147,"KUM0_stat_withMsgFlag") *** Unable to obtain
statistics ... | TRAIN_Q066 | 57 | 19,557 | 19,962 | |
66_58 | ,167,"KUM0_stat_withMsgFlag") Unsuccessfully stat
file C:/temp/[filename].log size=0 access time=0, modification
time=0, creation time=0
...
- - -
APAR: IV75603
Abstract: BACKSLASH \ INCORRECTLY TRANSLATED ON WINDOWS WHEN SENT
TO EIF
Additional information: On Windows systems when the event is
translated back fro... | TRAIN_Q066 | 58 | 19,962 | 20,394 | |
66_59 | EIF), the backslash character is incorrectly
translated. The backslash character (0x5c) is translated to
UTF-8 0xC2A5, and when it is translated back to the native
code page, it is incorrectly translated to 0x1A which may
show as a blank space or unprintable character. | TRAIN_Q066 | 59 | 20,394 | 20,663 | |
66_60 | As a result
of IV68698, code page 932 is used to translate the event to
UTF-8, however code page 943 is still being used to translate
the event from UTF-8 back to the native code page Shift-JIS. | TRAIN_Q066 | 60 | 20,663 | 20,858 | |
66_61 |
Example:
Log File Agent v6.3 GA <cache file>
70203_Base;msg='Tivoli [message]\[message]'
Log File Agent v6.3 and 6.3.0-TIV-ITM_LFA-IF0004
<cache file>
70203_Base;msg='Tivoli [message] [message]'
APAR: IV75336
Abstract: LFA ASSOCIATED WITH LOG ANALYSIS IS DROPPING EVENTS
Additional information: The agent when a... | TRAIN_Q066 | 61 | 20,858 | 21,208 | |
66_62 | dropping events. When sending large amounts of
events to Event Integration Facility (EIF), the agent is
unable to keep up. The message "WARNING: <1000> events
already on queue, dropping the oldest one", where <1000>
is the default MaxEventQueueDepth value, is seen in the
agent RAS1 log. | TRAIN_Q066 | 62 | 21,208 | 21,497 | |
66_63 |
APAR: IV74487
Abstract: ABLE TO MONITOR FILES GREATER THAN 2GB ON 32-BIT
LINUX
Additional information: When attempting to monitor files greater
than 2 gigabytes on a 32-bit Linux operating system, the
file is not monitored and is not displayed in the Monitored
File Workspace in the portal. A trace in the log shows
"F... | TRAIN_Q066 | 63 | 21,497 | 21,832 | |
66_64 |
Problem Determination: With a minimum of the following trace
enabled: "KBB_RAS1: ERROR (UNIT:kum0fdp0 ALL) (UNIT:kumpstdio
ALL)", the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following:
- - -
...
<timestamp>:kumpwfrm.c,261,"KUMP_WaitFileReadyForM... | TRAIN_Q066 | 64 | 21,832 | 22,239 | |
66_65 | too large, NO retry. Exiting
...
- - -
APAR: IV74480
Abstract: COMPAREBYLASTUPDATE DOES NOT MONITOR THE MOST RECENT
REMOTE FILE ACROSS MULTIPLE DIRECTORIES
Additional information: When monitoring a remote log file using
regular expression meta characters (wildcard) in one directory
pattern of the path, and using ... | TRAIN_Q066 | 65 | 22,239 | 22,778 | |
66_66 |
CompareByLastUpdate should monitor the file with the most
recent last update timestamp across all the directories.
This occurs on Log File Agent version 6.3.0 and appears to
be platform independent. It does not occur for local files. | TRAIN_Q066 | 66 | 22,778 | 23,017 | |
66_67 |
Problem Determination: With a minimum of the following trace
enabled: "KBB_RAS1: ERROR (UNIT:kum0sshlib ALL) (UNIT:kumpdcm ALL)",
the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following, where
'test0420' is not the last or only directory to search:
... | TRAIN_Q066 | 67 | 23,017 | 23,420 | |
66_68 | 38015DA0 name /<...>/pm_20150424 could not find any
(more) members to match pattern <^.* | TRAIN_Q066 | 68 | 23,420 | 23,509 | |
66_69 | \.log$>
...
...
<timestamp>:kum0sshlib.c,2184,"ssh_session_sftp_readdir")
Invalid data connInfo 7FF13800AE50 pDPAB 7FF138006640 ssh_ctx
7FF134007630 sftp_handle NULL buffer 7FF15C1DEE70 buflen 257
PEptr 7FF134004140
...
- - -
APAR: IV72073 | TRAIN_Q066 | 69 | 23,509 | 23,758 | |
66_70 |
Abstract: PATH TO MONITORED FILE NAME STARTS WITH DOUBLE SLASHES (//)
Additional information: Using the RegexLogSources option to
monitor a file which contains a regular expression meta
character in the first directory of the path, the resulting
monitored file name path starts with 2 forward slashes (//).
For examp... | TRAIN_Q066 | 70 | 23,758 | 24,286 | |
66_71 |
The extra forward slash at the beginning of the path can
be seen on the portal in the File Name field in the Monitored
File Status on the Data Collection workspace or in the agent
logs.
The problem exists on Log File Agent v6.3.0 and v6.2.3.2.
This problem is platform independent.
However on Windows systems, if y... | TRAIN_Q066 | 71 | 24,286 | 24,713 | |
66_72 |
Problem Determination:
On the the portal in the File Name field of the Data Collection
workspace, the File Name field contains, for example,
//LFA_test_logs/ts_01.log
With a minimum of the following trace enabled:
"KBB_RAS1: ERROR (UNIT:kumpdcm ALL)", the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<time... | TRAIN_Q066 | 72 | 24,713 | 25,144 | |
66_73 | Directory /
Member
LFA_test_logs matched ^LFA_.* | TRAIN_Q066 | 73 | 25,144 | 25,195 | |
66_74 | $; FilePathSpec2 NULL; and will
now use //LFA_test_logs
...:kumpdcm2.c,161,"KUMP_GetNextMember") Entry
...:kumpdir.c,139,"KUMP_OpenDir") Successfully opened
directory //LFA_test_logs 7F1748059310 7F1748059390
...:kumpdcm2.c,179,"KUMP_GetNextMember") Directory handle
7F1748059310 name //L | TRAIN_Q066 | 74 | 25,195 | 25,489 | |
66_75 | FA_test_logs was successfully opened
...
- - -
APAR: IV71539
Abstract: %NNNN SYSTEM PARAMETERS NOT RESOLVED IN WINDOWS EVENT
LOG EVENTS
Additional information: On Windows 2003, the Log File Agent does
not resolve %nnnn system parameters in Windows Event Log
events. Windows Event Viewer is able to resolve the %nnnn... | TRAIN_Q066 | 75 | 25,489 | 25,949 | |
66_76 |
For example, the event is seen as:
DCOM got error "%1058" attempting to start the service
COMSysApp with arguments "" in order to run the server:
{7F19-11D2}
With a minimum of the following tracing enabled:
"KBB_RAS1: ERROR (UNIT:EventLog ALL)", the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-0<n>... | TRAIN_Q066 | 76 | 25,949 | 26,369 | |
66_77 | Entry
...:eventlog.cpp,1969,"ModifyParameter") Scanning <DCOM
got error "%1058" attempting to start the service COMSysApp
with arguments "" in order to run the server:
{7F19-11D2} > for replaceable parameters.
...:eventlog.cpp,2175,"ModifyParameter") No parameters to
format. | TRAIN_Q066 | 77 | 26,369 | 26,650 | |
66_78 |
...:eventlog.cpp,2185,"ModifyParameter") Scan results
<DCOM got error "%1058" attempting to start the service
COMSysApp with arguments "" in order to run the server:
{7F19-11D2} >
...:eventlog.cpp,2192,"ModifyParameter") Exit
...:eventlog.cpp,1600,"DisplayRecord") Event Log Record:
<DCOM got error "%1058" atte... | TRAIN_Q066 | 78 | 26,650 | 27,055 | |
66_79 |
{7F19-11D2}>
...:eventlog.cpp,1607,"DisplayRecord") Exit
...
- -
APAR: IV79219
Abstract: SHIP LIBKLOSSH-GSK8 LIBRARIES FOR z/LINUX 32-bit and
64-bit FOR REMOTE FILE PROCESSING.
Additional information: The libklossh-gsk8 library was not included
and shipped for ls3263, ls3266, hp11, and hp116 interps. | TRAIN_Q066 | 79 | 27,055 | 27,365 | |
66_80 |
Defect 215184. | TRAIN_Q066 | 80 | 27,365 | 27,380 | |
66_81 |
Defect: 215412
Abstract: Improve servicability of Windows File Notification
WaitForSingleObject trace message
6.3.0-TIV-ITM_LFA-IF0004
------------------------
APAR: IV68698
Abstract: WITH JAPANESE LOCALE, BACKSLASH CHARACTER IS WRONGLY
TRANSLATED WHEN INCLUDED IN TAKE ACTION COMMAND STRING
Additional information:... | TRAIN_Q066 | 81 | 27,380 | 27,826 | |
66_82 | a single-byte backslash character ("\") is
displayed as a double-byte "middle point" character.
The character is correctly displayed in the portal indicating
that it is correctly read and translated by the agent when
read from the monitored log file.
The problem only occurs when the attribute containing
backslas... | TRAIN_Q066 | 82 | 27,826 | 28,334 | |
66_83 | When the take action is
performed either at the agent or the monitoring server, the
agent translates the 0xC2A5 from UTF-8 to the native CP932
which results in the 0xFCFC character code.
The problem exists on the Log File Agent version 6.3.0
Interim Fix 0003 (6.3.0-TIV-ITM_LFA-IF0003) and earlier, with
Japanese loc... | TRAIN_Q066 | 83 | 28,334 | 28,703 | |
66_84 |
Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:logmonitor all)(UNIT:kum0nget all)
(UNIT:kumprmfr ALL) (UNIT:task ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace entries similar to the following:
- - -
...
(54B982FE.000A-... | TRAIN_Q066 | 84 | 28,703 | 29,073 | |
66_85 | (54B982FE.000B-B30:kum0nget.c,419,"TranslateStringToUTF8")
Converting string buffer from ibm-943_P15A-2003 to UTF-8
...
(54B982FE.000F-B30:kumprmfr.c,449,"KUMP_ReadMonitorFileUnicodeRe
cord") <0x5FD6678,0x19>
+54B982FE.000F 0 | TRAIN_Q066 | 85 | 29,073 | 29,302 | |
66_86 | 0000000 2045206C 696E6461 C2A56C6D
6E6F61C2 .E.lmnoa..lmnoa. !!!! | TRAIN_Q066 | 86 | 29,302 | 29,368 | |
66_87 |
+54B982FE.000F 00000010 A56C6D6E 6F61200D 0A
...
...
(54B982FE.00BE-F20:tasklibrary.cpp,1531,"ConvertCommandToLocal")
Converting UTF-8 command to codepage 932
...
(54B982FE.00DC-F20:tasklibrary.cpp,864,"executeTaskRequest")
Executing task cmd /c | TRAIN_Q066 | 87 | 29,368 | 29,621 | |
66_88 | "echo lindaüülindaüülinda
>>c:\output.sit"
APAR: IV68574
Abstract: IN TAKEACTION, COMMAND OF MULTI-BYTE CHARACTERS WHICH HAVE 0XBA
OR 0XBB IS TRANSLATED TO LOCAL CODE PAGE INCORRECTLY.
Additional information: In takeAction processing, multi-byte
characters 0x82BA or 0x82BB in a command are translated to
local cod... | TRAIN_Q066 | 88 | 29,621 | 30,023 | |
66_89 |
The problem exists on Log File Agent v6.3.0 Interim Fix 0003
(6.3.0-TIV-ITM_LFA-IF0003) and earlier releases and is
platform independent. | TRAIN_Q066 | 89 | 30,023 | 30,165 | |
66_90 |
Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:Logmonitor ALL) (UNIT:Kumprmfr ALL)
(UNIT:kum0nget ALL) (UNIT:Task ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace entries similar to the following:
- - -
...
...:kum0nget.... | TRAIN_Q066 | 90 | 30,165 | 30,556 | |
66_91 | 5A-2003 to UTF-8
...:kum0nget.c,482,"TranslateStringToUTF8") Buffersize 31158
bytes; Translated size 4 ; Copied 31158 characters readBuffer
1113EE3B0
...:kum0nget.c,498,"TranslateStringToUTF8") Exit: 0x113EE3B0
...:kum0nget.c,397,"KUM0_Fgets") Exit: 0x11 | TRAIN_Q066 | 91 | 30,556 | 30,813 | |
66_92 | 3EE3B0
...:kumprmfr.c,449,"KUMP_ReadMonitorFileUnicodeRecord")
<0x1113EE3B0,0x4> ?
+5492C8B8.000A 00000000 E3819D0A
... !!!!!! | TRAIN_Q066 | 92 | 30,813 | 30,943 | |
66_93 |
...
<< The event is submitted to EIF - it still looks correct >>
(5492C8B8.005F-1B:logmonitorqueryclass.cpp,2433,"LogMonitorQuery
Class::setInstanceData") Submitting EIF event:
+5492C8B8.005F SOTEST_Event;C1='ã ';
E89 << hex character values>>
31D
...
...
...:tasklibrary.cpp,1225,"actionCallback") Received Ta... | TRAIN_Q066 | 93 | 30,943 | 31,274 | |
66_94 | Cmd=<print -r ' ã '>>/LFA/49806/sotestout.txt >,
User=<sysadmin>
...
...
...:tasklibrary.cpp,1531,"ConvertCommandToLocal") Converting
UTF-8 command to codepage 932
...:tasklibrary.cpp,1554,"ConvertCommandToLocal") Exit: 0x10F4BBF0
...
...
<< However when it is translated back from UTF-8 to codepage 943
it becom... | TRAIN_Q066 | 94 | 31,274 | 31,626 | |
66_95 | .cpp,749,"executeTaskRequest") Entry
...:tasklibrary.cpp,791,"executeTaskRequest")
taskInfo.name = print
...:tasklibrary.cpp,841,"executeTaskRequest") Did
not find Task name 'print'. Going to run 'system' on the
request print -r ' ?]
'>>/LFA/49806/sotestout.txt . | TRAIN_Q066 | 95 | 31,626 | 31,895 | |
66_96 |
...
- - -
APAR: IV68490
Abstract: ALL EVENTS ARE NOT DETECTED AND SENT AS EXPECTED WHEN
TRANSLATING FROM A MULTI-BYTE CODE PAGE
Additional information: All events are not matched and sent to the
event receiver. The events that are received might contain
garbled characters. Close examination of the agent log with
... | TRAIN_Q066 | 96 | 31,895 | 32,397 | |
66_97 | The conversion
fails because the agent was unable to read all the bytes
required for a complete character into its buffer. This might
occur if a group of messages are sent or when a message
exceeds the maximum event size (EventMaxSize). Increasing the
EventMaxSize might produce different results.
The problem exi... | TRAIN_Q066 | 97 | 32,397 | 32,858 | |
66_98 |
It is platform independent.
Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:logmonitor all)(UNIT:kum0nget all)
(UNIT:kumprmfr all)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log might
contain these error indicators:
"partial data", "RESIDUA... | TRAIN_Q066 | 98 | 32,858 | 33,233 | |
66_99 |
Trace entries are similar to the following where the
translation buffer ends 0x1A and contains partial data. | TRAIN_Q066 | 99 | 33,233 | 33,345 | |
66_100 |
- - -
...
...:kum0nget.c,411,"TranslateStringToUTF8") Entry
...:kum0nget.c,417,"TranslateStringToUTF8") translateBuffer
allocated 865 bytes at 43075E0
...:kum0nget.c,419,"TranslateStringToUTF8") Converting string
buffer from ibm-943_P15A-2003 to UTF-8
...:kum0nget.c,467,"TranslateStringToUTF | TRAIN_Q066 | 100 | 33,345 | 33,644 | |
66_101 | 8") Input buffer
43E31C3 of length 288 when translated into 43075E0 of
length 293 has partial data
...:kum0nget.c,469,"TranslateStringToUTF8") <0x43E31C3,0x120>
+... 00000000 23232323 3C323031 342F3132 2F303120
. . . | TRAIN_Q066 | 101 | 33,644 | 33,865 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.