IBM Support

PM63269: Server startup process (configuration manager) sets incorrect permissions

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an application server, node agent, or deployment manager is
    started using "startServer", the configuration manager assigns
    inappropriate permissions to files inside the profile.
    
    For example, on non-Windows distributed platforms, "755"
    permissions are applied recursively to the
    PROFILE_HOME/properties/service/productDir directory.
    
    This can be an issue in situations where the system umask is set
    to be more restrictive than "022".  For example, if the umask
    were set to "027", then by default files are created with no
    "other" permissions set.  But, assigning permissions of "755" to
    files would grant read-execute to "other" permissions, which is
    not intended when the umask is "027".
    
    The permissions on the files can be manually changed to be
    more restrictive, but the next server startup will set the
    permissions to "755" again.
    

Local fix

  • No workaround at this time.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Files being created by the post         *
    *                      install                                 *
    *                      process do not respect umask settings.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Currently when the post install process is run, files that are
    created during execution are hard coded to a set of
    permissions. If a umask setting is in place, it is not
    respected.
    

Problem conclusion

  • A property was added to the file
    INSTALL_HOME/properties/wasprofile.properties called
    WS_CMT_PI_MODPERMS. When set to false, the umask setting will
    be respected. When set to true, the default behavior will be
    used.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.6 and fix pack 8.5.0.2.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM63269

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-25

  • Closed date

    2012-10-16

  • Last modified date

    2012-12-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021