IBM Support

IJ52272: FILE AUDIT LOGGING PERIODIC LOGASSERT WHEN FILE AUDIT LOGGING IS ENABLED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Change to File Audit Logging code can cause periodic logAssert
    if operation context is not set. If encountered, and assert like
    the following will appear:
    2024-08-26_04:00:08.796+0100: [X] *** Assert exp(context !=
    unknownOp) in line 6125 of file /project/sprelgpfs519/build/rgp
    fs519s005i/src/avs/fs/mmfs/ts/fs/openfile.C
    2024-08-26_04:00:08.796+0100: [E] *** Traceback:
    2024-08-26_04:00:08.796+0100: [E] 2:0x55AE8B58E84A
    logAssertFailed + 0x3AA at ??:0
    2024-08-26_04:00:08.796+0100: [E] 3:0x55AE8B2E093D
    LockFile(OpenFile**, StripeGroup*, FileUID, OperationLockMode,
    LkObj::LockModeEnum, LkObj::LockModeEnum*, LkObj::LockModeEnum*,
    int, int) + 0x69D at ??:0
    2024-08-26_04:00:08.796+0100: [E] 4:0x55AE8B22CB2B
    FSOperation::createLockedFile(StripeGroup*, FileUID,
    OperationLockMode, LkObj::LockModeEnum, OpenFile**, unsigned
    int*, int, int) + 0x9B at ??:0
    2024-08-26_04:00:08.796+0100: [E] 5:0x55AE8B8D4F4C
    markAuditLogInactive(StripeGroup*, FileUID) + 0x5C at ??:0
    2024-08-26_04:00:08.796+0100: [E] 6:0x55AE8B8DE14C
    AuditWriter::processRequest(WriteRequest) + 0x3FC at ??:0
    2024-08-26_04:00:08.796+0100: [E] 7:0x55AE8B8C5DFE
    serveWriteRequests(WriteRequest const&, void*) + 0xBE at ??:0
    2024-08-26_04:00:08.796+0100: [E] 8:0x55AE8B8C61A0
    AuditWriter::callback() + 0x1A0 at ??:0
    2024-08-26_04:00:08.796+0100: [E] 9:0x55AE8B036C42
    RunQueue::threadBody(RunQueueWorker*) + 0x392 at ??:0
    2024-08-26_04:00:08.796+0100: [E] 10:0x55AE8B038EC2
    Thread::callBody(Thread*) + 0x42 at ??:0
    2024-08-26_04:00:08.796+0100: [E] 11:0x55AE8B025EC0
    Thread::callBodyWrapper(Thread*) + 0xA0 at ??:0
    2024-08-26_04:00:08.796+0100: [E] 12:0x7FA83AF9A1CA start_thread
    + 0xEA at ??:0
    2024-08-26_04:00:08.796+0100: [E] 13:0x7FA839C9F8D3 __GI___clone
    + 0x43 at ??:0 mmfsd: /project/sprelgpfs519/build/rgpfs519s005i
    /src/avs/fs/mmfs/ts/fs/openfile.C:6125:void logAssertFailed(UInt
    UInt32, const char*, const char*): Assertion `context !=
    unknownOp' failed.
    

Local fix

  • Disable file audit logging
    

Problem summary

  • Change to File Audit Logging code can cause periodic logAssert
    if operation context is not set. If encountered, and assert like
    
    the following will appear:
    2024-08-26_04:00:08.796+0100: [X] *** Assert exp(context !=
    unknownOp) in line 6125 of file /project/sprelgpfs519/build/rgp
    fs519s005i/src/avs/fs/mmfs/ts/fs/openfile.C
    2024-08-26_04:00:08.796+0100: [E] *** Traceback:
    2024-08-26_04:00:08.796+0100: [E] 2:0x55AE8B58E84A
    logAssertFailed + 0x3AA at ??:0
    2024-08-26_04:00:08.796+0100: [E] 3:0x55AE8B2E093D
    LockFile(OpenFile**, StripeGroup*, FileUID, OperationLockMode,
    LkObj::LockModeEnum, LkObj::LockModeEnum*, LkObj::LockModeEnum*,
    
    int, int) + 0x69D at ??:0
    2024-08-26_04:00:08.796+0100: [E] 4:0x55AE8B22CB2B
    FSOperation::createLockedFile(StripeGroup*, FileUID,
    OperationLockMode, LkObj::LockModeEnum, OpenFile**, unsigned
    int*, int, int) + 0x9B at ??:0
    2024-08-26_04:00:08.796+0100: [E] 5:0x55AE8B8D4F4C
    markAuditLogInactive(StripeGroup*, FileUID) + 0x5C at ??:0
    2024-08-26_04:00:08.796+0100: [E] 6:0x55AE8B8DE14C
    AuditWriter::processRequest(WriteRequest) + 0x3FC at ??:0
    2024-08-26_04:00:08.796+0100: [E] 7:0x55AE8B8C5DFE
    serveWriteRequests(WriteRequest const&, void*) + 0xBE at ??:0
    2024-08-26_04:00:08.796+0100: [E] 8:0x55AE8B8C61A0
    AuditWriter::callback() + 0x1A0 at ??:0
    2024-08-26_04:00:08.796+0100: [E] 9:0x55AE8B036C42
    RunQueue::threadBody(RunQueueWorker*) + 0x392 at ??:0
    2024-08-26_04:00:08.796+0100: [E] 10:0x55AE8B038EC2
    Thread::callBody(Thread*) + 0x42 at ??:0
    2024-08-26_04:00:08.796+0100: [E] 11:0x55AE8B025EC0
    Thread::callBodyWrapper(Thread*) + 0xA0 at ??:0
    2024-08-26_04:00:08.796+0100: [E] 12:0x7FA83AF9A1CA start_thread
    
    + 0xEA at ??:0
    2024-08-26_04:00:08.796+0100: [E] 13:0x7FA839C9F8D3 __GI___clone
    
    + 0x43 at ??:0 mmfsd: /project/sprelgpfs519/build/rgpfs519s005i
    /src/avs/fs/mmfs/ts/fs/openfile.C:6125:void logAssertFailed(UInt
    
    UInt32, const char*, const char*): Assertion `context !=
    unknownOp' failed.
    

Problem conclusion

  • This problem is fixed in 5.2.1.1
    To see all Spectrum Scale APARs and their respectiv
    Fix solutions refer to page: 
    https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale
    _apars.html
    
    
    Benefits of the solution:
    Avoid logAsserts on file audit logging code when file audit
    logging is enabled
    
    Work Around:
    Disable file audit logging
    
    Problem trigger:
    The problem happens when the file audit logging code is writing
    to the audit log, and attempts to grab a lock on the file. This
    happens frequently in file audit logging code, but the condition
    
    does not happen every time, so the logAsserts will be periodic.
    
    Symptom:
    Abend/Crash
    
    Platforms affected:
    Linux Only
    
    Functional Area affected:
    File Audit Logging
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ52272

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    521

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-09-06

  • Closed date

    2024-09-24

  • Last modified date

    2024-09-24

  • 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

    SPEC SCALE STD

  • Fixed component ID

    5737F33AP

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"STXKQY"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"521","Line of Business":{"code":"LOB69","label":"Storage TPS"}}]

Document Information

Modified date:
25 September 2024