IBM Support

PM86332: COMMAND "SERVER START <SERVER>" FAILS WHEN UMASK IS SET TO OTHER THAN 000

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 0- Install a Liberty Core edition using Installation Manager.
    1- Set umask to 022
    2- cd
    /qibm/proddata/websphere/appserver/v85xxx/liberty/wlp/bin
    3- server create xxx
    Server xxx created.
    CPC221C:  4 objects successfully changed.
    CPC221C:  9 objects successfully changed.
    4- server start xxx
    QEJBSVR: FAILED TO CREATE CONSOLE FILE:
    /QIBM/UserData/WebSphere/AppServer/V8
    5xxx/liberty/wlp/output/servers/xxx/logs/console.log
    Starting server xxx.
    Server xxx start failed. Check server logs for details.
    
    Analysis:
    
    The server script creates a X_PID_DIR and X_LOG_DIR
    folders before calling the start code. The folders are owned
    by the caller of the server script. The
    caller of the script will own those folders but others
    with get RX auth.
    When the server is started , the current user profile is
    swapped to the server profile 'QEJBSVR" which is classified as
    others and it cannot create the consoe.log or the server.pid
    file in the .pid folder.
    Server start fails with above error.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile V8.5                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application Server fails to start       *
    *                      when umask is not set to 000.           *
    ****************************************************************
    * RECOMMENDATION:  Apply the 8.5.5.0 fixpack.                  *
    ****************************************************************
    When umask is not set to 000, some folders and files that are
    used by the user profile QEJBSVR will not be accessible to
    the user profile. As a result, the Application Server will fail
    to start.
    

Problem conclusion

  • To fix the problem, the server command was modified to grant
    the user profile QEJBSVR the needed authorities.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.0. 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

    PM86332

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-04

  • Closed date

    2013-05-31

  • Last modified date

    2013-05-31

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 May 2013