IBM Support

PI92142: ADMU3011E UNABLE TO START A WEB SERVER USING STARTSERVER COMMAND

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

  • Created a web server from the admin console. The web server
    starts fine from the admin console.
    Attempting to start the web server with the command:
     startServer.sh webserver1
    fails with error:
    ADMU3011E: Server launched but failed initialization. Server
    logs, startServer.log, and other log files under
    /opt/IBM/Websphere/Appserver/profile1/logs/webserver1 should
    contain failure information.
     -
    Running with the -trace option the startserver.log shows the
    command being executed:
     AH00094: Command line:
    '/srv/filenet/IBM/HTTPServer/bin/httpd
    -d /srv/filenet/IBM/HTTPServer
    -Dwas.status.socket=40805
    -f /srv/filenet/IBM/HTTPServer/conf/httpd.conf'
    
    The "-Dwas.status.socket=40805" parameter is not a valid
    parameter for the httpd command.
    This parameter should not be part of the command.
    

Local fix

  • You can work around this issue by specifying the "-nowait"
    parameter. Run the command
     startServer.sh webserver1 -nowait
    to start the web server. When this parameter is specified the
    "-Dwas.status.socket=40805" keyword is not generated.
     -
    Keywords: httpd illegal option
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Starting a web server using the         *
    *                      startServer script failed although      *
    *                      the web server actually started.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Starting a web server using the
    startServer script failed although
    the web server actually started.
    Example error is below:
    ADMU0128I: Starting tool with the MAN_oeisfntl70_01 profile
    ADMU3100I: Reading configuration for server: WEB_oeisfntl70
    ADMU3200I: Server launched. Waiting for initialization status.
    ADMU3011E: Server launched but failed initialization. Server
    logs, startServer.log, and other log files under
    /srv/filenet/profiles/MAN_oeisfntl70_01/logs/WEB_oeisfntl70
    should contain failure information.
    

Problem conclusion

Temporary fix

  • Run startServer using -nowait option.
    

Comments

APAR Information

  • APAR number

    PI92142

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-08

  • Closed date

    2018-02-05

  • Last modified date

    2018-02-05

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 900

Reference #: PI92142

Modified date: 05 February 2018


Translate this page: