Technical data

Troubleshooting Node Manager
Configuring and Managing WebLogic Server 4-13
Troubleshooting Node Manager
The following sections describe how to diagnose and correct Node Manager problems.
Use the Node Manager log files to help troubleshoot problems in starting or stopping
individual Managed Servers. Use the steps in “Correcting Common Problems”on page
4-14 to solve problems in Node Manager configuration and setup.
Managed Server Log Files
When you start a WebLogic Server instance, startup or error messages are printed to
STDOUT or STDERROR and to the server log file. You can view the log file by right
clicking on the server in the left pane of the Administration Console and selecting the
option View server log, or by selecting the View server log link on any server tab
page.
If you start a server instance with Node Manager, Node Manager writes these
messages in the
NodeManagerLogs directory. By default, NodeManagerLogs is
created in the directory where you start Node Manager. A separate subdirectory is
created for each Managed Server that Node Manager starts on the machine. Each
subdirectory uses the naming convention
domain_server, which designates the
domain name and Managed Server name, respectively.
Logs files stored in the server directory include:
! servername_pid —This file saves the process ID of the Managed Server named
servername. Node Manager uses this information to kill the Managed Server, if
requested by the Administration Server to do so.
! config.xml—This file saves startup configuration information passed to Node
Manager from the Administration Server when starting a Managed Server.
! servername_output.log—This file saves Node Manager startup messages
generated when Node Manager attempts to start a Managed Server. If a new
attempt is made to start the server, this file is renamed by appending
_PREV to
the file name.
! servername_error.log—This file saves Node Manager error messages
generated when Node Manager attempts to start a Managed Server. If a new