IBM Support

IZ75539: SSM crashed when loading mib2 in a Solaris 8 Container environme nt (Solaris 10 host)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • SSM with FP8 installed on solaris 8. All required OS patches are
    in place. The SSM is crashing on startup with nothing written to
    the log file (even in debug).
    
    Pstack as follows:
    
    core 'core' of 25405:   ./ssmagent.bin
    
    -----------------  lwp# 1 / thread# 1  --------------------
     fec33d48 strncpy  (ffc00000, fe0f0745, ffffbfde, 3, 50,
    ffbfbfe0) +
    680
     fe0d9098 __1cGhamib2GCIpGrpQUpdateRouteTable6M_i_ (fe0f05d0, 1,
    fe0f06b8, 3, ffbfbfc8, ffbfbfb0) + 360
     fe0d1520 __1cGhamib2GCIpGrpEInit6M_b_ (0, 0, 0, 0, 0, 0) + a8
    -----------------  lwp# 2 / thread# 2  --------------------
     ff3db888 ???????? (fe77bc08, 4d, 0, 0, 0, ff2b0b90)
     ff3d3a94 ???????? (0, 0, 0, 5f264, fe7d0200, 5f258)
     ff3db7e8 ???????? (0, 0, 0, 5f264, fe7d0200, 5f258)
     fe9e1f6c cond_wait_queue (1, 5f258, 0, fe798440, 0, fe9f6000) +
    d0
     fe9e26e0 cond_wait (5f270, 5f258, 5f270, ff3807a8, 0, 5) + 10
     fe9e271c pthread_cond_wait (5f270, 5f258, 0, ff3807a8, 21404,
    fe8fa244)
    + 8
     fe8fa244 __1cEhipeJConditionEWait6Mi_b_ (5f250, 5f270, 5f258,
    0,
    2124c,
    1) + 110
     ff1502f8 __1cHharmoniOTCPTrapManagerDRun6M_v_ (5f0d0, 0, 1,
    ffffffff,
    5f1f8, 5f13c) + a0
     fe8f2d0c __1cEhipeGThreadKEntryPoint6M_v_ (61f60, 0, 5f0d0, 0,
    3, 1)
    +
    f4
     fe8f276c CommonThreadEntry (61f60, fe7d0200, 0, 0, 0, 0) + 4
     fe9e4c3c _lwp_start (0, 0, 0, 0, 0, 0)
    -----------------  lwp# 3 / thread# 3  --------------------
     ff3db888 ???????? (fe67bc38, 4d, 0, 0, 0, 62518)
     ff3d3a94 ???????? (0, 0, 0, 57ef4, fe7d0400, 57ee8)
     ff3db7e8 ???????? (0, 0, 0, 57ef4, fe7d0400, 57ee8)
     fe9e1f6c cond_wait_queue (1, 57ee8, 0, fe79e300, 0, fe9f6000) +
    d0
     fe9e26e0 cond_wait (57ed8, 57ee8, 57ed8, 0, 1, 0) + 10
     fe9e271c pthread_cond_wait (57ed8, 57ee8, 0, 0, 21404,
    feed8d3c) + 8
     feed8d3c
    __1cDnwhRCPThreadSemaphoreEWait6M_n0AJSemaphoreLEWaitStatus__
    (0, 0, 57ed0, 57ee8, 0, 0) + 38
     ff146418 __1cHharmoniLTrapManagerFStart6M_v_ (57e10, feed8a58,
    feefd958, ff1ac5c4, fe67bedc, ffffffff) + 88
     feee4b98 __1cDnwhICPThreadDRun6M_v_ (5dc60, 62518, 62874,
    feed8a58,
    feefd958, 62518) + 58
     feee4bf0 ThreadProc (5dc60, fe7d0400, 0, 0, 0, 0) + 4
     fe9e4c3c _lwp_start (0, 0, 0, 0, 0, 0)
    -----------------  lwp# 4 / thread# 4  --------------------
     ff3db888 ???????? (fe57bbc8, 4d, 0, 0, 0, 4dce8)
     ff3d3a94 ???????? (0, 0, 0, 5823c, fe7d0600, 58230)
     ff3db7e8 ???????? (0, 0, 0, 5823c, fe7d0600, 58230)
     fe9e1f6c cond_wait_queue (1, 58230, 0, fe798700, 0, fe9f6000) +
    d0
     fe9e26e0 cond_wait (58220, 58230, 58220, 0, 0, 1) + 10
     fe9e271c pthread_cond_wait (58220, 58230, 0, 0, 21404,
    feed8d3c) + 8
     feed8d3c
    __1cDnwhRCPThreadSemaphoreEWait6M_n0AJSemaphoreLEWaitStatus__
    (0, 58218, 58218, 58230, 0, 0) + 38
     fe9a4e68 __1cEsnmpJMsgSenderMProcessSocks6M_v_ (581a0,
    fe9ca990,
    4beb0,
    feed8a58, feefd958, fe57be78) + 8c
     fe9a9460 __1cEsnmpNSockProcessorFStart6M_v_ (581a0, 0, 63754,
    fe9a4ddc,
    fe9caa0c, 4dce8) + 40
     feee4b98 __1cDnwhICPThreadDRun6M_v_ (5dd20, 63378, 63754,
    feed8a58,
    feefd958, 63378) + 58
     feee4bf0 ThreadProc (5dd20, fe7d0600, 0, 0, 0, 0) + 4
     fe9e4c3c _lwp_start (0, 0, 0, 0, 0, 0)
    -----------------  lwp# 5 / thread# 5  --------------------
     fec9da40 _poll    (7, 0, 0, fe47bd28, fecbf1bc, fe47bd20) + 8
     fe9a840c __1cEsnmpLMsgReceiverMProcessSocks6M_v_ (5adc8, 1,
    3d090,
    fe47bdfc, 7, fe47bde8) + 1d4
     fe9a9460 __1cEsnmpNSockProcessorFStart6M_v_ (5adc8, 0, 64304,
    fe9a8238,
    fe9caae4, 4dd68) + 40
     feee4b98 __1cDnwhICPThreadDRun6M_v_ (5ddc8, 63f28, 64304,
    feed8a58,
    feefd958, 63f28) + 58
     feee4bf0 ThreadProc (5ddc8, fe7d0800, 0, 0, 0, 0) + 4
     fe9e4c3c _lwp_start (0, 0, 0, 0, 0, 0)
    -----------------  lwp# 6 / thread# 6  --------------------
     ff3db888 ???????? (fe37bc40, 4d, 0, 0, 0, 0)
     ff3d3a94 ???????? (0, 0, 0, 98924, fe7d0a00, 98918)
     ff3db7e8 ???????? (0, 0, 0, 98924, fe7d0a00, 98918)
     fe9e1f6c cond_wait_queue (1, 98918, 0, fe79ee40, 0, fe9f6000) +
    d0
     fe9e26e0 cond_wait (98908, 98918, 98908, fe9c9eb4, 770, 400) +
    10
     fe9e271c pthread_cond_wait (98908, 98918, 0, 0, 21404,
    feec6a1c) + 8
     feec6a1c __1cEnhrtICPTEventEWait6M_n0AGIEventLEWaitStatus__ (0,
    0,
    98908, 98918, 98900, 0) + 2c
     ff0f762c __1cICNHTimerSWaitForTimerExpire6M_v_ (6d1a0, f4000,
    d, 1,
    0,
    6d1b8) + e4
     ff0f77c0 __1cICNHTimerDRun6MpnEnhrtGIEvent__v_ (6d1a0, 8a918,
    0,
    ff1ac5c4, fffe3c99, 1c000) + 74
     ff0f78ec NHTimerThread (8a918, fe7d0a00, ff1ae5d4, ff1ac5c4,
    2010,
    2000) + 28
     fe9e4c3c _lwp_start (0, 0, 0, 0, 0, 0)
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Solaris 8 containers in Solaris 10+.
    ****************************************************************
    PROBLEM DESCRIPTION:
    In a Solairs 8 container on a Solaris 10 host, SSM 4.0 crashes
    on startup in mib2:
    
     fec33d48 strncpy  (ffc00000, fe0f0745, ffffbfde, 3, 50,
    ffbfbfe0) + 680
    
     fe0d9098 __1cGhamib2GCIpGrpQUpdateRouteTable6M_i_ (fe0f05d0,
    1, fe0f06b8, 3, ffbfbfc8, ffbfbfb0) + 360
    
     fe0d1520 __1cGhamib2GCIpGrpEInit6M_b_ (0, 0, 0, 0, 0, 0) +
    a8
    ****************************************************************
    RECOMMENDATION:
    Upgrade to Fix Pack 10 for SSM 4.0.
    ****************************************************************
    

Problem conclusion

  • The problem was that the SSM detected Solaris version 8 so
    assumed the kernel structures would be Solaris version 8.
    However in the case of a container, the kernel structures are
    still Solaris 10 format.
    
    Rewrote the Solaris MIB2 logic to dynamically detect kernel
    structure sizes instead of being hardcoded for just a few
    Solaris releases.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    | fix pack | 4.0.0-TIV-SSM-FP0010
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ75539

  • Reported component name

    NETCOOL SYS SVC

  • Reported component ID

    5724P4300

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-05-02

  • Closed date

    2010-06-21

  • Last modified date

    2010-06-21

  • 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

    NETCOOL SYS SVC

  • Fixed component ID

    5724P4300

Applicable component levels

  • R400 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCP7NT","label":"Netcool System Service Monitor"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"400","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
21 June 2010