IV20671: CORE FILE GENERATED WHEN AGENT STOPPED.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem Description:
    
    When the Watchdog code which is part of the OS agent is stopped,
    it writes a message to the RAS1 log indicating that a signal was
    captured, the signal number, and the signal name. When it writes
    this mesage, it calls a basic services routine to convert the
    signal number to a name, which resulted in a core file being
    generated. Since this occurred on agent shutdown, there is no
    operational problem
    resulting from the core file.
    
    Local fix/workaround:  None.
    
    Related Files and Output:
    
    Stack trace shows (at the bottome), SignalKCA receiving the
    signal=15 and making the call to SIG1_SignalName. There are then
    multiple calls to SIG1_Raise and BSS1_InitializeOnce.
    
    BSS1_InitializeOnce(0x9001000a0979a70, 0x9001000a097bed0,
    0x9001000a0979a58, 0x9000000048dd030, 0x2500000025) at
    0x90000000488d224
    BSS1_ResolveProcess(0x9001000a0979a58, 0x9000000048dd030,
    0x2500000025)
    at 0x90000000488d0f0
    SIG1_Raise(0x1300000013) at 0x9000000048d2ee4
    Handler(0x600000006, 0x1100e5710, 0x1100e5460) at
    0x9000000048d2808
    abort() at 0x900000000054018
    BSS1_InitializeOnce(0x9001000a0979a70, 0x9001000a097bed0,
    0x9001000a0979a58, 0x9000000048dd030, 0x2500000025) at
    0x90000000488d224
    BSS1_ResolveProcess(0x9001000a0979a58, 0x9000000048dd030,
    0x2500000025)
    at 0x90000000488d0f0
    SIG1_Raise(0x700000007) at 0x9000000048d2ee4
    Handler(0x1300000013, 0x1100e60e0, 0x1100e5e30) at
    0x9000000048d2808
    _sigsetmask(??, ??, ??) at 0x9000000009396dc
    _p_sigaction(??, ??, ??) at 0x90000000093a404
    SetHandler(0x2800000028, 0x9001000a097df58) at 0x9000000048d29fc
    SIG1C_RegisterHandler() at 0x9000000048d2d54
    SIG1C_NewProcess(0x11002cf20) at 0x9000000048d25d4
    InitializeProcess(0x9001000a0979a58) at 0x90000000488d044
    BSS1_InitializeOnce(0x9001000a0979a70, 0x9001000a097bed0,
    0x9001000a0979a58, 0x9000000048dd060, 0x2500000025) at
    0x90000000488d3c0
    BSS1_ResolveProcess(0x9001000a0979a58, 0x9000000048dd060,
    0x2500000025)
    at 0x90000000488d0f0
    SIG1_SignalName(0xf0000000f) at 0x9000000048d30cc
    SignalKCA(int)(signal = 15), line 608 in "kcaunx.cpp".
    

Local fix

Problem summary

  • Core file generated when agent stopped.
    
    When the Watchdog component of the OS Agent is stopped, it
    writes a message to the agent log indicating that a signal was
    captured, the signal number, and the signal name. The code that
    generates this message had an error that caused the core file.
    Since the symptom occurs on agent shutdown, there is no
    operational problem resulting from the core file.
    

Problem conclusion

  • The code was changed to prevent the core file.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.2.3-TIV-ITM-FP0002
      | release  | 6.3.0-TIV-ITM
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV20671

  • Reported component name

    ITM AGENT UNIX

  • Reported component ID

    5724C040U

  • Reported release

    622

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-06

  • Closed date

    2012-09-25

  • Last modified date

    2013-01-04

  • 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 AGENT UNIX

  • Fixed component ID

    5724C040U

Applicable component levels

  • R623 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Components
ITM Agent UNIX V6

Software version:

622

Reference #:

IV20671

Modified date:

2013-01-04

Translate my page

Machine Translation

Content navigation