The NodeManager1.0 catalog contains messages in the range
BEA300000 - BEA309999. Messages in this catalog are part of the
weblogic.nodemanager
Internationalization package and the weblogic.i18n Localization package.
|
BEA-300000
|
Debug: arg0
|
Description
| Uncatalogued debug message - please do not change. |
|
Cause
| Debugging - please do not change. |
|
Action
| No action required. |
|
|
BEA-300001
|
Error: Could not execute command cmd for the managed server through the node manager, because the server name is not set.
|
Description
| The command cmd could not be executed using the node manager, as the server name is not set. |
|
Cause
| No name has been specified for the managed server. |
|
Action
| Specify a name for the managed server in its configuration settings. |
|
|
BEA-300002
|
Error: Could not execute command cmd for the managed server svrName through the node manager, because the domain name is not set.
|
Description
| The command cmd cannot be executed using the node manager, as the domain name is not set. |
|
Cause
| No domain has been specified for the managed server. |
|
Action
| Verify that a domain has been specified for the managed server. |
|
|
BEA-300004
|
Error: Could not execute command cmd for the managed server svrName through the node manager, because this command can only be performed from an sdmin server.
|
Description
| The command cmd can only be executed on the admin server. It cannot be executed from a managed server. |
|
Cause
| The WebLogic Server where the Admin Console is running is not an admin server. |
|
Action
| Run your WebLogic Admin Console on the admin server. |
|
|
BEA-300005
|
Error: Could not execute command cmd for server svrName through the node manager. This command cmd cannot be executed on the admin server using the node manager.
|
Description
| svrName is the admin server. This command cmd cannot be executed on the admin server. |
|
Cause
| The node manager does not perform any operations on the admin server. |
|
Action
| No action is required, as this operation is not supported on the admin server. |
|
|
BEA-300006
|
Error: Could not execute command cmd for server svrName using the Node Manager. Logs cannot be obtained for the admin server using the node manager.
|
Description
| Cannot obtain the logs for the admin server using the node manager. See the command shell of the admin server for StdOut and StdErr logs. |
|
Cause
| The node manager does not perform any operations on the admin server. |
|
Action
| No action is required, as this operation is not supported on the admin server. |
|
|
BEA-300007
|
Error: Could not execute command cmd for server svrName using the node manager, because the node manager does not monitor the admin server.
|
Description
| The node manager is not designed to monitor the admin server. |
|
Cause
| The node manager does not perform any operations on the admin server. |
|
Action
| No action is required, as this operation is not supported on the admin server. |
|
|
BEA-300009
|
Error: Server svrName cannot be started in the standby state, because the administration port is not configured.
|
Description
| If the server is to be started in the standby state, the administration port should be enabled for the server. This is because there must be a way to manage the server. When in the standby state, the listen ports are not started and the admin server communicates with the managed server over the administration port. |
|
Cause
| The user tried to start a server in the standby state without configuring an administration port. |
|
Action
| Configure an administration port for the domain and retry the operation. |
|
|
BEA-300010
|
Error: Could not execute command cmd for server svrName using the node manager, because the target machine configuration was not found.
|
Description
| The command cmd cannot be executed for the server svrName, as no machine is associated with this server. The server should be started using the node manager. |
|
Cause
| No target machine has been associated with this server. |
|
Action
| Select a target machine on which this server will run. |
|
|
BEA-300011
|
Error: Could not execute command cmd for server svrName using the node manager, because the target machine configuration was not found. This feature is applicable only for servers that are started up through the node manager
|
Description
| The command cmd cannot be executed for the server svrName, because no machine is associated with this server. The server should be started using the node manager. |
|
Cause
| The user attempted to use the node manager to perform an operation on a server that is only valid if the server was started using the node manager. |
|
Action
| Start the server using the node manager. |
|
|
BEA-300012
|
Error: Could not execute command cmd for server svrName using the node manager, because the node manager configuration for target machine machName was not found.
|
Description
| The node manager is not configured for the machine associated with server svrName. |
|
Cause
| This is an internal error. |
|
Action
| Associate a machine on which server svrName is to be started by the node manager. Then, execute command cmd. |
|
|
BEA-300013
|
Error: Could not execute command cmd for server svrName using the node manager, because the node manager configuration for target machine machName was not found. This feature is applicable only for servers that were started up using the node manager.
|
Description
| The node manager is not configured for machine null. |
|
Cause
| The user attempted to use the the node manager to perform an operation on a server that is only valid if the server was started using the node manager. |
|
Action
| Configure the node manager for machine null. Then, execute command cmd for server svrName. |
|
|
BEA-300014
|
Error: Could not execute command cmd for server svrName using the node manager, because the node manager listen address is not set.
|
Description
| The listen address for the node manager is not set. Set a valid listen address for the node manager on the machine associated with server svrName. |
|
Cause
| The node manager address has not been set. |
|
Action
| Set a valid node manager listen address. |
|
|
BEA-300015
|
Error: Could not execute command cmd for server svrName using the node manager, because the node manager listen port is not set.
|
Description
| The listen port for the node manager is not set. Set a valid listen port for the node manager on the machine associated with server svrName. |
|
Cause
| The node manager port has not been set. |
|
Action
| Set a valid node manager listen port. |
|
|
BEA-300016
|
Error: Could not execute command cmd for server svrName using the node manager, because the remote start configuration was not found.
|
Description
| The remote start configuration for the server svrName is not set. |
|
Cause
| The remote start configuration is missing. |
|
Action
| Set the remote start configuration for server svrName in the Remote Start tab on the configuration page for this server in the Admin Console. |
|
|
BEA-300017
|
Error: Could not execute command cmd for server svrName using the node manager, because the username and password are not set.
|
Description
| The username and password for getting the configuration from the admin server are not set in the Remote Start tab on the configuration page for this server in the Admin Console. |
|
Cause
| The username and password to be used to boot the server are not set. |
|
Action
| Set the username and password in the Remote Start tab for the server in the Admin Console. |
|
|
BEA-300018
|
Error: Could not execute command cmd for server svrName using the node manager, because the server listen address is not set.
|
Description
| The listen address for server svrName is not a valid listen address. |
|
Cause
| The server listen address has not been set. |
|
Action
| Set a valid server listen address. |
|
|
BEA-300019
|
Error: Could not execute command cmd for server svrName using the node manager, because the server listen port or protocol is not set.
|
Description
| The listen port or protocol is not valid for server svrName. |
|
Cause
| The server listen port or protocol has not been set. |
|
Action
| Set a valid server listen port or protocol. |
|
|
BEA-300020
|
Error: Could not get logs for server svrName using the node manager, because the log type logType specified is invalid. This type can only be either WL_output or WL_error.
|
Description
| The log to be fetched by the node manager for server svrName is an invalid type. It should be either of type WL_output or WL_error. |
|
Cause
| The user tried to get a log of an invalid type. |
|
Action
| Specify a valid type and retry the operation. |
|
|
BEA-300021
|
Error: Could not execute command cmd for server svrName using the node manager. Failed to create output file fileName in the directory logDirectory.
|
Description
| Creation of output file fileName in directory logDirectory failed. Make sure the directory is writable and there is enough space. |
|
Cause
| Unable to create specified log file. |
|
Action
| Verify that the disk is not full and retry the operation. |
|
|
BEA-300022
|
Error: Could not execute command cmd for server svrName using the node manager, due to an internal error.
|
Description
| Command cmd could not be executed on server svrName using the node manager. |
|
Cause
| This is an internal error. |
|
Action
| Contact BEA Technical Support. |
|
|
BEA-300026
|
Error: The node manager command servlet was unable to send a reply to the node manager health query.
|
Description
| The node manager command servlet was unable to send a reply to the node manager health query. |
|
Cause
| This is an internal error. |
|
Action
| Contact BEA Technical Support. |
|
|
BEA-300027
|
Error: The node manager command servlet received an invalid command.
|
Description
| The node manager command servlet received an invalid internal query. |
|
Cause
| This is an internal error. |
|
Action
| Contact BEA Technical Support. |
|
|
BEA-300028
|
Error: Error: Authentication Failure - arg.
|
Description
| The node manager command servlet was unable to authenticate the credentials of the internal query. |
|
Cause
| Security configuration error. The identity (username/password) specified in the Remote Start configuration of this server, which is used to boot the server, is being denied access to the server at runtime. |
|
Action
| Make sure that the identity specified in the Remote Start parameters for this server also has the privileges to access this server at runtime. |
|
|
BEA-300029
|
Error: Error: Action Failure - arg.
|
Description
| The node manager command servlet was unable to perform the action specified in the internal query. |
|
Cause
| This is an internal error. |
|
Action
| Contact BEA Technical Support. |
|
|
BEA-300030
|
Error: The socket close failed. Reason: arg.
|
Description
| The SSL socket opened to the node manager to execute a command could not be closed for the indicated reason. |
|
Cause
| This is an internal error. |
|
Action
| Contact BEA Technical Support. |
|
|
BEA-300031
|
Debug: Could not execute command arg0 for server arg1 using the node manager, because the server is already running.
|
Description
| The server is already running, so the command specified using the node manager cannot be executed. |
|
Cause
| The server is already running. |
|
Action
| No action required. |
|
|
BEA-300032
|
Error: Could not execute command cmd on the node manager. Unable to create file fileName under directory logDirectory.
|
Description
| Creation of file fileName failed under directory logDirectory. Make sure that the directory is writeable and the disk is not full. |
|
Cause
| Unable to create the specified log file. |
|
Action
| Verify that the disk is not full and the directory is writeable. Then retry the operation. |
|
|
BEA-300033
|
Error: Could not execute command "arg0" on the node manager. Reason: "arg1".
|
Description
| No details. |
|
Cause
| The node manager command execution failed. |
|
Action
| No action required. |
|
|
BEA-300034
|
Error: Could not execute command "arg0" for server "arg1" using the node manager. Reason: arg2.
|
Description
| No details. |
|
Cause
| Command execution for the server using the node manager failed. |
|
Action
| No action required. |
|
|
BEA-300035
|
Warning: Warning : arg0
|
Description
| Warning condition encountered by the node manager. |
|
Cause
| Details of the cause are provided in the message. |
|
Action
| Details of the action are provided in the message. |
|
|
BEA-300036
|
Error: Error :arg0
|
Description
| Error condition encountered by the node manager. |
|
Cause
| Details of the cause are provided in the message. |
|
Action
| Details of the action are provided in the message. |
|
|
BEA-300037
|
Warning: The node manager at host arg0 and port arg1 seems to be down. Start the node manager and rerun the command.
|
Description
| A connect exception was encountered while creating a socket to the node manager. |
|
Cause
| The node manager is not running. |
|
Action
| Start the node manager and rerun the command. |
|
|
BEA-300038
|
Warning: The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : arg0
|
Description
| An exception was encountered while attempting to create an SSL connection to the node manager. |
|
Cause
| Check the message for details. This error might be due to a faulty SSL configuration. |
|
Action
| Check the message for details. |
|
|
BEA-300039
|
Error: The state change notification registration failed. The server will only be able to respond to the GETSTATE messages by the node manager. Reason : arg0
|
Description
| Registration of the node manager agent for state change notification of the server failed. The server will not proactively be able to notify the node manager of its changed state. |
|
Cause
| See the message for details. |
|
Action
| Check the message for details and take corrective action accordingly. |
|
|
BEA-300040
|
Error: I/O error while writing node manager status change message.
|
Description
| An I/O error occurred while attempting to write a node manager status change message to the standard output stream. While the server will continue to run, this will prevent the node manager from being able to continue monitoring the server properly. |
|
Cause
| Possibly the standard output stream has been closed or the node manager has stopped monitoring. |
|
Action
| Restart the server if this server requires monitoring. |
|
|
BEA-300041
|
Error: Failed to register for startup mode change notfication. Reason : arg0
|
Description
| Registering of node manager agent as startup mode change notification listener failed. |
|
Cause
| Check the message for details. |
|
Action
| Check the message for details and take action accordingly. |
|
|
BEA-300042
|
Warning: Failed to cancel the startup request to start the server arg0 of domain arg1.
|
Description
| The request to cancel the server arg0 of domain arg1 could not be completed successfully. The server has advanced too far in the startup sequence. |
|
Cause
| The server has advanced too far in the startup sequence. |
|
Action
| Shutdown the server gracefully. |
|
|
BEA-300043
|
Warning: Node manager native library not found - server process id not saved.
|
Description
| Could not load the node manager native library or it is not available on this platform. As a result, the current server process id will not be saved and the node manager will be unable to kill this server. |
|
Cause
| Node manager native library not in library search path or is unavailable on this platform. |
|
Action
| Make sure that the node manager native library is available and in the library search path. |
|
|
BEA-300044
|
Error: An I/O error occurred while writing the server pid file: "name".
|
Description
| An I/O exception occurred while writing the current server process id to the server pid file. As a result the current server process id will not be saved and the node manager will be unable to kill this server. |
|
Cause
| Server pid file might be write protected. |
|
Action
| Make sure that the server pid file is not write protected. Also check to see if the parent directory exists (should have been created by the node manager server before starting the server) |
|
|
BEA-300045
|
Error: I/O error while executing command "cmd" on the node manager.
|
Description
| No details. |
|
Cause
| The node manager command execution failed due to an I/O error. |
|
Action
| No action required. |
|
|
BEA-300046
|
Error: I/O error while executing command "cmd" for server "serverName" using the node manager.
|
Description
| No details. |
|
Cause
| THe node manager command execution failed due to an I/O error. |
|
Action
| No action required. |
|
|
BEA-300047
|
Debug: msg
|
Description
| Uncatalogued debug message - please do not change. |
|
Cause
| Debugging - please do not change. |
|
Action
| No action required. |
|
|
BEA-300048
|
Error: I/O error while trying to start the specified server: e
|
Description
| An I/O error occurred while attempting to start the specified server. |
|
Cause
| The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration. |
|
Action
| Make sure that you can access the remote NodeManager. This may require setting up SSH permissions for the SSH-based NodeManager. Also ensure that the default PATH settings for the remote NodeManager are correct. See the NodeManager documentation for more information. |
|
|
BEA-300049
|
Error: An I/O error occurred while writing the server URL file: "name".
|
Description
| An I/O exception occurred while writing the current server default URL to the server URL file. As a result the current server default URL will not be saved. The node manager uses the contents of this file on restart in conjunction with the pid file. After checking the existence of the process using the PID stored in the pid file, the node manager will try to communicate to the server using the default URL to make sure that the process is indeed the WLS server. Without this file, nodemanager will not be able to perform the second check. |
|
Cause
| Server URL file might be write protected. |
|
Action
| Make sure that the server URL file is not write protected. Also check to see if the parent directory exists (should have been created by the node manager server before starting the server) |
|
|
BEA-300050
|
Error: An I/O error occurred while updating the node manager secret file : "file".
|
Description
| An I/O exception occurred while updating the domain wide node manager password hash after the nodemanager user and/or password were changed and activated. Access to the nodemanager with the current domain credentials will not be successful until the node manager hash is updated |
|
Cause
| The file might be write protected. |
|
Action
| Make sure that the file is not write protected. To recover from the failure, WLST nmEnroll command can be used to update the node manager secret |
|
