Application Server installation program completes successfully,
but the Application Server does not start, or starts with errors
- Browse the Application
Server log files for clues. The log files are located by default in:
![[Linux]](../../linux.gif)
install_root\ profiles\ profile_name\
logs\ server_name\ SystemErr.log and SystemOut.log
install_root/ profiles/ profile_name/
logs/ server_name/ SystemErr.log and SystemOut.log
Several applications deployed on an Application Server or node can take
time to start. Browse the SystemOut.log periodically
and look at the most recent updates to see if the server is still starting
up.
![[Linux]](../../linux.gif)
The tail -f install_root/
profiles/ profile_name/ logs/ server_name/
SystemOut.log is a convenient way to watch the progress of the
server.
- Look for any errors or warnings relating to specific resources with the
module, such as Web modules, enterprise beans and messaging resources. If
you find any, examine the Application Server configuration file for the configuration
settings of that resource. For example, in a base or non-distributed configuration
on Windows systems, browse install_root/ profiles/ profile_name/
config/ cells/ ApplicationServerCell/ nodes/ node_name/
servers/ server_name/server.xml, and examine
the XML tags for the properties of that resource. Change its initialState value
from START to STOP. Then restart the
server to see if this component causes the problem.
- Look up any error or warning messages in the message reference table by
clicking the Reference view of the information center navigation and
expanding Messages in the navigation tree.
- Verify that the logical name that you specified to appear on the console
for your Application Server does not contain invalid characters like: - /
\ : * ? " < > and leading or trailing spaces.
- If you are using IBM Cloudscape and receive an ERROR XSDB6: Another
instance of Cloudscape may have already booted the database databaseName error
when starting the Application Server, consult
this topic for more information.
- When using a non-root user ID to run Application Servers, verify that:
- The non-root user has write access to the install_root/temp directory.
- The JVM has write access to install_root/config/plugin-cfg.xml file.
- The non-root user has access to the logs directory.
Message "The socket bind failed for host hostname and
port portnumber. The port may already be in use." occurs when restarting
an Application Server.
The following error message might appear
in the SystemOut.log after restarting the Application Server:
The socket bind failed for host hostname and port portnumber. The port may already be in use.
This
problem might occur if the network is slow, and the port listed in the message
text did not finish listening when the application was stopped and restarted.
To
verify that this is the problem, check the port status.
To correct this
problem, wait for a few minutes after stopping the server:
- Verify that no ports are listening. Use the command: 'netstat
-a .
- Restart the server
For current information available from IBM Support on known problems and
their resolution, see the IBM Support page. You should also refer to this page
before opening a PMR because it contains documents that can save you time
gathering information needed to resolve a problem.
If you do not see a problem that resembles yours, or if the information
provided does not solve your problem, seeObtaining help from IBM.