IV93401: USING REGEXLOGSOURCES TO MONITOR A REMOTE FILE FAILS WITH FILE NOT FOUND

Tivoli Log File Agent, Version 6.3.0 Fix Pack 02 (6.3.0-TIV-ITM_LFA-FP0002)

APAR status

• Closed as program error.

Error description

• 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 also found locally, it succeeds and monitors the local
  file.)
  
  Using the same file in LogSources results in a match.
  
  Environment:
     Product/VRM:Log File Agent V6.3 and later
     Operating System/VRM: Platform independent.
  
  Problem Determination:
  On the Log File 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
  /LFA_test_logs matched <test_1.log> to pattern <^test_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_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 file </LFA_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 skipped, stat failed -1
  ...
  - - -
  
  
  RECREATE INSTRUCTIONS:
  1.  Configure a Log File instance, specifying a configuration
  (.conf) file and a format (.fmt) file.
  
  
  In the configuration file  (.conf), include RegexLogSources
  specifying a remote file with or without wildcards:
  
  RegexLogSources=<Remote log file to monitor>
  # Include the machine information for the remote log file
  SshAuthType=PASSWORD
  SshHostList=<machine.ibm.com>
  SshUserid=<userid>
  SshPassword=<password>
  
  2. Start the Log File agent instance, waiting for
  initialization to complete.
  

Local fix

Problem summary

• Using RegexLogSources to monitor a remote file fails with
  errno 2 'No such file or directory, right after the file has
  been successfully found and matched.
  It succeeds using the same file in LogSources parameter, or
  if the file also exists locally, it monitors the local file.
  This is because the remote connection info was not properly
  reset when traversing the directory structure.
  

Problem conclusion

• Reset remote connection information inside the loop when
  traversing the directory structure.
  
  The fix for this APAR is included in the following
  maintenance vehicle:
  
  | fix pack | 6.3.0-TIV-ITM_LFA-FP0002 |
  
  
  Note: The Log File Agent fix is available at
  http://www.ibm.com/support/docview.wss?uid=swg24043263
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  ITM LOG FILE AG

• Fixed component ID

  5724C04LF

Applicable component levels