IBM Support

IJ53034: RKM.CONF: MISSING PORT NUMBER FROM KMIPSERVERURI

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 unknown reasons (a possible reason is /tmp full), the update
    of RKM.conf was not able to obtain the KMIP port from a file.
    The code does not check for any error and continues to produce
    the kmipServerUri line with missing port number. Encrypted files
    may not be accessible due to this issue.
    

Local fix

  • On the problem node, remove the bad RKM.conf file then run a
    GPFS command to regenerate the RKM.conf file. For example, run
    mmlscluster.
    

Problem summary

  • For unknown reasons (a possible reason is /tmp full), the update
    of RKM.conf was not able to obtain the KMIP port from a file.
    The code does not check for any error and continues to produce
    the kmipServerUri line with missing port number. Encrypted files
    may not be accessible due to this issue.
    

Problem conclusion

  • This problem is fixed in 5.1.9.7
    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:
    This fix ensures the KMIP port number is not null before
    producing the kmipServerUri line for RKM stanza. If error is
    detected, it stops processing and will not update the RKM.conf
    file. Errors will be logged in syslog and mmfs.log.In this fix,
    a /tmp file system full should not cause a null KMIP port
    number.
    
    Work Around:
    On the problem node, remove the bad RKM.conf file then run a
    GPFS command to regenerate the RKM.conf file. For example, run
    mmlscluster.
    
    Problem trigger:
    mount file system; access file
    
    Symptom:
    File system unmount
    
    Platforms affected:
    All
    
    Functional Area affected:
    encryption, admin command
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ53034

  • 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-11-12

  • Closed date

    2024-11-12

  • Last modified date

    2024-11-12

  • 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:
12 November 2024