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

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

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  ihs  stopserver
  

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

• The code is fixed to set the correct option to launch the web
  server.
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.8.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Run startServer using -nowait option.
  

Comments

APAR Information

• 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

• R900 PSY

     UP