IV60331: RESETTING OF MULTIPLE CONF/FORMAT FILES CAUSES A CRASH

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

• ABSTRACT: Resetting of multiple conf/format files causes a crash
  
  PROBLEM DESCRIPTION:
  When updating multiple configuration (.conf) or format (.fmt)
  files, usually via a script or situation that runs frequently,
  which causes the Log File agent to reset might result in a core
  or crash. This also might be more likely to occur when using
  multiple subnodes to monitor a large number of files, for
  example, 100 files.
  
  ENVIRONMENT: This problem occurs on Linux with Log File Agent
  v6.3.
  
  lo   Tivoli Log File Agent  lx8266 06.30.00.00
  
  The <hostname>_lo_1396376010.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]
  /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]
  /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)[0x7f222427fb56
  ]
  /lib64/libpthread.so.0[0x3c16007851]
  /lib64/libc.so.6(clone+0x6d)[0x3c158e890d]
  . . .
  
  
  RECREATE INSTRUCTIONS:
  Monitor a large number of files, using subnodes, and use a
  script or situation to update the conf or fmt files while
  monitoring the files.
  
  An example script to update fmt files.
  @echo bat
  dos2unix lo_<instance>.fmt
  dos2unix lo_<instance>.fmt
  dos2unix lo_<instance>.fmt
  dos2unix lo_<instance>.fmt
  
  Approver Initials:    LD
  

Local fix

• None.
  
  However, avoid high-frequency scripted file updates to
  minimize effects.
  

Problem summary

• When the agent attempts to close a monitored file that is
  already closed or no longer exists, the agent crashes.  This
  has been seen, mainly on Linux, on agent start-up, shut-down
  and reset as a result of configuration file changes.
  
  The problem was originally discovered in Log File Agent 6.2.3.1.
  

Problem conclusion

• Correctly mark the file as closed so a second file close is not
  attempted causing it to crash.
  
  
  The fix for this APAR will be included in the following
  maintenance vehicle:
  
  | fix pack | 6.3.0-TIV-ITM_LFA-FP0002 |
  
  
  Note: The fix will be 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

• R630 PSY

     UP