IBM Support

IJ50373: MMSYSMON.LOG GETTING VERY LARGE

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

  • For certain performance monitoring operations in the case of an
    error the query and response get logged. That response can be
    large and logging it regularly will cause mmsysmon.log to grow
    rapidly.
    

Local fix

  • Changing the log level or altering the log line in the python
    code.Alternative would be to eliminate the trigger, either by
    re-doing ?mmperfmon delete ?expiredKeys? or removing all
    collected performance data in /opt/IBM/zimon/data/
    

Problem summary

  • For certain performance monitoring operations in the case of an
    error the query and response get logged. That response can be
    large and logging it regularly will cause mmsysmon.log to grow
    rapidly.
    

Problem conclusion

  • This problem is fixed in 5.1.9.3
    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:
    Fix only logs a subset of data and also eliminates one of the
    causes that could trigger the situation.
    
    Work Around:
    Changing the log level or altering the log line in the python
    code.Alternative would be to eliminate the trigger, either by
    re-doing ?mmperfmon delete ?expiredKeys? or removing all
    collected performance data in
    /opt/IBM/zimon/data/
    
    Problem trigger:
    Incomplete delete of performance metrics. Some checks are done
    on so called ?measurements? which take several metrics and
    calculate a composite result.If only a subset of the metrics for
    the calculation is available, the error is triggered.
    
    Symptom:
    Unexpected Results/Behavior
    
    Platforms affected:
    ALL Linux OS environments
    
    Functional Area affected:
    System Health / perfmon (Zimon)
    
    Customer Impact:
    Suggested
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ50373

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    519

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-03-07

  • Closed date

    2024-03-13

  • Last modified date

    2024-03-13

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

Document Information

Modified date:
04 April 2024