IBM Support

IJ53214: MISSING NFS CLIENT IPS IN AUDIT LOG WHEN WORKLOADS ARE RUNNING FOR LONG PERIODS

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

  • With FAL and NFS Ganesha enabled, running workloads with path to
    an NFS export for long periods of time could result in NFS
    client ips not being logged in the audit log.
    

Local fix

  • - Restart NFS Ganesha if NFS client ips are not being logged
    

Problem summary

  • With FAL and NFS Ganesha enabled, running workloads with path to
    an NFS export for long periods of time could result in NFS
    client ips not being logged in the audit log.
    

Problem conclusion

  • This problem is fixed in 5.2.2.1
    To see all Spectrum Scale APARs and their respective
    Fix solutions refer to page: 
    https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale
    _apars.html
    
    Benefits of the solution:
    Fixed the code so that the NFS client ips are logged during long
    running workloads.
    
    Work Around:
    - Restart NFS Ganesha if NFS client ips are not being logged
    
    Problem trigger:
    - Wit FAL and NFS Ganesha enabled, run workloads with path to
    the NFS mount point for long periods of time
    
    Symptom:
    Unexpected Results/Behavior
    
    Platforms affected:
    Linux
    
    Functional Area affected:
    File Audit Logging, NFS
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ53214

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    522

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-12-20

  • Closed date

    2025-02-19

  • Last modified date

    2025-02-19

  • 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":"522","Line of Business":{"code":"LOB69","label":"Storage TPS"}}]

Document Information

Modified date:
19 February 2025