Summary on solving the problem of WebSphere services cannot start issues
Li Shouliang SLLI@founder.com.cn
Last Version: 2003-3-20
Brief description
The reason why the WebSphere service cannot start is usually caused by the following conditions. There is a clean Java process; the database is not started; the database part parameter setting error; the database structure is broken; the SCHEMA of the WAS connection database is inconsistent; viruses; patch and other reasons. At first, the WebSpher service could not start, but I had to reinstall, waste a lot of time, and walked a lot of detours. When the WebSphere service does not start, please first follow the steps below. Normally, you can reinitialize the management library.
table of Contents
First, first check if there is no clean Java process
Second, check if the DB2 database is started normally
Third, check if the management database was exist
Fourth, check if the device stored in the database is normal MOUNT
5. Check if the Schema of the WebSphere join the WAS library is consistent
Sixth, the fix of the WAS management database (initialization)
7. Check if the file library is broken away from the reconstruction of the WAS management library.
Eight, the Windows platform should also exclude if the virus reasons
Nine, Linux platform usually related to system patches
content
First, check if there is any cleaner Java process
Under UNIX:
# ps -ef | grep java
# Kill -9 PID (Note Confirmation is the Java process of WAS)
Then restart a WAS service.
# / OPT / WebSphere / AppServer / Bin / StartupServer SH &
# Tail -f Opt / WebSphere / AppServer / logs / tracelog
Use the Explorer to view and kill WAS Java, restart the service.
Second, check if the DB2 database is started normally
If the DB2 used by WebSphere is used as a management library, then the DB2 should be checked normally. If you don't start, you should start it: Check if there is a database mount fsck
Under UNIX:
# su - db2as
$ db2admin start
$ su - db2inst1
$ db2start
Start from the CMD window or service under the WIN platform.
Third, check if the management database was exist
If the DB2 server is normal, it is still unable to start, you need to check if the database exists.
Under UNIX:
$ DB2
=> List DB Directory
=> Connect to Was User
View from DB2 Command WiDow or Control Center under the Window platform.
Fourth, check if the device stored in the database is normal MOUNT
If there is a database but not on, one of possible situations is that the database device is not correct, in the UNIX platform, abnormal shutdown or some operations that have damage to the disk can cause this.
Use the following command to check the disk without mount.
# df -k
# mount
# mountall
# cat / etc / vfstab
Suppose checks to / dev / dsk / c0t0d0s6 device does not have correct Mount, use # fsck -f / dev / dsk / c0t0d0s6 to repair it, restart the server.
5. Check if the Schema of the WebSphere join the WAS library is consistent
phenomenon:
$ DB2
=> DB2
=> Force Application All
# / OPT / WebSphere / AppServer / Bin / StartupServer SH &
Run after starting the service
=> List Applications
You can also list the WAS libraries, but still start failed. At this time, confirm whether the DBUser for the WebSphere join database is changed because the table created in DB2 is placed under different schema, if the initialization is successful, the connection is normal, for some reason (such as confidential), join the WebSphere connection WAS library The user has changed, resulting in WebSphere not found the initialization table, causing the service unable to start.
There are two solutions:
A), modify the original dbuser, in /opt/websphere/appserver/bin/admin.config (Win version in the relevant directory), related lines:
com.ibm.ejs.sm.adminserver.dbuser =
com.ibm.ejs.sm.adminserver.dbschema =
Second), reinitialize the management database
1. WebSphere 3.54 version Previous (included)
1), modify /opt/websphere/appserver/bin/admin.config (WIN version in the relevant directory):
Install.initial.config = false Modified to True
2), # /opt/websphere/appserver/bin/startserver.sh &
2, WebSphere 3.55, 3.56 version, relatively large change relatively 3.54 version
1), modify /opt/websphere/appserver/bin/admin.config (WIN version in the relevant directory):
Install.initial.config = false Modified to True
Also modified
com.ibm.ejs.sm.adminserver.dbinitialized = true change to False
2), # /opt/websphere/appserver/bin/startserver.sh &
Sixth, the fix of the WAS management database (initialization)
Using the file management library (INSTDB) does not exist, it is sometimes setting an error in the environment variable, which can still cause the WAS service that cannot be started. At this time, it is necessary to fix the management library, so that some start-up parameters return to the initialization state. After the management library is initialized, some settings that are not coherent to the initial parameters will remain. Some reset time can be saved. But if you don't have a problem, there is a problem, only re-establish the management library.
For DB2 management libraries, and use INSTDB file management libraries, this method is applicable:
A), WebSphere 3.54 version Previous (included)
1. Modify /opt/websphere/appserver/bin/admin.config (WIN version in the relevant directory):
Install.initial.config = false Modified to True
2, # /opt/websphere/appserver/bin/startserver.sh &
2), WebSphere 3.55, 3.56, relatively large changes in the 3.54 version, so pay special attention
1. Modify /opt/websphere/appserver/bin/admin.config (WIN version in the relevant directory):
Install.initial.config = false Modified to True
Also modified
com.ibm.ejs.sm.adminserver.dbinitialized = true change to False
2, # /opt/websphere/appserver/bin/startserver.sh &
7. Check if the file library is broken away from the reconstruction of the WAS management library.
Confirm is that the database is corrupt, the following work is to re-create the library, reinitialize. (The earliest time, because I don't know the problem, I have to reload, have gone a lot of detours). In Xiangyu Enp2000 servers, I have encountered an incident that INSTDB file library causing WebSphere can't start. Solution one and list:
A), DB2 database, as an example of UNIX platform:
1. Delete the database
# su - db2inst1
$ DB2
=> Disconnect All
=> Force Application All
=> Termenate
$ DB2 DROP DB WAS
2, create a database
$ DB2
=> CREATE DB WAS
=> Update DB CFG for Was Using ApplHeapsz 256
3, modify admin.config, database initialization
1) WebSphere 3.54 Previous (included)
A, modify /opt/websphere/appserver/bin/admin.config
Install.initial.config = false Modified to True
B, # /opt/websphere/appserver/bin/startserver.sh &
2) WebSphere 3.55, 3.56 version
A, modify /opt/websphere/appserver/bin/admin.config
Install.initial.config = false Modified to True
Also modified
com.ibm.ejs.sm.adminserver.dbinitialized = true change to False
B, # /opt/websphere/appserver/bin/startserver.sh &
2), document management library
1. Delete the database
Delete or change your name file library directory:
# rm -r / opt / webSphere / appserver / bin / idbstore or
# CD / OPT / WebSphere / AppServer / BIN / IDBSTORE
# mv ./idbstore ./IDBStore.bak
2, modify admin.config, database initialization
1) WebSphere 3.54 Previous (included)
A, modify /opt/websphere/appserver/bin/admin.config
Install.initial.config = false Modified to True
B, # /opt/websphere/appserver/bin/startserver.sh &
2) WebSphere 3.55, 3.56 version
A, modify /opt/websphere/appserver/bin/admin.config
Install.initial.config = false Modified to True
Also modified
com.ibm.ejs.sm.adminserver.dbinitialized = true change to False
B, # /opt/websphere/appserver/bin/startserver.sh &
Eight, the Windows platform should also rule out whether the virus causes.
Nine, the Linux platform frequently can't start the service, except for the above reasons, you should check the patches needed by the version, many of the cases because the patch is not causing. Li Shouliang SLLI@founder.com.cn
2003-03-20
