Shulou(Shulou.com)06/01 Report--

This article introduces the relevant knowledge of "how to solve the failure error of WebSphere startup initialization". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

A server failed to initialize the restart report after stopping WAS, and even the WAS console could not be started. The specific information is as follows:

Root@test03/scripts: >. / startWAS.sh

ADMU0116I: in progress file

/ home/wasuser/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log

Record tool information in

ADMU0128I: starting tools with Dmgr01 profiles

ADMU3100I: reading configuration from server: dmgr

ADMU3200I: the server has been started. Wait for the initialization state.

ADMU3011E:

The server was started, but initialization failed. StartServer.log, SystemOut.log (or

Job log in zOS) and

/ home/wasuser/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr

Other log files under may contain fault information.

There is no valuable information to check the log. What's going on?

After careful examination, it is found that the owners of many files and subdirectories under the / home/wasuser/IBM/WebSphere directory have become ROOT, while under normal circumstances they should be WASUSER owners. The reason is that when the developer is online, the misuse of ROOT users in transmitting packages and files.

The next step is to process:

# cd / home/wasuser/IBM

# chown-R wasuser:wasgrp WebSphere

# ps-ef | grep java

Find out if there are any JAVA processes and kill them all.

Then start WAS, and everything is fine.

Normal information:

Root@test03/scripts: >. / startWAS.sh

ADMU0116I: in progress file

/ home/wasuser/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log

Record tool information in

ADMU0128I: starting tools with Dmgr01 profiles

ADMU3100I: reading configuration from server: dmgr

ADMU3200I: the server has been started. Wait for the initialization state.

ADMU3000I: open server for e-commerce dmgr; process identified as 360632

ADMU0116I: in progress file

/ home/wasuser/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/startServer.log

Record tool information in

ADMU0128I: starting tools with AppSrv01 profiles

ADMU3100I: reading configuration from server: nodeagent

ADMU3200I: the server has been started. Wait for the initialization state.

ADMU3000I: open server for e-commerce the nodeagent; process is identified as

569588

ADMU0116I: in progress file

/ home/wasuser/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/app01/startServer.log

Record tool information in

ADMU0128I: starting tools with AppSrv01 profiles

ADMU3100I: reading configuration from server: app01

ADMU3200I: the server has been started. Wait for the initialization state.

ADMU3000I: open server for e-commerce the app01; process is identified as

528470

ADMU0116I: in progress file

/ home/wasuser/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/app02/startServer.log

Record tool information in

ADMU0128I: starting tools with AppSrv01 profiles

ADMU3100I: reading configuration from server: app02

ADMU3200I: the server has been started. Wait for the initialization state.

ADMU3000I: open server for e-commerce the app02; process is identified as

365240

ADMU0116I: in progress file

/ home/wasuser/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/app03/startServer.log

Record tool information in

ADMU0128I: starting tools with AppSrv01 profiles

ADMU3100I: reading configuration from server: app03

ADMU3200I: the server has been started. Wait for the initialization state.

ADMU3000I: open server for e-commerce the app03; process is identified as

512348

ADMU0116I: in progress file

/ home/wasuser/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/app04/startServer.log

Record tool information in

ADMU0128I: starting tools with AppSrv01 profiles

ADMU3100I: reading configuration from server: app04

ADMU3200I: the server has been started. Wait for the initialization state.

ADMU3000I: open server for e-commerce the app04; process is identified as

492136

Httpd (pid 442796) already running

/ home/wasuser/IBM/HTTPServer/bin/adminctl start: admin http (pid 483454) already running

In addition, when it is too slow to start an application in the WAS console, there is no response for a long time. You can check to see if there are any comments in the XML file in the WAS package you uploaded. If you have comments to change it to English, restart it.

In another case, you upload the application and start normally, but you cannot access the service or data, which is generally related to the fact that your uploaded application is not uploaded by WASUSER users, resulting in incorrect directory and file permissions of individual applications.

This is the end of the content of "how to solve the failure error of WebSphere startup initialization". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.