13.4 Messages from KEOS20000 to KEOS29999
This section describes the messages from KEOS20000 to KEOS29999 output when Cosminexus Manager is used for system setup, operation, and maintenance.
-
KEOS20001-I (W/F)
The start/stop settings of aa....aa(bb....bb) was changed.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The start and stop settings were changed.
-
KEOS20002-E (W)
The start/stop settings contain an error. detail=aa....aa
aa....aa: Details
- Description
-
An invalid value was specified in the start or stop settings.
The update process will not be performed.
- Action
-
Enter a correct settings value.
-
KEOS20003-E (W/F)
The start/stop cannot be execute because the status of aa....aa(bb....bb)is cc....cc.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Status
- Description
-
The logical server cannot be started or stopped, because a process is being executed.
The logical server will not be started or stopped.
- Action
-
Perform the process after the logical server becomes executable.
Re-confirm the following details if the administration agent is running but the status does not change from communication failure even after sometime:
-
Does the application server version of the Administration Agent match with the Management Server?
-
If the application server editions of the Administration Agent and the Management Server are different, confirm that these editions can be connectable each other.
-
-
KEOS20004-I (W/F)
cc....cc request of aa....aa(bb....bb) was accepted.
aa....aa: Logical server name (management domain name or host name)
bb....bb: Logical server type (management domain or host)
cc....cc: Start/ Stop/ Batch Start/ Batch Stop/ Batch Restart
- Description
-
A request was issued to the Management Agent.
-
KEOS20005-E (W/F)
The start of aa....aa(bb....bb) failed. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to start the logical server has failed.
The startup process will be interrupted after starting the logical server in the same startup order.
- Action
-
Confirm that the settings information is distributed. See the detailed information and the Management Agent log, remove the errors, and then re-execute the process.
For details on how to collect the material and investigate cause of the error, see 6.4.2 Troubleshooting during operations in the uCosminexus Application Server Maintenance and Migration Guide.
-
KEOS20007-I (W/F)
aa....aa(bb....bb) has started.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server starts.
-
KEOS20008-E (W/F)
The collective start canceled.
- Description
-
Collective startup was suspended.
- Action
-
See the detailed information and the Management Agent log generated so far, remove the errors, and then re-execute the process.
-
KEOS20009-I (W/F)
The collective start has started.
- Description
-
The collective start has started.
-
KEOS20010-I (W/F)
The collective start ended.
- Description
-
The collective start process ends.
-
KEOS20011-E (W/F)
The stop of aa....aa(bb....bb) failed. detail= cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to stop the logical server has failed.
The processing continues if there are other logical servers to be stopped.
- Action
-
See the detailed information and the Management Agent log, remove the errors, and then re-execute the process.
For details on how to collect the material and investigate the cause, see 4.3.1(2) Acquiring the log of Administration agent, Management agent, and Management Server in the uCosminexus Application Server Maintenance and Migration Guide.
If the detailed information indicates that the termination monitoring time has expired, confirm that the specified operation check interval for the logical server is not greater than the termination check interval.
-
KEOS20012-I (W/F)
aa....aa(bb....bb) was stopped.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server was stopped.
-
KEOS20014-I (W/F)
The collective stop has started.
- Description
-
The collective stop has started.
-
KEOS20015-I (W/F)
The collective stop ended.
- Description
-
The collective start process ends.
-
KEOS20016-I (W/F)
The collective restart has started.
- Description
-
The collective restart has started.
-
KEOS20017-I (W/F)
The collective restart ended.
- Description
-
The collective restart process ends.
-
KEOS20018-E (W/F)
The logical server for processing does not exist.
- Description
-
There are no logical servers to be collectively processed in the specified domain, host, and cluster.
The collective processing will not be performed.
- Action
-
The possible causes are as follows: Take the necessary action depending on the cause.
-
Logical server is not created in the specified domain, host, and cluster.
Create the logical server.
-
The startup order is not specified in the logical server, so the server is not out of scope of collective processing.
Specify the startup order.
-
-
KEOS20019-E (W)
The starting order of aa....aa(bb....bb) contains an error. input=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Inputted value
- Description
-
An invalid value is entered in the startup order.
The startup order will not be updated.
- Action
-
Enter a numeric value from 0 to 99 in the startup order or do not enter anything (do not specify the startup order).
-
KEOS20020-E (W)
The starting order of aa....aa(bb....bb) is before the starting order of cc....cc(dd....dd) to use.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Logical server name
aa....aa: Logical server type
- Description
-
The startup order of dependent logical servers is invalid.
The startup order will not be updated.
- Action
-
Specify the startup order of the J2EE servers after the startup order of the naming services to be used.
-
KEOS20021-E (W/F)
The stating order could not be changed. detail=aa....aa
aa....aa: Details
- Description
-
The stating order could not be changed.
The startup order will not be updated.
- Action
-
See the detailed information, remove the error, and then re-execute the process.
-
KEOS20022-I (W/F)
The stating order has changed.
- Description
-
The stating order has changed.
-
KEOS20023-E (W/F)
The starting order of cc....cc(dd....dd) which aa....aa(bb....bb) is used for is invalid.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Logical server name
aa....aa: Logical server type
- Description
-
The startup order is invalid.
The startup order will not be updated.
The startup order is not specified in the applicable logical server, but is specified in the logical server that uses the applicable logical server.
- Action
-
Revise the startup order.
-
KEOS20024-E (W/F)
The collective start failed. detail=aa....aa
aa....aa: Details
- Description
-
The collective start failed.
The collective startup will not be performed.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the process.
-
KEOS20025-E (W/F)
The collective stop failed. detail=aa....aa
aa....aa: Details
- Description
-
The collective stop failed.
The collective termination will not be performed.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the process.
-
KEOS20026-E (W/F)
The collective restart failed. detail=aa....aa
aa....aa: Details
- Description
-
The collective restart failed.
The collective restart will not be performed.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the process.
-
KEOS20027-E (W/F)
The auto restart of aa....aa (bb....bb) failed. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempted auto restart has failed.
The auto restart will not be performed.
- Action
-
See the detailed information, remove the error, and then start from the start or stop screen.
-
KEOS20028-E (W/F)
The automatic restart count specified in aa....aa (bb....bb) has exceeded. Restart count =cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Restart count
- Description
-
The specified automatic restart count has exceeded. Automatic restart will end.
- Action
-
Remove the causes of the error output to the logical server, and then start the logical server.
-
KEOS20029-E (F)
The thread for the watcher of a force stop could not be created. detail=aa....aa
aa....aa: Details
- Description
-
The thread for the watcher of a force stop could not be created.
The forced termination process will not be performed.
- Action
-
See the detailed information, remove the error, and then restart the Management Server.
-
KEOS20030-E (W/F)
aa....aa(bb....bb) cannot start because invalid settings. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
The logical servers cannot be started or stopped individually.
The starting or stopping process will not be performed.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the process.
-
KEOS20031-E (W/F)
aa....aa(bb....bb) stopped abnormally.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server has abended.
- Action
-
Run auto restart if auto restart is specified.
For details on how to collect the material and investigate the cause of the error, see 6.4.2 Troubleshooting during operations in the uCosminexus Application Server Maintenance and Migration Guide.
-
KEOS20032-I (W/F)
aa....aa(bb....bb) was stopped automatically.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server was stopped automatically.
-
KEOS20033-E (W/F)
The auto stop of aa....aa(bb....bb) failed. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to stop the logical server automatically has failed.
Automatic stopping of the logical server will not be performed.
The process exists in the logical server, but does not operate normally.
- Action
-
See the detailed information, remove the error, and then stop the server.
If the detailed information indicates that the termination monitoring time has expired, confirm that the specified operation check interval for the logical server is not greater than the termination check interval.
-
KEOS20034-I (W/F)
The auto stop of aa....aa(bb....bb) has started.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The auto stop process starts.
-
KEOS20035-I (W/F)
The auto stop of aa....aa(bb....bb) ended.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The auto stop process ends.
-
KEOS20036-I (W/F)
The auto restart of aa....aa(bb....bb) has started.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The auto restart process starts.
-
KEOS20037-I (W/F)
The auto restart of aa....aa(bb....bb) ended.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The auto restart process ends.
-
KEOS20040-E (W/F)
The force stop of aa....aa(bb....bb) failed. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to stop the logical server forcibly has failed.
The forced termination will not be performed.
- Action
-
See the detailed information, remove the error, and then terminate the process manually.
If the detailed information indicates that the termination monitoring time has expired, confirm that the specified operation check interval for the logical server is not greater than the termination check interval.
-
KEOS20042-I (W/F)
cc....cc status of aa....aa(bb....bb) was received.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Status
- Description
-
Received the status of the logical server.
-
KEOS20050-E (W/F)
The start/stop settings of aa....aa(bb....bb) could not be changed. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to update the start or stop settings of the logical server has failed.
The update process will not be performed.
- Action
-
See the detailed information, remove the error, and then re-execute the termination process.
-
KEOS20051-I (W/F)
The snapshot log of aa....aa(bb....bb) was collected. file name=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: snapshot log file name
- Description
-
The snapshot log was acquired.
-
KEOS20052-E (W/F)
The snapshot log of aa....aa(bb....bb) could not be collected. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An error occurred while the snapshot log was being collected.
- Action
-
See the details, remove the cause of the error, and then re-execute the processing.
If "A timeout occurred while collecting the snapshot log." is displayed in the details, take action using one of the following:
-
Collect the snapshot log manually from mngsvrutil command and management portal.
-
Increase the value of the com.cosminexus.mngsvr.snapshot.auto_collect.timeout key in the Management Server configuration file (mserver.properties).
-
Review, and if necessary revise, the snapshot log collection definition file (snapshotlog.conf and snapshotlog.2.conf).
-
-
KEOS20053-I (W/F)
The snapshot log of aa....aa(bb....bb) was not collected because the target file does not exist.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The snapshot log was not collected because there were no target files.
-
KEOS20054-I (W/F)
aa....aa(bb....bb) is starting.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server will start.
-
KEOS20055-I (W/F)
aa....aa(bb....bb) is stopping.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server will terminate.
-
KEOS20056-I (W/F)
aa....aa(bb....bb) is stopping forcefully.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server will forcibly be stopped.
-
KEOS20057-I (W/F)
The snapshot log of aa....aa(bb....bb) is collecting.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The snapshot log will be collected.
-
KEOS20058-I (W/F)
The auto restart of aa....aa(bb....bb) and the Logical Server cc....cc premised has started.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: List of logical server names
- Description
-
The auto restart process starts.
-
KEOS20059-I (W/F)
The auto restart of aa....aa(bb....bb) and the Logical Server cc....cc premised ended.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: List of logical server names
- Description
-
The auto restart ended.
-
KEOS20060-W (W/F)
The logical server specified for use in the environment configuration is not set up as a prerequisite logical server.
- Description
-
The logical server specified for using the environment configuration is not set up as a prerequisite logical server.
The processing continues.
-
KEOS20061-I (W/F)
The auto stop of aa....aa (bb....bb) and the logical server cc....cc premised has started.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: List of logical server names
- Description
-
The automatic stop process starts.
-
KEOS20062-I (W/F)
The auto stop of aa....aa(bb....bb) and the Logical Server cc....cc premised ended.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: List of logical server names
- Description
-
The auto stop ended.
-
KEOS20063-I (W/F)
The auto stop of the Logical Server cc....cc premised on aa....aa(bb....bb) has started.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: List of logical server names
- Description
-
The auto stop process starts.
-
KEOS20064-I (W/F)
The auto stop of the Logical Server cc....cc premised on aa....aa(bb....bb) ended.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: List of logical server names
- Description
-
The auto stop ended.
-
KEOS20065-E (W)
The starting order of aa....aa(bb....bb) is not set up before other logical servers.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The startup order of the logical servers is invalid.
The startup order will not be updated.
- Action
-
Specify the startup order of the applicable logical servers before the startup order of other logical servers.
-
KEOS20067-I (W/F)
The snapshot log of aa....aa(bb....bb) was interrupted.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The process of collecting the snapshot log was interrupted.
-
KEOS20068-E (W/F)
The snapshot log of aa....aa(bb....bb) could not be interrupted. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
The collection process of the snapshot log cannot be interrupted.
The collection process of the snapshot log continues.
- Action
-
See the detailed information, remove the error, and then re-execute the process.
-
KEOS20069-I (W/F)
The command at the time of abnormal end detection for aa....aa(bb....bb) is starting.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The failure detection command of the logical server starts.
-
KEOS20070-I (W/F)
The command at the time of abnormal end detection for aa....aa(bb....bb)is complete.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The failure detection command of the logical server has finished.
-
KEOS20071-E (W/F)
The command at the time of abnormal end detection for aa....aa(bb....bb) failed. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to execute the failure detection command of the logical server has failed.
The failure detection command will not run.
- Action
-
See the detailed information, remove the error, and then re-execute the process.
-
KEOS20072-I (W/F)
The command at the time of abnormal end detection for aa....aa(bb....bb) is not defined.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The failure detection command is not defined.
The failure detection command will not run.
-
KEOS20073-I (W/F)
aa....aa(bb....bb) is stopping gracefully.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The planned termination process was started.
-
KEOS20074-E (W/F)
The graceful stop of aa....aa(bb....bb) failed. detail=cc....cc
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempted planned termination has failed.
- Action
-
See the detailed information and the Management Agent log, remove the error, and then re-execute the process.
If the detailed information indicates that the termination monitoring time has expired, confirm that the specified operation check interval for the logical server is not greater than the termination check interval.
-
KEOS20075-I (W/F)
The snapshot log(cc....cc) of aa....aa(bb....bb) is collecting.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: snapshot log collection target
- Description
-
The snapshot log will be acquired.
-
KEOS20076-I (W/F)
The snapshot log(cc....cc) of aa....aa(bb....bb) was collected. file name=dd....dd
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: snapshot log collection target
dd....dd: snapshot log file name
- Description
-
The snapshot log was acquired.
-
KEOS20077-I (W/F)
The snapshot log(cc....cc) of aa....aa(bb....bb) was not collected because the target file does not exist.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: snapshot log collection target
- Description
-
The snapshot log was not collected because there were no target files.
-
KEOS20078-E (W/F)
The snapshot log(cc....cc) of aa....aa(bb....bb) could not be collected. detail=dd....dd
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: snapshot log collection target
dd....dd: Details
- Description
-
The snapshot log cannot be acquired.
- Action
-
See the detailed information, remove the error, and then re-execute the process.
-
KEOS20079-W (W/F)
The snapshot log(cc....cc) of aa....aa(bb....bb) was collected. file name=dd....dd detail=ee....ee
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: snapshot log collection target
dd....dd: snapshot log file name
ee....ee: Detailed information
- Description
-
The snapshot log was collected, but an error occurred.
- Action
-
See the detailed information, remove the error, and then re-execute the process.
-
KEOS20080-I (F)
The environment variable for starting aa....aa(bb....bb) was get. cc....cc=dd....dd
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Environment variable
dd....dd: Environment variable value
- Description
-
The environment variable information used during logical server startup was acquired.
-
KEOS20100-E (W/F)
An unexpected exception occurred. detail=aa....aa
aa....aa: Details
- Description
-
An unexpected exception occurred.
The specified request will not be performed.
- Action
-
See the detailed information, remove the error, and then re-execute the termination process.
If the error recurs and it cannot be resolved even after restarting, contact maintenance personnel.
-
KEOS20501-I (F)
The watcher of aa....aa(bb....bb) was started.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
Monitoring the logical server was started.
-
KEOS20502-I (F)
The watcher of aa....aa(bb....bb) was stopped.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
Monitoring the logical server was stopped.
-
KEOS20505-E (F)
Administration Agent on cc....cc(Host) could not be connected in aa....aa(bb....bb) processing.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Host name
- Description
-
A connection cannot be established with the Administration Agent.
The start and stop process will be interrupted.
- Action
-
Start and stop once again from the start/stop screen of the logical server. If the same phenomenon occurs even if started and stopped once again, check whether the Administration Agent is running in the operation host of the applicable logical server.
Check the following details if the Administration Agent is running:
-
Does the application server version of the Administration Agent match with the Management Server?
-
If the application server editions of the Administration Agent and the Management Server are different, confirm that these editions can be connectable each other.
-
-
KEOS20506-E (F)
The host name and the port number of aa....aa(bb....bb) could not be acquired.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
An attempt to acquire the host name and the port number has failed.
The monitoring process will be interrupted.
- Action
-
Confirm whether the following files are deleted or whether the file permissions are changed:
-
In Windows
Cosminexus-HTTP-Server-installation-directory\conf\httpsd.conf
-
In UNIX
/opt/hitachi/httpsd/conf/httpsd.conf
-
-
KEOS20507-E (F)
The process ID of aa....aa(bb....bb)could not be acquired.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
An attempt to acquire the process ID has failed.
The monitoring process will be interrupted.
A reason may be that the service account of the Administration Agent is being changed.
- Action
-
Change the service account of the Administration Agent to system account, restart the Administration Agent, and then restart the logical server. When the error cannot be removed by this action, restart the logical server.
If the same phenomenon occurs even after the logical server is restarted, contact maintenance personnel.
-
KEOS20508-E (F)
The period of watching aa....aa(bb....bb)start up was expired.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The start monitoring time was exceeded.
The logical server will terminate.
- Action
-
Specify the start monitoring time of the logical server according to the environment.
In the logical J2EE server or the logical SFO server, a possible cause might be that the naming service to which Management Server will connect is not running. Confirm that the naming service set up in the Naming Service Connection Settings screen of the management portal is running.
-
KEOS20509-I (F)
The process ID(cc....cc) of aa....aa(bb....bb) could be acquired.
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Process ID
- Description
-
The process ID was acquired successfully.
-
KEOS20510-E (F)
Cannot open file: aa....aa
aa....aa: File name
- Description
-
An attempt to open the file has failed.
The monitoring process will be interrupted.
- Action
-
Check the operating environment and the settings such as file name and permissions.
-
KEOS20511-E (F)
A hang-up was detected during watch of aa....aa(bb....bb)
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server was found to have hung up.
The errors in the logical server will be reported to the Management Server.
- Action
-
Extract the data through actions such as collection of snapshot log, and then investigate the causes that led to the hang up.
-
KEOS21000-I (F)
The administration agent has started.
- Description
-
The administration agent has started.
-
KEOS21001-I (F)
The administration agent has finished.
- Description
-
The administration agent has finished.
-
KEOS21002-E (F)
An attempt to start the administration agent has failed.
- Description
-
An attempt to start the Administration Agent has failed.
- Action
-
Check the operating environment and the settings.
-
KEOS21003-E (F)
An attempt to stop the administration agent has failed.
- Description
-
An attempt to stop the administration agent has failed.
- Action
-
Check the operating environment and the settings.
-
KEOS21004-E (F)
An attempt to open the file has failed. (file name = aa....aa)
aa....aa: File name
- Description
-
An attempt to open the file has failed.
The operations of the Administration Agent will continue if possible, and will terminate if operations cannot be continued.
- Action
-
Check the operating environment and the settings such as file name and permissions.
-
KEOS21005-E (F)
The port number is invalid. (port number = aa....aa)
aa....aa: Port number
- Description
-
An invalid value is set in the port number.
The processing will be interrupted.
- Action
-
Check the operating environment and the settings.
-
KEOS21006-E (F)
A port number is already in use. (port number = aa....aa)
aa....aa: Port number
- Description
-
The specified port number is already being used.
The processing will be interrupted.
- Action
-
Check the operating environment and the settings.
-
KEOS21007-W (F)
An attempt to execute the command has failed. (command = aa....aa)
aa....aa: Command line string
- Description
-
An attempt to execute the displayed command has failed.
The processing continues.
- Action
-
Confirm the following details:
-
The command path is correct (whether it exists).
-
The command is executable (there are executable attributes).
-
The command access permission is appropriate.
-
Memory and disk space is sufficient.
-
-
KEOS21008-W (F)
The command finished with an error. (command = aa....aa; exit code = bb....bb)
aa....aa: Command line string
bb....bb: Exit code
- Description
-
The displayed command finished with an error.
The processing continues.
- Action
-
Confirm whether the preconditions (such as settings and environment variables) for executing the command are fulfilled, and remove the cause of the error in the command.
-
KEOS21009-I (F)
The log file specified in aa....aa does not exist.
aa....aa: Path of the snapshot log settings file
- Description
-
The log file described in the displayed snapshot log settings file does not exist.
The processing continues. The snapshot log file (zip) will not be created.
-
KEOS21010-I (F)
An access from aa....aa was refused.
aa....aa: IP address
- Description
-
There was an access from a host that is not permitted access.
This access will be ignored, and then the processing continues.
- Action
-
Specify settings so that access is permitted as and when required.
-
KEOS21011-E (F)
The connection was refused. (host = aa....aa; port = bb....bb)
aa....aa: Host name or IP address
bb....bb: Port number
- Description
-
The connection was refused.
The operations will continue if possible, and will terminate if operations cannot be continued.
- Action
-
Check the operating environment and settings shown below:
-
Is the Administration Agent running on the specified host?
-
Is the port number valid?
-
Is the access to the Administration Agent to which you will connect denied?
-
-
KEOS21012-I (F)
The command has started. (command = aa....aa ; pid = bb....bb ; cc....cc, dd....dd)
aa....aa: Command line string
bb....bb: Process ID
cc....cc: Environment variable
dd....dd: Environment information (In Windows, owner and group are always blank)
- Description
-
The command described in the command starts.
-
KEOS21013-I (F)
The command has finished. (command = aa....aa; pid = bb....bb, exit code = cc....cc)
aa....aa: Command line string
bb....bb: Process ID
cc....cc: Exit code
- Description
-
The command described in the command has finished.
-
KEOS21014-E (F)
An attempt to execute the command has failed. (command = aa....aa; cause = bb....bb)
aa....aa: Command line string
bb....bb: Cause
- Description
-
An attempt to execute the command described in the command has failed.
The processing will now stop.
- Action
-
Remove the error described in the cause, and then re-execute the command.
-
KEOS21015-I (F)
Collection of Snapshotlog was canceled.
- Description
-
A request was received to interrupt Snapshotlog collection while collection is in process.
-
KEOS21016-I (C)
Usage: snapshotlog output
- Description
-
This message is the usage method the snapshotlog command.
A message is displayed in the standard error output, and then the processing terminates.
- Action
-
See the message, and check the usage method of the command.
-
KEOS21017-I (C)
Collection of Snapshotlog has started.
- Description
-
The collection of Snapshotlog has started.
-
KEOS21018-I (C)
Collection of Snapshotlog has finished.
- Description
-
The collection of Snapshotlog has finished.
-
KEOS21019-E (C)
An attempt to collect Snapshotlog has failed. (cause = aa....aa)
aa....aa: Cause
- Description
-
An attempt to collect the Snapshotlog has failed.
- Action
-
Check the cause.
-
KEOS21020-E (F)
An attempt to initialize the administration agent has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to initialize the administration agent has failed.
- Action
-
Check the operating environment and the settings. When checking, confirm the following details:
-
Has a used port number been specified?
-
If specifying the settings for bind address, are those settings valid?
-
If the bind address is specified with the IP address pattern, does the pattern match with the local IP address?
-
-
KEOS21021-W (F)
The setting for Snapshotlog is invalid. (details = aa....aa)
aa....aa: Details
- Description
-
The specified Snapshotlog collection target is invalid. This specification will be ignored and the processing continues.
- Action
-
Revise the settings.
-
KEOS21022-W (F)
The specified property aa....aa is invalid. bb....bb will be used instead.
aa....aa: Property name
bb....bb: Default value
- Description
-
The specified property value is invalid.
The default value will be used.
- Action
-
Revise the settings.
-
KEOS21023-W (F)
An attempt to delete the file has failed. (file name = aa....aa)
aa....aa: File name
- Description
-
The file cannot be deleted.
The operations of the Administration Agent will continue if possible, and will terminate if operations cannot be continued.
- Action
-
Check the operating environment and the settings such as file name and permissions.
-
KEOS21024-E (F)
An attempt to create the directory has failed. (directory name = aa....aa)
aa....aa: Directory name
- Description
-
The directory cannot be created.
The operations of the Administration Agent will continue if possible, and will terminate if operations cannot be continued.
- Action
-
Check the operating environment and the settings such as file name and permissions.
-
KEOS21025-E (F)
An attempt to write to the file has failed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Detailed message
- Description
-
An attempt to write to the file has failed.
The operations of the Administration Agent will continue if possible, and will terminate if operations cannot be continued.
- Action
-
Check the operating environment and the settings such as file name and permissions.
-
KEOS21026-I (F)
Process monitoring will now start. (command = aa....aa, pid = bb....bb)
aa....aa: Command line string
bb....bb: Process ID
- Description
-
The monitoring of the process used in logical server monitoring will be restarted. The command line is the command line used in logical server startup.
-
KEOS21027-I (F)
The process has completed. (command = aa....aa, pid = bb....bb)
aa....aa: Command line string
bb....bb: Process ID
- Description
-
The process to be used in logical server monitoring was terminated. The command line is the command line used in logical server startup.
-
KEOS21028-W (F)
The specified property(aa....aa) is over. (bb....bb) is used.
aa....aa: Property name
bb....bb: Default value
- Description
-
The property specification has exceeded the permissible range. The default value will be used.
- Action
-
Revise the settings.
-
KEOS21029-W (F)
The period of watching the server dumping its thread information was expired.
- Description
-
The monitoring time of the thread dump output during forced termination was exceeded.
The termination process of the logical server will continue.
- Action
-
Revise the settings.
-
KEOS21030-I (F)
Collection of Snapshotlog specified in aa....aa has started.
aa....aa: Path of the snapshot log settings file
- Description
-
The collection of the snapshot log starts.
-
KEOS21031-I (F)
Collection of Snapshotlog specified in aa....aa has finished.
aa....aa: Path of the snapshot log settings file
- Description
-
The collection of the Snapshotlog has finished.
-
KEOS21032-W (F)
The IP address applicable to specified IP address pattern(aa....aa) found more than one. (bb....bb) is used.
aa....aa: IP address pattern string
bb....bb: Used IP address
- Description
-
Multiple local IP addresses were found corresponding to the IP address pattern specified in the adminagent.adapter.bind_host key in adminagent.properties file. Bind will be performed with the smallest IP address from among the corresponding IP addresses.
- Action
-
Change to an IP address pattern applicable only to one IP address.
-
KEOS21033-W (F)
Processing to check the operation of aa....aa (bb....bb) timed out. A retry will now be performed. (set value = cc....cc, current value = dd....dd)
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Setup value of the retry count
dd....dd: Current value of the retry count
- Description
-
Retry will be executed as the operation confirmation process has timed out. The operation confirmation process will be re-executed.
- Action
-
Extract the data through actions such as collection of snapshot log, and then investigate the causes that led to the timeout.
-
KEOS21034-W (F)
Processing to check the operation of aa....aa(bb....bb) has failed. A retry will now be performed. (set value = cc....cc, current value = dd....dd)
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Setup value of the retry count
dd....dd: Current value of the retry count
- Description
-
Retry will be executed as the operation confirmation process has failed. The operation confirmation process will be re-executed.
- Action
-
Extract the data through actions such as collection of snapshot log, and then investigate the causes for the failure in the operation confirmation process.
-
KEOS21035-E (F)
An abnormal status was detected during monitoring of aa....aa (bb....bb).
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
An abnormal status of the logical server was found. The errors in the logical server will be reported to the Management Server.
- Action
-
Extract the data through actions such as collection of snapshot log, and then investigate the causes for the detection of the abnormal status.
-
KEOS21036-I (F)
The log file specified in aa....aa and bb....bb does not exist.
aa....aa: Path of the Snapshot log settings file for primary data
bb....bb: Path of the Snapshot log settings file for secondary data
- Description
-
The log file described in the displayed snapshot log settings file does not exist. The processing continues. The Snapshot log file (zip) will not be created.
-
KEOS21037-I (F)
Collection of Snapshotlog specified in aa....aa and bb....bb has started.
aa....aa: Path of the Snapshot log settings file for primary data
bb....bb: Path of the Snapshot log settings file for secondary data
- Description
-
The collection of the Snapshotlog starts.
-
KEOS21038-I (F)
Collection of Snapshotlog specified in aa....aa and bb....bb has finished.
aa....aa: Path of the Snapshot log settings file for primary data
bb....bb: Path of the Snapshot log settings file for secondary data
- Description
-
The collection of the Snapshotlog has finished.
-
KEOS21039-E (F)
The local address was not found. A forced stop will be performed. (address = aa....aa)
aa....aa: IP address
- Description
-
The logical server was terminated forcefully, and the Administration Agent was terminated on detection of the standby node.
- Action
-
Check the operating environment and the settings.
-
KEOS21040-W (F)
Cannot specify the unique user name from the owner of the file aa....aa, because there are two or more users related to user ID bb....bb. The user name cc....cc is used to execute dd....dd.
aa....aa: File name
bb....bb: User ID
cc....cc: User name
dd....dd: Command
- Description
-
The user name could not be specified because more than one user is registered in relation to the file owner. The user name displayed in the message is used, and the processing is continued.
- Action
-
For any problem with the user name displayed in the message, enable the specification of the user name from the user ID.
-
KEOS21041-W (F)
Could not connect to the RMI registry. detail=aa....aa
aa....aa: Details
- Description
-
Could not connect to the RMI registry. The processing of the Administration Agent will be continued.
- Action
-
If any error occurs after this message, see the detailed information, and then check the operating environment or settings.
-
KEOS21042-W (F)
An attempt to substitute the variable for collecting Snapshotlog has failed using the snapshotlog command. Variable name= aa....aa, Details= bb....bb within the collection target definition file
aa....aa: Variable name within the collection target definition file
bb....bb: Details
- Description
-
An attempt to substitute the variable for collecting Snapshotlog has failed using the snapshotlog command. The variable will be ignored for which an attempt to substitute has failed, and the process will be continued.
- Action
-
See the details of the message, and if necessary, revise the variable settings.
-
KEOS21100-I (L/F)
The administration agent service has started.
- Description
-
The Administration Agent service has started.
-
KEOS21101-I (L/F)
The administration agent service has stopped.
- Description
-
The Administration Agent service has stopped.
-
KEOS21102-E (L/F)
The administration agent service could not be initialized.
- Description
-
An attempt to initialize the Administration Agent service has failed.
The processing will be interrupted.
- Action
-
A message describing the details is output. See the message, and then remove the error.
-
KEOS21103-E (L/F)
The administration agent service could not be started.
- Description
-
The Administration Agent service cannot be started.
The processing will be interrupted.
- Action
-
Check the operating environment and the settings.
-
KEOS21104-E (F)
The administration agent service could not output information to the Event Log service. (ec = aa....aa)
aa....aa: Error code
- Description
-
The information cannot be output to the event log.
The process will continue without output to the event log.
- Action
-
Confirm that the event log service is operating normally.
-
KEOS21105-E (L/F)
The administration agent could not be started.
- Description
-
The Administration Agent cannot be started.
The processing will be interrupted.
- Action
-
A message describing the details is output. See the message, and then remove the error.
-
KEOS21106-E (L/F)
The administration agent command could not be acquired from the registry.
- Description
-
The Administration Agent command cannot be acquired from the registry.
The processing will be interrupted.
- Action
-
If the problem cannot be resolved even after restarting the server, contact maintenance personnel.
-
KEOS21107-E (L/F)
The administration agent could not be started. (ec = aa....aa)
aa....aa: Error code
- Description
-
An attempt to start the Administration Agent service has failed.
- Action
-
Check the operating environment and the settings.
-
KEOS21108-E (L)
The administration agent could not be started. (detail = aa....aa)
aa....aa: Detail
- Description
-
The Administration Agent service could not be started. The processing will be interrupted.
- Action
-
Reference the message details, and then remove the cause of the error. If the details are "The logon user is not using a local system account, or does not belong to the Administrators group", specify a local system account or an account belonging to the Administrators group in the Administration Agent log on account.
-
KEOS21109-W (F)
Synchronous execution of Administration Agent failed.
- Description
-
The synchronous execution of Administration Agent has failed.
The synchronous execution will be interrupted.
- Action
-
After a pause, use the mngsvrutil check command or the adminagentcheck command, and confirm that Administration Agent is operating. If you are unable to confirm the operation, see the message output to adminagentctl.exe.[1 through 16].log and adminagentsv.exe.[1 through 16].log, remove cause of the error, and then re-execute the command.
-
KEOS21120-I (L/F)
The executing TerminateProcess() will now start. (handle = aa....aa, pid = bb....bb, command = cc....cc)
aa....aa: Handle of the process to be stopped
bb....bb: Process ID of the process to be stopped
cc....cc: Command line string used for starting the process to be stopped
- Description
-
The execution of TerminateProcess() will start.
-
KEOS21121-I (L/F)
The executing TerminateProcess() ended. (handle = aa....aa, pid = bb....bb, rc = cc....cc, ec = dd....dd, command = ee....ee)
aa....aa: Handle of the process to be stopped
bb....bb: Process ID of the process to be stopped
cc....cc: Return value of TerminateProcess()
dd....dd: Error code of TerminateProcess()
ee....ee: Command line string used for starting the process to be stopped
- Description
-
The execution of TerminateProcess() has ended.
-
KEOS21200-I (C/F)
The administration agent has started.
- Description
-
The Administration Agent service has started.
-
KEOS21201-I (C/F)
The administration agent has stopped.
- Description
-
The Administration Agent service has stopped.
-
KEOS21202-E (C/F)
An attempt to start the administration agent has failed.
- Description
-
An attempt to start the Administration Agent service has failed.
The command execution will be suspended.
- Action
-
-
If end code is 1
Check the operating environment and settings.
-
If end code is 3
After a pause, use the mngsvrutil check command or the adminagentcheck command, and check that Administration Agent is operating.
If you are unable to check the operations, see the messages output to adminagentctl.exe.[1 through 16].log and adminagentsv.exe.[1~16].log console in Windows, and adminagentctl.[1 through 16].log and the console in UNIX, remove the cause of the error, and re-execute the command.
-
-
KEOS21203-E (C/F)
An attempt to stop the administration agent service has failed.
- Description
-
An attempt to stop the Administration Agent service has failed.
The command execution will be suspended.
- Action
-
-
If end code is 1
Check the operating environment and settings.
-
If end code is 3
After a pause, check that Administration Agent is stopped.
If you are unable to check that Administration Agent is stopped, see the messages output to adminagentctl.exe.[1 through 16].log and adminagentsv.exe.[1 through 16].log in Windows, and adminagentctl.[1 through 16].log and the console in UNIX, remove the cause of the error, and re-execute the command.
-
-
KEOS21206-E (C) (Windows)
Usage : adminagentctl {start|stop} [-sync [-timeout <timeout>]]
start : start Administration Agent Service
stop : stop Administration Agent Service
-sync : Synchronously executes the command.
-timeout <timeout> : Sets the timeout for synchronous execution.
- Description
-
The method of starting the command is incorrect.
The command execution will be suspended.
- Action
-
Enter the correct command again.
-
KEOS21206-E (C) (UNIX)
Usage : adminagentctl {start|stop} [-sync [-timeout <timeout>]] [-daemon]
start : start Administration Agent Service
stop : stop Administration Agent Service
-sync : Synchronously executes the command.
-timeout <timeout> : Sets the timeout for synchronous execution.
-daemon : Starts the command as a daemon process.
- Description
-
The method of starting the command is incorrect.
The command execution will be suspended.
- Action
-
Enter the correct command again.
-
KEOS21207-E (C/F)
The administration agent service could not be started. (ec = aa....aa)
aa....aa: Error code
- Description
-
An attempt to start the Administration Agent service has failed.
- Action
-
Check the operating environment and the settings.
-
KEOS21300-I (C)
Usage: mngautorun -d | [once|respawn] {server|agent|both} [-sync [-timeout <timeout>]]
-d: Restores the setting to its installation time state.
once : Sets automatic starting.
respawn: Sets automatic restarting.
server: Configures Management Server to run automatically
when this computer is started.
agent : Configures Administration Agent to run automatically
when this computer is started.
both : Configures both Management Server and Administration Agent
to run automatically, IN ORDER, when this computer is started.
-sync : Synchronously executes the command.
-timeout <timeout> : Sets the timeout for synchronous execution.
- Description
-
This message describes the usage method of the mngautorun command.
A message is displayed in the standard error output, and then the processing terminates.
- Action
-
See the message, and check the usage method of the command.
-
KEOS21301-E (C)
An internal error occurred. [aa....aa failed. ec=bb....bb]
aa....aa: API name
bb....bb: Error code
- Description
-
An API has failed.
The command execution will be suspended.
This command may have been used when some other application was operating the registry.
- Action
-
Re-execute the command later or terminate the other application, and then re-execute the command.
-
KEOS21302-E (C)
An attempt to allocate memory has failed.
- Description
-
An attempt to secure memory has failed.
The command execution will be suspended.
- Action
-
Secure sufficient memory by actions such as terminating other applications, and then re-execute the command.
-
KEOS21303-I (C)
Settings have been successfully completed.
- Description
-
The settings are successfully completed.
-
KEOS21304-I (F)
A network drive was successfully allocated. (drive = aa....aa, path = bb....bb)
aa....aa: Allocated drive name
bb....bb: Allocated path name
- Description
-
A network drive was successfully allocated.
-
KEOS21305-W (F)
An attempt to allocate a network drive has failed. (drive = aa....aa, path = bb....bb, winapi ec = cc....cc)
aa....aa: Allocated drive name
bb....bb: Allocated path name
cc....cc: WindowsAPI error code
- Description
-
An attempt to allocate a network drive has failed. The processing continues.
- Action
-
Check the error code contents, and revise the network drive settings.
Also, if the path specified in add.network.drive ends with \, the network drive might fail to connect. Revise the settings.
-
KEOS21306-E (F)
System call error. (func=aa....aa, ec=bb....bb)
aa....aa: API name
bb....bb: Error code
- Description
-
An attempt to process API has failed. The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS21307-W (F)
The network drives are not allocated because the logon account of the administration agent is a local system account.
- Description
-
The network drives are not allocated because the log on account of the Administration Agent is a local system account. The processing continues.
- Action
-
Start the Administration Agent using an account belonging to the Administrators group other than the local system account.
-
KEOS21309-E (C/F)
Configuration failed. (detail = aa....aa)
aa....aa: Details
- Description
-
The configuration failed. The processing will be cancelled.
- Action
-
See the message output in the details to remove the cause of the error, and then re-execute the command.
-
KEOS21310-I (C)
Usage: mngautorun -d | [once|respawn] {server|agent|both} [-runlevel <runlevel>] [-sync [-timeout <timeout>]]
-d: Restores the setting to its installation time state.
once : Sets automatic starting.
respawn: Sets automatic restarting.
server: Configures Management Server to run automatically
when this computer is started.
agent : Configures Administration Agent to run automatically
when this computer is started.
both : Configures both Management Server and Administration Agent
to run automatically, IN ORDER, when this computer is started.
-runlevel <runlevel> : Specifies the runlevel for performing
automatic starting and restarting.
-sync : Synchronously executes the command.
-timeout <timeout> : Sets the timeout for synchronous execution.
- Description
-
This message is the usage method of the mngautorun command.
-
KEOS21400-E (F)
An attempt to open the file has failed. (file = aa....aa)
aa....aa: Path of the defined file
- Description
-
An attempt to open the defined file has failed.
- Action
-
Check the environment such as the permissions for the defined file.
-
KEOS21401-E (F)
The specified option is invalid. (line = aa....aa)
aa....aa: Line number
- Description
-
The option in line number aa....aa is not specified properly.
- Action
-
Check the contents of the adminagentuser.cfg file.
-
KEOS21500-I (C)
Usage: adminagentcheck [-t <time>][<host>[:<port>]]
-t <time>
Specifies the command timeout limit
<time> - command timeout limit
<host>[:<port>]
Specifies the host and the port number of the Administration Agent to be connected.
<host> - host name or IP address
<port> - port number
- Description
-
This message describes the usage method of the adminagentcheck command.
A message is displayed in the standard error output, and then the processing terminates.
- Action
-
See the message, and check the usage method of the command.
-
KEOS22000-I (C)
The process was successfully killed. (pid=aa....aa)
aa....aa: Process ID
- Description
-
The process was stopped successfully.
-
KEOS22001-E (C)
The pid is invalid. (pid = aa....aa)
aa....aa: Process ID
- Description
-
The process ID is invalid.
The processing continues for the next process.
- Action
-
Check the command argument.
-
KEOS22002-E (C)
The process does not exist. (pid = aa....aa)
aa....aa: Process ID
- Description
-
The process does not exist.
The processing continues for the next process.
- Action
-
Check the command argument.
-
KEOS22003-E (C)
Access for execution of the command was denied.
- Description
-
The command execution was rejected.
The processing terminates.
- Action
-
A user belonging to the Administrators group needs to execute the command.
-
KEOS22004-E (C)
An attempt to kill the process has failed. (aa....aa)
aa....aa: Details
- Description
-
An attempt to stop the process has failed.
The processing will continue if possible, and will terminate if processing cannot be continued.
- Action
-
Contact maintenance personnel.
-
KEOS22005-I (C)
Usage: kill pid ...
- Description
-
This message describes the usage method of the Kill command.
A message is displayed in the standard error output, and then the processing terminates.
- Action
-
See the message, and check the usage method of the command.
-
KEOS22006-W (F)
The writing of the entry to a Zip file has failed. File=aa....aa detail=bb....bb
aa....aa: File name
bb....bb: Detailed message
- Description
-
The writing of the entry to a Zip file has failed.
The processing continues.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the process.
-
KEOS22100-I (C)
Usage:
mngsvrupdate [-t <target name>] [-k <target kind>] <command> [<args>]
where:
-t <target name>
Specifies a target name, such as a logical server or host.
-k <target kind>
Indicates the kind of a target. <target kind>:=logicalServer|host (the default is logicalServer)
<command>
"d2r" - Convert DataSource to Resource Adapter.
<args>
For the "d2r" command:
[<dataSource> [<resAdapter>]]
<dataSource> - DataSource
<resAdapter> - Resource Adapter
- Description
-
This message describes the usage method of the mngsvrupdate command.
A message is displayed in the standard error output, and then the processing terminates.
- Action
-
See the message, and check the usage method of the command.
-
KEOS22101-I (C/F)
No convertible datasource was found for the specified parameters.
- Description
-
There was not data source that can be converted.
-
KEOS22102-I (C/F)
The conversion ended successfully. (Logical Server = aa....aa, Datasource = bb....bb, Resource Adapter= cc....cc)
aa....aa: Logical server name
bb....bb: Display name of the data source before conversion
cc....cc: Display name of the resource adapter after conversion
- Description
-
The data source was converted to a resource adapter.
-
KEOS22103-W (C/F)
The conversion cannot be performed. (Logical Server = aa....aa, Datasource = bb....bb)
aa....aa: Logical server name
bb....bb: Display name of the data source before conversion
- Description
-
The conversion cannot be performed as the display name may have been changed.
The processing will be skipped, and then the processing for the next data source continues.
- Action
-
Specify the display name of the data source and resource adapter, and then execute the conversion command.
-
KEOS22104-E (C/F)
An attempt to convert the datasource has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to convert the data source has failed.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the process.
-
KEOS22300-W (F)
The default settings will be used because the manager.cfg file cannot be read.
- Description
-
The manager.cfg file cannot be read. The default value will be used. The processing continues using the default value.
- Action
-
Confirm whether:
-
manager.cfg file exists.
-
There are access permissions to manager.cfg file.
-
The format of the manager.cfg file is valid.
-
-
KEOS22301-W (F)
The specified property aa....aa is invalid. bb....bb will be used instead.
aa....aa: Property name
bb....bb: Default value
- Description
-
The specified property value is invalid. The processing continues using the default value.
- Action
-
Revise the settings.
-
KEOS22302-E (C)
An attempt to initialize the log has failed. (file name = aa....aa, reason = bb....bb)
aa....aa: Log file name
bb....bb: Cause of failure
- Description
-
An attempt to initialize the log has failed. The processing will be executed without log output.
- Action
-
Confirm the environment of the location where the log is to be output.
- Supplementary note
-
The processing continues after this message is output, but an error occurs in the subsequent processing due to causes related to the cause of this message, and the Management Server and Administration Agent might fail to start.
-
KEOS22303-I (F)
aa....aa
aa....aa: Continuation message
- Description
-
This message is a continuation message.
This message and the process ID and thread ID are the same and the message is a continuation of the message output just before this message.
-
KEOS22304-I (F)
The command has started. (command = aa....aa, pid = bb....bb, start time = cc....cc)
aa....aa: Command line
bb....bb: Process ID
cc....cc: Command start time
- Description
-
The command described in the message starts.
-
KEOS22305-I (F)
The command has finished. (pid = aa....aa, start time = bb....bb, exit code = cc....cc)
aa....aa: Process ID
bb....bb: Command start time
cc....cc: Exit code
- Description
-
The command, described in the process ID and the command start time, has finished.
-
KEOS22400-E (C)
Usage: mngenvsetup [-mng | -ua] { <Management User Group> | -d }
- Description
-
This message displays the usage method of the mngenvsetup command. The message code and message will be displayed in standard error output, and the processing will be suspended.
- Action
-
Execute the command with the correct syntax.
-
KEOS22401-I (C/F)
The configuration of permission has succeeded.(Command Name = aa....aa)
aa....aa: Name of the command for change
- Description
-
An attempt to set up the permission using the command for change was successful.
-
KEOS22402-I (C/F)
The configuration of group has succeeded.(Command Name = aa....aa, Group Name = bb....bb)
aa....aa: Name of the command for change
bb....bb: Specified group name
- Description
-
An attempt to set up the specified group using the command for change was successful.
-
KEOS22403-I (C/F)
The both configurations of MNG Administration Group and Integration User Administration Group have succeeded.(Group Name = aa....aa)
aa....aa: Specified group name
- Description
-
The Management Server Management Group and Integrated User Management Group are set up in the specified group.
-
KEOS22404-I (C/F)
The configuration of MNG Administration Group has succeeded.(Group Name = aa....aa)
aa....aa: Specified group name
- Description
-
The Management Server Management Group is set up in the specified group.
-
KEOS22405-I (C/F)
The configuration of Integration User Administration Group has succeeded.(Group Name = aa....aa)
aa....aa: Specified group name
- Description
-
The Integrated User Management Group is set up in the specified group.
-
KEOS22406-E (C)
Specified group is not in existence. (Group name = aa....aa)
aa....aa: Specified group name
- Description
-
The specified group is not registered in the OS. A message will be displayed in the standard error output, and the processing will be suspended.
- Action
-
Specify an existent group.
-
KEOS22407-E (C/F)
The configuration of permission has failed.(Command Name = aa....aa, errno = bb....bb)
aa....aa: Name of the command for change
bb....bb: Detailed message
- Description
-
An attempt for setting the permission using the command for change has failed. A message is displayed in the standard error output, and then the processing continues.
- Action
-
Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.
-
KEOS22408-E (C/F)
The configuration of group has failed.(Command Name = aa....aa, Group Name = bb....bb, errno = cc....cc)
aa....aa: Name of the command for change
bb....bb: Specified group name
cc....cc: Details
- Description
-
An attempt for setting the specified group with the command for change has failed. A message will be displayed in the standard error output, and the processing will be continued.
- Action
-
Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.
-
KEOS22409-E (C/F)
The both configurations of MNG Administration Group and Integration User Administration Group have failed.(Group Name = aa....aa)
aa....aa: Specified group name
- Description
-
An attempt for setting the Management Server Management Group and Integrated User Management Group in the specified group has failed. A message will be displayed in the standard error output, and the processing will be suspended.
- Action
-
Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.
-
KEOS22410-E (C/F)
The configuration of MNG Administration Group has failed.(Group Name = aa....aa)
aa....aa: Specified group name
- Description
-
An attempt for setting up the Management Server Management Group in the specified group has failed. A message will be displayed in the standard error output, and the processing will be suspended.
- Action
-
Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.
-
KEOS22411-E (C/F)
The configuration of Integration User Administration Group has failed.(Group Name = aa....aa)
aa....aa: Specified group name
- Description
-
An attempt for setting the Integrated User Management Group in the specified group has failed. A message will be displayed in the standard error output, and the processing will be suspended.
- Action
-
Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.
-
KEOS22415-E (C/F)
The memory allocation has failed.
- Description
-
An attempt to allocate the memory has failed. A message will be displayed in the standard error output, and the processing will be suspended.
- Action
-
Remove the cause of the error, and then re-execute the process.
-
KEOS22416-E (C)
The process of the log initialization has failed.
- Description
-
An attempt to initialize the log has failed. A message will be displayed in the standard error output, and the processing will be suspended.
- Action
-
Confirm the environment of the location where the log is to be output.
-
KEOS22417-E (C/F)
An attempt to open the file has failed.(File Path = aa....aa, errno = bb....bb)
aa....aa: File path
bb....bb: Detailed message
- Description
-
An attempt to open the file has failed.
The processing continues.
- Action
-
When an error occurs, delete the aa....aa file displayed in the message, and then re-execute the process.
-
KEOS22418-E (C/F)
An attempt to remove the file has failed.(File Path = aa....aa, errno = bb....bb)
aa....aa: File path
bb....bb: Detailed message
- Description
-
The deletion of the file has failed.
The processing continues.
- Action
-
When an error occurs, delete the aa....aa file displayed in the message, and then re-execute the process.
-
KEOS22419-E (C/F)
An attempt to change the process authority has failed.(Detail = aa....aa )
aa....aa: Details
- Description
-
An attempt to change the process permission has failed.
The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS23001-E (C)
The option is specified incorrectly.
- Description
-
An invalid option is specified in the command argument.
The command process will be interrupted.
- Action
-
Specify the option correctly, and then re-execute the command.
-
KEOS23002-E (C)
JP1/Base was not properly installed.
- Description
-
The JP1/BASE product is not installed.
The command process will be interrupted.
- Action
-
Install the JP1/BASE product, and then re-execute the command.
-
KEOS23003-I (C)
The adapter command setup has started.
- Description
-
The adapter command setup starts.
The processing continues.
-
KEOS23004-I (C)
The adapter command setup finished successfully.
- Description
-
The adapter command setup finished successfully.
The processing terminates.
-
KEOS23005-E (C)
Access to the adapter command settings file (aa....aa) was denied.
aa....aa: Name of the adapter command settings file
- Description
-
An attempt to access the adapter command settings file has failed.
The command process will be interrupted.
- Action
-
Check whether the user who executes the command has permissions to create or delete files. Also, check whether any free space is available on the disk where the file exists.
-
KEOS23006-I (C)
The adapter command unsetup has started.
- Description
-
The adapter command un-setup starts.
The processing continues.
-
KEOS23007-I (C)
The adapter command unsetup finished successfully.
- Description
-
The adapter command un-setup finished normally.
The processing terminates.
-
KEOS23008-E (C)
usage : mngsvr_adapter_setup [-i|-u] [-t IM_CS|IM_CM]
-i installing adapter command(default)
-u uninstalling adapter command
-t selection of the target JP1 product(default IM_CS)
- Description
-
This message describes the usage method of the mngsvr_adapter_setup command.
A message is displayed in the standard error output, and then the processing terminates.
- Action
-
See the message, and check the usage method of the command.
-
KEOS23053-E (C)
An error exists in the parameter set up in the standard input.
- Description
-
The parameter set up in the standard input is invalid.
The command process will be interrupted.
- Action
-
Check the prerequisite version of the related JP1 products.
-
KEOS23054-E (C)
The parameter of the format version set up in the standard input cannot be processed.
- Description
-
The parameter of the format version set up in the standard input cannot be processed.
The command process will be interrupted.
- Action
-
Check the prerequisite version of the related JP1 products.
-
KEOS23101-E (C)
The option is specified incorrectly.
- Description
-
An invalid option is specified in the command argument.
The command process will be interrupted.
- Action
-
Specify the option correctly, and then re-execute the command.
-
KEOS23102-E (C)
An attempt to access the registry has failed.
- Description
-
An attempt to access the registry has failed.
The command process will be interrupted.
The operating environment such as a registry may be corrupt.
- Action
-
Restart the OS, and then re-execute the process. If the problem is not resolved even after re-execution, contact maintenance personnel.
-
KEOS23103-E (C)
An internal error occurred.
- Description
-
An internal error occurred.
The command process will be interrupted.
- Action
-
If the error is not removed even after the command is re-executed, contact maintenance personnel.
-
KEOS23201-I (F)
The JP1 event was successfully sent. (pid = aa....aa, tid = bb....bb, time of occurrence = cc....cc)
aa....aa: Process identifier
bb....bb: Thread identifier
cc....cc: JP1 event request time
- Description
-
The JP1 event was successfully sent.
The processing continues.
-
KEOS23202-W (F)
An attempt to send the JP1 event has failed. (pid= aa....aa, tid= bb....bb, time of occurrence = cc....cc, status = dd....dd)
aa....aa: Process identifier
bb....bb: Thread identifier
cc....cc: JP1 event request time
dd....dd: Status code indicating cause of the failure
- Description
-
An attempt to send the JP1 event has failed.
The processing continues.
- Action
-
Remove the cause of the error based on actions for each of the following status codes:
- 40:
-
The JP1 event service cannot be connected. Check that the JP1 event service to which you will connect is running.
- 43:
-
An file I/O error occurred. Check the usage status of the system resources.
- 51:
-
Memory is insufficient. Check the usage status of the system resources.
- 52:
-
The number of open files has reached the limit. Check the usage status of the system resources.
- Others:
-
Contact maintenance personnel.
-
KEOS23203-E (F)
An attempt to read the settings file has failed. (file = aa....aa)
aa....aa: File name
- Description
-
Access denied.
The processing continues, but JPI events will not be issued hereafter.
- Action
-
Confirm that the settings file exists and also check the access permissions. Then, restart the J2EE server or the Management Server.
-
KEOS23204-I (F)
The processing to send a JP1 event was successfully initialized.
- Description
-
The processing to send a JP1 event was successfully initialized.
The processing continues.
-
KEOS23205-E (F)
Initialization of the processing to send a JP1 event has failed. (details = The function to initialize the processing to send a JP1 event has failed with status = aa....aa)
aa....aa: Status code indicating cause of the failure
- Description
-
The function to initialize JP1 event issue processing has been aborted.
The processing continues, but JPI events will not be issued hereafter.
- Action
-
Remove the cause of the error based on the actions for each of the following status codes, and then restart the J2EE server, the Management Server, or the Administration Agent.
- 50:
-
The library was not found. Check that JP1/Base of the prerequisite version is installed.
- 51:
-
Memory is insufficient. Check the usage status of the system resources.
- Others:
-
Contact maintenance personnel.
-
KEOS23206-E (F)
An attempt to initialize the processing to send a JP1 event has failed. (details = An attempt to load aa....aa failed.)
aa....aa: Shared library name that has been failed to load
- Description
-
An attempt to load the shared library has failed.
The processing continues, but JPI events will not be issued hereafter.
- Action
-
Contact maintenance personnel.
-
KEOS23207-E (F)
An internal error occurred.
- Description
-
An internal error occurred.
The processing continues, but JPI events will not be issued hereafter.
- Action
-
If the errors are not removed even after restarting the J2EE server, Management Server, or Administration Agent, contact maintenance personnel.
-
KEOS23301-I (F)
The web system aa....aa was added.
aa....aa: Name of the added Web system
- Description
-
The Web system was added.
-
KEOS23302-I (F)
The web system aa....aa was deleted.
aa....aa: Name of the deleted Web system
- Description
-
The Web system was deleted.
-
KEOS23303-I (F)
The web system aa....aa was modified.
aa....aa: Name of the modified Web system
- Description
-
The Web system was modified.
-
KEOS24000-E (C)
Usage:
aa....aa
aa....aa: Usage of the command
- Description
-
An invalid value is specified in the command argument.
- Action
-
See the message, and check the usage method of the command.
The possible errors are as follows:
-
The required option is not specified.
-
Specification of common arguments is omitted, and the client settings property file (.cmxrc) cannot be correctly read. The client settings property file is not created under the home directory of the OS login user or an error exists in the file access permissions.
-
Option that cannot be specified is specified.
-
A mistake exists in the relationship specified for the option and option argument. The option argument is not specified when the specification is mandatory, or the option argument is specified for options where the option argument cannot be specified.
-
-
KEOS24001-E (C)
The specified file is not a normal file. file name = aa....aa
aa....aa: File name
- Description
-
A special file is specified.
The processing will be interrupted.
- Action
-
Check the specified file.
-
KEOS24002-E (C)
An exception occurred during an attempt to read .cmxrc. (details =aa....aa)
aa....aa: Details
- Description
-
An attempt to read the .cmxrc file has failed.
The processing will be interrupted.
- Action
-
Check the access permissions of the .cmxrc file.
If no error exists in the file access permissions, but if the error is not resolved even after re-executing the command, contact maintenance personnel.
-
KEOS24003-E (C)
The host or userid common option has not been specified.
- Description
-
The host or user ID has not been specified in the common argument.
The processing will be interrupted.
- Action
-
Check that the cmx.connect.host key and cmx.connect.userid key is set in the client settings property file (.cmxrc).
-
KEOS24004-E (C)
aa....aa and bb....bb cannot be specified simultaneously.
aa....aa: Option
bb....bb: Option
- Description
-
These options cannot be specified simultaneously.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
-
KEOS24005-E (C)
The file does not exist. file name = aa....aa
aa....aa: File name
- Description
-
The specified file does not exist.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
-
KEOS24006-E (C)
A parser error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred in the parser.
The processing will be interrupted.
- Action
-
Confirm that the Cosminexus XML Processor is installed and that no mistake exists in the version of the installed Cosminexus XML Processor.
-
KEOS24007-E (C)
The definition file is invalid. file name = aa....aa line number = bb....bb column number = cc....cc details = dd....dd
aa....aa: File name
bb....bb: Line number
cc....cc: Column number
dd....dd: Details
- Description
-
An error occurred while analyzing the file. The contents of the specified Easy Setup definition file or the configuration change definition file are invalid.
The processing will be interrupted.
- Action
-
Correct the errors in the Easy Setup definition file or Configuration Change definition file, and then re-execute the command. Note that a Cosminexus XML Processor message is output in the details. For details on the message, see 11. KECX (Messages Output by Cosminexus XML Processor).
-
KEOS24008-E (C)
An exception occurred while reading the file. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Detailed message
- Description
-
An Error occurred while reading the file.
The processing will be interrupted.
- Action
-
Check the file access permissions.
If no error exists in the file access permissions, but if the error is not resolved even after re-executing the command, contact maintenance personnel.
-
KEOS24009-E (C)
The host is invalid. (details = aa....aa)
aa....aa: Details
- Description
-
The specified host name or port number is invalid.
The processing will be interrupted.
- Action
-
Confirm how to specify the host name and the port number.
-
KEOS24010-E (C)
A communication error occurred. (details =aa....aa)
aa....aa: Details
- Description
-
A communication error occurred.
The processing will be interrupted.
- Action
-
Confirm that the Management Server is running or check the values specified in the host name and the port number that are specified in the -m option of the common arguments. Also, check that the products of the connection source and the connection destination can be connected.
-
KEOS24011-E (C)
An exception occurred while creating the temporary file. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred while creating the temporary file.
The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS24012-E (C)
The option value is invalid. (option = aa....aa, value = bb....bb)
aa....aa: Option
bb....bb: Option value
- Description
-
An invalid value was specified in the option.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file or the configuration change definition file.
-
KEOS24013-E (C)
The parameter aa....aa cannot be specified for a logical server of type bb....bb. (line number = cc....cc)
aa....aa: Parameter
bb....bb: Logical server type
cc....cc: Line number
- Description
-
An invalid parameter is specified in the logical server type. The processing will be interrupted at the location of the displayed line number.
- Action
-
Check the contents of the configuration definition file.
-
KEOS24014-E (C)
Multiple parameter values cannot be specified for the parameter aa....aa. (line number = bb....bb)
aa....aa: Parameter
bb....bb: Line number
- Description
-
Multiple values cannot be specified in the parameter. The processing will be interrupted at the location of the displayed line number.
- Action
-
Check the contents of the configuration definition file.
-
KEOS24015-E (C)
The parameter value aa....aa cannot be specified for the parameter bb....bb. (line number = cc....cc)
aa....aa: Parameter value
bb....bb: Parameter
cc....cc: Line number
- Description
-
An invalid value is specified in the parameter. The processing will be interrupted at the location of the displayed line number.
- Action
-
Check the contents of the configuration definition file.
-
KEOS24016-E (C)
An invalid namespace was used in the XML file.
- Description
-
An invalid name space is used.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file or the configuration change definition file.
-
KEOS24017-E (C)
File open failed. File Name=aa....aa detail=bb....bb
aa....aa: File name
bb....bb: Detailed message
- Description
-
An attempt to open the file has failed.
The processing will be interrupted.
- Action
-
Check the file access permissions.
-
KEOS24018-E (C)
Invalid Tier combinations have been specified.
- Description
-
The combination of physical tiers is invalid.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file or the configuration change definition file.
-
KEOS24019-E (C)
Two or more aa....aa were allocated for a unit. (unit name = bb....bb)
aa....aa: Physical tier type
bb....bb: Service unit name
- Description
-
Multiple allocated-host elements specified with the same physical tier type (aa....aa) are coded in the service unit bb....bb.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file or the configuration change definition file.
-
KEOS24020-E (C)
No tier (tier type = aa....aa) was allocated for a unit (unit name = bb....bb).
aa....aa: Physical tier type
bb....bb: Service unit name
- Description
-
The allocated-host element with the physical tier type specified is not defined in a service unit.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file or the configuration change definition file.
-
KEOS24021-E (C)
A aa....aa and other tiers were allocated for a unit. (unit name = bb....bb)
aa....aa: Physical tier type
bb....bb: Service unit name
- Description
-
Multiple allocated-host elements specified with the physical tier type (aa....aa) and other physical tier types are defined in the service unit bb....bb.
The processing will be interrupted.
- Action
-
Check the contents of the configuration change definition file.
-
KEOS24022-E (C)
An invalid logical server type (aa....aa) is defined in bb....bb.
aa....aa: Logical server type
bb....bb: Physical tier type
- Description
-
A logical server type that cannot be specified in the physical tier type is specified.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file or the configuration change definition file.
-
KEOS24023-I (C)
The translations of the abstract parameters were successful.
- Description
-
An attempt to expand the abstract parameters was successful.
-
KEOS24024-E (C)
An invalid server ID rule (aa....aa) is defined.
aa....aa: Server ID rule
- Description
-
An invalid server ID rule is specified.
The processing will be interrupted.
- Action
-
Revise the server ID rule.
-
KEOS24025-E (C)
A number of units exceeding the number that can be generated for the server ID rule was specified.
- Description
-
Service units exceeding the number of server IDs that can be generated for the server ID rule cannot be registered.
The processing will be interrupted.
- Action
-
Revise the server ID rule.
-
KEOS24026-E (C)
An invalid number of elements is specified.
- Description
-
The number of elements in the option argument is invalid.
The processing will be interrupted.
- Action
-
Check the command execution method.
-
KEOS24027-E (C)
An invalid element is specified. (option = aa....aa, element = bb....bb)
aa....aa: Option
bb....bb: Element in the option argument
- Description
-
An invalid element is specified in the option argument.
The processing will be interrupted.
- Action
-
Check the command execution method.
-
KEOS24028-E (C)
A duplicated element is specified. (option = aa....aa, element = bb....bb)
aa....aa: Option
bb....bb: Element in the option argument
- Description
-
A duplicated element is specified in the option argument.
The processing will be interrupted.
- Action
-
Check the command execution method.
-
KEOS24029-E (C)
An invalid combination of tiers is specified.
- Description
-
An invalid combination of physical tiers is specified.
The processing will be interrupted.
- Action
-
Check the command execution method.
-
KEOS24030-E (C)
An invalid command is specified. (command = aa....aa)
aa....aa: Command
- Description
-
An invalid command is specified.
The processing will be interrupted.
- Action
-
Check the command execution method.
-
KEOS24031-E (C)
The sfo-tier and other tiers are allocated to the unit. (unit name = aa....aa)
aa....aa: Service unit name
- Description
-
An sfo-tier and other tiers are allocated to the service unit.
The processing will be interrupted.
- Action
-
Check the contents of the configuration definition file.
-
KEOS24032-E (C)
The parameter aa....aa cannot be used with the product bb....bb. (line number =cc....cc)
aa....aa: Parameter
bb....bb: Product name
cc....cc: Line number of the definition file
- Description
-
The parameter aa....aa cannot be used in the product bb....bb.
The processing will be interrupted.
- Action
-
Delete this parameter from the definition file.
-
KEOS24033-E (C)
The aa....aa cannot be used with the product bb....bb.
aa....aa: Tier
bb....bb: Product name
- Description
-
The tier aa....aa cannot be used in the product bb....bb.
The processing will be interrupted.
- Action
-
Delete the tier specification from the definition file.
-
KEOS24035-E (C)
In the product aa....aa, you must specify the IP address of the local host (the host executing the command) for the management IP or operational IP address. (host name = bb....bb)
aa....aa: Product name
bb....bb: Host name
- Description
-
In the product aa....aa, you must specify the IP address of the local host (the host executing the command) for the operationalIP or managementIP.
The processing will be interrupted.
- Action
-
Change the IP address specified for the host in the definition statement to the IP address of the local host.
-
KEOS24036-E (C)
The load balancer cannot be defined in the ctm-tier. (Web system name = aa....aa)
aa....aa: Web system name
- Description
-
The load balancer cannot be defined in the CTM tier.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24037-E (C)
The j2ee-server-count cannot be specified for the aa....aa. (Web system name = bb....bb)
aa....aa: Physical tier type
bb....bb: Web system name
- Description
-
You cannot specify the j2ee-server-count tag in the physical tier aa....aa (Web system name = bb....bb).
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
Delete the j2ee-server-count tag of the tier aa....aa from the Easy Setup definition file.
-
KEOS24038-E (C)
When the j2ee-server-count is specified as 0, the j2ee-server cannot be specified for the logical-server-type. (Web system name = aa....aa)
aa....aa: Web system name
- Description
-
When the specified value of the j2ee-server-count tag is 0, you cannot specify j2ee-server as the logical server type (Web system name = aa....aa).
The processing will be interrupted.
- Action
-
Delete the specification of the logical server type aa....aa from the Easy Setup definition file.
-
KEOS24039-E (C)
When the logical-server-type is specified as aa....aa, the server-no cannot be specified. (Web system name = bb....bb)
aa....aa: Logical server type
bb....bb: Web system name
- Description
-
You cannot specify the server-no tag in the logical server type aa....aa (Web system name = bb....bb).
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
Delete the server-no tag of the logical server type aa....aa from the Easy Setup definition file.
-
KEOS24040-E (C)
The server-no(aa....aa) is larger than the j2ee-server-count(bb....bb). (Web system name = cc....cc)
aa....aa: Specified value of the server-no tag
bb....bb: Specified value of the j2ee-server-count tag
cc....cc: Web system name
- Description
-
A value greater than the specified value of the j2ee-server-count tag (bb....bb) is specified for the server-no tag (aa....aa) (Web system name = cc....cc).
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24041-E (C)
The server-no is not specified for the define-server. (Web system name = aa....aa, unit name = bb....bb)
aa....aa: Web system name
bb....bb: Unit name
- Description
-
The server-no tag is not specified in the server definition of the unit (Web system name = aa....aa, unit name = bb....bb).
The processing will be interrupted.
- Action
-
Specify the server-no tag in the server definition (j2ee-server tag) of the unit bb....bb.
-
KEOS24042-E (C)
When the j2ee-server-count is not specified, the server-no cannot be specified. (Web system name = aa....aa)
aa....aa: Web system name
- Description
-
When the j2ee-server-count tag is not specified, you cannot specify the server-no tag (Web system name = aa....aa).
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
Delete the server-no tag from the Easy Setup definition file.
-
KEOS24043-E (C)
Multiple logical-server-type of the aa....aa are specified. (Web system name = bb....bb)
aa....aa: Logical server type
bb....bb: Web system name
- Description
-
There is more than one specification of the logical server type aa....aa (Web system name = bb....bb).
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24044-E (C)
aa....aa cannot be specified in this Web system. (Web system name = bb....bb)
aa....aa: Tier type
bb....bb: Web system name
- Description
-
You cannot specify aa....aa in this Web system.
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
When free-tier is specified in tier type, omit the Web system name. If the Web system name is specified, free-tier cannot be specified in the tier type. Check the contents of the Easy Setup definition file.
-
KEOS24045-E (C)
A configuration tag cannot be specified for a free-tier tier tag.
- Description
-
A configuration tag cannot be specified for a tier tag in free-tier. The processing will be interrupted.
- Action
-
Delete the configuration tag specified in the tier tag, and then specify the configuration tag for the unit tag.
-
KEOS24046-E (C)
A user-server configuration cannot be specified for the aa....aa. (Web system name = bb....bb)
aa....aa: Tier type
bb....bb: Web system name
- Description
-
You cannot specify the user-server configuration in the tier tag.
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
Delete the user-server configuration tag specified in the tier tag, and specify the user-server configuration tag in the unit tag.
-
KEOS24047-E (C)
The logical server type (aa....aa) cannot be used with the product (bb....bb).
aa....aa: Logical server type
bb....bb: Product name
- Description
-
You cannot use the logical server type aa....aa with the product bb....bb.
The processing will be interrupted.
- Action
-
Delete the specification of the logical server type aa....aa from the Easy Setup definition file.
-
KEOS24048-E (C)
The load balancer cannot be defined.
- Description
-
If the Web system name is omitted, you cannot specify the load-balancer tag.
The processing will be interrupted.
- Action
-
Delete the definition of the load-balancer tag.
-
KEOS24049-E (C)
The cluster-ref aa....aa is invalid.(Web system name = bb....bb)
aa....aa: Cluster name
bb....bb: Web system name
- Description
-
Clustering is specified for a logical server that cannot be clustered. Either the specified value aa....aa of the cluster-ref tag is not defined or the cluster type is different.
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24050-E (C)
The logical-server-name must be specified for the free-tier.
- Description
-
The logical-server-name tag cannot be omitted for free-tier.
The processing will be interrupted.
- Action
-
Specify the logical-server-name tag.
-
KEOS24051-E (C)
The configuration cannot be specified for the cluster aa....aa.
aa....aa: Cluster name
- Description
-
You cannot specify the configuration tag in the cluster.
The processing will be interrupted.
- Action
-
Delete the definition of the configuration tag of the cluster.
-
KEOS24052-E (C)
More than one Web system does not have a name.
- Description
-
More than one Web system does not have a name. The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24053-E (C)
More than one unit does not have a name.
- Description
-
More than one unit does not have a name. The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24054-E (C)
A unit for a Web system that does not have a name, or a Web system that does have a name but for which the unit is omitted, is specified.(Web system name = aa....aa)
aa....aa: Web system name
- Description
-
The service unit name is specified in the unit tag of a Web system for which the Web system name is not defined. Alternatively, the unit tag is omitted in a Web system for which the Web system name is defined.
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24055-E (C)
In the product aa....aa, you must specify the IP address or host name of the local host (the host executing the command) for the host-name or agent-host. (host name = bb....bb)
aa....aa: Product name
bb....bb: Host name
- Description
-
In the product aa....aa, you cannot specify other than the IP address or host name of the local host (the host that executes the command) in the host-name tag or agent-host tag.
The processing will be interrupted.
- Action
-
Change the IP address specified for the host in the definition statement to the IP address of the local host.
-
KEOS24056-E (C)
The logical-server-type must be specified for the configuration of tier. (Web system name = aa....aa, tier type = bb....bb)
aa....aa: Web system name
bb....bb: Tier type
- Description
-
You cannot omit the logical-server-type tag for the configuration tag of the tier.
The processing will be interrupted.
- Action
-
Specify the logical-server-type tag.
-
KEOS24057-E (C)
The command (aa....aa) cannot be used with the product (bb....bb).
aa....aa: Command name
bb....bb: Product name
- Description
-
The command aa....aa cannot be used with the product bb....bb. The processing will be interrupted.
-
KEOS24058-W (C/F)
The parameter (aa....aa) cannot be used with the product (bb....bb). (line number = cc....cc)
aa....aa: Parameter
bb....bb: Product name
cc....cc: Line number in the definition file
- Description
-
The parameter aa....aa cannot be used with the product bb....bb. The error is ignored, and the processing continues.
- Action
-
Delete the parameter aa....aa from the definition file.
-
KEOS24059-I (C)
The user ID and password of the Management Server administrator account is not set because the management user account is disabled.
- Description
-
The user ID and password of the Management Server administrator account is not set up because the management user account is disabled.
-
KEOS24100-I (F)
CMX processing will now start. (client = aa....aa)
aa....aa: Connection source
- Description
-
The setup process will start using the Smart Composer.
-
KEOS24101-I (F)
CMX processing has finished.
- Description
-
The setup process will terminate using the Smart Composer.
-
KEOS24102-E (C)
A communication error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
A communication error occurred.
The processing will be interrupted.
- Action
-
If the error is not resolved even after re-executing the command, contact maintenance personnel.
-
KEOS24103-E (C)
An exception occurred while creating a temporary file. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred while creating the temporary file.
The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS24104-E (C)
An administrator's user ID or a password is incorrect.
- Description
-
The administrator user ID or password is invalid.
The processing will be interrupted.
- Action
-
Check the specified administrator user ID and password.
-
KEOS24105-E (C)
An administrator's user account is already specified.
- Description
-
The administrator user ID and password of the Management Server are already registered.
The processing will be interrupted.
- Action
-
With this command, you cannot change a registered administrator user ID and password. If you need to change the management user ID and the password, use the management portal.
-
KEOS24106-E (C)
The configuration file could not be saved. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to save the settings file has failed.
- Action
-
Contact maintenance personnel.
-
KEOS24107-I (F)
The processing for aa....aa will now start.
aa....aa: Details
- Description
-
The command process starts.
-
KEOS24108-I (F)
The processing for aa....aa has finished.
aa....aa: Details
- Description
-
The command process has finished.
-
KEOS24109-E (C)
The specified Web system (Web system name = aa....aa) is not registered.
aa....aa: Web system name
- Description
-
The Web system specified in the -s option of the command or the configuration change definition file is not registered.
The processing will be interrupted.
- Action
-
Check the argument specified in the command or the configuration change definition file contents.
-
KEOS24110-E (C)
The specified unit (Web system name = aa....aa, unit name = bb....bb) is not registered.
aa....aa: Web system name
bb....bb: Service unit name
- Description
-
The service unit specified in the -unit option of the command is not registered in the Web system.
The processing will be interrupted.
- Action
-
Check the argument specified in the command or the configuration change definition file contents.
-
KEOS24111-E (C)
The specified tier (Web system name = aa....aa, tier type = bb....bb) is not registered.
aa....aa: Web system name
bb....bb: Physical tier type
- Description
-
The physical tier type specified in the configuration change definition file is not registered in the Web system.
The processing will be interrupted.
- Action
-
In the physical tier type (tier-type tag of physical tier definition or host-for tag of the service unit definition) of the configuration change definition file, the specified tier type is other than the physical tier defined while building the Web system.
Modify the configuration change definition file, and then re-execute the command.
-
KEOS24112-E (C)
No units are registered in the Web system. (Web system name = aa....aa)
aa....aa: Web system name
- Description
-
The service unit is not registered in the Web system.
All service units are deleted.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
Add the service unit if errors do not exist in the command arguments.
-
KEOS24113-E (C)
The Web system (Web system name = aa....aa) is already registered.
aa....aa: Web system name
- Description
-
The Web system specified in the Easy Setup definition file is already registered.
The processing will be interrupted.
- Action
-
Check the Easy Setup definition file contents and how to execute the command.
-
KEOS24114-E (C)
The unit (Web system name = aa....aa, unit name = bb....bb) is already registered.
aa....aa: Web system name
bb....bb: Service unit name
- Description
-
The service unit specified in the configuration change definition file is already registered in the Web system.
The processing will be interrupted.
- Action
-
Check the configuration change definition file contents and how to execute the command.
-
KEOS24115-E (C)
The host (host name/IP address = aa....aa) is already registered.
aa....aa: Host name or operation IP address
- Description
-
The host is already registered.
The processing will be interrupted.
- Action
-
Check the Easy Setup definition file contents and how to execute the command.
Check that a host with the same operation IP address is not specified in another Web system or that the same host name is not used in the Web system.
-
KEOS24116-E (C)
An attempt to register the host that registers the naming service for the management server (host name = aa....aa) has failed.
aa....aa: Host name that registers the naming service used by the Management Server
- Description
-
An attempt to register the host that registers the naming service used by the Management Server has failed.
The processing will be interrupted.
- Action
-
If the error is not resolved even after re-executing the command, contact maintenance personnel.
-
KEOS24117-I (C)
The settings of the administrator's user account were changed.
- Description
-
The settings of the administrator's user account were changed.
-
KEOS24119-I (C)
The naming service for the management server (logical server name = aa....aa) has already started.
aa....aa: Host name that registers the naming service used by the Management Server
- Description
-
The naming service used by the Management Server has already started.
-
KEOS24120-E (C)
An attempt to start the naming service for the management server (logical server name = aa....aa) has failed.
aa....aa: Host name that registers the naming service used by the Management Server
- Description
-
An attempt to start the naming service used by the Management Server has failed.
The processing will be interrupted.
- Action
-
Examine the log file of the Management Server, check the log related to the logical server start and stop, remove the error, and then re-execute the command.
-
KEOS24121-I (C)
The naming service for the management server (logical server name = aa....aa) has started.
aa....aa: Host name that registers the naming service used by the Management Server
- Description
-
An attempt to start the naming service used by the Management Server was successful.
-
KEOS24122-E (C)
The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has been deleted.
aa....aa: Web system name
bb....bb: Service unit name
cc....cc: Logical server name
- Description
-
The logical server is deleted.
The logical server might have been deleted by using the management portal.
- Action
-
Add the service unit after deleting it once.
-
KEOS24123-I (C)
The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has already started.
aa....aa: Web system name
bb....bb: Service unit name
cc....cc: Logical server name
- Description
-
The logical server has already started.
-
KEOS24124-E (C)
An attempt to start the logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has failed.
aa....aa: Web system name
bb....bb: Service unit name
cc....cc: Logical server name
- Description
-
An attempt to start the logical server has failed.
- Action
-
Examine the log file of the Management Server, check the log related to the logical server start and stop, remove the error, and then re-execute the command.
-
KEOS24125-I (C)
The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has started.
aa....aa: Web system name
bb....bb: Service unit name
cc....cc: Logical server name
- Description
-
An attempt to start the logical server was successful.
-
KEOS24126-I (C)
The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has already stopped.
aa....aa: Web system name
bb....bb: Service unit name
cc....cc: Logical server name
- Description
-
The logical server has already stopped.
-
KEOS24127-E (C)
An attempt to stop the logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has failed.
aa....aa: Web system name
bb....bb: Service unit name
cc....cc: Logical server name
- Description
-
An attempt to stop the logical server has failed.
- Action
-
Examine the log file of the Management Server, check the log related to the logical server start and stop, remove the error, and then re-execute the command.
-
KEOS24128-I (C)
The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has stopped.
aa....aa: Web system name
bb....bb: Service unit name
cc....cc: Logical server name
- Description
-
An attempt to stop the logical server was successful.
-
KEOS24129-I (C)
The Web system (Web system name = aa....aa) was successfully built.
aa....aa: Web system name
- Description
-
The Web system was successfully built.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
-
KEOS24130-I (C)
The Web system (Web system name = aa....aa) was successfully changed.
aa....aa: Web system name
- Description
-
The Web system was successfully changed.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
-
KEOS24131-E (C/F)
This command is not supported. (details = aa....aa)
aa....aa: Details
- Description
-
This command is not supported.
The processing will be interrupted.
- Action
-
Check the version of the product installed in the operation management machine and the version of the product installed in the machine executing the command.
-
KEOS24132-I (C)
The operation on the load balancer was successful. (load balancer = aa....aa)
aa....aa: Management IP address of the load balancer
- Description
-
The operation on the load balancer was successful.
-
KEOS24133-E (C/F)
The attempted operation on the load balancer has failed. (load balancer = aa....aa, details = bb....bb)
aa....aa: Management IP address of the load balancer
bb....bb: Detailed message
- Description
-
An attempted operation on the load balancer has failed.
The processing will be interrupted.
- Action
-
Remove the error based on the detailed information described in the following table, and then re-execute the command.
Table 13‒1: List of error details described in KEOS24133-E Details
Description
Action
ncm.host is null or empty.
The ncm.host key of the load balancer definition property file (lb.properties) is not set or the value of the ncm.host key is null.
Set the ncm.host key of the lb.properties file appropriately.
Invalid xxx
The value of the xxx key of the load balancer definition property file (lb.properties) is invalid.
Set the xxx key of the lb.properties file appropriately.
ncm.user is null or empty.
The ncm.user key of the load balancer definition property file (lb.properties) is not set or the value of the ncm.user key is null.
Set the ncm.user key of the lb.properties file appropriately.
ncm.passwd is null.
The ncm.passwd key of the load balancer definition property file (lb.properties) is not set.
Set the ncm.passwd key of the lb.properties file appropriately.
The LB named xxx.xxx.xxx.xxx is not configured.
The load balancer of xxx.xxx.xxx.xxx is not defined in the lb.list key of the load balancer definition property file (lb.properties).
Set the lb.list key of the lb.properties file appropriately.
Access denied: <file>
The <file> either does not exist, is not a normal file, or is not readable.
Confirm that the <file> exists, is a normal file, and that it is readable.
The script named xxx does not exist: <file>
The script (xxx) is not defined in the script definition file <file>.
Copy the latest script definition file supported in <file> to the following locations:
-
In Windows
Cosminexus-installation-directory\manager\config
-
In UNIX
/opt/Cosminexus/manager/config
The connection failed.
An attempted connection has failed.
Set the lb.telnet.port.xxx, lb.ssh.port.xxx, and lb.API.port.xxx key of the lb.properties file or the management IP address of the Easy Setup file load balancer definition appropriately.
An I/O error occurred during data transfer from the load balancer.
An I/O error has occurred while receiving the data.
Re-execute the cmx command. If the problem is not resolved, contact maintenance personnel.
An I/O error occurred during data transfer to the load balancer.
An I/O error has occurred while sending the data.
Re-execute the cmx command. If the problem is not resolved, contact maintenance personnel.
A timeout occurred while waiting for a response to the user prompt.
A timeout occurred while receiving the user prompt.
Set the lb.telnet.user_prompt.xxx key of the lb.properties file appropriately. If the above keys are appropriate, set a value greater than the value of the lb.telnet.login_timeout.xxx key.
A timeout occurred while waiting for a response to the password prompt.
A timeout occurred while receiving the password prompt.
Set the lb.telnet.user_prompt.xxx key of the lb.properties file appropriately. If the above keys are appropriate, set a value greater than the value of the lb.telnet.login_timeout.xxx key.
A timeout occurred while waiting for a response to the login prompt.
A timeout occurred while receiving the login prompt.
Se the lb.telnet.user.xxx, lb.telnet.passwd.xxx, lb.telnet.login_prompt.xxx keys appropriately. If the above keys are appropriate, set a value greater than the value of the lb.telnet.login_timeout.xxx key.
A timeout occurred.
A timeout occurred.
Set a value greater than the value of the lb.telnet.command_timeout.xxx, lb.ssh.timeout.xxx, or lb.API.timeout.xxx keys. If the problem is not resolved, contact maintenance personnel.
An I/O error occurred.
An I/O error occurred.
Re-execute the cmx command. If the problem is not resolved, contact maintenance personnel.
The connection closed.
The connection to the load balancer was disconnected.
Set the lb.telnet.user.xxx, lb.telnet.passwd.xxx, lb.telnet.user_prompt.xxx, lb.telnet.passwd_prompt.xxx, lb.telnet.login_prompt.xxx keys of the lb.properties file appropriately. If the problem is not resolved, contact maintenance personnel.
xxx is null or empty.
The xxx key of the load balancer definition property file (lb.properties) is not set or the value of the xxx key is null.
Set the xxx key of the lb.properties file appropriately.
Authentication has failed.
An attempted authentication has failed.
Set the lb.ssh.user.xxx, lb.ssh.passwd.xxx keys of the lb.properties file appropriately.
A command execution error occurred: (<returncode>, <errormessage>)
An error occurred in command execution.
Specify the error cause from the command return code <returncode> and error message <errormessage>.
An API processing error occurred: (<returncode>, <errormessage>)
An error occurred in API processing.
Identify the cause of the error from the return code <returncode> and the error message <errormessage>.
An unexpected exception occurred.
An unexpected exception occurred.
Contact maintenance personnel.
The load balancer type is incorrect.
The load balancer type is incorrect.
Set up an appropriate value in the <load-balancer-type> tag of the Easy Setup definition file.
Others
An attempt to execute the CLI command of load balancer has failed.
Re-execute the cmx command. If the problem is not resolved, contact maintenance personnel.
-
-
KEOS24135-E (C)
An attempt to register the host (host name = aa....aa) has failed.
aa....aa: Host name
- Description
-
An attempt to register the host has failed.
The logical server and application might have been updated by using the management portal.
- Action
-
If the error is not resolved even when the command is re-executed after some time, contact maintenance personnel.
-
KEOS24138-W (C)
The load balancer is not defined on the Web system (Web system name = aa....aa).
aa....aa: Web system name
- Description
-
The load balancer is not defined in the specified Web system (The connection test of the load balancer is not implemented with the cmx_test_lb command).
The processing will be interrupted.
- Action
-
Check how to execute the command and the Easy Setup definition file contents.
-
KEOS24139-E (C)
The load balancer (Web system name = aa....aa, load balancer name = bb....bb) is not registered.
aa....aa: Web system name
bb....bb: Load balancer name
- Description
-
The load balancer is not registered.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24140-E (C)
The virtual server (Web system name = aa....aa, load balancer name = bb....bb, virtual server name = cc....cc) is not registered.
aa....aa: Web system name
bb....bb: Load balancer name
cc....cc: Virtual server name
- Description
-
The virtual server is not registered.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24141-E (C)
An internal error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
An internal error occurred.
The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS24142-E (F/C)
A timeout occurred.
- Description
-
A timeout occurred.
Commands that cannot be executed concurrently are being executed.
The processing will be interrupted.
- Action
-
Re-execute after some time.
-
KEOS24143-E (F/C)
An exclusion error occurred.
- Description
-
An exclusion error has occurred.
Commands that cannot be executed concurrently are being executed.
The processing will be interrupted.
- Action
-
Re-execute after some time.
-
KEOS24144-I (F)
Processing for aa....aa(Web system name = aa....aa) has been accepted.
aa....aa: Command name
bb....bb: Web system name
- Description
-
Received a command process for the Web system.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
-
KEOS24145-E (C)
An attempt to set up the logical server (Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc) has failed.
aa....aa: Web system name
bb....bb: Unit name
cc....cc: Logical server name
- Description
-
An attempt to set up the logical server has failed.
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.
- Action
-
Examine the log file of the Management Server, remove the error, and then re-execute the command.
-
KEOS24146-I (C)
An attempt to set up the logical server (Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc) was successful.
aa....aa: Web system name
bb....bb: Unit name
cc....cc: Logical server name
- Description
-
An attempt to set up the logical server was successful.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.
-
KEOS24147-E (C)
An attempt to distribute the configuration file has failed. Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc
aa....aa: Web system name
bb....bb: Unit name
cc....cc: Logical server name
- Description
-
An attempt to distribute the environment settings of the logical server has failed.
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name or the unit name.
- Action
-
Examine the log file of the Management Server, remove the error, and then re-execute the command.
-
KEOS24148-I (C)
An attempt to distribute the configuration file was successful. Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc
aa....aa: Web system name
bb....bb: Unit name
cc....cc: Logical server name
- Description
-
An attempt to distribute the environment settings of the logical server was successful.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.
-
KEOS24149-I (C)
The logical server (Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc) has already set upped.
aa....aa: Web system name
bb....bb: Unit name
cc....cc: Logical server name
- Description
-
The logical server has already been set up.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.
-
KEOS24150-I (C)
The configuration file has already distributed. Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc
aa....aa: Web system name
bb....bb: Unit name
cc....cc: Logical server name
- Description
-
The environment settings of the logical server have already been distributed.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.
-
KEOS24151-E (C)
An invalid XML Schema(aa....aa) was used.
aa....aa: XML schema
- Description
-
An invalid XML schema is used.
The processing will be interrupted.
- Action
-
Check the version of the server and the client.
-
KEOS24153-E (C)
An attempt to allocate memory has failed.
- Description
-
An attempt to secure memory has failed. A standard error message will be displayed, and the processing will be terminated.
- Action
-
Allocate sufficient memory by terminating the other applications, and re-execute the process.
-
KEOS24154-E (C)
An error occurred in the system function. function name = aa....aa, errno = bb....bb
aa....aa: Function name
bb....bb: Error number
- Description
-
An error has occurred in the system function. A standard error message will be displayed, and the processing will be terminated.
- Action
-
See the error number of the function, remove the error, and re-execute the process.
-
KEOS24157-E (C)
The host(Web system name=aa....aa, unit name=bb....bb, host name=cc....cc) is not registered.
aa....aa: Web system name
bb....bb: Unit name
cc....cc: Host name
- Description
-
The host (host name = cc....cc) is not registered.
The processing will be interrupted.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.
- Action
-
Check the contents of the Easy Setup definition file.
-
KEOS24158-W (C/F)
The setting value aa....aa of the specified parameter bb....bb is already being used. (logical server name = cc....cc)
aa....aa: Parameter value
bb....bb: Parameter
cc....cc: Logical server wherein an error occurred
- Description
-
The settings value of the parameter specified in the logical server is being used elsewhere. The error will be ignored, and then the processing continues.
- Action
-
The settings value of this parameter must be a unique value in the same server machine. Revise the settings value of the parameter specified in each logical server, and then change the Web system.
-
KEOS24159-W (C/F)
The aa....aa part of the specified parameter bb....bb is not defined as the setting value of the parameter cc....cc. (logical server name = dd....dd)
aa....aa: Value of part of the parameter name
bb....bb: Parameter
cc....cc: Parameter in which the settings for value of the parameter name is not defined
dd....dd: Logical server wherein an error occurred
- Description
-
The value of part of the parameter specified in the logical server is not defined as the settings value of the parameter. The error will be ignored, and then the processing continues.
- Action
-
Revise the settings value of the parameter specified in the configuration tag, and then change the Web system.
-
KEOS24160-W (C/F)
The logical server aa....aa specified in the parameter bb....bb of the logical server cc....cc is not defined.
aa....aa: Logical server name
bb....bb: Parameter
cc....cc: Logical server wherein an error occurred
- Description
-
The logical server specified in the logical server parameter is not defined. The error will be ignored, and then the processing continues.
- Action
-
Revise the settings value of the parameter specified in the configuration tag, and then change the Web system.
-
KEOS24161-W (C/F)
There is a correlation error in the setting value of the parameter aa....aa(value = bb....bb) and the parametercc....cc(value = dd....dd).(logical server name = ee....ee)
aa....aa: Parameter 1
bb....bb: Setting value of parameter 1
cc....cc: Parameter 2
dd....dd: Setting value of parameter 2
ee....ee: Logical server name wherein an error occurred
- Description
-
A correlation error (such as maximum or minimum related errors) exists in the values of parameter 1 and parameter 2. The error will be ignored, and then the processing continues.
- Action
-
Revise the settings value of the parameter specified in the configuration tag, and then change the Web system.
-
KEOS24162-W (C/F)
The attempted operation on the load balancer has failed. (load balancer = aa....aa, details = bb....bb)
aa....aa: Management IP address of the load balancer
bb....bb: Detailed message
- Description
-
An attempted operation on the load balancer has failed. The error will be ignored, and then the processing continues.
For the detailed information, see Table 13-1 List of error details described in KEOS24133-E.
- Action
-
Remove the error in the load balancer, and then test the load balancer with cmx_test_lb.
-
KEOS24163-W (C/F)
The attempted operation on the load balancer has failed. The operation on this load balancer will be suspended.(load balancer = aa....aa, details = bb....bb)
aa....aa: Management IP address of the load balancer
bb....bb: Detailed message
- Description
-
An attempted operation on the load balancer has failed. The proceeding operations of this load balancer will be suspended.
For the detailed information, see Table 13-1 List of error details described in KEOS24133-E.
- Action
-
Remove the error in the load balancer, and then test the load balancer with cmx_test_lb.
-
KEOS24164-I (C/F)
The operation on the suspended load balancer was successful.(load balancer = aa....aa)
aa....aa: Management IP address of the load balancer
- Description
-
The operation on the suspended load balancer was successful.
- Action
-
If the other load balancer is normal, issue an instruction (cmx_recover_lb) of error recovery to the Smart Composer after recovering the settings of this load balancer.
In the case of an error, remove the error, and then test the load balancer with cmx_test_lb.
-
KEOS24165-W (C/F)
The attempted operation on the suspended load balancer has failed. (load balancer = aa....aa, details =bb....bb)
aa....aa: Management IP address of the load balancer
bb....bb: Detailed message
- Description
-
An attempted operation of a suspended load balancer has failed. The error will be ignored, and then the processing continues.
For the detailed information, see Table 13-1 List of error details described in KEOS24133-E.
- Action
-
Remove the error in the load balancer, and then test the load balancer with cmx_test_lb.
-
KEOS24166-W (C/F)
The operation on the load balancer canceled because it was suspended. (load balancer = aa....aa)
aa....aa: Management IP address of the load balancer
- Description
-
The load balancer operations could not be performed because the load balancer was suspended. The error will be ignored, and then the processing continues.
- Action
-
Remove the error in the load balancer, and then test the load balancer with cmx_test_lb.
-
KEOS24167-E (C)
The logical server (logical server name = aa....aa) is already registered.
aa....aa: Logical server ID
- Description
-
The logical server is already registered. The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file or the configuration change definition file.
-
KEOS24168-I (C)
The host (host name=aa....aa) has been registered.
aa....aa: Host name (if there are one or more host names, demarcate with commas)
- Description
-
The host is registered.
-
KEOS24169-E (C)
The operation is not available on this unit(Web system name =aa....aa, unit name = bb....bb).
aa....aa: Web system name
bb....bb: Service unit name
- Description
-
This operation is not valid for this service unit. The processing will be interrupted.
- Action
-
Check that no error exists in the specified service unit name.
-
KEOS24170-E (C)
The host cannot be identified because a host with the same name exists. (host name = aa....aa)
aa....aa: Host name
- Description
-
The host cannot be identified because a host with the same name exists. The processing will be interrupted.
- Action
-
This host cannot be used. Re-create (add after deleting) the service unit such that the host name within the domain becomes unique.
-
KEOS24171-I (C)
The logical servers were successfully added to the Web system.
- Description
-
An attempt to add the logical servers to the Web system was successful.
-
KEOS24172-I (C)
The logical server was successfully deleted from the Web system.
- Description
-
An attempt to delete the logical server from the Web system was successful.
-
KEOS24173-E (C)
The logical server has already been added to the Web system. (Logical Server Name = aa....aa)
aa....aa: Logical server name
- Description
-
The logical server aa....aa is already added in the Web system. The processing will be interrupted.
- Action
-
Check the logical server name.
-
KEOS24174-E (C)
The logical server has not been added to the Web system. (Logical Server Name = aa....aa)
aa....aa: Logical server name
- Description
-
The logical server aa....aa is not added to the Web system. The processing will be interrupted.
- Action
-
Check the logical server name.
-
KEOS24175-E (C)
A nonexistent logical server has been specified. (Logical Server Name = aa....aa)
aa....aa: Logical server name
- Description
-
A logical server aa....aa that does not exist is specified. The processing will be interrupted.
- Action
-
Check the logical server name.
-
KEOS24176-E (C)
A logical server that is not a user server has been specified. (Logical Server Name = aa....aa)
aa....aa: Logical server name
- Description
-
A logical server aa....aa that is not a user server is specified. The processing will be interrupted.
- Action
-
Check the logical server name.
-
KEOS24177-E (C)
An invalid logical server type (aa....aa) is specified in the unit (unit name = bb....bb).
aa....aa: Logical server type
bb....bb: Service unit name
- Description
-
An invalid logical server type aa....aa is specified in the server definition in the service unit bb....bb. The processing will be interrupted.
- Action
-
Check the definition file contents.
-
KEOS24178-I (C/F)
The settings for the load balancer have resumed. (load balancer = aa....aa)
aa....aa: Management IP address of the load balancer
- Description
-
The settings for the load balancer, suspended because of an error, have resumed.
-
KEOS24179-E (C)
The suspended load balancer does not exist.
- Description
-
The suspended load balancer does not exist. The processing will be interrupted.
- Action
-
The cmx_resume_lb command is valid only when the load balancer, suspended because of an error, exists.
-
KEOS24180-E (C)
A combination of the values specified to hosts-for element(aa....aa) and host-ref element(bb....bb) is invalid .(Web system name = cc....cc, unit name = dd....dd)
aa....aa: Tier type
bb....bb: Host name
cc....cc: Web system name
dd....dd: Service unit name
- Description
-
The combination of the values specified for hosts-for element and host-ref element is invalid.
- Action
-
Modify the values specified for hosts-for element and host-ref element specified in the service unit (service unit name) of the configuration change definition file to the combination of values specified while building the Web system or while adding the service unit, and then re-execute the command.
-
KEOS24181-I (C/F)
The Web system host information was changed successfully.
- Description
-
An attempt to change the Web system host information was successful.
-
KEOS24182-E (C/F)
An attempt to change the Web system host information has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to change the Web system host information has failed. The processing will be interrupted.
- Action
-
Check the detailed information, and remove the cause of the error.
-
KEOS24183-W (C/F)
The same CTMID is specified more than once for the same host. (logical server name = aa....aa)
aa....aa: Logical server name
- Description
-
The same CTMID is specified more than once for the same host. The error will be ignored, and then the processing continues.
- Action
-
You cannot define the same CTM more than once for the same host. Revise the configuration of the Web system.
-
KEOS24184-E (C/F)
The settings information for the load balancer is invalid. (Web system name = aa....aa, details = bb....bb)
aa....aa: Web system name
bb....bb: Detailed message
- Description
-
The settings information for the load balancer is incorrect. The processing will be interrupted.
- Action
-
Check the detailed information and the contents of the definition file.
-
KEOS24185-E (C)
The operation is not available on this web system(Web system name = aa....aa).
aa....aa: Web system name
- Description
-
The executed operation is not valid for this Web system. The processing will be interrupted.
- Action
-
Check that no errors exist in the specified Web system name.
-
KEOS24186-W (C)
The host aa....aa specified in the parameter bb....bb of the logical server cc....cc is not defined.
aa....aa: Host name
bb....bb: Parameter name
cc....cc: Logical server name wherein an error occurred
- Description
-
The host name specified in the parameter of the logical server where an error occurred is not defined. The error will be ignored, and then the processing continues.
- Action
-
Revise the settings value of the parameter specified in the configuration tag, and then change the Web system.
-
KEOS24187-W (C)
A recommended parameter and a non-recommended parameter were specified together. (parameter name - aa....aa ,bb....bb)
aa....aa: Recommended parameter
bb....bb: Non-recommended parameter
- Description
-
A recommended parameter and non-recommended parameter were specified together. The recommended parameter will be enabled.
The error will be ignored, and then the processing continues.
- Action
-
Check the settings of the recommended parameter and non-recommended parameter.
-
KEOS24188-W (C)
The logical server corresponding to the specified parameter was not found. (parameter name = aa....aa, logical server name = bb....bb)
aa....aa: Parameter
bb....bb: Logical server name
- Description
-
The logical server corresponding to the specified parameter aa....aa was not found.
The error will be ignored, and then the processing continues.
- Action
-
Check the specified parameter.
-
KEOS24189-E (C)
No hosts are defined for the management server.
- Description
-
Not even a single host is defined in the Management Server. The processing will be interrupted.
- Action
-
Define one or more hosts in the Management Server, and then re-execute the process.
-
KEOS24191-E (C)
The host name aa....aa cannot be converted to an IP address.
aa....aa: Host name
- Description
-
The host name cannot be converted to the IP address. The processing will be interrupted.
- Action
-
In the host name mentioned in the definition, specify a resolvable name as the host name or IP address.
-
KEOS24192-E (C)
The host name cannot be converted because more than one host will be replaced.
- Description
-
The host name cannot be converted because more than one host name will be converted to the same name. The processing will be interrupted.
- Action
-
Execute the command without specifying the -myhost option.
-
KEOS24193-E (C)
The host name cannot be converted because the host name and agent host do not match.
- Description
-
The host name cannot be converted because the host-name and agent-host tags are different. The processing will be interrupted.
- Action
-
Execute the command without specifying the -myhost option.
-
KEOS24194-E (C)
The host name cannot be converted because the host name aa....aa cannot be converted to IP addresses.
aa....aa: Host name
- Description
-
The host name cannot be converted because either a local host or an undecided host exists. The processing will be interrupted.
- Action
-
Execute the command without specifying the -myhost option.
-
KEOS24195-W (C)
A parameter specification linked to worker settings is incorrect. (logical server name = aa....aa)
aa....aa: Logical server name
- Description
-
A parameter specification linked to worker settings is incorrect. The processing will be interrupted.
- Action
-
Check the specified parameter.
-
KEOS24196-W (C)
The logical server aa....aa cannot be exported.
aa....aa: Logical server name
- Description
-
The logical server aa....aa could not be exported. A member of the cluster not related to the Web system cannot be exported.
-
KEOS24197-I (C)
The management server information was exported successfully.
- Description
-
An attempt to export the Management Server information was successful.
-
KEOS24198-E (C)
There are no logical servers that are not linked to the Web system.
- Description
-
There is not even a single logical server that is not related to the Web system to be distributed. The processing will be interrupted.
- Action
-
Examine the log file of the Management Server, remove the error, and then re-execute the command.
-
KEOS24200-E (C)
The specified application file is invalid. file name = aa....aa
aa....aa: File name
- Description
-
An invalid application file is specified.
The processing will be interrupted.
- Action
-
Check the file contents.
-
KEOS24201-E (C)
The application (display name = aa....aa, version = bb....bb) has already been deployed.
aa....aa: Application display name
bb....bb: Application version ID
- Description
-
An application with the same display name as the specified application has already been deployed.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
If no mistake exists in the command argument, un-deploy the application, and then re-execute the command.
-
KEOS24202-E (C)
An attempt to operate the model has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempted operation of the Web system information model has failed.
The processing will be interrupted.
The logical server and the application might have been updated by using the management portal.
- Action
-
If the error is not resolved even when the command is re-executed after some time, contact maintenance personnel.
-
KEOS24203-E (C)
The application (display name = aa....aa, version = bb....bb) is already registered.
aa....aa: Application display name
bb....bb: Application version ID
- Description
-
The application is already registered.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments and if the application is re-registered, specify the -replace option, and re-execute the cmx_register_application command.
-
KEOS24204-I (C)
The application (display name = aa....aa, version = bb....bb) was successfully registered.
aa....aa: Application display name
bb....bb: Application version ID
- Description
-
An attempt to register the application was successful.
-
KEOS24205-E (C)
The application (display name = aa....aa, version = bb....bb) is defined for a Web system. (Web system name = cc....cc)
aa....aa: Application display name
bb....bb: Application version ID
cc....cc: Web system name
- Description
-
The operation cannot be performed because the application was correlated to the Web system.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, delete the correlation between the application and the Web system, and then re-execute the command.
-
KEOS24206-E (C)
The application (display name = aa....aa, version = bb....bb) does not exist.
aa....aa: Application display name
bb....bb: Application version ID
- Description
-
The specified application does not exist.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
-
KEOS24207-I (C)
The application (display name =aa....aa, version = bb....bb) does not exist.
aa....aa: Application display name
bb....bb: Application version ID
- Description
-
The specified application does not exist.
The specified application is already deleted with other operations in the deletion process.
-
KEOS24208-E (C)
The application (display name=aa....aa, version=bb....bb) was deleted.
aa....aa: Application display name
bb....bb: Application version ID
- Description
-
The applicable application does not exist.
The application might have been deleted by using the management portal.
- Action
-
Re-register the application with the cmx_register_application command.
-
KEOS24209-I (C)
The application (display name = aa....aa, version = bb....bb) was successfully unregistered.
aa....aa: Application display name
bb....bb: Application version ID
- Description
-
An attempt to delete the application was successful.
-
KEOS24210-E (C)
The application (display name = aa....aa, version = bb....bb) is already defined for a Web system. (Web system name = cc....cc)
aa....aa: Application display name
bb....bb: Application version ID
cc....cc: Web system name
- Description
-
The application is already correlated to the Web system.
The processing will be interrupted.
- Action
-
Check the Web system information model contents and how to execute the command.
-
KEOS24211-I (C)
The application (display name = aa....aa, version = bb....bb) was successfully defined for the Web system (Web system name = cc....cc).
aa....aa: Application display name
bb....bb: Application version ID
cc....cc: Web system name
- Description
-
An attempt to correlate the application to the Web system was successful.
-
KEOS24212-E (C)
The application (display name = aa....aa, version = bb....bb) has no definitions for the Web system (Web system name = cc....cc).
aa....aa: Application display name
bb....bb: Application version ID
cc....cc: Web system name
- Description
-
The application is not correlated to the Web system.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, execute the cmx_define_application command, and then correlate the application to the Web system.
-
KEOS24213-E (C)
There is no logical server in the Web system (Web system name = aa....aa).
aa....aa: Web system name
- Description
-
The logical server does not exist in the Web system.
The processing will be interrupted.
- Action
-
Check the Web system information model contents and how to execute the command.
-
KEOS24215-I (C)
The application's (display name = aa....aa version = bb....bb) Web system definition was successfully deleted (Web system name = cc....cc).
aa....aa: Application display name
bb....bb: Application version ID
cc....cc: Web system name
- Description
-
The correlation between the application and the Web system was cancelled.
-
KEOS24216-E (C)
The application has no definitions for the Web system (Web system name = aa....aa).
aa....aa: Web system name
- Description
-
The application is not correlated to the Web system.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, execute the cmx_define_application command, and then correlate the application to the Web system.
-
KEOS24217-E (C)
The application (display name = aa....aa) has no definitions for the Web system (Web system name = bb....bb).
aa....aa: Application display name
bb....bb: Web system name
- Description
-
The application is not correlated to the Web system.
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, execute the cmx_define_application command, and then correlate the application to the Web system.
-
KEOS24218-I (C)
The application (display name =aa....aa) was successfully deployed to the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
An attempt to deploy the application was successful.
-
KEOS24219-E (C)
An attempt to deploy the application (display name = aa....aa) to the logical server (logical server name = bb....bb) has failed.
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
An attempt to deploy the application has failed.
- Action
-
Examine the log file of the Management Server, check the application operations-related log, remove the error, and then re-execute the command.
-
KEOS24220-E (C)
The application (display name = aa....aa) was undeployed from the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
The application is not deployed.
The application may have been un-deployed in other operations during command execution.
- Action
-
Deploy the application.
-
KEOS24221-I (C)
The application (display name = aa....aa) has already been deployed to the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
The application is already deployed.
-
KEOS24222-E (C)
The application (display name = aa....aa) has not been deployed to the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
The application is not deployed.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, deploy the application.
-
KEOS24223-I (C)
The application (display name = aa....aa) was successfully undeployed from the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
An attempt to un-deploy the application was successful.
-
KEOS24224-E (C)
An attempt to undeploy the application (display name = aa....aa) from the logical server (logical server name = bb....bb) has failed.
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
An attempt to un-deploy the application has failed.
- Action
-
Examine the log file of the Management Server, check the application operations-related log, remove the error, and then re-execute the command.
-
KEOS24225-E (C)
The system is busy. (logical server name = aa....aa, application display name = bb....bb)
aa....aa: Logical server name
bb....bb: Application display name
- Description
-
The operations cannot be executed because other operations are being executed for the application.
- Action
-
Terminate other operations, and then re-execute the operation.
-
KEOS24227-I (C)
The application (display name = aa....aa) was successfully started on the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
An attempt to starting the application was successful.
-
KEOS24228-E (C)
An attempt to start the application (display name = aa....aa) on the logical server (logical server name = bb....bb) has failed.
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
An attempt to start the application has failed.
- Action
-
Examine the log file of the Management Server, check the application operations-related log, remove the error, and then re-execute the command.
-
KEOS24229-I (C)
The application (display name = aa....aa) on the logical server (logical server name = bb....bb) was successfully stopped.
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
An attempt to stop the application was successful.
-
KEOS24230-E (C)
An attempt to stop the application (display name = aa....aa) on the logical server (logical server name = bb....bb) has failed.
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
An attempt to stop the application has failed.
- Action
-
Examine the log file of the Management Server, check the application operations-related log, remove the error, and then re-execute the command.
-
KEOS24231-I (C)
The application (display name = aa....aa) has already started on the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
The application is already running.
-
KEOS24232-I (C)
The application (display name = aa....aa) has already stopped on the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
The application has already stopped.
-
KEOS24233-I (C)
The application (display name = aa....aa) does not exist on the logical server (logical server name = bb....bb).
aa....aa: Application display name
bb....bb: Logical server name
- Description
-
The application is not deployed. The application need not be un-deployed.
-
KEOS24234-E (C)
A J2EE application with a different format is already registered. (display name = aa....aa)
aa....aa: Application display name
- Description
-
A J2EE application with a different format is already registered. The processing will be interrupted.
- Action
-
Check the command execution method.
-
KEOS24300-I (C)
The resource (display name = aa....aa) was successfully registered.
aa....aa: Resource display name
- Description
-
An attempt to register the resource was successful.
-
KEOS24301-I (C)
The resource (display name = aa....aa) was successfully unregistered.
aa....aa: Resource display name
- Description
-
An attempt to delete the resource was successful.
-
KEOS24302-I (C)
The resource (display name = aa....aa) was successfully defined for the Web system (Web system name = bb....bb).
aa....aa: Resource display name
bb....bb: Web system name
- Description
-
The resource was correlated to the Web system (resource name = aa....aa, Web system name = bb....bb).
-
KEOS24303-I (C)
The resource's (display name = aa....aa) definition for the Web system (Web system name = bb....bb) was successfully deleted.
aa....aa: Resource display name
bb....bb: Web system name
- Description
-
The correlation between the resource and the Web system was deleted (resource name = aa....aa, Web system name = bb....bb).
-
KEOS24304-I (C)
The resource (display name = aa....aa) was successfully deployed to the logical server (logical server name = bb....bb).
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
An attempt to deploy the resource was successful.
-
KEOS24305-I (C)
The resource (display name = aa....aa) was successfully undeployed from the logical server (logical server name = bb....bb).
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
An attempt to un-deploy the resource was successful.
-
KEOS24306-I (C)
The resource (display name = aa....aa) on the logical server (logical server name = bb....bb) was successfully started.
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
An attempt to start the resource was successful.
-
KEOS24307-I (C)
The resource (display name = aa....aa) on the logical server (logical server name = bb....bb) was successfully stopped.
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
An attempt to stop the resource was successful.
-
KEOS24308-E (C)
The resource display name has not been set.
- Description
-
The display name of the resource has not been set.
- Action
-
Check the resource file contents.
-
KEOS24309-E (C)
The resource (display name = aa....aa) is already registered.
aa....aa: Resource display name
- Description
-
The resource is already registered.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments and while re-registering the resource, specify the -replace option, and then re-execute the cmx_register_resource command.
-
KEOS24310-E (C)
The resource was not defined for the Web system (Web system name = aa....aa).
aa....aa: Web system name
- Description
-
A resource correlated to the Web system does not exist (Web system name = aa....aa).
The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, execute the cmx_define_resource command, and then correlate the resource to the Web system.
-
KEOS24311-E (C)
The resource (display name = aa....aa) does not exist.
aa....aa: Resource display name
- Description
-
The resource does not exist.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, execute the cmx_register_resource command, and then register the resource.
-
KEOS24312-E (C)
The resource (display name = aa....aa) is already defined for the Web system (Web system name = bb....bb).
aa....aa: Resource display name
bb....bb: Web system name
- Description
-
The resource is already correlated to the Web system (resource name = aa....aa, Web system name = bb....bb).
- Action
-
Check the Web system information model contents and how to execute the command.
-
KEOS24314-E (C)
The resource (display name = aa....aa) is not defined for the Web system (Web system name = bb....bb).
aa....aa: Resource display name
bb....bb: Web system name
- Description
-
The specified resource is not correlated to the Web system (resource name = aa....aa, Web system name = bb....bb).
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, execute the cmx_define_resource command, and then correlate the resource to the Web system.
-
KEOS24315-E (C)
The resource (display name = aa....aa) has already been deployed for the Web system (Web system name = bb....bb).
aa....aa: Resource display name
bb....bb: Web system name
- Description
-
The resource is already deployed (resource name = aa....aa, Web system name = bb....bb).
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, un-deploy the resource, and then re-execute the command.
-
KEOS24316-E (C)
The resource (display name = aa....aa) has not been deployed to the logical server (logical server name = bb....bb).
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
The resource has not been deployed.
- Action
-
Check the arguments specified in the command.
If no error exists in the command arguments, deploy the resource, and then re-execute the command.
-
KEOS24317-E (C)
An attempt to deploy the resource (display name = aa....aa) to the logical server (logical server name = bb....bb) has failed.
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
An attempt to deploy the resource has failed.
- Action
-
Examine the log file of the Management Server, check the resource operations-related log, remove the error, and then re-execute the command.
-
KEOS24318-E (C)
An attempt to undeploy the resource (display name = aa....aa) from the logical server (logical server name = bb....bb) has failed.
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
An attempt to un-deploy the resource has failed.
- Action
-
Examine the log file of the Management Server, check the resource operations-related log, remove the error, and then re-execute the command.
-
KEOS24319-E (C)
The system is busy. (logical server name = aa....aa, resource display name = bb....bb)
aa....aa: Logical server name
bb....bb: Resource display name
- Description
-
The operations cannot be executed because other operations are being executed for the resource.
- Action
-
Terminate other operations, and then re-execute the operation.
-
KEOS24320-I (C)
The resource (deployed resource display name = aa....aa) has already been deployed. (resource display name = bb....bb)
aa....aa: Resource display name (imported)
bb....bb: Resource display name
- Description
-
The resource is already deployed.
-
KEOS24321-I (C)
The resource (display name = aa....aa) has already started on the logical server (logical server name = bb....bb).
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
The resource has already started.
-
KEOS24322-I (C)
The resource (display name = aa....aa) has already stopped on the logical server (logical server name = bb....bb).
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
The resource has already stopped.
-
KEOS24323-E (C)
An attempt to start the resource (display name = aa....aa) on the logical server (logical server name = bb....bb) has failed.
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
An attempt to start the resource has failed.
- Action
-
Examine the log file of the Management Server, check the resource operations-related log, remove the error, and then re-execute the command.
-
KEOS24324-E (C)
An attempt to stop the resource (display name = aa....aa) on the logical server (logical server name = bb....bb) has failed.
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
An attempt to stop the resource has failed.
- Action
-
Examine the log file of the Management Server, check the resource operations-related log, remove the error, and then re-execute the command.
-
KEOS24325-I (C)
The resource (display name = aa....aa) does not exist on the logical server (logical server name = bb....bb).
aa....aa: Resource display name
bb....bb: Logical server name
- Description
-
The resource does not exist.
-
KEOS24326-E (C)
The specified file is invalid. file name = aa....aa
aa....aa: File name
- Description
-
An invalid file is specified.
The processing will be interrupted.
- Action
-
Check the file contents.
-
KEOS24401-I (C)
The operation on the Web system (Web system name = aa....aa) was successful.
aa....aa: Web system name
- Description
-
The operation on the Web system was successful.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
-
KEOS24402-W (C)
The operation on the Web system (Web system name = aa....aa) was partially successful.
aa....aa: Web system name
- Description
-
The operation on the Web system was partially successful.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
Examine the log file of the Management Server, remove the error, and then re-execute the command.
-
KEOS24403-E (C)
The attempted operation on the Web system (Web system name = aa....aa) has failed.
aa....aa: Web system name
- Description
-
The attempted operation on the Web system has failed.
Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
- Action
-
Examine the log file of the Management Server, remove the error, and then re-execute the command.
-
KEOS24404-I (C)
The operation on the unit (Web system name = aa....aa, unit name = bb....bb) was successful.
aa....aa: Web system name
bb....bb: Service unit name
- Description
-
The operation on the service unit was successful.
-
KEOS24405-E (C)
The attempted operation on the unit (Web system name = aa....aa, unit name = bb....bb) has failed.
aa....aa: Web system name
bb....bb: Service unit name
- Description
-
The attempted operation of the service unit has failed.
- Action
-
Examine the log file of the Management Server, remove the error, and then re-execute the command.
-
KEOS24406-I (C/F)
The operation was executed successfully.
- Description
-
The operation was executed successfully.
-
KEOS24407-E (C/F)
An attempt to execute the operation has failed.
- Description
-
An attempt to execute the operation has failed.
-
KEOS24408-E (C/F)
An attempt to build the model of Web systems has failed.
- Description
-
An attempt to build the Web system information model has failed.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file, and then re-execute the operation.
-
KEOS24409-E (C/F)
An attempt was made to modify unmodifiable definitions of Web system.
- Description
-
An attempt was made to modify unmodifiable tags and parameters of the Web system.
The processing will be interrupted.
- Action
-
Check the Web system contents in the Easy Setup definition file, and re-execute the operation.
-
KEOS24410-E (C/F)
An attempt was made to modify unmodifiable definitions of host.
- Description
-
An attempt was made to modify unmodifiable tags in the host definition.
The processing will be interrupted.
- Action
-
Check the contents of host definition in the Easy Setup definition file, and re-execute the operation.
-
KEOS24411-E (C/F)
An attempt to modify definitions of the Web system (Web system name = aa....aa) has failed.
aa....aa: Web system name
- Description
-
An attempt to change tags and parameters of the Web system has failed.
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file, and then re-execute the operation.
-
KEOS24412-E (C/F)
An attempt to build the Web system (Web system name = aa....aa) has failed.
aa....aa: Web system name
- Description
-
An attempt to build the Web system has failed.
The processing will be interrupted.
- Action
-
If an Easy Setup definition file is specified, check the contents of the Easy Setup definition file, and then re-execute the operation.
If a Web system name is specified, check the registered Web system information model.
-
KEOS24500-E (C)
The logical server or host not linked to the Web system is not registered.
- Description
-
The logical server or host not linked to the Web system is not registered.
The processing will be interrupted.
- Action
-
Check the command execution method.
-
KEOS24501-I (C)
A logical server or host not linked to the Web system was deleted successfully.
- Description
-
An attempt to delete the logical server and host not linked to the Web system was successful.
-
KEOS24502-E (C)
An attempt to change the model has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to change the model has failed. (details = aa....aa).
The processing will be interrupted.
- Action
-
Check the contents of the Easy Setup definition file based on the detailed information described in the following table:
Table 13‒2: List of detailed information of errors described in KEOS24502-E Details
Description
Action
- The Web system does not exist. (Web system name = aa....aa)
-
aa....aa: Web system name
The Web system does not exist (Web system name = aa....aa)#.
Make sure that the specified Web system is registered in the model.
- The number of tiers in the Web system does not match the number of tiers in the model. (Web system name = aa....aa)
-
aa....aa: Web system name
The number of tiers in the Web system is not matching (Web system name = aa....aa)#.
Make sure that tiers are not added or deleted from the specified Web system.
- The tier type cannot be changed. (tier type = aa....aa, Web system name = bb....bb)
-
aa....aa: Tier type
bb....bb: Web system name
The tier type cannot be changed (Tier type = aa....aa, Web system name = bb....bb)#.
Make sure that the specified tier is registered in the model.
- The number of J2EE servers for the tier cannot be changed. (tier type = aa....aa, Web system name = bb....bb)
-
aa....aa: Tier type
bb....bb: Web system name
The number of J2EE servers for the tier cannot be changed (Tier type = aa....aa, Web system name = bb....bb).
Make sure that the number of J2EE servers for the specified tier is not changed.
- The number of units in the Web system does not match the number of units in the model. (Web system name = aa....aa)
-
aa....aa: Web system name
The number of units in the Web system is not matching (Web system name = aa....aa).
Make sure that units are not added or deleted from the specified Web system.
- The unit does not exist. (unit name = aa....aa, Web system name = bb....bb)
-
aa....aa: Unit name
bb....bb: Web system name
The unit does not exist (Unit name = aa....aa, Web system name = bb....bb).
Make sure that the specified unit name is registered in the model.
- The number of hosts in the unit does not match the number of hosts in the model. (unit name = aa....aa, Web system name = bb....bb)
-
aa....aa: Unit name
bb....bb: Web system name
The number of hosts in the unit is not matching (Unit name = aa....aa, Web system name = bb....bb)#.
Make sure that hosts are not added or deleted from the specified unit.
- The host specified in the unit does not exist. (unit name = aa....aa, host name = bb....bb, Web system name = cc....cc)
-
aa....aa: Unit name
bb....bb: Host name
cc....cc: Web system name
The host specified in the unit does not exist (Unit name = aa....aa, host name = bb....bb, Web system name = cc....cc)#.
Make sure that the specified host is registered in the model.
- The specified logical server does not exist. (logical server name = aa....aa, Web system name = bb....bb)
-
aa....aa: Logical server name
bb....bb: Web system name
The specified logical server does not exist (Logical server name = aa....aa, Web system name = bb....bb)#.
Make sure that the specified logical server is registered in the model.
- The logical server name cannot be changed. (host name = aa....aa, Web system name = bb....bb)
-
aa....aa: Host name
bb....bb: Web system name
The logical server name cannot be changed (Host name = aa....aa, Web system name = bb....bb).
Make sure that the specified logical server is registered in the model.
- The number of logical servers cannot be changed. (Web system name = aa....aa)
-
aa....aa: Web system name
The number of logical servers cannot be changed (Web system name = aa....aa)#.
Make sure that the definitions of the logical server are not added or deleted.
- The load balancer definition cannot be changed. (Web system name = aa....aa)
-
aa....aa: Web system name
The load balancer definition cannot be changed (Web system name = aa....aa).
Make sure that the definition of the LoadBalancer tag is not changed from the definition file used when the previous system was built.
- The host does not exist. (host name = aa....aa)
-
aa....aa: Host name
The host does not exist (Host name = aa....aa).
Make sure that the specified host is registered in the model.
- The definition of the administration agent cannot be changed. (host name = aa....aa)
-
aa....aa: Host name
The definition of the host agent cannot be changed (Host name = aa....aa).
Make sure that the definition of the host agent is not changed from the definition file used when the previous system was built.
# If the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.
-
KEOS24503-E (C)
An enabled In-process HTTP server cannot be disabled. (Web system name = aa....aa, parameter = bb....bb)
aa....aa: Web system name
bb....bb: Parameter
- Description
-
You cannot disable an enabled in-process HTTP server.
The processing will be interrupted.
- Action
-
Check the specified parameter bb....bb.
-
KEOS24504-E (C)
An error occurred in the starting process of the previous level. (Web system name = aa....aa, logical server name = bb....bb)
aa....aa: Web system name
bb....bb: Logical server name
- Description
-
An error occurred in the starting process of the previous level, and therefore, the corresponding logical server cannot be started.
The processing will be interrupted.
- Action
-
Check that the setup information of the logical server, which is failed to start first, is distributed.
See the detailed information and the Management Agent log, remove the errors, and then re-execute the process.
-
KEOS24505-W (C)
An attempt to verify the configuration file failed. (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc, details = dd....dd)
aa....aa: Web system name
bb....bb: Unit name
cc....cc: Logical server name
dd....dd: Details
- Description
-
An attempt to verify the configuration file failed.
The processing continues.
- Action
-
Check the logical server settings, and then re-execute the operation.
-
KEOS24506-W (C/F)
Specified value is duplicated. (Web system name = aa....aa, parameter name = bb....bb, parameter value = cc....cc)
aa....aa: Web system name
bb....bb: Parameter name
cc....cc: Parameter value
- Description
-
Specified value is duplicated.
The changes are ignored and the processing continues.
- Action
-
Correct the definition file so that the specified value of the relevant parameter is not duplicated, and then re-execute the operation.
-
KEOS24507-W (C/F)
The specified J2EE server was not found. (logical server name = aa....aa, parameter name = bb....bb, parameter value = cc....cc)
aa....aa: Logical server name
bb....bb: Parameter name
cc....cc: Parameter value
- Description
-
The specified J2EE server was not found.
The error will be ignored, and then the processing continues.
- Action
-
Correct the logical server name of the specified J2EE server, and then re-execute the operation.
-
KEOS24508-W (C/F)
There is a correlation error in the setting values of the parameters. (logical server name = aa....aa, parameter name 1 = bb....bb, parameter value 1 = cc....cc, parameter name 2 = dd....dd, parameter value 2 = ee....ee, parameter name 3 = ff....ff, parameter value 3 = gg....gg)
aa....aa: Logical server name
bb....bb: Parameter name 1
cc....cc: Parameter value 1
dd....dd: Parameter name 2
ee....ee: Parameter value 2
ff....ff: Parameter name 3
gg....gg: Parameter value 3
- Description
-
A correlation error between parameter 2 and parameter 3 (such as errors related to maximums or minimums) exists in the value of parameter 1. The error is ignored and processing continues.
- Action
-
Revise the set value of the parameter specified in the configuration tag, and then change the Web system configuration.
-
KEOS24700-I (F)
Connecting to the load balancer of aa....aa will now start.
aa....aa: IP address of load balancer
- Description
-
The load balancer will be connected.
-
KEOS24701-I (F)
The connection to the load balancer of aa....aa was terminated.
aa....aa: IP address of load balancer
- Description
-
The load balancer will be disconnected.
-
KEOS24710-I (F)
Sending the following command to the load balancer of aa....aa will now start: script-name=[bb....bb], command-name=[cc....cc], command=[dd....dd]
aa....aa: IP address of load balancer
bb....bb: Script name
cc....cc: Command name
dd....dd: Command
- Description
-
A command will be sent to the load balancer.
-
KEOS24711-I (F)
Output of the previous command was received from the load balancer of aa....aa: [bb....bb]
aa....aa: IP address of load balancer
bb....bb: Output of command
- Description
-
The output of the command was received from the load balancer.
-
KEOS26000-I (F)
The management event sending function has started.
- Description
-
The management event sending function has started.
The processing continues.
-
KEOS26001-I (F)
The management event sending function has stopped.
- Description
-
The management event sending function has stopped.
The processing continues.
-
KEOS26002-E (F)
An attempt to start the management event sending function has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to start the management event sending function has failed.
The processing continues.
- Action
-
See the detailed information, and then revise the operating environment and settings.
-
KEOS26010-E (F)
An attempt to read the settings file has failed. (file = aa....aa)
aa....aa: File name
- Description
-
An attempt to read the property file or message ID list file for Management event invocation has failed.
The processing continues, but the Management event will not be issued.
- Action
-
Confirm that the settings file exists, check the specified contents and access permissions, and then restart the J2EE server.
-
KEOS26011-E (F)
A required property (aa....aa) is not specified.
aa....aa: Property key
- Description
-
The necessary properties are not specified in the Management event issue properties file.
The operations of the Management event issue function will stop.
- Action
-
Revise the contents of the Management event issue properties file.
-
KEOS26012-E (F)
The specified property (aa....aa) is invalid.
aa....aa: Property key
- Description
-
The contents specified in the Management event issue properties file are invalid.
- Action
-
Revise the contents of the Management event issue properties file.
-
KEOS26013-E (F)
The message ID was not specified.
- Description
-
The contents specified in the Management event issue message ID list file are invalid.
The operations of the Management event issue function will stop.
- Action
-
Revise the contents of the Management event issue message ID list file.
-
KEOS26014-W (F)
The specified property (aa....aa) is invalid. The default value (bb....bb) will be used.
aa....aa: Property key
bb....bb: Default value
- Description
-
The contents specified in the Management event issue properties file are invalid.
The operations of the Management event issue function will continue using the default value.
- Action
-
Revise the contents of the Management event issue properties file.
-
KEOS26050-I (F)
The management event was sent successfully. (message ID = aa....aa, occurred time = bb....bb, optional information = cc....cc)
aa....aa: Message ID
bb....bb: Management event request time
cc....cc: Additional information (demarcate with colon if there is one or more additional information)
- Description
-
The management event was sent successfully.
-
KEOS26051-E (F)
An attempt to send the management event has failed. (message ID = aa....aa, occurred time = bb....bb, optional information = cc....cc, details = dd....dd)
aa....aa: Message ID
bb....bb: Management event request time
cc....cc: Additional information (demarcate with colon if there is one or more additional information)
dd....dd: Details
- Description
-
An attempt to send the management event has failed.
The processing continues. If the resend settings are specified, an attempt will be made to resend the Management event.
The possible causes are as follows:
-
The Management Server described in the settings file is not running.
-
An error or temporary load occurred in the network.
-
- Action
-
See the detailed information, and then revise the operating environment and the contents of the Management event issue properties file.
-
KEOS26052-E (F)
The management event could not be sent. (details = aa....aa)
aa....aa: Details
- Description
-
The management event could not be sent.
The operations of the Management event issue function will stop.
- Action
-
See the detailed information, and then revise the operating environment and the contents of the Management event issue properties file.
-
KEOS26053-W (F)
The retry limit for sending management events was exceeded. (message ID = aa....aa, occurred time = bb....bb, optional information = cc....cc)
aa....aa: Message ID
bb....bb: Management event request time
cc....cc: Additional information (demarcate with colon if there is one or more additional information)
- Description
-
The retry limit for sending management events was exceeded.
The applicable Management event will be destroyed.
- Action
-
Revise the operating environment and the contents of the Management event issue properties file.
-
KEOS26054-W (F)
The management events could not be sent, because the maximum number of simultaneous send operations was exceeded. (message ID = aa....aa, optional information = bb....bb)
aa....aa: Message ID
bb....bb: Additional information (demarcate with colon if there is one or more additional information)
- Description
-
The maximum number of concurrently-issued Management events was exceeded.
The applicable Management event will be destroyed.
- Action
-
Revise the operating environment and the contents of the Management event issue properties file.
-
KEOS26100-E (F)
An internal error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
An internal error occurred in the Management event issue functionality.
The operations of the Management event issue functionality will continue if possible, and will terminate if operations cannot be continued.
- Action
-
If the error cannot be removed even after restarting the J2EE server, contact maintenance personnel.
-
KEOS26500-E (F)
An attempt to initialize the management action has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to initialize the management action has failed.
The processing continues, but the Management action will not run.
- Action
-
See the detailed information, and then revise the operating environment and the contents of the settings file.
-
KEOS26510-I (F)
A management event was received. (logical server name = aa....aa, message ID = bb....bb, optional information = cc....cc, occurred time = dd....dd)
aa....aa: Logical server name
bb....bb: Message ID
cc....cc: Additional information (demarcate with colon if there is one or more additional information)
dd....dd: Event issuing time
- Description
-
A management event was received.
-
KEOS26520-W (F)
The management action was not defined. (logical server name = aa....aa, message ID = bb....bb)
aa....aa: Logical server name
bb....bb: Message ID
- Description
-
The management action was not defined.
The processing continues.
- Action
-
Revise the settings of the Management action.
-
KEOS26521-E (F)
The definition of the management action is invalid. (management action ID = aa....aa)
aa....aa: Management action ID
- Description
-
The definition of the management action is invalid.
The processing continues.
- Action
-
Revise the settings of the Management action.
-
KEOS26522-W (F)
A management event had already been received. (logical server name = aa....aa, message ID = bb....bb, optional information = cc....cc, occurred time = dd....dd)
aa....aa: Logical server name
bb....bb: Message ID
cc....cc: Additional information (demarcate with colons if there is one or more additional information)
dd....dd: Original event issuing time when the management event was requested
- Description
-
The Management event that was received has already been received.
The processing continues without executing the Management action.
The causes for the error may be duplicate sending of Management events due to temporary load and network error.
- Action
-
Revise the operating environment or the contents of the following settings files:
-
Management event issue properties file
- manager.mevent.send.timeout
- manager.mevent.retry.limit
-
-
KEOS26523-W (F)
The oldest receiving information of management event is deleted, because the number of receiving information exceeded the maximum number. (maximum number = aa....aa, deleted receiving information = [bb....bb])
aa....aa: Maximum number of stored receiving information
bb....bb: Receiving information to be deleted
- Description
-
The oldest receiving information of management event is deleted, because the number of receiving information exceeded the maximum number.
The processing continues.
Multiple Management events may have been issued.
- Action
-
Revise the operating environment or the contents of the following settings files:
-
Management action execution properties file
- maction.mevent.receiving_info.keep_size.max
-
-
KEOS26530-I (F)
The management action will now be executed. (management action ID = aa....aa)
aa....aa: Management action ID
- Description
-
The management action will now be executed.
The processing continues.
-
KEOS26531-I (F)
The management action execution has finished. (management action ID = aa....aa, exit code = bb....bb)
aa....aa: Management action ID
bb....bb: Exit code
- Description
-
The management action execution has finished.
The processing continues.
-
KEOS26532-W (F)
The management action execution has exceeded the timeout limit. (management action ID = aa....aa)
aa....aa: Management action ID
- Description
-
The management action execution has exceeded the timeout limit.
The processing continues.
- Action
-
Revise the settings of the Management action.
-
KEOS26533-E (F)
An attempt to execute the management action has failed. (management action ID = aa....aa, details = bb....bb)
aa....aa: Management action ID
bb....bb: Detailed message
- Description
-
An attempt to execute the management action has failed.
The processing continues.
- Action
-
See the detailed information, and then revise the operating environment and the contents of the settings file.
-
KEOS26534-W (F)
Execution of management action was controlled because execution was requested during a lock period. (management action ID = aa....aa)
aa....aa: Management action ID
- Description
-
Execution of management action was controlled because execution was requested during a lock period. The processing continues without executing the Management action.
- Action
-
If this problem occurs frequently, revise the operating environment and the contents of the settings file.
-
KEOS26535-W (F)
Execution of management action was controlled because the maximum number of simultaneous executions was exceeded. (management action ID = aa....aa)
aa....aa: Management action ID
- Description
-
The execution of the Management action was controlled by limiting the concurrently executing Management actions. The processing continues without executing the Management action.
- Action
-
If this problem occurs frequently, revise the operating environment and the contents of the settings file.
-
KEOS26600-E (F)
An internal error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
An internal error occurred in the Management action execution function.
The operations of the Management Server will continue if possible, and will terminate if operations cannot be continued.
- Action
-
If the error cannot be removed even after restarting the Management Server, contact maintenance personnel.
-
KEOS27000-I (F)
Authentication was successful. (user ID = aa....aa)
aa....aa: User ID
- Description
-
Authentication was successful.
-
KEOS27001-E (F)
Authentication failed. An administrator's user ID or a password is incorrect. (userID = aa....aa)
aa....aa: User ID
- Description
-
An attempted authentication has failed. An administrator's user ID or a password is incorrect. The processing will be interrupted.
- Action
-
Enter the correct administrator user ID or password.
-
KEOS27002-E (F)
Authentication failed. Authentication request expired. (userID=aa....aa)
aa....aa: User ID
- Description
-
An attempted authentication has failed. Authentication request expired. The processing will be interrupted.
- Action
-
Review the operating environment if the error occurs frequently. The possible causes are as follows:
-
The network is highly loaded.
-
The computer is highly loaded.
-
-
KEOS27010-I (F)
The external MBean was successfully registered. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to register an external Mbean was successful.
-
KEOS27011-I (F)
The external MBean was successfully unregistered. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to cancel the registration of the external Mbean was successful.
-
KEOS27012-E (F)
An attempt to read the MBean plug-in definition file (aa....aa) has failed.
aa....aa: File name
- Description
-
An attempt to read the Mbean plug definition file has failed. The registration process of the external Mbean will be interrupted.
- Action
-
Check the read permission of the Mbean plug definition file.
-
KEOS27013-E (F)
The MBean plug-in definition file is invalid. file name = aa....aa line number = bb....bb column number = cc....cc details = dd....dd
aa....aa: File name
bb....bb: Line number
cc....cc: Column number
dd....dd: Details number
- Description
-
An attempt to parse the external Mbean plugin definition file has failed. The registration process of the external Mbean will be interrupted.
- Action
-
Check the contents of the Mbean plugin definition file.
-
KEOS27014-E (F)
An object name that is invalid in external MBean has been specified. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to register the external Mbean has failed. An invalid object name is specified. The proceeding the registration process of the external Mbean will continue.
- Action
-
Specify a valid object name.
-
KEOS27015-E (F)
An external MBean class was not found. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to register the external Mbean has failed. Class implementation could not be found. The proceeding the registration process of the external Mbean will continue.
- Action
-
Check that the external JAR file supporting Mbean plug-in definition files exists. Specify a valid object name.
-
KEOS27016-E (F)
An attempt to create an external MBean instance has failed. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to register the external Mbean has failed. An attempted instance generation has failed. The proceeding the registration process of the external Mbean will continue.
- Action
-
Contact maintenance personnel.
-
KEOS27017-E (F)
The external MBean is already registered. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to register the external Mbean has failed. An already registered object name is specified. The proceeding the registration process of the external Mbean will continue.
- Action
-
Check that an MBean plug-in definition file with the same contents exists.
-
KEOS27018-E (F)
An attempt to register an external MBean has failed. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd, details = An exception was thrown by the MBeanRegistration#preRegister method.)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to register the external Mbean has failed. An exception was thrown in the MBeanRegistration#preRegister method. The proceeding the registration process of the external Mbean will continue.
- Action
-
Contact maintenance personnel.
-
KEOS27019-E (F)
The external MBean is not a JMX compliant MBean. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to register the external Mbean has failed. An Mbean not complying with JMX was specified. The proceeding the registration process of the external Mbean will continue.
- Action
-
Contact maintenance personnel.
-
KEOS27020-E (F)
An attempt to unregister the external MBean has failed. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd, details = An exception was thrown by the MBeanRegistration#preDeregister method.)
aa....aa: Class name
bb....bb: Object name
cc....cc: File name
dd....dd: Definition order
- Description
-
An attempt to cancel the registration of an external Mbean has failed. An exception was thrown in the MBeanRegistration#preRegister method. The proceeding the registration process of the external Mbean will continue.
- Action
-
Contact maintenance personnel.
-
KEOS27021-E (F)
The MBean plug-in definition file is invalid. file name = aa....aa details = bb....bb
aa....aa: File name
bb....bb: Detailed message
- Description
-
An analysis error occurred in the Mbean plug-in function. The registration process of the external Mbean will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS27030-I (F)
The manager remote access function has started.
- Description
-
The Manager Server remote access function has started.
-
KEOS27031-I (F)
The manager remote access function has stopped.
- Description
-
The Manager Server remote access function has stopped.
-
KEOS27032-I (F)
The external connection function of the manager remote access function has started.
- Description
-
The external connection function of the Management Server remote access function has started.
-
KEOS27033-I (F)
The external connection function of the manager remote access function has stopped.
- Description
-
The external connection function of the Management Server remote access function has stopped.
-
KEOS27034-E (F)
An attempt to start the external connection function of the manager remote access function has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to start the external connection function of the Management Server remote access function has failed. The processing continues.
- Action
-
Check the contents of the settings file, and then restart the Management Server.
-
KEOS27040-E (C)
A communication error occurred.
- Description
-
An error occurred while communicating with the Administration Agent. The processing will be interrupted.
- Action
-
Check the contents of the settings file, and then restart the Management Server.
-
KEOS27099-E (F)
An internal error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
An internal error occurred in the Mbean server function. The processing continues.
- Action
-
If the error cannot be removed even after restarting the Management Server, contact maintenance personnel.
-
KEOS27101-E (V)
Authentication failed. An administrator's user ID or a password is incorrect.
- Description
-
An attempted authentication has failed. An administrator's user ID or a password is incorrect. The processing will be interrupted.
- Action
-
Enter the correct administrator user ID or password.
-
KEOS27102-E (V)
Authentication failed. Authentication request expired.
- Description
-
An attempted authentication has failed. Authentication request expired. The processing will be interrupted.
- Action
-
Review the operating environment if the error occurs frequently. The possible causes are as follows:
-
The network is highly loaded.
-
The computer is highly loaded.
-
-
KEOS27103-E (V)
An internal error occurred. Detail=aa....aa
aa....aa: Details
- Description
-
An internal error occurred. The processing will be interrupted.
- Action
-
If the error cannot be removed even after restarting the Management Server, contact maintenance personnel.
-
KEOS27105-E (V)
An error occurred while connecting to the RMI registry. Detail=aa....aa
aa....aa: Details
- Description
-
An error occurred while connecting to the RMI registry. The processing will be interrupted.
- Action
-
See the detailed information, and then revise the operating environment and the contents of the settings file.
-
Is the Management Server running?
-
Are the specified host name and the port number invalid?
-
-
KEOS27106-E (V)
An error occurred during JMXConnector generation. Detail=aa....aa
aa....aa: Details
- Description
-
An error occurred during JMXConnector generation. The processing will be interrupted.
- Action
-
See the detailed information, and then revise the operating environment and the contents of the settings file.
-
Is the Management Server running?
-
Are the specified host name and the port number invalid?
-
-
KEOS28001-I (F)
The Setup Wizard (aa....aa) has started.
aa....aa: GUI/CUI
- Description
-
The Setup Wizard has started.
-
KEOS28002-I (F)
The Setup Wizard (aa....aa) has ended.
aa....aa: GUI/CUI
- Description
-
The Setup Wizard has ended.
-
KEOS28003-E (C/F)
An error occurred in the Setup Wizard (aa....aa). (details = bb....bb)
aa....aa: GUI/CUI
bb....bb: Detailed message
- Description
-
An error occurred in the Setup Wizard.
The processing will be interrupted.
- Action
-
See details, remove the cause of the error, and then re-execute the Setup Wizard.
Table 13‒3: List of the detailed information in KEOS28003-E Details
Description
Action
An I/O error occurred in the lock file for mutual exclusion. file name = aa....aa, details = bb....bb
An I/O error occurred in the lock file for exclusion. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Detailed message
An I/O error occurred in the lock file for mutual exclusion.
The processing will be interrupted.
Contact maintenance personnel.
-
KEOS28004-I (F)
The setup has started.
- Description
-
The setup has started.
-
KEOS28005-I (F)
The setup has ended.
- Description
-
The setup has ended.
-
KEOS28006-E (F)
An error occurred in the setup.
- Description
-
An error occurred during the setup process.
The processing will be interrupted.
- Action
-
See the action for the error-level message that is output before this message.
-
KEOS28007-I (F)
The unsetup has started.
- Description
-
The unsetup process has started.
-
KEOS28008-I (F)
The unsetup has ended.
- Description
-
The unsetup process has ended.
-
KEOS28009-E (F)
An error occurred in the unsetup.
- Description
-
An error occurred during the unsetup process.
The processing will be interrupted.
- Action
-
See the action for the error-level message that is output before this message.
-
KEOS28010-I (F)
Command execution has started. (command = aa....aa)
aa....aa: Command name
- Description
-
The Setup Wizard has executed the command.
-
KEOS28011-I (F)
Command execution has ended. (command = aa....aa, exit code = bb....bb)
aa....aa: Command name
bb....bb: Exit code
- Description
-
The command executed by the Setup Wizard has ended.
-
KEOS28012-E (C/F)
An error occurred during command execution. (command = aa....aa, details = bb....bb)
aa....aa: Command name
bb....bb: Detailed message
- Description
-
An error occurred in the command executed by the Setup Wizard.
The processing will be interrupted.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard. If one of the following messages is output in the detailed information, re-execute the Setup Wizard:
-
hwsserveredit: cannot delete
-
KDJE40028-E The deletion of the J2EE server has failed. Server name = aa....aa, Reason = Deletion of file failed
aa....aa: Server name
-
-
KEOS28014-E (C/F)
An error occurred during an attempt to access the file. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Detailed message
- Description
-
An error occurred while accessing to the file from the Setup Wizard.
The processing will be interrupted.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.
-
KEOS28015-I (F)
The setup information file has been output. (file name = aa....aa)
aa....aa: File name
- Description
-
The setup information file is output.
-
KEOS28016-I (F)
The setup information list has been output. (file name = aa....aa)
aa....aa: File name
- Description
-
The setup information list is output.
-
KEOS28017-I (F)
Collection of the snapshot log files has started.
- Description
-
The Setup Wizard has started collecting the snapshot log.
-
KEOS28018-I (F)
Collection of the snapshot log files has ended. (file name = aa....aa)
aa....aa: File name
- Description
-
The collection of the snapshot log by the Setup Wizard has ended.
-
KEOS28019-E (C/F)
An error occurred during collection of the snapshot log files. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred in the collection of the snapshot log by the Setup Wizard.
The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS28020-I (F)
Backup has started.
- Description
-
The Setup Wizard has started the backup process.
-
KEOS28021-I (F)
Backup has ended.
- Description
-
The backup process in the Setup Wizard has ended.
-
KEOS28022-E (C/F)
An error occurred during backup. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred during the backup process in the Setup Wizard.
The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS28023-I (F)
The port number check has started.
- Description
-
The port number check has started in the setup.
-
KEOS28024-I (F)
The port number check has ended.
- Description
-
The port number check has ended in the setup.
-
KEOS28025-I (F)
The Component Container administrator has been changed.
- Description
-
The Component Container administrator was changed in the setup.
-
KEOS28026-E (C/F)
An error occurred during an attempt to change the Component Container administrator. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred during an attempt to change the Component Container administrator in the setup.
The processing will be interrupted.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.
-
KEOS28027-E (C)
An instance of the Setup Wizard is already running.
- Description
-
The Setup Wizard cannot be started because the Setup Wizard is already running for some another process on the same machine.
The processing will be interrupted.
- Action
-
Stop the running Setup Wizard.
-
KEOS28028-E (C/F)
The setup cannot be executed by the Setup Wizard, because it has already done by a utility other than the Setup Wizard.
- Description
-
The Setup Wizard cannot be started because the Management Server is already set up using another method.
The processing will be interrupted.
- Action
-
Delete the entire Application Server environment, and then re-install the Management Server.
-
KEOS28029-E (C/F)
The setup information file does not exist. (file name = aa....aa)
aa....aa: File name
- Description
-
The specified setup information file does not exist.
The processing will be interrupted.
- Action
-
Revise file name or path of the setup information file.
-
KEOS28030-E (C/F)
The setup information file is corrupted. (file name = aa....aa)
aa....aa: File name
- Description
-
The specified setup information file has corrupted.
The processing will be interrupted.
- Action
-
Check the specified file.
-
KEOS28031-E (C/F)
A specified command option is invalid. (details = aa....aa)
aa....aa: Details
- Description
-
The specified command option is invalid.
The processing will be interrupted.
- Action
-
Revise command options.
Table 13‒4: List of the detailed information in KEOS28031-E Details
Description
Action
The same option is specified more than once. Option = aa....aa
The same option has been specified more than once. (option = aa....aa)
aa....aa: Option
The same option is specified more than once in the command option.
The processing will be interrupted.
Revise command options.
A value was not specified for the option. Option = aa....aa
An option value is not specified. (option = aa....aa)
aa....aa: Option
A value was not specified for the option.
The processing will be interrupted.
Revise command options.
An invalid option is specified. Option = aa....aa
An invalid option is specified. (option = aa....aa)
aa....aa: Option
An invalid option is specified.
The processing will be interrupted.
Revise command options.
The option aa....aa and the option bb....bb cannot be specified simultaneously.
The option aa....aa and the option bb....bb cannot be specified simultaneously.
aa....aa: Option 1
bb....bb: Option 2
Option that cannot be specified at the same time is specified.
The processing will be interrupted.
Revise command options.
A required option is not specified. Option = aa....aa
A required option is not specified. (option = aa....aa)
aa....aa: Option
A required option is not specified.
The processing will be interrupted.
Revise command options.
-
KEOS28032-E (C/F)
The Setup Wizard was forced to terminate.
- Description
-
The Setup Wizard was terminated forcibly.
The processing will be interrupted.
- Action
-
Re-execute the Setup Wizard. Restart the OS, if an error occurs even after re-executing the Setup Wizard.
-
KEOS28033-E (C)
Usage :
setupwizard
setupwizard -f <setup information file> [-force]
setupwizard -f <setup information file> -md <definition file> [-force]
setupwizard -export -omd <definition file>
setupwizard -view -f <setup information file>
setupwizard -clean [-force]
setupwizard -h | -help
- Description
-
The method of starting the command is incorrect. The command execution will be suspended.
- Action
-
Enter the correct command, and then re-execute the command.
-
KEOS28034-E (C/F)
A value from 1024 to 65535 must be specified because aa....aa has been specified for the Component Container administrator. (bb....bb=cc....cc)
aa....aa: Component Container administrator
bb....bb: Corresponding item
cc....cc: Port number
- Description
-
A user other than root has been specified for the Component Container administrator, and therefore, a value outside the range of 1024 to 65535 cannot be specified in the port number.
The processing will be interrupted.
- Action
-
If a user other than root has been specified for the Component Container administrator, specify a value in the range of 1024 to 65535 in the port number.
-
KEOS28035-E (C/F)
A duplicate port number is specified. (port number = aa....aa, duplicate item = bb....bb)
aa....aa: Port number
bb....bb: Duplicate item
- Description
-
A duplicate port number is specified in the Setup Wizard, and therefore, the setup cannot be started.
The processing will be interrupted.
- Action
-
Revise the port number specified in the Setup Wizard.
-
KEOS28036-E (C/F)
This version(aa....aa) does not support the specified setup information file. (file name = bb....bb, file version = cc....cc)
aa....aa: Application server version
bb....bb: File name
cc....cc: Application Server version in which the file is created
- Description
-
The setup cannot be executed with the setup information file having version later than that of the Setup Wizard version.
The processing will be interrupted.
- Action
-
Check the specified file.
-
KEOS28037-E (C/F)
The Cosminexus environment is corrupted. (details = aa....aa)
aa....aa: Details
- Description
-
Cannot continue processing because the Application Server environment has corrupted.
The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS28038-E (C/F)
An attempt to start the Setup Wizard has failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to start the Setup Wizard has failed.
The processing will be interrupted.
- Action
-
If the following message is output in the detailed information, revise the log settings for the Setup Wizard definition file:
-
Failed to initialize trace file.
-
Failed to make directory
For other than the above-mentioned cases, contact maintenance personnel.
-
-
KEOS28040-I (F)
The Management Server administrator's group has been changed.
- Description
-
The Setup Wizard modified the Management Server administrator group.
-
KEOS28041-E (C/F)
An error occurred during an attempt to change the Management Server administrator's group. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred during an attempt to modify the Management Server administrator group by the Setup Wizard.
The processing will be interrupted.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.
-
KEOS28042-E (C/F)
An error occurred during analysis of the simple configuration definition file. (file name = aa....aa)
aa....aa: File name
- Description
-
An error occurred during the analysis of the Easy Setup definition file. A cording error exists in the Easy Setup definition file.
The processing will be interrupted.
- Action
-
See the message displayed after this message, remove the cause of error, and then re-execute the Setup Wizard.
-
KEOS28043-E (C/F)
A syntax error exists in the simple configuration definition file. (line number = aa....aa, column number = bb....bb, details = cc....cc)
aa....aa: Line number
bb....bb: Column number
cc....cc: Details
- Description
-
A syntax error exists in coding of the Easy Setup definition file.
The processing will be interrupted.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.
-
KEOS28044-E (C/F)
Contents that cannot be specified for the Setup Wizard exist. (details = aa....aa)
aa....aa: Details
- Description
-
The Easy Setup definition file contains coding that cannot be specified for the Setup Wizard.
The processing will be interrupted.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.
Table 13‒5: List of detailed information in KEOS28044-E Details
Description
Action
An unusable XML namespace is specified in the xmlns attribute of <model-definition>. Value=aa....aa
An unusable XML namespace is specified for the xmlns attribute of <model-definition>. (value = aa....aa)
aa....aa: Value specified in the xmlns attribute of <model-definition>
An unusable XML namespace is specified in <model-definition> of the Easy Setup definition file.
The processing will be interrupted.
Change the definition of <model-definition> in the Easy Setup definition file.
The XML namespace of the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.
An XML namespace is not specified in the xmlns attribute of <model-definition>.
An XML namespace is not specified for the xmlns attribute of <model-definition>
An XML namespace is not specified in the xmlns attribute of <model-definition> in the Easy Setup definition file.
The processing will be interrupted.
Change the definition of <model-definition> in the Easy Setup definition file.
The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.
<model-definition>-<web-system> is not defined.
No definition of <model-definition>-<web-system> exists.
The definition of <model-definition>-<web-system> does not exist in the Easy Setup definition file.
The processing will be interrupted.
Add the Web system definition (<model-definition>-<web-system>) in the Easy Setup definition file.
Multiple <model-definition>-<web-system> are defined.
Multiple definitions of <model-definition>-<web-system> exist.
Multiple <model-definition>-<web-system> are defined in the Easy Setup definition file.
The processing will be interrupted.
Consolidate the definitions of <model-definition>-<web-system> in the Easy Setup definition file.
<web-system>-<load-balancer> is defined.
A definition of <web-system>-<load-balancer> exists.
A definition of <web-system>-<load-balancer> exists in the Easy Setup definition file.
The processing will be interrupted.
Delete the definition of <web-system>-<load-balancer> from the Easy Setup definition file.
Multiple <web-system>-<tier> are defined.
Multiple definitions of <web-system>-<tier> exist.
Multiple <web-system>-<tier> are defined in the Easy Setup definition file.
The processing will be interrupted.
Consolidate the definitions of <web-system>-<tier> in the Easy Setup definition file.
A value other than "combined-tier" or "j2ee-tier" is specified in <tier>-<tier-type>. Value=aa....aa
The value of <tier>-<tier-type> is not "combined-tier" or "j2ee-tier". (value = aa....aa)
aa....aa: Value specified in <tier-type>.
A value other than "combined-tier" or "j2ee-tier" is specified in <tier>-<tier-type> in the Easy Setup definition file.
The processing will be interrupted.
Specify "combined-tier" or "j2ee-tier" as the value of <tier>-<tier-type> in the Easy Setup definition file.
A value other than "1" is specified in <tier>-<j2ee-server-count>. Value=aa....aa
The value of <tier>-<j2ee-server-count> is not "1". (value = aa....aa)
aa....aa: Value specified in <j2ee-server-count>
A value other than "1" is specified in <tier>-<j2ee-server-count> in the Easy Setup definition file.
The processing will be interrupted.
Delete the <tier>-<j2ee-server-count> tag from the Easy Setup definition file or specify "1" as the value of <tier>-<j2ee-server-count>.
Multiple <web-system>-<unit> are defined.
Multiple definitions of <web-system>-<unit> exist.
Multiple <web-system>-<unit> are defined in the Easy Setup definition file.
The processing will be interrupted.
Consolidate the definitions of <web-system>-<unit> in the Easy Setup definition file.
A value other than "@myhost" is specified in <unit>-<allocated-host>-<host-ref>. Value=aa....aa
The value of <unit>-<allocated-host>-<host-ref> is not "@myhost". (value = aa....aa)
aa....aa: Value specified in <host-ref>
A value other than "@myhost" is specified in <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.
The processing will be interrupted.
Specify "@myhost" as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.
The <logical-server-name> is not defined for the item in which the <unit>-<allocated-host>-<define-server>-<logical-server-type> value is aa....aa.
No definition of <logical-server-name> exists that corresponds to the item whose <unit>-<allocated-host>-<define-server>-<logical-server-type> value is aa....aa.
aa....aa: Logical server type
The <logical-server-name> is not defined for the item in which the <unit>-<allocated-host>-<define-server>-<logical-server-type> value is aa....aa in the Easy Setup definition file. The processing will be interrupted.
For the logical server definition in which logical server type is aa....aa in the Easy Setup definition file, add the following <logical-server-name> tag and define the logical server name:
- <unit> - <allocated-host> - <define-server>
-
<logical-server-type>aa....aa</logical-server-type>
<logical-server-name>logical server name</logical-server-name>
A value other than "web-server", "j2ee-server", or "performance-tracer" is specified in <unit>-<allocated-host>-<define-server>-<logical-server-type>. Value=aa....aa
The value of <unit>-<allocated-host>-<define-server>-<logical-server-type> is not "web-server", "j2ee-server", or "performance-tracer". (value = aa....aa)
aa....aa: Logical server type
A value other than "web-server", "j2ee-server", or "performance-tracer" is specified in <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file.
The processing will be interrupted.
Specify "web-server", "j2ee-server", or "performance-tracer" as the value of <web-system>-<unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file.
Multiple <model-definition>-<host> are defined.
Multiple definitions of <model-definition>-<host> exist.
Multiple <model-definition>-<host> are defined in the Easy Setup definition file.
The processing will be interrupted.
Consolidate the definitions of <model-definition>-<host> in the Easy Setup definition file.
A value other than "@myhost" is specified in <model-definition>-<host>-<host-name>. Value=aa....aa
The value of <model-definition>-<host>-<host-name> is not "@myhost". (value = aa....aa)
aa....aa: Value specified in <host-name>
A value other than "@myhost" is specified in <model-definition>-<host>-<host-name> in the Easy Setup definition file.
The processing will be interrupted.
Specify "@myhost" as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file.
A value other than "@myhost" is specified in <model-definition>-<host>-<agent-host>. Value=aa....aa
The value of <model-definition>-<host>-<agent-host> is not "@myhost". (value = aa....aa)
aa....aa: Value specified in <agent-host>
A value other than "@myhost" is specified in <model-definition>-<host>-<agent-host> in the Easy Setup definition file.
The processing will be interrupted.
Specify "@myhost" as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file.
The value of <model-definition>-<host>-<agent-port> is not equal to the port number (aa....aa) of the Administration Agent specified in the setup information file.
The value of <model-definition>-<host>-<agent-port> is not equal to aa....aa, the port number specified for the Administration Agent in the setup information file.
aa....aa: Port number specified for the Administration Agent in the setup information file
The value of <model-definition>-<host>-<agent-port> in the Easy Setup definition file is not equal to the port number of Administration Agent specified in the Easy Setup definition file.
The processing will be interrupted.
For the value of <model-definition>-<host>-<agent-port> in the Easy Setup definition file, specify port number of the Administration Agent that was specified when the setup information file was created.
-
KEOS28045-E (C/F)
No simple configuration definition file exists. (file name = aa....aa)
aa....aa: File name
- Description
-
The specified Easy Setup definition file does not exist.
The processing will be interrupted.
- Action
-
Revise the file name or path of the Easy Setup definition file.
-
KEOS28046-W (C/F)
A warning-level problem occurred during command execution. (command = aa....aa, details = :bb....bb)
aa....aa: Command name
bb....bb: Detailed message
- Description
-
A warning-level problem occurred in the command executed by the Setup Wizard.
The processing continues.
-
KEOS28047-I (C/F)
The simple configuration definition file was correctly exported.
- Description
-
The Easy Setup definition file was exported correctly.
-
KEOS28048-I (F)
The export of the simple configuration definition file has started.
- Description
-
The export of the Easy Setup definition file has started.
-
KEOS28049-I (F)
The export of the simple configuration definition file has ended. (file name = aa....aa)
aa....aa: File name
- Description
-
The export of the Easy Setup definition file has ended.
-
KEOS28050-E (C/F)
The simple configuration definition file cannot be exported.
- Description
-
The Easy Setup definition file cannot be exported.
The processing will be interrupted.
- Action
-
See the message displayed after this message, remove the cause of error, and then re-execute the export process.
-
KEOS28051-E (C/F)
A change that cannot be exported exists. (details = aa....aa)
aa....aa: Details
- Description
-
A change in the system that cannot be exported exists in the Setup Wizard.
The processing will be interrupted.
- Action
-
See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.
Table 13‒6: List of detailed information in KEOS28051-E Details
Description
Action
A valid Web system does not exist.
No valid Web system exists.
A valid Web system does not exist.
The processing will be interrupted.
Contact maintenance personnel.
Multiple Web systems are defined.
Multiple Web systems are defined.
Multiple Web systems are defined.
The processing will be interrupted.
Delete the added Web system. Alternatively, delete the logical server that is added using the management portal.
A load balancer is defined.
A load balancer is defined.
A load balancer is defined.
The processing will be interrupted.
Delete the added load balancer definition.
Multiple tiers are defined.
Multiple tiers are defined.
Multiple tiers are defined.
The processing will be interrupted.
Delete the added tier definition.
A tier other than "combined-tier" or "j2ee-tier" is defined. Tier type=aa....aa
A tier other than "combined-tier" or "j2ee-tier" is defined. (tier type = aa....aa)
aa....aa: Tier type
A tier other than "combined-tier" or "j2ee-tier" is defined.
The processing will be interrupted.
Change the tier type to "combined-tier" or "j2ee-tier".
Multiple J2EE servers are defined.
Multiple J2EE servers are defined.
Multiple J2EE servers are defined.
The processing will be interrupted.
Delete the added J2EE server.
Multiple units are defined.
Multiple units are defined.
Multiple units are defined.
The processing will be interrupted.
Delete the added units.
A logical server is added using a method other than the Setup Wizard.
A logical server has been added using a method other than the Setup Wizard.
A logical server is added using a method other than the Setup Wizard.
The processing will be interrupted.
Delete the added logical server.
Multiple hosts are defined.
Multiple hosts are defined.
Multiple hosts are defined.
The processing will be interrupted.
Delete the definition of added hosts.
A host other than a local host is defined. Host name= aa....aa
A host other than a local host is defined. (host name = aa....aa)
aa....aa: Host name
A host other than a local host is defined.
The processing will be interrupted.
Change the host definition to local host.
A host other than a local host is defined for the Administration Agent host. Host name= aa....aa
An Administration Agent host other than a local host is defined. (host name = aa....aa)
aa....aa: Host name
A host other than a local host is defined for the Administration Agent host.
The processing will be interrupted.
Change the host definition to the local host.
The port number of the Administration Agent is changed. Value=aa....aa
The port number of the Administration Agent has been changed. (value = aa....aa)
aa....aa: Port number of Administration Agent
The port number of the Administration Agent is changed.
The processing will be interrupted.
Change the port number of the Administration Agent to the value specified when the setup information file was created.
-
KEOS28052-E (C/F)
The simple configuration definition file cannot be exported because the management user ID or password has been changed.
- Description
-
The management user ID or password is changed, and therefore, the Easy Setup definition file cannot be exported.
The processing will be interrupted.
- Action
-
Change the management user ID or password to the one specified during the set up by the Setup Wizard, and then re-execute the export process.
-
KEOS28053-E (C/F)
An error occurred during connection to the Management Server. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred when connecting to the Management Server, and therefore, the Easy Setup definition file cannot be exported.
The processing will be interrupted.
- Action
-
Confirm that the Management Server is running. Also check whether the HTTP port number connected to the Management Server was changed after executing setup using the Setup Wizard.
-
KEOS28054-E (C/F)
The export cannot be executed because the environment was not set up using the Setup Wizard
- Description
-
Export cannot be executed in an environment that was not set up using the Setup Wizard.
The processing will be interrupted.
- Action
-
Export and system replication cannot be executed using the Setup Wizard in an environment that is already set. Execute export and system migration using a method that supports the setup environment.
-
KEOS28055-W (C)
The specified value of property (aa....aa) is invalid. The default value (bb....bb) will be used. (file name = cc....cc)
aa....aa: Property name
bb....bb: Default value
cc....cc: File name
- Description
-
The specified property value is invalid. The processing continues using the default value.
- Action
-
Revise the settings.
-
KEOS28056-E (C)
An attempt to read the SetupWizard definition file has failed.(file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Detailed message
- Description
-
An attempt to read the Setup Wizard definition file has failed.
The processing will be interrupted.
- Action
-
The following messages are displayed in the details: See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.
-
Failed to open the configuration file.
Check that the Cosminexus-installation-directory/manager/setup/config/setup.cfg file exists and the user has read permission for the file.
-
The line of 64 kilobytes or more exists.
Check that lines of 64 kilobytes or more exist in the contents of the Setup Wizard definition file.
-
-
KEOS28057-E (C/F)
The port number is already in use by another process. (port number = aa....aa, duplicate item = bb....bb)
aa....aa: Port number
bb....bb: Duplicate item
- Description
-
Setup cannot start because the port number specified in the Setup Wizard is being used in another process.
The processing will be cancelled.
- Action
-
Change the port number specified in the Setup Wizard to a value that is not being used in another process or stop the process that is using the duplicated port number.
-
KEOS28058-I (C/F)
An environment cannot be removed because no environment has been set up by the Management Server.
- Description
-
Unsetup need not be executed because no environment has been set up by the Management Server.
-
KEOS28500-I (F)
Removal of the environment built by the Management Server is started.
- Description
-
The unset up of the environment set up by the Management Server will start.
-
KEOS28501-I (C/F)
Removal of the environment built by the Management Server was succeeded.
- Description
-
The environment set up by the Management Server was unset up successfully.
-
KEOS28502-E (C/F)
Removal of the environment built by the Management Server was failed.
- Description
-
An attempt to unset up the environment set up by the Management Server failed.
The processing will be cancelled.
- Action
-
Check the message output before this message.
Remove the cause of the error, and then re-execute the command.
-
KEOS28503-E (C)
Removal of the environment built by the Management Server is already executing.
- Description
-
The environment set up by the Management Server is being unset up.
The processing will be cancelled.
- Action
-
Re-execute the command after the unsetup processing terminates.
-
KEOS28504-I (F)
The Management Server has stopped.
- Description
-
The Management Server has stopped.
-
KEOS28505-E (C/F)
An attempt to stop the Management Server has failed.
- Description
-
An attempt to stop the Management Server failed.
The processing will be cancelled.
- Action
-
Check the Management Server log.
Remove the cause of the error, and then re-execute the command.
-
KEOS28506-I (F)
The Management Server has deleted.
- Description
-
The Management Server has been deleted.
-
KEOS28507-E (C/F)
An attempt to delete the Management Server has failed.
- Description
-
An attempt to delete the Management Server failed.
The processing will be cancelled.
- Action
-
If the mngautorun respawn command was used to specify auto-restart settings for the Management Server, the Management Server might have been restarted by the init program of the OS.
If the settings to auto-restart the Management Server are specified, cancel the auto-restart settings in the -d option of the mngautorun, restart the computer, and then re-execute the command.
If the settings to auto-restart the Management Server are not specified, see the Management Server log, remove the cause of the error, and then re-execute the command.
-
KEOS28508-I (F)
The Administration Agent has stopped.
- Description
-
The Administration Agent has stopped.
-
KEOS28509-E (C/F)
An attempt to stop the Administration Agent has failed.
- Description
-
An attempt to stop the Administration Agent failed.
The processing will be cancelled.
- Action
-
Check the Administration Agent log.
Remove the cause of the error, and then re-execute the command.
-
KEOS28510-E (C/F)
An internal error occurred. (detail = aa....aa)
aa....aa: Details
- Description
-
An internal error occurred in the unsetup functionality.
The processing will be cancelled.
- Action
-
Check the details.
Remove the cause of the error, and then re-execute the command.
-
KEOS28511-I (F)
aa....aa(bb....bb) was stopped.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server has stopped.
-
KEOS28512-E (C/F)
The stop of aa....aa(bb....bb) failed. (detail = cc....cc)
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to stop the logical server failed.
The processing will be cancelled.
- Action
-
Check the details.
Remove the cause of the error, and then re-execute the command.
-
KEOS28513-I (F)
aa....aa(bb....bb) was deleted.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server is deleted.
-
KEOS28514-E (C/F)
The delete of aa....aa(bb....bb) failed. (detail = cc....cc)
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to delete the logical server failed.
The processing will be cancelled.
- Action
-
Check the details.
Remove the cause of the error, and then re-execute the command.
-
KEOS28515-I (F)
The Component Container administrator was removed.
- Description
-
The Component Container administrator was removed.
-
KEOS28516-E (C/F)
Removal of the Component Container administrator failed. (detail = aa....aa)
aa....aa: Details
- Description
-
An attempt to remove the Component Container administrator failed.
The processing will be cancelled.
- Action
-
Check the details.
Remove the cause of the error, and then re-execute the command.
-
KEOS28517-E (C/F)
An attempt to write to the file failed. (file name = aa....aa, detail = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to write to the file failed.
The processing continues.
- Action
-
The possible causes are as follows:
-
The user does not the permission to access the write destination file and directory.
-
The disk space at the write destination has depleted.
-
The write destination directory does not exist.
Check the access permissions and the disk space for the output destination file and directory.
See the details, remove the cause of the error, and then re-execute the command.
-
-
KEOS28518-E (C/F)
An attempt to read the file failed. (file name = aa....aa, detail = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to read the file failed.
The processing will be cancelled.
- Action
-
Check the access permissions for the file and directory.
See the details, remove the cause of the error, and then re-execute the command.
-
KEOS28522-E (C/F)
An attempt to delete file failed. (file name = aa....aa)
aa....aa: File name
- Description
-
An attempt to delete the file failed.
The processing will be cancelled.
- Action
-
Check whether the file exists.
If the file does not exist, and then re-execute the command.
If the file exists, check the access permissions for the file and directory. Remove the cause of the error, and then re-execute the command.
-
KEOS28525-I (C)
Usage: mngunsetup [options]
options
-force: Executes without requesting confirmation for execution.
- Description
-
This message describes the usage method of the command.
-
KEOS28526-E (C/F)
An attempt to execute the command has failed. (command name = aa....aa, detail = bb....bb)
aa....aa: Command name
bb....bb: Details
- Description
-
An attempt to execute a command during unsetup failed.
The processing will be cancelled.
- Action
-
Check the details.
Remove the cause of the error, and then re-execute the mngunsetup command.
-
KEOS28527-I (F)
The automatic starting and automatic restarting settings for the Management Server and the Administration Agent were removed.
- Description
-
The auto-start and auto-restart settings for the Management Server and Administration Agent were cancelled.
-
KEOS28528-E (C/F)
Removal of the automatic starting and automatic restarting settings for the Management Server and the Administration Agent failed. (detail = aa....aa)
aa....aa: Details
- Description
-
An attempt to cancel the auto-start and auto-restart settings for the Management Server and Administration Agent failed.
The processing will be cancelled.
- Action
-
Check the details.
Remove the cause of the error, and then re-execute the command.
-
KEOS28529-I (F)
The CTM domain information has deleted.
- Description
-
The CTM domain information was deleted.
-
KEOS28530-E (C/F)
An attempt to delete the CTM domain information has failed. (detail = aa....aa)
aa....aa: Details
- Description
-
An attempt to delete the CTM domain information failed.
The processing will be cancelled.
- Action
-
Check the access permissions for the following file and directory:
- In Windows
-
Windows-directory\TPBrokerOTM.dat
- In Linux
-
/var/spool/TPBrokerOTM/TPBrokerTSC
- Other than above
-
/usr/spool/TPBrokerOTM/TPBrokerTSC
Remove the cause of the error, and then re-execute the command.
-
KEOS28532-E (C/F)
The built and status for the logical server cannot be acquired.
- Description
-
The setup and operation status of the logical server cannot be acquired.
The processing will be cancelled.
- Action
-
Check whether the following file exists:
Cosminexus-installation-directory/manager/spool/logicalserver.xml.bak
Take the following action based on whether the logicalserver.xml.bak file exists:
- If the logicalserver.xml.bak file exists
-
Rename the logicalserver.xml.bak file to logicalserver.xml, and then re-execute the command.
Note that even if unsetup is successful with this action, a stopped or undeleted logical server might exist and the rebuilding of the environment might fail. In such a case, stop the running logical server processes manually and then delete the real server.
- If the logicalserver.xml.bak does not exist
-
Stop the running logical server processes manually, delete the real server, and then re-execute the command.
-
KEOS28533-E (F)
An attempt to save the built and status for logical server failed. (file name = aa....aa)
aa....aa: File name
- Description
-
An attempt to save the setup and operation information for the logical server failed.
The processing will be cancelled.
- Action
-
Take action in the following order:
-
Check whether the disk drive on which the Administration Agent is installed has sufficient free space.
The disk might be full. If there is no free space, allocate sufficient free space.
-
Take one of the following actions based on the file name:
- If Cosminexus-installation-directory/manager/spool/logicalserver.xml is output in the file name
-
Take action in the following order:
-
Delete Cosminexus-installation-directory/manager/spool/logicalserver.xml.
-
Rename Cosminexus-installation-directory/manager/spool/logicalserver.xml.bak to Cosminexus-installation-directory/manager/spool/logicalserver.xml.
-
Re-execute the operations that were performed just before this message was displayed.
-
- If Cosminexus-installation-directory/manager/spool/logicalserver.xml.bak is output in the file name
-
Re-execute the operations that were performed just before this message was displayed.
-
-
KEOS28534-W (F)
The period of watching aa....aa(bb....bb) stopped was expired.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The monitoring time of the termination for the logical server is expired.
The process will be continued.
- Action
-
Set up the monitoring time of the termination for the logical server in conformity to the environment.
-
KEOS28535-W (F)
The period of watching aa....aa(bb....bb) force stopped was expired.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The monitoring time of the forced termination for the logical server is expired.
The process will be continued.
- Action
-
Set up the monitoring time of the forced termination for the logical server in conformity to the environment.
-
KEOS28536-I (F)
aa....aa(bb....bb) is stopping.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server will be stopped.
-
KEOS28537-I (F)
aa....aa(bb....bb) is stopping forcefully.
aa....aa: Logical server name
bb....bb: Logical server type
- Description
-
The logical server will be forcefully terminated.
-
KEOS28538-E (C/F)
The force stop of aa....aa(bb....bb) failed. (detail = cc....cc)
aa....aa: Logical server name
bb....bb: Logical server type
cc....cc: Details
- Description
-
An attempt to forcefully terminate the logical server has failed.
The process will be interrupted.
- Action
-
See the detail, remove the cause of the error, and then re-execute the command.
-
KEOS28700-I (C)
Usage: mngenvupdate
- Description
-
This message describes the usage method of the command.
-
KEOS28701-I (C/F)
The conversion of the Management Server is started.
- Description
-
The migration of the Management Server will start.
-
KEOS28702-I (C/F)
The conversion of the Management Server was successfully.
- Description
-
The migration of the Management Server was successful.
-
KEOS28703-E (C/F)
An attempt to convert the Management Server has failed.
- Description
-
An attempt to migrate the Management Server failed.
The processing will be cancelled.
- Action
-
Check the message output before this message.
Remove the cause of the error, and then re-execute the command.
-
KEOS28704-E (C/F)
An attempt to convert file failed. (file name = aa....aa, detail = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to migrate file failed.
The processing will be cancelled.
- Action
-
Make sure that the file to be migrated exists, or that the disk space at the migration destination has not depleted.
Check the details.
Remove the cause of the error, and then re-execute the command.
-
KEOS28705-W (C/F)
An attempt to delete file or directory has failed. (file name or directory name = aa....aa)
aa....aa: File name or directory name
- Description
-
An attempt to delete a file or directory failed.
The processing continues.
- Action
-
Check whether the user has the permission to delete the file or directory, and whether a running process is being used.
Remove the cause of the error, and then re-execute the command.
-
KEOS28706-E (C/F)
An internal error occurred. (detail = aa....aa)
aa....aa: Details
- Description
-
An internal error occurred.
The processing will be cancelled.
- Action
-
Check the details.
Remove the cause of the error, and then re-execute the command. If this action does not resolve the error, contact maintenance personnel.
-
KEOS28707-E (C/F)
An attempt to setup the Management Server has failed. (detail = aa....aa)
aa....aa: Detail
- Description
-
An attempt to set up Management Server has failed.
The process will be interrupted.
- Action
-
Check the detail.
Remove the cause of the error, and then re-execute the command. If this action does not resolve the error, contact maintenance personnel.
-
KEOS29001-E (C)
Usage:
aa....aa
aa....aa: Command usage
- Description
-
The command usage is incorrect. The processing will be interrupted.
- Action
-
Check the command usage, and then re-execute the command.
-
KEOS29002-E (C)
The host or user ID has not been specified in the common option.
- Description
-
The host or user ID has not been specified in the common option. The processing will be interrupted.
- Action
-
Check that the vmx.connect.host and vmx.connect.userid keys are set up in the client settings property file (vmxclient.properties).
-
KEOS29003-E (C)
The host name or port number is invalid. (details = aa....aa)
aa....aa: Details
- Description
-
The host name or the port number is invalid. The processing will be interrupted.
- Action
-
Check the specification method of the host name and the port number.
-
KEOS29004-E (C)
A communication error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
A communication error occurred. The processing will be interrupted.
- Action
-
Check that Management Server is running or check the values of the host name and the port number specified in the -m option of the common arguments. Also, confirm that the products at the connection source and the connection destination can be connected.
-
KEOS29005-E (C)
An exception occurred during creation of a temporary file. (details = aa....aa)
aa....aa: Details
- Description
-
An exception occurred during creation of a temporary file. The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS29006-I (F)
The command started. (command = aa....aa, process id = bb....bb, start time = cc....cc)
aa....aa: Command line
bb....bb: Process ID
cc....cc: Command start time
- Description
-
The command described in the message will start.
-
KEOS29007-I (F)
The command finished. (process id = aa....aa, start time = bb....bb, code = cc....cc)
aa....aa: Process ID
bb....bb: Command start time
cc....cc: End code
- Description
-
The command indicated in the process ID and the command start time will end.
-
KEOS29008-E (C)
The specified file does not exist. (file name = aa....aa)
aa....aa: File name
- Description
-
The specified file does not exist. The processing will be interrupted.
- Action
-
Check the arguments specified in the command.
-
KEOS29009-E (C)
The specified file is not a normal file. (file name = aa....aa)
aa....aa: File name
- Description
-
The specified file is not a normal file. The processing will be interrupted.
- Action
-
Check the specified file.
-
KEOS29010-E (C)
An exception occurred during creation of a temporary file. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to create a temporary file has failed. The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS29011-E (C)
An exception occurred while reading the file. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An exception occurred while reading the file. The processing will be interrupted.
- Action
-
Check the file access permission. If the file access permission is correct and the exception is not recovered even after re-executing the command, contact maintenance personnel.
-
KEOS29012-E (C)
An attempt to write to the file failed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to write to the file failed. The processing continues.
- Action
-
Check the file permissions, and then restart the virtual server manager.
-
KEOS29051-E (W/F)
No administrator user account has been configured.
- Description
-
No administrator user account has been registered in the Cosminexus Management Server configuration file. The processing will be interrupted.
- Action
-
Use the mngsvrctl setup command to set up the administrator user account.
-
KEOS29052-E (W/F)
The administrator user ID or password is incorrect.
- Description
-
The administrator user ID or password for logging into the Cosminexus Virtual Server Manager is different. The specified request is ignored, and the Login Screen anchor will be displayed.
- Action
-
Set up the correct administration user ID or password into the login screen.
If you click the Login Screen anchor, you will return to the login screen.
-
KEOS29053-E (W/F)
The administrator user ID is logged out either because it is not logged in, or the session has timed out.
- Description
-
The user is currently not logged into Cosminexus Virtual Server Manager. The specified request is ignored, and the Login Screen anchor will be displayed.
- Action
-
Log in from the login screen.
If you click the Login Screen anchor, you will return to the login screen.
-
KEOS29054-I (W/F)
The administrator user ID logged out normally.
- Description
-
The administrator user ID logged out normally from the Cosminexus Virtual Server Manager.
-
KEOS29055-Q (W)
All virtual servers on management unit aa....aa will be started. Are you sure?
aa....aa: Management unit name
- Description
-
Confirm the batch start of management unit. The OK and Cancel buttons is displayed. If you click the OK button, the processing continues. If you click the Cancel button, the processing will be interrupted.
- Action
-
If you want to batch start the management unit, click the OK button.
-
KEOS29056-I (W/F)
The start for management unit aa....aa completed normally.
aa....aa: Management unit name
- Description
-
The batch start processing of the management unit completed normally.
- Action
-
Check the virtual server manager log for the execution result of batch start.
-
KEOS29057-E (W/F)
The start for management unit aa....aa failed.
aa....aa: Management unit name
- Description
-
An attempt to batch start the management unit has failed. The batch start processing is interrupted, and the Return anchor is displayed.
- Action
-
Check the virtual server manager log, remove the cause of the error, and then re-execute the process.
-
KEOS29058-Q (W)
All virtual servers on management unit aa....aa will be stopped. Are you sure?
aa....aa: Management unit name
- Description
-
The batch stop of the management unit will be confirmed. The OK and Cancel buttons will be displayed. If you click the OK button, the processing continues. If you click the Cancel button, the processing will be interrupted.
- Action
-
If you want to batch stop the management unit, click the OK button.
-
KEOS29059-I (W/F)
The stop for management unit aa....aa completed normally.
aa....aa: Management unit name
- Description
-
The batch stop processing of the management unit completed normally.
- Action
-
Check the virtual server manager log for the execution result of batch stop.
-
KEOS29060-E (W/F)
The stop for management unit aa....aa failed.
aa....aa: Management unit name
- Description
-
An attempt to batch stop the management unit has failed. The batch stop processing is interrupted, and then the Return anchor is displayed.
- Action
-
Check the virtual server manager log, remove the cause of the error, and then re-execute the process.
-
KEOS29101-I (W/F)
The virtual server manager started.
- Description
-
The virtual server manager is started.
-
KEOS29102-E (W/F)
An attempt to start the virtual server manager failed.
- Description
-
An attempt to start the virtual server manager has failed. The processing will be interrupted.
- Action
-
Take action according to the message output just before this message.
-
KEOS29103-I (W/F)
The virtual server manager finished.
- Description
-
The virtual server manager is finished.
-
KEOS29104-E (W/F)
A required property was not specified. (property = aa....aa, file name = bb....bb)
aa....aa: Property key
bb....bb: File name
- Description
-
A required property was not specified. The processing continues.
- Action
-
Check the contents of the file, and then restart the virtual server manager.
-
KEOS29105-E (W/F)
An invalid value was specified for the property. (property = aa....aa, invalid value = bb....bb, file name = cc....cc)
aa....aa: Property key
bb....bb: Value specified for the property (invalid value)
cc....cc: File name
- Description
-
An invalid value was specified for the property. The processing continues.
- Action
-
Check the contents of the file, and then restart the virtual server manager.
-
KEOS29106-W (W/F)
An invalid value was specified for the property. The default value will be used. (property = aa....aa, invalid value = bb....bb, default value = cc....cc, file name = dd....dd)
aa....aa: Property key
bb....bb: Value specified for the property (invalid value)
cc....cc: Default property value
dd....dd: File name
- Description
-
An invalid value was specified for the property, so the default value is used and the processing continues.
- Action
-
Check the contents of the file, and restart the virtual server manager as and when required.
-
KEOS29107-I (W/F)
The directory was created. (directory type = aa....aa, directory name = bb....bb).
aa....aa: Directory type
bb....bb: Directory name
- Description
-
The directory was created.
-
KEOS29108-E (W/F)
An attempt to create a directory failed. (directory type = aa....aa, directory name = bb....bb)
aa....aa: Directory type
bb....bb: Directory name
- Description
-
An attempt to create the directory has failed. The processing continues.
- Action
-
Check the directory permissions, and restart the virtual server manager as and when required.
-
KEOS29109-E (W/F)
An attempt to connect to VMware vCenter Server failed.
- Description
-
An attempt to connect to VMware vCenter Server has failed. The processing continues.
- Action
-
Check the settings for connecting to VMware vCenter Server in vmx.properties, and then restart the virtual server manager.
-
KEOS29110-E (W/F)
An attempt to read the file failed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to read the file has failed. The processing continues.
- Action
-
Check the file permissions, and then restart the virtual server manager.
-
KEOS29111-E (C/W/F)
An attempt to write to the file failed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to write to the file has failed. The processing continues.
- Action
-
Check the file permissions and the empty disk space, and then perform the following process for every trigger:
-
If the message occurs when the virtual server manager starts, restart the virtual server manager.
-
If the message occurs when the virtual server manager commands are executed, take the action specified for the message that is output just before this message.
-
-
KEOS29112-I (W/F)
The sub-process (Agent for VMware vCenter Server) will now start.
- Description
-
The sub-process (Agent for VMware vCenter Server) will start.
-
KEOS29113-E (W/F)
An attempt to start the sub-process (Agent for VMware vCenter Server) failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to start the sub-process (Agent for VMware vCenter Server) has failed. The processing will be interrupted.
- Action
-
Check the details, and then restart the virtual server manager. If timeout has occurred, revise the value of vmx.vcenterserver.agent.start.timeout in the virtual server manager property file.
-
KEOS29114-I (W/F)
The sub-process (Agent for VMware vCenter Server) started.
- Description
-
The sub-process (Agent for VMware vCenter Server) has started.
-
KEOS29116-I (W/F)
Operation of the virtual machine will now start. (operation type = aa....aa, operation target = bb....bb)
aa....aa: Operation type (reproduce, start, stop, suspend, shutdown, delete, confirm start, and confirm stop)
bb....bb: Operation target (reproduction source virtual machine, reproduction destination virtual machine, reproduction destination host, and virtual machine)
- Description
-
The virtual machine operations will be executed.
-
KEOS29117-I (W/F)
Operation of the virtual machine successfully finished. (operation type = aa....aa, operation target = bb....bb)
aa....aa: Operation type (reproduce, start, stop, suspend, shutdown, delete, confirm start, and confirm stop)
bb....bb: Operation target (reproduction source virtual machine, reproduction destination virtual machine, reproduction destination host, and virtual machine)
- Description
-
The virtual machine operations were successful.
-
KEOS29118-E (W/F)
Operation of the virtual machine failed. (operation type = aa....aa, operation target = bb....bb)
aa....aa: Operation type (reproduce, start, stop, suspend, shutdown, delete, confirm start, and confirm stop)
bb....bb: Operation target (reproduction source virtual machine, reproduction destination virtual machine, reproduction destination host, and virtual machine)
- Description
-
An attempt to execute the virtual machine operations has failed. The processing continues.
- Action
-
Take action according to the error messages output before and after this message.
-
KEOS29119-E (W/F)
The virtual server manager will now end because the sub-process (Agent for VMware vCenter Server) has stopped abnormally.
- Description
-
The virtual server manager will stop because the sub-process (Agent for VMware vCenter Server) terminated abnormally. The processing will be interrupted.
- Action
-
Restart the virtual server manager.
-
KEOS29131-E (C/W/F)
A timeout occurred in communicating with the VMware vCenter Server communication process. (details = aa....aa)
aa....aa: Details
- Description
-
A timeout occurred during communication with the process for VMware vCenter Server communication. The processing will be interrupted.
- Action
-
The processing in VMware vCenter Server did not finish within the specified time. Check the settings, and then re-execute the processing.
-
KEOS29132-E (C/W/F)
An attempt to communicate with the VMware vCenter Server communication process failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to communicate with the process for VMware vCenter Server communication has failed. The processing will be interrupted.
- Action
-
Restart the virtual server manager.
-
KEOS29133-E (C/W/F)
An attempt to communicate with VMware vCenter Server failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to communicate with VMware vCenter Server has failed. The processing will be interrupted.
- Action
-
Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29134-E (C/W/F)
An attempt to log in to VMware vCenter Server failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to login to VMware vCenter Server has failed. The processing will be interrupted.
- Action
-
Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29135-E (C/W/F)
An operation in VMware vCenter Server failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to execute operations in VMware vCenter Server has failed. The processing will be interrupted.
- Action
-
Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29136-E (C/W/F)
An operation in VMware vCenter Server failed because a file operation in a virtual server failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to execute operations in VMware vCenter Server failed because the virtual server file operations failed. The processing will be interrupted.
- Action
-
Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29137-E (C/W/F)
An operation target does not exist in VMware vCenter Server. (details = aa....aa)
aa....aa: Details
- Description
-
The operation target in VMware vCenter Server does not exist. The processing will be interrupted.
- Action
-
Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29138-E (C/W/F)
An operation in VMware vCenter Server failed because resources are insufficient. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to execute operations in VMware vCenter Server has failed because of insufficient resources. The processing will be interrupted.
- Action
-
Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29139-E (C/W/F)
An operation in VMware vCenter Server failed because there is a problem in the current state of the system. (details = aa....aa)
aa....aa Details
- Description
-
An attempt to execute operations in VMware vCenter Server has failed because of an incorrect status. The processing will be interrupted.
- Action
-
Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29140-E (C/W/F)
An operation in VMware vCenter Server failed because another operation is being performed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to execute operations in VMware vCenter Server has failed because another operation is running. The processing will be interrupted.
- Action
-
Check status of the VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29141-E (C/W/F)
An operation in VMware vCenter Server failed because there is a configuration problem. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to execute operations in VMware vCenter Server has failed because of incorrect settings. The processing will be interrupted.
- Action
-
Check status of the VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29142-E (C/W/F)
An operation in VMware vCenter Server failed because there is a datastore problem. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to execute operations in VMware vCenter Server has failed because of incorrect data store. The processing will be interrupted.
- Action
-
Check status of the VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29143-E (C/W/F)
An attempt to migrate the virtual server failed. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to migrate the virtual server has failed. The processing will be interrupted.
- Action
-
Check status of the VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.
-
KEOS29144-E (C/W/F)
It is required that the number of network adaptors is one.
- Description
-
The number of network adapters must be one. The processing will be interrupted.
- Action
-
Check the virtual machine settings, and then re-execute the processing.
-
KEOS29145-E (C/W/F)
There are no network adapters that attached network label aa....aa.
aa....aa: Network label name
- Description
-
A network adapter to which the specified network label is allocated does not exist. The processing will be interrupted.
- Action
-
Check the virtual machine settings, and then re-execute the processing.
-
KEOS29146-E (C/W/F)
There are more than one network adapters that attached network label aa....aa.
aa....aa: Network label name
- Description
-
There are two or more network adapters to which the specified network label is allocated. The processing will be interrupted.
- Action
-
Check the virtual machine settings, and then re-execute the processing.
-
KEOS29151-I (W/F)
Processing of the virtual server manager command will now start. (client = aa....aa)
aa....aa: Connection source host
- Description
-
The processing of the virtual server manager commands will start.
-
KEOS29152-I (W/F)
Processing of the virtual server manager command ended.
- Description
-
The processing of the virtual server manager commands will end.
-
KEOS29153-E (C/W/F)
This command is not supported. (details = aa....aa)
aa....aa: Details
- Description
-
This command is not supported. The processing will be interrupted.
- Action
-
Check the product version installed on the management machine and the product version installed on the machine executing the command.
-
KEOS29154-E (C/W/F)
An internal error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
An internal error occurred. The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS29155-I (W/F)
Processing of aa....aa was received.
aa....aa: Command name
- Description
-
A command processing was received.
-
KEOS29156-I (W/F)
Processing of the aa....aa command will now start.
aa....aa: Command name
- Description
-
The command processing will start.
-
KEOS29157-I (W/F)
Processing of the aa....aa command ended.
aa....aa: Command name
- Description
-
The command processing ended.
-
KEOS29159-E (C)
A communication error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
A communication failure occurred. The processing will be interrupted.
- Action
-
If the failure is not recovered even after re-executing the command, contact maintenance personnel.
-
KEOS29161-E (C/W/F)
This operation cannot be executed because other operations are executing.
- Description
-
This operation cannot be executed because another operation is running. The processing will be interrupted.
- Action
-
Wait for some time, and then execute the operation again.
-
KEOS29162-E (C)
The administrator user ID or password is invalid.
- Description
-
The management user ID or password is invalid. The processing will be interrupted.
- Action
-
Check the specified management user ID and the password.
-
KEOS29163-E (C/W)
The connection failed because either the virtual server manager is not enabled, or startup of the virtual server manager is in progress.
- Description
-
The connection cannot be established because the virtual server manager is not enabled or the virtual server manager is running. The processing will be interrupted.
- Action
-
Specify the settings to enable the virtual server manager, and then restart the virtual server manager. If the settings for enabling the virtual server manager are already specified, wait for some time, and then re-execute the operation.
-
KEOS29164-E (C/W/F)
The file cannot be accessed because it is not a normal file. (file name = aa....aa)
aa....aa: File name
- Description
-
The specified file is not a regular file, so the file cannot be accessed. The processing will be interrupted.
- Action
-
Specify a regular file, and then re-execute the operation.
-
KEOS29165-E (C/W/F)
An attempt to read the file failed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to read the file has failed. The processing will be interrupted.
- Action
-
Check whether the file exists or whether you have the permission to access the file.
-
KEOS29167-E (C/W/F)
A connection to VMware vCenter Server could not be established. (details = aa....aa)
aa....aa: Details
- Description
-
Connection could not be established with VMware vCenter Server. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the operation.
-
KEOS29168-E (C/W/F)
Information from VMware vCenter Server could not be acquired. (details = aa....aa)
aa....aa: Details
- Description
-
Information could not be acquired from VMware vCenter Server. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the operation.
-
KEOS29169-E (C/W/F)
An exception occurred during creation of a temporary file. (details = aa....aa)
aa....aa: Details
- Description
-
A failure occurred while creating the temporary file. The processing will be interrupted.
- Action
-
Contact maintenance personnel.
-
KEOS29170-E (C/W/F)
A virtual server does not exist for the management unit. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The virtual server does not exist in the management unit. The processing will be interrupted.
- Action
-
The virtual server does not exist in the specified management unit. Use the vmx_deploy_unit command to deploy, and then re-execute the operation.
-
KEOS29172-E (C/W/F)
Creation of the management unit is not complete. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
Creation of the management unit is not complete. The processing will be interrupted.
- Action
-
Create the management unit, and then re-execute the operation.
-
KEOS29173-E (W/F)
An error response was returned from the HTTP server. (details = aa....aa)
aa....aa: Response code
- Description
-
The HTTP server returned an error response. The processing will be interrupted.
- Action
-
See the details, and then take action according to the response code of the server communication agent.
-
KEOS29174-E (W/F)
An error occurred during file transfer. (details = aa....aa)
aa....aa: Error information
- Description
-
An error occurred during file transfer. The processing will be interrupted.
- Action
-
Take action according to the details.
- FileNotFoundException
-
Revise the transfer destination directory specified in the virtual server manager.
- IOException
-
Check the file in which the error occurred.
- SocketIOException
-
Revise the network environment or settings.
-
KEOS29175-E (W/F)
An error occurred during processing of the server communication agent. (details = aa....aa)
aa....aa: Error information
- Description
-
An error occurred in the processing of the server communication agent. The processing will be interrupted.
- Action
-
Take action according to the details.
- DuplicateFileNameException
-
Revise the file or the directory to be transmitted that is specified in the server communication agent.
- FileNotFoundException
-
Revise the file or the directory to be transmitted that is specified in the server communication agent.
- IOException
-
Check the file in which the error occurred.
- SocketIOException
-
Revise the network environment or settings.
-
KEOS29176-E (W/F)
The version of the server communication agent is inconsistent with the version of the virtual server manager.
- Description
-
The version of the server communication agent is inconsistent with the version of the virtual server manager. The processing will be interrupted.
- Action
-
Use a Cosminexus version supported by the virtual server manager for Application Servers running on the virtual application server.
-
KEOS29177-E (W/F)
A timeout occurred during command execution. (details = aa....aa)
aa....aa: Process ID
- Description
-
A timeout occurred during the execution of the command. The processing will be interrupted.
- Action
-
Check the process status output to details. If necessary, terminate the process forcibly.
-
KEOS29179-E (C/W/F)
The specified management unit does not exist. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The specified management unit does not exist. The processing will be interrupted.
- Action
-
Specify an existing management unit name.
-
KEOS29180-E (C/W/F)
The specified management unit already exists. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The specified management unit already exists. The processing will be interrupted.
- Action
-
Check the management unit name, and then re-execute the operation.
-
KEOS29181-E (C/W/F)
Information for the management target host is not set.
- Description
-
The information about the administered machine is not set up. The processing will be interrupted.
- Action
-
Use the vmx_set_machine_info command to set up the information about the administered machine.
-
KEOS29182-E (W/F)
An error occurred during file transfer. (details = aa....aa)
aa....aa: Error information
- Description
-
An error occurred in the file transmit processing.
The processing continues for the vmx_deploy_unit, vmx_start_unit, and vmx_stop_unit commands.
The processing will be cancelled for other commands.
- Action
-
Take action according to the details.
- DuplicateFileNameException
-
Revise the file or the directory to be transmitted that is specified in the virtual server manager.
- FileNotFoundException
-
Revise the file or the directory to be transmitted that is specified in the virtual server manager.
- IOException
-
Check the file in which the error occurred.
- SocketIOException
-
Revise the network environment or settings.
-
KEOS29183-E (W/F)
An error occurred during processing of the server communication agent. (details = aa....aa)
aa....aa: Error information
- Description
-
An error occurred in the processing of the server communication agent.
The processing continues for the vmx_deploy_unit, vmx_start_unit, and vmx_stop_unit commands.
The processing will be cancelled for other commands.
- Action
-
Take action according to the details.
- FileNotFoundException
-
Revise the transmission destination directory specified in the server communication agent.
- IOException
-
Check the file in which the error occurred.
- SocketIOException
-
Revise the network environment or settings.
-
KEOS29184-E (W/F)
An error occurred during processing of the server communication agent. (details = aa....aa)
aa....aa Details
- Description
-
An error occurred in the processing of the server communication agent.
The processing continues for the vmx_deploy_unit, vmx_start_unit, and vmx_stop_unit commands.
The processing will be cancelled for other commands.
- Action
-
Take action according to the details.
- CommandInterruptedException
-
The processing was interrupted while waiting for the command to terminate, so check the status of the server communication agent and the status of the running process. If necessary, terminate the process forcibly.
- IOException
-
Check the file in which the error occurred.
- SocketIOException
-
Revise the network environment or settings.
-
KEOS29201-W (C/W/F)
An attempt to output a snapshot log failed. (virtual server name = aa....aa, details = bb....bb)
aa....aa: Virtual server name
bb....bb: Details
- Description
-
An attempt to output the snapshotlog has failed. The processing continues.
- Action
-
Check whether snapshotlog can be executed on the virtual server.
-
KEOS29202-W (C/W/F)
An attempt to collect the event log failed. (virtual server name = aa....aa, details = bb....bb)
aa....aa: Virtual server name
bb....bb: Details
- Description
-
An attempt to collect the event log has failed. The processing continues.
- Action
-
Check whether the event log can be collected on the virtual server.
-
KEOS29203-W (C/W/F)
An attempt to collect the system log failed. (virtual server name = aa....aa, details = bb....bb)
aa....aa: Virtual server name
bb....bb: Details
- Description
-
An attempt to collect the system log has failed. The processing continues.
- Action
-
Check whether the system log can be collected on the virtual server.
-
KEOS29204-E (C/W/F)
An attempt to create a ZIP file failed. (virtual server name = aa....aa, details = bb....bb)
aa....aa: Virtual server name
bb....bb: Details
- Description
-
An attempt to create the Zip file has failed. The processing will be interrupted.
- Action
-
Check whether you have the file write permission.
-
KEOS29213-E (C/W/F)
An attempt to confirm whether the virtual server is working has failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to check the virtual server operations has failed. Virtual server failure monitoring will be interrupted.
- Action
-
See the user action for the error message output just before this message. After finishing the investigation, delete the virtual server from VMware vCenter Server, and then execute the vmx_deploy_unit command as and when required.
-
KEOS29214-W (C/W/F)
An attempt to stop a virtual server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Administered machine name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to stop the virtual server has failed. The processing will be interrupted.
- Action
-
Check the network settings or check whether the virtual server is running normally. If the network settings are incorrect, specify the correct settings. If the virtual server has stopped, use the hypervisor functionality to start and check the failed virtual server. Remove the cause of the error, update the management unit, and then apply the settings to the virtual server. After this, start the virtual server.
-
KEOS29221-E (C/W/F)
An invalid entry was found. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
Contents that cannot be specified in the Easy Setup definition file exist. The processing will be interrupted.
- Action
-
Remove the cause of the error based on the details described in the following table, and then re-execute the vmx_create_unit command.
Table 13‒7: List of error details described in KEOS29221-E Details
Description
Action
An unusable XML namespace is specified for the xmlns attribute of <model-definition>. (value = aa....aa)
An XML namespace that cannot be used is specified in <model-definition> of the Easy Setup definition file. The processing will be interrupted.
Change the <model-definition> definition in the Easy Setup definition file. The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.
An XML namespace is not specified for the xmlns attribute of <model-definition>.
XML namespace is not specified in the xmlns attribute of <model-definition> in the Easy Setup definition file. The processing will be interrupted.
Change the <model-definition> definition in the Easy Setup definition file. The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.
No definition of <model-definition>-<web-system> exists.
<model-definition>-<web-system> is not defined in the Easy Setup definition file. The processing will be interrupted.
Add the Web system definition (<model-definition>-<web-system>) in the Easy Setup definition file.
Multiple definitions of <model-definition>-<web-system> exist.
Multiple <model-definition>-<web-system> are defined in the Easy Setup definition file. The processing will be interrupted.
Unify the <model-definition>-<web-system> definitions in the Easy Setup definition file.
Multiple definitions of <web-system>-<tier> exist.
Multiple <web-system>-<tier> are defined in the Easy Setup definition file. The processing will be interrupted.
Unify the <web-system>-<tier> definitions in the Easy Setup definition file.
The value of <tier>-<tier-type> is not "combined-tier". (value = aa....aa)
A value other than combined-tier is specified as the value of <tier>-<tier-type> in the Easy Setup definition file. The processing will be interrupted.
Specify combined-tier as the value of <tier>-<tier-type> in the Easy Setup definition file.
The value of <tier>-<j2ee-server-count> is not "1". (value = aa....aa)
A value other than 1 is specified as the value of <tier>-<j2ee-server-count> in the Easy Setup definition file. The processing will be interrupted.
Delete the <tier>-<j2ee-server-count> tag specified in the Easy Setup definition file or specify 1 as the value of <tier>-<j2ee-server-count>.
Multiple definitions of <web-system>-<unit> exist.
Multiple <web-system>-<unit> are defined in the Easy Setup definition file. The processing will be interrupted.
Unify the <web-system>-<unit> definitions in the Easy Setup definition file.
No definition of <logical-server-name> exists that corresponds to the item whose <unit>-<allocated-host>-<define-server>-<logical-server-type> value is aa....aa.
<logical-server-name> is not defined for the items that have aa....aa as the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file. The processing will be interrupted.
Add the following <logical-server-name> tag, and define the logical server name in the definition for the logical server with the logical server type aa....aa in the Easy Setup definition file:
<unit>
<allocated-host>
<define-server>
<logical-server-type>aa....aa</logical-server-type>
<logical-server-name>logical-server-name</logical-server-name>
The value of <unit>-<allocated-host>-<define-server>-<logical-server-type> is not "web-server", "j2ee-server", or "performance-tracer". (value = aa....aa)
A value other than web-server, j2ee-server, or performance-tracer is specified as the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file. The processing will be interrupted.
Specify web-server, j2ee-server, or performance-tracer as the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file.
Multiple definitions of <model-definition>-<host> exist.
Multiple <model-definition>-<host> are defined in the Easy Setup definition file. The processing will be interrupted.
Unify the <model-definition>-<host> definitions in the Easy Setup definition file.
The value of <unit>-<allocated-host>-<host-ref> is not "localhost". (value = aa....aa)
A value other than localhost is specified as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file. The processing will be interrupted.
Specify localhost as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.
The value of <model-definition>-<host>-<host-name> is not "localhost". (value = aa....aa)
A value other than localhost is specified as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file. The processing will be interrupted.
Specify localhost as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file.
The value of <model-definition>-<host>-<agent-host> is not "localhost". (value = aa....aa)
A value other than localhost is specified as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file. The processing will be interrupted.
Specify localhost as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file.
-
KEOS29222-E (C/W/F)
A syntax error was found in the simple configuration definition file. (line number = aa....aa, column number = bb....bb, details = cc....cc)
aa....aa: Line number
bb....bb: Column number
cc....cc: Details
- Description
-
There is a syntax error in the Easy Setup definition file. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the vmx_create_unit command.
-
KEOS29224-E (C/W/F)
An invalid value was specified for the file. (parameter name = aa....aa, value = bb....bb, file name = cc....cc)
aa....aa: Parameter name
bb....bb: Value
cc....cc: File name
- Description
-
An invalid value was specified in the file. The processing will be interrupted.
- Action
-
Check the contents specified in the file, and then re-execute the command.
-
KEOS29231-E (C/W/F)
An XML namespace is not specified for the xmlns attribute of <machine-info>. (file name = aa....aa)
aa....aa: File path
- Description
-
The XML namespace is not specified in the xmlns attribute of the <machine-info> tag in the administered machine information file. The processing will be interrupted.
- Action
-
Change the <machine-info> definition in the administered machine information file. The XML namespace for the administered machine information file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/MachineInfo-1.0.
-
KEOS29232-E (C/W/F)
An unusable XML namespace is specified for the xmlns attribute of <machine-info>. (value = aa....aa, file name = bb....bb)
aa....aa: Value specified in the xmlns attribute of the <machine-info> tag
bb....bb: File path
- Description
-
An unavailable XML namespace is specified in the <machine-info> tag of the administered machine information file. The processing will be interrupted.
- Action
-
Change the <machine-info> definition in the administered machine information file. The XML namespace for the administered machine information file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/MachineInfo-1.0.
-
KEOS29233-E (C/W/F)
An invalid value is specified. (tag name = aa....aa, invalid value = bb....bb, file name = cc....cc)
aa....aa: Tag name
bb....bb: Value specified for the tag (Invalid value)
cc....cc: File name
- Description
-
The specified value is invalid. The processing will be interrupted.
- Action
-
Check the file contents, and then re-execute the command.
-
KEOS29234-E (C/W/F)
A syntax error was found in the information file for the management target host. (line number = aa....aa, column number = bb....bb, details = cc....cc)
aa....aa: Line number
bb....bb: Column number
cc....cc: Details
- Description
-
There is a syntax error in the administered machine information file. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the operation.
-
KEOS29301-E (C/W/F)
An error occurred during analysis of the XML file. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An error occurred while parsing the xml file. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the operation.
-
KEOS29302-E (C/W/F)
The specified management target host does not exist. (management target host name = aa....aa)
aa....aa: Management target machine name
- Description
-
The specified management target machine does not exist. The processing will be interrupted.
- Action
-
Specify an existing management target machine name, and then re-execute the operation.
-
KEOS29303-E (C/W/F)
The management target host specified for deletion contains a virtual server that is working. (management target host name = aa....aa, virtual server name = bb....bb)
aa....aa: Management target machine name
bb....bb: Virtual server name
- Description
-
A virtual server is running in the management target machine you want to delete. The processing will be interrupted.
- Action
-
Stop all the virtual servers (including the failed virtual servers) running on the management target machine.
-
KEOS29304-E (C/W/F)
An attempt to delete a virtual server failed. (virtual server name = aa....aa, details = bb....bb)
aa....aa: Virtual server name
bb....bb: Details
- Description
-
An attempt to delete the virtual server has failed. The processing continues and another virtual server will be deleted.
- Action
-
See the details, remove the cause of the error, and then delete the virtual server manually.
-
KEOS29305-I (C/W/F)
Setting the information for the management target host succeeded.
- Description
-
The management target machine information was set up successfully.
-
KEOS29306-E (C/W/F)
The management target host specified for deletion is being used by a management unit. (management target host name = aa....aa, management unit name = bb....bb)
aa....aa: Management target machine name
bb....bb: Management unit name
- Description
-
The management target machine you tried to delete is being used in a management unit. The processing will be interrupted.
- Action
-
From the management unit operation rule, delete the management target machine you want to delete, and then re-execute the command.
-
KEOS29311-E (C/W/F)
The information file for the management target host cannot be acquired.
- Description
-
The administered machine information file cannot be acquired. The processing will be interrupted.
- Action
-
Use the vmx_set_machine_info command to execute the processing in an environment where the administered machine information is set up.
-
KEOS29312-I (C/W/F)
Acquisition of the management target host information succeeded.
- Description
-
The management target machine information was acquired successfully.
-
KEOS29321-E (C/W/F)
An attempt to copy a master virtual server failed. (server image store host name = aa....aa, details = bb....bb)
aa....aa: Virtual server image management host name at the copy destination
bb....bb: Details
- Description
-
An attempt to copy the master virtual server has failed. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the operation.
-
KEOS29322-E (C/W/F)
An attempt to save the file failed. (file name = aa....aa)
aa....aa: File name
- Description
-
An attempt to save the file has failed. The processing will be interrupted.
- Action
-
Confirm that there is sufficient disk space on the virtual server manager host, and then re-execute the operation.
-
KEOS29323-E (C/W/F)
An attempt to copy a virtual application server failed. (server image store host name = aa....aa, details = bb....bb)
aa....aa: Virtual server image management host name at the copy destination
bb....bb: Details
- Description
-
An attempt to copy the virtual application server has failed. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the operation.
-
KEOS29324-E (C/W/F)
An attempt to allocate an IP address on an operational network failed. (minimum value = aa....aa, maximum value = bb....bb)
aa....aa: Minimum value
bb....bb: Maximum value
- Description
-
IP address could not be allocated to the business network. The processing will be interrupted.
- Action
-
Revise the range of IP addresses allocated to the business network, and then re-execute the operation.
-
KEOS29326-E (C/W/F)
An attempt to start a virtual application server failed. (server image store host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Virtual server image management host name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to start the virtual application server has failed. The processing will be interrupted.
- Action
-
See the details, as and when required, remove the cause of the error, use the vmx_delete_unit command to delete the management unit, and then re-execute the operation.
-
KEOS29328-E (C/W/F)
An attempt to copy an application information file directory failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to copy the application information file directory has failed. The processing will be interrupted.
- Action
-
See the server communication agent log of the virtual server, and then remove the cause of the error. Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
KEOS29329-E (C/W/F)
An attempt to build a web system failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to set up the Web system has failed. The processing will be interrupted.
- Action
-
See the following virtual server log and remove the cause of the error:
-
Log output by the rasetup command.
-
ManagementServer log.
-
Server communication agent log.
Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
-
KEOS29331-E (C/W/F)
An attempt to import an application failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc, J2EE server name = dd....dd, port number = ee....ee, file name = ff....ff)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: ManagementServer port number
dd....dd: J2EE server name
ee....ee: Naming service port number
ff....ff: File name
- Description
-
An attempt to import the application has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server management command log.
-
Server communication agent log.
Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
-
KEOS29333-E (C/W/F)
An attempt to start an application failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc, J2EE server name = dd....dd, port number = ee....ee, application name = ff....ff)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: ManagementServer port number
dd....dd: J2EE server name
ee....ee: Naming service port number
ff....ff: Application name
- Description
-
An attempt to start the application has failed. The processing will be interrupted.
- Action
-
See the following virtual server log and remove the cause of the error:
-
ManagementServer log.
-
Server management command log.
-
Server communication agent log.
Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
-
KEOS29334-E (C/W/F)
An attempt to stop an application failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc, J2EE server name = dd....dd, port number = ee....ee, application name = ff....ff)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: ManagementServer port number
dd....dd: J2EE server name
ee....ee: Naming service port number
ff....ff: Application name
- Description
-
An attempt to stop the application has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log
-
Server management command log.
-
Server communication agent log.
Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
-
KEOS29335-E (C/W/F)
A batch stop of the logical servers failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: ManagementServer port number
- Description
-
An attempt to batch stop the logical servers has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
-
KEOS29336-E (C/W/F)
An attempt to stop Management Server failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: ManagementServer port number
- Description
-
An attempt to stop the Management Server has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
-
KEOS29337-E (C/W/F)
An attempt to stop Administration Agent failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to stop the Administration Agent has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
Administration Agent log.
-
Server communication agent log.
Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
-
KEOS29339-E (C/W/F)
The value specified for the parameter is invalid. (option = aa....aa, value = bb....bb)
aa....aa: Option name
bb....bb: Value
- Description
-
The value specified in the argument is invalid. The processing will be interrupted.
- Action
-
Check the value, and then re-execute the operation.
-
KEOS29343-E (C/W/F)
In the virtual server property file, the specified minimum value for allotment of IP addresses is above the maximum value. (file name = aa....aa, parameter name = bb....bb, minimum value = cc....cc, parameter name = dd....dd, maximum value = ee....ee)
aa....aa: File name
bb....bb: Parameter name
cc....cc: Value
dd....dd: Parameter name
ee....ee: Value
- Description
-
The minimum value of the allocated IP address specified in the property file for virtual server setup exceeds the maximum value. The processing will be interrupted.
- Action
-
Check the parameters and values in such a way so that the minimum value of the allocated IP address of the management unit does not exceed the maximum value, and then re-execute the operation.
-
KEOS29344-E (C/W/F)
In the virtual server property file, the range for allotment of operation IP addresses overlaps with the range for management IP addresses. (file name = aa....aa, operation IP parameter name = bb....bb, operation IP minimum value = cc....cc, operation IP parameter name = dd....dd, operation IP maximum value = ee....ee, management IP parameter name = ff....ff, management IP minimum value = gg....gg, management IP parameter name = hh....hh, management IP maximum value = ii....ii)
aa....aa: File name
bb....bb: Parameter name of the minimum operation IP value
cc....cc: Value of the minimum operation IP value
dd....dd: Parameter name of the maximum operation IP value
ee....ee: Value of the maximum operation IP value
ff....ff: Parameter name of the minimum management IP value
gg....gg: Value of the minimum management IP value
hh....hh: Parameter name of the maximum management IP value
ii....ii: Value of the maximum management IP value
- Description
-
The allocated IP address range of the property file for virtual server setup overlaps the allocated IP address range for the other management units. The processing will be interrupted.
- Action
-
Check the parameters and values in such a way so that the allocated IP address range does not overlap with the range set up in the other management units, and then re-execute the operation.
-
KEOS29345-I (C/W/F)
Creation of management unit succeeded. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was created successfully.
-
KEOS29347-E (C/W/F)
An attempt to allocate an IP address on a management network failed. (minimum value = aa....aa, maximum value = bb....bb)
aa....aa: Minimum value
bb....bb: Maximum value
- Description
-
The management network IP address could not be allocated. The processing will be interrupted.
- Action
-
Revise the allocation range of the management network IP address, and then re-execute the operation.
-
KEOS29348-E (C/W/F)
An attempt to stop a virtual application server failed. (server image store host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Virtual server image management host name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to stop the virtual application server has failed. The processing will be interrupted.
- Action
-
See the details, and then remove the cause of the error. Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
KEOS29349-E (C/W/F)
An attempt to confirm whether the virtual application server started has failed. (server image store host name = aa....aa, virtual server name = bb....bb)
aa....aa: Administered machine name
bb....bb: Virtual server name
- Description
-
An attempt to confirm the start of the virtual application server has failed. The processing will be interrupted.
- Action
-
If "Connection timed out" is output in the details for the previous message, revise the value of vmx.virtualserver.start.timeout in the virtual server manager property file. In the case of any other message, see the server communication agent log of the virtual server, and then remove the cause of the error. Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
KEOS29350-E (C/W/F)
Application name cannot be acquired. (application file name = aa....aa, details = bb....bb)
aa....aa: Application file name
bb....bb: Details
- Description
-
An attempt to acquire the application name has failed. The processing will be interrupted.
- Action
-
See the details, and then remove the cause of the error. Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.
-
KEOS29355-I (C/W/F)
Deployment of the management unit succeeded. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was deployed successfully.
-
KEOS29356-W (C/W/F)
Deployment of the management unit partially succeeded. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The deployment of the management unit was partially successful. The processing continues.
- Action
-
See the log, remove the cause of the error, and then re-execute the operation.
-
KEOS29357-E (C/W/F)
Deployment of the management unit failed. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
An attempt to deploy the management unit has failed. The processing will be interrupted.
- Action
-
See the log, remove the cause of the error, and then re-execute the operation.
-
KEOS29358-E (C/W/F)
An attempt to delete a virtual server failed. (host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management target machine name or virtual server image management host name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to delete the virtual server has failed. If the vmx_deploy_unit command was executed, the processing continues and another virtual server will be started. If the vmx_update_unit command or the vmx_delete_unit command was executed, the processing will be interrupted.
- Action
-
If an error occurs in the vmx_deploy_unit command, see the details, remove the cause of the error, and then manually delete the virtual server from VMware vCenter Server. If an error occurs in the vmx_update_unit command or vmx_delete_unit command, see the details, remove the cause of the error, and then re-execute the command.
-
KEOS29359-E (C/W/F)
An attempt to start Administration Agent failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to start the Administration Agent has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
Administration Agent log.
-
Server communication agent log.
After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.
-
-
KEOS29360-E (C/W/F)
An attempt to start Management Server failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to start the Management Server has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.
-
-
KEOS29361-E (C/W/F)
An attempt to create a host definition file for scale-out failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to create the host definition file for scale out has failed. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the operation.
-
KEOS29362-E (C/W/F)
An attempt to copy a file using the server communication agent failed. (management unit name = aa....aa, virtual server name = bb....bb, copy source local path = cc....cc, copy target remote path = dd....dd)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Copy source local path
dd....dd: Copy destination remote path
- Description
-
An attempt to copy the file in the server communication agent has failed. The processing will be interrupted.
- Action
-
See the server communication agent log of the virtual server, and then remove the cause of the error. After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.
-
KEOS29363-E (C/W/F)
An attempt to execute the cmx_scaleout_host command failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to execute the cmx_scaleout_host command has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.
-
-
KEOS29364-E (C/W/F)
An attempt to create a configuration change definition file failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to create the configuration change definition file has failed. The processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the operation.
-
KEOS29365-E (C/W/F)
An attempt to execute the cmx_change_mode command failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to execute the cmx_change_model command has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.
-
-
KEOS29366-E (C/W/F)
An attempt to execute the cmx_build_system command failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to execute the cmx_build_system command has failed. The processing will be interrupted.
- Action
-
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
After finishing the investigation, delete the virtual server from VMware vCenter Server, and re-execute the processing as and when required.
-
-
KEOS29367-E (C/W/F)
An attempt to start a logical server failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to start the logical server has failed. The processing will be interrupted.
- Action
-
See the following virtual server log and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.
-
-
KEOS29368-E (C/W/F)
An attempt to start an application failed. (management unit name = aa....aa, virtual server name = bb....bb, application name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Application name
- Description
-
An attempt to start the application has failed. The processing will be interrupted.
- Action
-
See the following virtual server log and remove the cause of the error:
-
ManagementServer log.
-
Server management command log.
-
Server communication agent log.
After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.
-
-
KEOS29369-E (C/W/F)
An attempt to stop a logical server failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to stop the logical server has failed. The processing will be interrupted.
- Action
-
See the following virtual server log and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.
-
-
KEOS29371-E (C/W/F)
An exception occurred during creation of a temporary file. (details = aa....aa)
aa....aa: Details
- Description
-
An attempt to create a temporary file has failed. If the vmx_deploy_unit command is executed, the processing continues, and then another virtual server starts. If the vmx_rolling_update command is executed, the processing will be interrupted.
- Action
-
See the details, remove the cause of the error, and then delete manually.
-
KEOS29372-E (C/W/F)
An attempt to read the file failed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to read the file has failed. If the vmx_deploy_unit command is executed, the processing continues, and then another virtual server starts. If the vmx_rolling_update command is executed, the processing will be interrupted.
- Action
-
Confirm that you have the permission to access the file.
-
KEOS29374-W (C/W/F)
The specified management unit is already deployed. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The specified management unit is already deployed. The processing will be interrupted.
- Action
-
Check whether there is an error in the specified management unit name. If there is an error, specify the correct management unit name, and then re-execute the operation.
-
KEOS29375-E (C/W/F)
An attempt to deploy a virtual application server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Administered machine name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to deploy the virtual application server has failed. The processing continues, and another virtual application server is deployed.
- Action
-
Remove the cause of the error based on the details described in the following table, and then delete the virtual application server manually.
Table 13‒8: List of error details described in KEOS29375-E Details
Description
Action
- An exception occurred during creation of a temporary file. (details = aa....aa)
-
aa....aa: Details
A failure occurred while creating the temporary file. If the vmx_deploy_unit command or the vmx_start_unit command was executed, the processing continues, and another virtual server starts. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to start Administration Agent failed.
An attempt to start the Administration Agent has failed. If the vmx_deploy_unit command or the vmx_start_unit command was executed, the processing continues and another virtual server will be started. If the vmx_scaleout_unit command was executed, the processing will be interrupted.
See the following virtual server log, and remove the cause of the error:
-
Administration Agent log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to start the Management Server failed.
An attempt to start the Management Server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
- An attempt to create a host definition file for scale-out failed. (details = aa....aa)
-
aa....aa: Details
An attempt to create the host definition file for scale out has failed. The processing continues, and another virtual server will start.
See the details, remove the cause of the error, and then re-execute the operation.
- An attempt to copy a file failed. (copy source local path = aa....aa, copy target remote path = bb....bb, details = cc....cc)
-
aa....aa: Copy source local path
bb....bb: Copy destination remote path
cc....cc: Details
An attempt to copy the file has failed. The processing continues and another virtual server will start.
See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to execute the cmx_scaleout_host command failed.
An attempt to execute the cmx_scaleout_host command has failed. The processing continues and another virtual server will start.
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
- An attempt to create a configuration change definition file failed. (details = aa....aa)
-
aa....aa: Details
An attempt to create the configuration change definition file has failed. The processing continues and another virtual server will start.
See the details, remove the cause of the error, and then re-execute the operation.
An attempt to execute the cmx_change_model command failed.
An attempt to execute the cmx_change_model command has failed. The processing continues and another virtual server will start.
See the following virtual server log and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to execute the cmx_build_system command failed.
An attempt to execute the cmx_build_system command has failed. The processing continues and another virtual server will start.
See the following virtual server log and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to start a logical server failed.
An attempt to start the logical server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to stop a logical server failed.
An attempt to stop the logical server has failed. If the vmx_deploy_unit command is executed, the processing continues and another virtual server will start. If the vmx_stop_unit command is executed, the processing continues and another virtual server will stop. If the vmx_scalein_unit command is executed, the processing will be interrupted.
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
- An attempt to start an application failed. (application name = aa....aa)
-
aa....aa: Application name
An attempt to start the application has failed. The processing continues, and another virtual server will start.
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server management command log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
- An attempt to stop a virtual server failed. (details = aa....aa)
-
aa....aa: Details
An attempt to stop the virtual server has failed. The processing continues, and another virtual server will start.
See the details, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to confirm whether the virtual server stopped has failed. (details = aa....aa)
aa....aa: Details
An attempt to confirm the stopping of the virtual server has failed. If the vmx_deploy_unit command is executed, the processing continues and another virtual server will start. If the vmx_stop_unit command is executed, the processing continues and another virtual server will stop. If the vmx_scalein_unit command is executed, the processing will be interrupted.
Revise the value of vmx.virtualserver.stop.timeout in the virtual server manager property file. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
- An attempt to start a virtual server failed. (details = aa....aa)
-
aa....aa: Details
An attempt to start the virtual server has failed. The processing continues, and another virtual server will start.
See the details, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to confirm whether the virtual server started has failed.
An attempt to confirm the starting of the virtual server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
If "Connection timed out" is output to the details for the previous message, revise the value of vmx.virtualserver.start.timeout in the virtual server manager property file. In the case of any other message, see the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
- An attempt to copy a virtual application server failed. (details = aa....aa)
-
aa....aa: Details
An attempt to copy the virtual application server has failed. The processing continues, and another virtual application server is copied.
See the details, remove the cause of the error, and then re-execute the command when required.
An attempt to copy a user script failed.
An attempt to copy the virtual server runtime user script has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to execute a user script failed.
An attempt to execute the virtual server runtime user script has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the server communication agent log of the virtual server, and then remove the cause of the error. Also, use the vmx_create_unit command or the vmx_update_unit command to confirm that the description of the specified virtual server runtime user script is correct. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to set the server communication agent to start automatically failed.
An attempt to specify settings to automatically start the server communication agent has failed. The processing continues, and another virtual server will start.
See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to rewrite the hosts file failed.
An attempt to rewrite the hosts file failed. The processing continues, and the other virtual servers will be started.
See the action to be taken for the error message output just before this message. If no error message was output, see the server communication agent log of the virtual server, and then remove the cause of the error.
When the investigation is complete, stop and delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
-
KEOS29376-W (C/W/F)
The management unit cannot be deployed because a management target host has not been configured for it. (management unit name = aa....aa, management target host name = bb....bb)
aa....aa: Management unit name
bb....bb: Management target machine name
- Description
-
The management unit cannot be deployed because the management target host to be used in the management unit has not been configured. The processing continues, and the processing for the other management target hosts will be executed.
- Action
-
Use the vmx_set_machine_info command to set up the administered machine that will be used in the management unit, and then re-execute the command.
-
KEOS29377-W (C/W/F)
A virtual server cannot be deployed because it is working. (management unit name = aa....aa, management target host name = bb....bb, virtual server name = cc....cc)
aa....aa: Management unit name
bb....bb: Management target machine name
cc....cc: Virtual server name
- Description
-
The virtual server cannot be deployed because the server is running. The processing continues and the processing for another virtual server will be executed.
- Action
-
Scale in the virtual servers that are not the current version, and then re-execute the command.
-
KEOS29378-I (C/W/F)
A virtual server cannot be deployed because it is the current version. (management unit name = aa....aa, management target host name = bb....bb, virtual server name = cc....cc)
aa....aa: Management unit name
bb....bb: Management target machine name
cc....cc: Virtual server name
- Description
-
The virtual server cannot be deployed because the server version is the current version. The processing continues, and the processing for another virtual server will be executed.
-
KEOS29379-W (C/W/F)
A virtual server cannot be deployed because it is currently malfunctioning. (management unit name = aa....aa, management target host name = bb....bb, virtual server name = cc....cc)
aa....aa: Management unit name
bb....bb: Management target machine name
cc....cc: Virtual server name
- Description
-
The virtual server cannot be deployed because the server has failed. The processing continues and the processing for another virtual server will be executed.
- Action
-
To deploy the virtual server, delete the virtual server from VMware vCenter Server manually, and then re-execute the command.
-
KEOS29380-W (C/W/F)
One or more working or malfunctioning virtual servers exist in management target hosts that are not used by a management unit. (management target host name = aa....aa, virtual server name = bb....bb)
aa....aa: Administered machine name
bb....bb: Virtual server name
- Description
-
A failed or running virtual server exists on an administered machine other than the administered machine to be used in the management unit. The processing continues and the deploy processing will be executed.
- Action
-
Delete or stop the virtual servers existing on the administered machines that are not used in the management unit, and then re-execute the command.
-
KEOS29381-I (C/W/F)
Management unit updated. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was successfully updated.
-
KEOS29382-E (C/W/F)
An attempt was made to delete the oldest version of the specified management unit, but a current version cannot be deleted. (management unit name = aa....aa, virtual application server version = bb....bb)
aa....aa: Management unit name
bb....bb: Version number of the virtual application server
- Description
-
An attempt was made to delete the oldest version of the specified management unit, but the version could not be deleted because it is the current version. The processing will be interrupted.
- Action
-
Check the versions of the virtual application server belonging to the management unit, delete the virtual application server versions that are not required, and then re-execute the operation.
-
KEOS29394-I (C/W/F)
Management unit deleted. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was successfully deleted.
-
KEOS29395-E (C/W/F)
An attempt to delete management unit failed, because a working virtual server exists. (virtual server name = aa....aa)
aa....aa: Virtual server name
- Description
-
The management unit cannot be deleted because a virtual server is running. The processing will be interrupted.
- Action
-
Stop the virtual server, and then re-execute the operation.
-
KEOS29396-E (C/W/F)
An attempt to delete management unit failed, because a malfunctioning virtual server exists. (virtual server name = aa....aa)
aa....aa: Virtual server name
- Description
-
The management unit cannot be deleted because a virtual server has failed. The processing will be interrupted.
- Action
-
Manually delete the checked virtual servers from VMware vCenter Server, and then re-execute the operation.
-
KEOS29401-E (C/W/F)
An invalid value was specified as the argument for the aa....aa option.
aa....aa: Specified option
- Description
-
An invalid number was specified in the argument for the option aa....aa. The processing will be interrupted.
- Action
-
Check whether the argument has an error. If an error exists, correct it, and then execute the command.
-
KEOS29402-E (C/W/F)
The specified version is already set as the current version. (management unit name = aa....aa, version = bb....bb)
aa....aa: Management unit name
bb....bb: Version
- Description
-
The specified version is already set up as the current version. The processing of the command will be interrupted.
- Action
-
Check the management unit name and version number where the current version will be set up, and then re-execute the operation.
-
KEOS29403-E (C/W/F)
The specified version is malfunctioning. (management unit name = aa....aa, version = bb....bb)
aa....aa: Management unit name
bb....bb: Version
- Description
-
The specified version is an error. The processing will be interrupted.
- Action
-
Confirm that a failure does not occur in the version, and then re-execute the operation.
-
KEOS29404-E (C/W/F)
The specified version number does not exist in the specified management unit. (management unit name = aa....aa, version = bb....bb)
aa....aa: Management unit name
bb....bb: Version
- Description
-
The specified version number does not exist in the specified management unit. The processing of the command will be interrupted.
- Action
-
Specify an existing version number.
-
KEOS29405-I (C/W/F)
Setting the status of the virtual application server completed normally. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The setup status of the virtual application server has finished successfully.
-
KEOS29411-E (C/W/F)
The specified management unit does not exist. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The specified management unit does not exist. The processing of the command will be interrupted.
- Action
-
Check the management unit name, and then re-execute the operation.
-
KEOS29413-E (C/W/F)
An attempt to update a virtual server failed because copying of the image of a virtual application server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
An attempt to copy the virtual application server image has failed because the update failed. The processing of the command will be interrupted.
- Action
-
Check whether a virtual server with the same name exists. If such a virtual server exists, confirm that the virtual server with the same name is not used, and then delete the virtual server. After this, re-execute the command.
-
KEOS29414-E (C/W/F)
An attempt to delete an older-version virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
An attempt to delete a virtual server of an old version has failed. The processing of the command will be interrupted.
- Action
-
Check whether you have the permission to access the administered machine.
-
KEOS29416-E (C/W/F)
An attempt to deploy a new virtual server failed because acquisition of an IP address failed. (management unit name = aa....aa, management target host name = bb....bb)
aa....aa: Management unit name
bb....bb: Administered machine name
- Description
-
An attempt to deploy the new virtual server has failed because an attempt to acquire the IP address failed. The processing of the command will be interrupted.
- Action
-
Check whether the IP address is missing.
-
KEOS29417-E (C/W/F)
An attempt to update a virtual server failed because configuration of the virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
An attempt to update the virtual server has failed because the virtual server setup failed. The processing of the command will be interrupted.
- Action
-
See the previous error message, remove the cause of the error, and then re-execute the command.
-
KEOS29418-E (C/W/F)
An attempt to update a virtual server failed because stopping the virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
An attempt to update the virtual server has failed because an attempt to stop the virtual server failed. The processing of the command will be interrupted.
- Action
-
Check why the virtual server cannot be stopped, remove the cause of the error, and then re-execute the command.
-
KEOS29419-W (C/W/F)
A virtual server will be deployed because the number of deployed servers is less than the initial number. (management unit name = aa....aa, management target host name = bb....bb)
aa....aa: Management unit name
bb....bb: Administered machine name
- Description
-
The virtual server will be deployed because the number is less than the initial deployment count. The processing of the command will be interrupted.
-
KEOS29420-E (C/W/F)
An attempt to update a virtual server failed because the current status of the virtual server does not allow updates. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc, virtual server status = dd....dd)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
dd....dd: Virtual server status
- Description
-
An attempt to update the virtual server has failed because the virtual server status cannot be updated. The processing of the command will be interrupted.
- Action
-
Check the cause of the error for the virtual server with the failed status, and then delete that virtual server.
-
KEOS29423-E (C/W/F)
An attempt to update a virtual server failed because startup of the virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc, details = dd....dd)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
dd....dd: Details
- Description
-
An attempt to update the virtual server has failed because an attempt to start the virtual server failed. The processing of the command will be interrupted.
- Action
-
See the details, remove the cause of the error, and then re-execute the command.
-
KEOS29424-I (C/W/F)
The stopped virtual server has been updated. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
A stopped virtual server was updated.
-
KEOS29425-I (C/W/F)
The working virtual server has been updated. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
A running virtual server was updated.
-
KEOS29426-I (C/W/F)
A virtual server has been deployed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
The virtual server is deployed.
-
KEOS29427-E (C/W/F)
An attempt to start a web system failed. (unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
An attempt to start the Web system has failed. The processing of the command will be interrupted.
- Action
-
See the error message, remove the cause of the error, and then re-execute the command.
-
KEOS29428-E (C/W/F)
An attempt to stop a web system failed. (unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
An attempt to stop the Web system has failed. The processing of the command will be interrupted.
- Action
-
See the error message, remove the cause of the error, and then re-execute the command.
-
KEOS29429-W (C/W/F)
The virtual server has already been updated. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Administered machine name
- Description
-
The virtual server has already been updated.
-
KEOS29430-I (C/W/F)
Rolling update of the virtual servers completed successfully. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The rolling update of the virtual servers was successful.
-
KEOS29431-W (C/W/F)
An attempt to perform a rolling update of the virtual servers was made, but some virtual servers failed to update. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The rolling update of the virtual servers was executed, but an attempt to update some of the virtual servers has failed.
-
KEOS29432-E (C/W/F)
An attempt to perform a rolling update of the virtual servers failed. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
An attempt to perform rolling update of the virtual servers has failed.
- Action
-
See the error message, remove the cause of the error, and then re-execute the command.
-
KEOS29433-E (C/W/F)
An attempt to create a temporary directory to store user scripts failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to create the temporary directory for storing the virtual server runtime user script has failed. The processing will be interrupted.
- Action
-
See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
-
KEOS29434-E (C/W/F)
An attempt to execute a user script failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to execute the virtual server runtime user script has failed. The processing will be interrupted.
- Action
-
See the server communication agent log of the virtual server, and then remove the cause of the error. Also, use the vmx_create_unit command or vmx_update_unit command to confirm that the description of the specified virtual server runtime user script is correct. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
-
KEOS29435-W (C/W/F)
The virtual server will be undeployed because the default deploy count has been exceeded. (management unit name = aa....aa, management target host name = bb....bb)
aa....aa: Management unit name
bb....bb: Management target host name
- Description
-
The virtual server will be undeployed because the number of deployed virtual servers exceeded the value in the unit.rule.deploy.num property of the management unit operation tool. The processing continues, and the other virtual servers will be updated.
-
KEOS29436-I (C/W/F)
The virtual server has been undeployed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Management target host name
- Description
-
The virtual server has been undeployed.
-
KEOS29437-W (C/W/F)
The undeploy operation could not be completed because a running or failed virtual server was found. (management unit name = aa....aa, management target host name = bb....bb)
aa....aa: Management unit name
bb....bb: Management target host name
- Description
-
The undeploy operation could not be completed because a running or failed virtual server was found. The processing continues, and the other virtual servers will be updated.
-
KEOS29438-E (C/W/F)
An attempt to set the server communication agent to start automatically failed.(management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to specify settings to automatically start the server communication agent has failed. The processing will be interrupted.
- Action
-
See the server communication agent log of the virtual server, and then remove the cause of the error. After finishing the investigation, delete the virtual server from VMware vCenter Server, and re-execute the processing as and when required.
-
KEOS29441-E (C/W/F)
A virtual server that is not the current version is working. (management target host name = aa....aa, virtual server name = bb....bb)
aa....aa: Management target machine name
bb....bb: Virtual server name
- Description
-
A virtual server of a version that is not the current version is running. The processing will be interrupted.
- Action
-
Use the vmx_scalein_unit command to stop the virtual server of the version that is not the current version, and then re-execute the operation.
-
KEOS29442-I (C/W/F)
A virtual server is already working. (management target host name = aa....aa, virtual server name = bb....bb)
aa....aa: Management target machine name
bb....bb: Virtual server name
- Description
-
The virtual server is already running. The processing continues.
-
KEOS29443-W (C/W/F)
The number of virtual servers that are expected to be working are already running. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The number of virtual servers that must be started are already running. The processing continues.
- Action
-
If the virtual servers are not sufficient, use the vmx_scaleout_unit command to start the virtual servers.
-
KEOS29444-I (C/W/F)
A management unit started. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit is started. The processing will end.
-
KEOS29445-E (C/W/F)
An attempt to start a management unit failed. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit cannot be started. The processing will end.
- Action
-
Check the previous message. If an error has occurred, remove the cause of the error.
-
KEOS29446-W (C/W/F)
Some virtual servers could not be started. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
Some of the virtual servers could not be started. The processing will end.
- Action
-
Check the previous message. If an error has occurred, remove the cause of the error. If no error has occurred, revise the value of unit.rule.start.num in the management unit operation rule.
-
KEOS29447-E (C/W/F)
An attempt to start a virtual server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Administered machine name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to start the virtual server has failed. If the vmx_start_unit command was executed, the processing continues and another virtual server will be started. If the vmx_scaleout_unit command was executed, the processing will be interrupted.
- Action
-
Remove the cause of the error based on the details described in the following table, and then delete the virtual server manually.
Table 13‒9: List of error details described in KEOS29447-E Details
Description
Action
- An exception occurred during creation of a temporary file. (details = aa....aa)
-
aa....aa: Details
An attempt to create a temporary file has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the server communication agent log of the virtual server, and remove the cause of the error. After finishing the investigation, delete the virtual server from VMware vCenter Server, and re-execute the processing as and when required.
An attempt to start Administration Agent failed.
An attempt to start the Administration Agent has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, and the processing will be interrupted.
See the following virtual server log, and remove the cause of the error:
-
Administration Agent log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to start Management Server failed.
An attempt to start the Management Server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to start a logical server failed.
An attempt to start the logical server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to confirm whether the virtual server started has failed.
An attempt to confirm the starting of the virtual server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
If "Connection timed out" is output in the details for the previous message, revise the value of vmx.virtualserver.start.timeout in the virtual server manager property file. In the case of any other message, see the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
An attempt to copy a user script failed.
An attempt to copy the virtual server runtime user script has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the server communication agent log of the virtual server, and then remove the cause of the error. After finishing the investigation, delete the virtual server from VMware vCenter Server, and re-execute the processing as and when required.
An attempt to execute a user script failed.
An attempt to execute the virtual server runtime user script has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.
See the server communication agent log of the virtual server, and then remove the cause of the error. Also, use the vmx_create_unit command or the vmx_update_unit command to confirm that the description of the specified virtual server runtime user script is correct. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
-
KEOS29449-I (C/W/F)
A virtual server started. (management target host name = aa....aa, virtual server name = bb....bb)
aa....aa: Management target machine name
bb....bb: Virtual server name
- Description
-
The virtual server was started.
-
KEOS29451-W (C/W/F)
The management target host specified in the management unit operational rules does not exist. (management unit name = aa....aa, management target host name = bb....bb)
aa....aa: Management unit
bb....bb: Management target machine name
- Description
-
The management target machine specified in the management unit operation rule does not exist. The processing continues.
- Action
-
Use the vmx_set_machine_info command to set up the management target machine information.
-
KEOS29461-E (C/W/F)
No virtual servers are working. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
A running virtual server does not exist. The processing will be interrupted.
- Action
-
If no virtual server is running, the processing cannot be executed.
-
KEOS29462-I (C/W/F)
A management unit stopped. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was stopped. The processing will end.
-
KEOS29463-E (C/W/F)
One or more of the virtual servers managed by the management unit could not be stopped. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
All or some of the virtual servers managed by the management unit could not be stopped. The processing will end.
- Action
-
Manually stop the virtual servers that are already running.
-
KEOS29465-E (C/W/F)
An attempt to collect vm log data failed. (management target host name = aa....aa, virtual server name = bb....bb)
aa....aa: Management target machine name
bb....bb: Virtual server name
- Description
-
An error occurred during the collection of the vm log. The processing continues and another virtual server will be stopped.
- Action
-
See the following virtual server log, and then remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
After the investigation is complete, re-execute the operation as and when required.
-
-
KEOS29466-E (C/W/F)
An attempt to stop a virtual server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management target machine name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to stop the virtual server has failed. If the vmx_stop_unit command is executed, the processing continues and another virtual server will be stopped. If the vmx_scalein_unit command was executed, the processing will be interrupted.
- Action
-
Remove the cause of the error based on the details described in the following table, and then use the vmx_scalein_unit command to stop the virtual server.
Table 13‒10: List of error details described in KEOS29466-E Details
Description
Action
An attempt to stop a logical server failed.
An attempt to stop the logical server has failed. If the vmx_deploy_unit command is executed, the processing continues, and another virtual server will start. If the vmx_stop_unit command is executed, the processing continues, and another virtual server will stop. If the vmx_scalein_unit command is executed, the processing will be interrupted.
See the following virtual server log, and remove the cause of the error:
-
ManagementServer log.
-
Server communication agent log.
When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.
- An attempt to confirm whether the virtual server stopped has failed. (details = aa....aa)
-
aa....aa: Details
An attempt to confirm the stopping of the virtual server has failed. If the vmx_deploy_unit command is executed, the processing continues, and another virtual server will start. If the vmx_stop_unit command is executed, the processing continues, and another virtual server will stop. If the vmx_scalein_unit command is executed, the processing will be interrupted.
Revise the value of vmx.virtualserver.stop.timeout in the virtual server manager property file. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the command as and when required.
-
-
KEOS29471-E (C/W/F)
The specified management target host does not exist. (management target host name = aa....aa)
aa....aa: Management target machine name
- Description
-
The specified management target machine does not exist. The processing will be interrupted.
- Action
-
Specify an existing management target machine name, and then re-execute the operation.
-
KEOS29472-E (C/W/F)
An attempt to start a virtual server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management target machine name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to start the virtual server has failed. The processing continues and another virtual server will be started.
- Action
-
If an error occurs, see the details and remove the cause of the error as and when required.
-
KEOS29473-E (C/W/F)
The management unit does not contain any virtual servers that can be started. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The virtual servers that can be started in the management unit do not exist. The processing will be interrupted.
- Action
-
Check whether the management unit is already deployed or whether all the virtual servers have failed.
-
KEOS29474-I (C/W/F)
The management unit completed scale-out successfully. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
The management unit was successfully scaled out.
-
KEOS29475-E (C/W/F)
The specified management target host is not used by the management unit. (management unit name = aa....aa, management target host name = bb....bb)
aa....aa: Management unit name
bb....bb: Management target machine name
- Description
-
The specified management target machine cannot be used in the management unit. The processing will be interrupted.
- Action
-
Specify an management target machine that is used in the management unit, and then re-execute the command.
-
KEOS29481-E (C/W/F)
The specified virtual server does not exist. (virtual server name = aa....aa)
aa....aa: Virtual server name
- Description
-
The specified virtual server does not exist. The processing will be interrupted.
- Action
-
Check the specified virtual server name, and then re-execute the operation.
-
KEOS29482-E (C/W/F)
The specified virtual is either malfunctioning or already stopped. (virtual server name = aa....aa)
aa....aa: Virtual server name
- Description
-
The specified virtual server has already stopped or failed. The processing will be interrupted.
- Action
-
Select a virtual server that has not stopped or failed, and then re-execute the operation.
-
KEOS29484-I (C/W/F)
The management unit completed scale-in successfully. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
The management unit was successfully scaled in.
-
KEOS29491-E (C/W/F)
The management unit operational rules could not be opened. (management unit name = aa....aa, details = bb....bb)
aa....aa: Management unit name
bb....bb: Details
- Description
-
The management unit operation rule does not open. The processing of the command will be interrupted.
- Action
-
The management unit operation rule is corrupted. Contact maintenance personnel.
-
KEOS29492-I (C/W/F)
The management unit operational rules have been exported. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit operation rule was exported.
-
KEOS29501-E (C/W/F)
An attempt to delete deployed virtual servers that are not management target hosts used by the management unit failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management target machine name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
An attempt to delete the virtual server of the management target machine that is not used in the management unit has failed. The processing continues and another virtual server will be started.
- Action
-
See the details, remove the cause of the error, and then delete the virtual server.
-
KEOS29502-E (C/W/F)
An attempt to rewrite the hosts file failed. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
An attempt to rewrite the hosts file failed. The processing will be cancelled.
- Action
-
See the action to be taken for the error message output just before this message.
If no error message was output, see the server communication agent log of the virtual server, and then remove the cause of the error.
When the investigation is complete, stop the virtual server from VMware vCenter Server as and when required.
If an error occurs in the vmx_create_unit or vmx_update_unit commands, use the vmx_delete_unit command to delete the virtual application server with error, and then re-execute the operation.
If an error occurs in the vmx_rolling_update command, stop and delete the virtual server from VMware vCenter Server, and then re-execute the command.
-
KEOS29601-I (C)
Usage :
- Description
-
This message describes the usage method of the command.
-
KEOS29602-E (C)
Usage :
- Description
-
The command format is incorrect.
The processing will be cancelled.
- Action
-
Check the usage method displayed in the Usage.
Specify the correct command format, and then re-execute the command.
-
KEOS29603-E (C/F)
The host or user ID is not specified in the common arguments.
- Description
-
The host or user ID are not specified in any of the following common arguments:
-
Command line arguments
-
.vmirc (client settings property file)
-
vmiclient.properties (client common configuration file)
The processing will be cancelled.
-
- Action
-
-
To specify the host or user ID in common arguments
Make sure that the host or user ID are specified, and then re-execute the command.
-
To use the default values
Make sure that the vmi.connect.m key and vmi.connect.u key is set up in .vmirc (client settings property file) or vmiclient.properties (client common configuration file), and then re-execute the command.
-
-
KEOS29604-E (C/F)
The specified host name or port number is invalid. (details = aa....aa)
aa....aa: Details
- Description
-
An invalid value has been specified in the host name or port number.
The processing will be cancelled.
- Action
-
-
To specify the host name or port number in the common arguments
Check how the host name and port number have been specified, and then re-execute the command.
-
To use the default value
Make sure that an invalid value has not been set up in the vmi.connect.m key of .vmirc (client settings property file) or vmiclient.properties (client common configuration file), and then re-execute the command.
-
-
KEOS29605-E (C/F)
There was a communication failure with the client. (details = aa....aa)
aa....aa: Details
- Description
-
There was a communication failure with the client.
The processing will be cancelled.
- Action
-
The possible causes are as follows. Remove the cause of the error, and then re-execute the command.
-
The virtual server manager is not running.
Check the running status of the virtual server manager.
-
The host name or port number specified in the -m option of the common arguments is incorrect.
Check the value specified for the host name and port number in the -m option of the common arguments. If the default value is being used, make sure that the vmi.connect.m key and vmi.connect.u key are set up in the .vmirc (client settings property file) or vmiclient.properties (client common configuration file).
-
The combination of the connection source and destination products cannot be connected.
Check whether the combination of the connection source and destination products can be connected.
-
There is a network problem.
Check the network status.
-
-
KEOS29606-E (C/F)
An error occurred while a temporary file was being created. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred while a temporary file was being created. The possible causes are as follows. If the file name is output in the details, check the following errors in that file, and if the file name is not output in the details, check the following errors in the directory storing the processing data of the virtual server manager (directory specified in the vmi.spool.dir key of vmi.properties):
-
There is no access permission.
-
The disk space has depleted.
-
The directory does not exist.
-
The directory could not be created.
The processing will be cancelled.
-
- Action
-
Check the access permissions and disk space for the file name output in the details, or the directory storing the processing data of the virtual server manager, remove the cause of the error, and then re-execute the command.
-
KEOS29607-I (F)
The command will start now. (command = aa....aa, process ID = bb....bb, start time = cc....cc)
aa....aa: command line
bb....bb: Process ID
cc....cc: Command start time
- Description
-
The command described in the message will start.
-
KEOS29608-I (F)
The command will terminate now. (process ID = aa....aa, start time = bb....bb, exit code = cc....cc)
aa....aa: Process ID
bb....bb: Command start time
cc....cc: Exit code
- Description
-
The command described in the process ID and command start time will terminate.
-
KEOS29609-E (C/F)
The specified directory does not exist. (directory path = aa....aa)
aa....aa: Directory path
- Description
-
The specified directory does not exist. The possible causes are as follows:
-
The specified directory name or directory path is incorrect.
-
The specified directory path is a file.
-
The user does not have the permission to access the specified directory path.
The processing will be cancelled.
-
- Action
-
Check whether the specified directory path is a directory, or check the directory name and directory path. If there is no error in the directory path, check whether the user has the access permissions.
Specify the correct directory, and then re-execute the command.
-
KEOS29610-E (C/F)
The specified file does not exist. (file path = aa....aa)
aa....aa: File path
- Description
-
The specified file does not exist.
The processing will be cancelled.
- Action
-
The possible causes are as follows. Take action based on the respective causes.
-
The file path name or path is incorrect.
Check the name and path.
-
The file path is a directory.
Check whether the file path is a file.
-
The user does not have permission to access the file path.
If there is no error in the file path, check if the user has access permissions.
Specify a file with the correct file path and access permissions, and then re-execute the command.
-
-
KEOS29611-E (C/F)
An error occurred while reading the file. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An error occurred while reading the file. The possible causes might be the access permissions for the file and directory, or an error in the I/O environment.
The processing will be cancelled.
- Action
-
Check the details.
If the user does not have the permission to read the file, grant the required permissions. If the file access permissions are correct, and the failure is not recovered even after re-executing the command, contact maintenance personnel.
-
KEOS29612-E (C/F)
A required file does not exist. (management unit name = aa....aa, file name = bb....bb)
aa....aa: Management unit name
bb....bb: File name
- Description
-
The distinguished-name-of-LB-connection-information.properties or tierlb.properties (load balancer connection configuration property file) does not exist in the virtual server manager or definition directory.
The processing will be cancelled.
- Action
-
Check whether the distinguished-name-of-LB-connection-information.properties or tierlb.properties (load balancer connection configuration property file) exists in the following directory:
-
If the virtual server manager is Windows
The Cosminexus-installation-directory\manager\vmi\config\lb directory of the virtual server manager.
-
If the virtual server manager is UNIX
The /opt/Cosminexus/manager/vmi/config/lb directory of the virtual server manager
-
Definition directory
Store distinguished-name-of-LB-connection-information.properties or tierlb.properties (load balancer connection configuration property file) at an appropriate location, and then re-execute the command.
-
-
KEOS29613-I (F)
The virtual server manager was started.
- Description
-
The virtual server manager was started.
-
KEOS29614-E (F)
The virtual server manager failed to start.
- Description
-
The virtual server manager failed to start. A possible cause is an error in the execution environment of the virtual server manager.
The processing will be cancelled.
- Action
-
See the message output just before this message, remove the cause of the error, and then restart the virtual server manager.
-
KEOS29615-I (F)
The virtual server manager was terminated.
- Description
-
The virtual server manager was terminated.
-
KEOS29616-E (F)
A required property is not specified. (aa....aa) (file name = bb....bb)
aa....aa: Property key
bb....bb: File name
- Description
-
A required property is not specified.
The processing will be cancelled.
- Action
-
Check the contents of the file, remove the cause of the error, and then restart the virtual server manager.
-
KEOS29618-W (F)
An invalid value is specified for the property. (aa....aa = bb....bb) default value (cc....cc) will be used. (file name = dd....dd)
aa....aa: Property key
bb....bb: Value specified for the property (invalid value)
cc....cc: Default value of property
dd....dd: File name
- Description
-
An invalid value is specified for the property. The default value will be used.
The processing continues.
- Action
-
Check the file contents.
Remove the cause of the warning as and when required, and then restart the virtual server manager.
-
KEOS29619-I (F)
The directory (aa....aa = bb....bb) has been created.
aa....aa: Directory type
bb....bb: Directory name
- Description
-
The directory has been created.
-
KEOS29620-E (F)
An attempt to create the directory (aa....aa = bb....bb) failed.
aa....aa: Directory type
bb....bb: Directory name
- Description
-
An attempt to create the directory failed. A possible cause is that the access permissions for the directory are invalid.
The processing continues.
- Action
-
Check the directory access permissions.
Remove the cause of the error as and when required, and then restart the virtual server manager.
-
KEOS29621-E (F)
An attempt to read the file failed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to read the file failed. A possible cause is that the access permissions for the file are invalid. The processing continues.
- Action
-
Check the file access permissions.
Remove the cause of the error as and when required, and then restart the virtual server manager.
-
KEOS29622-E (C/F)
An attempt to store the internal status failed. (processing result = aa....aa, file name = bb....bb, details = cc....cc)
aa....aa: Processing results other than the stored internal status (return value of the command when the storage operation is successful)
bb....bb: File name for which storage failed
cc....cc: Details
- Description
-
An attempt to store the internal status failed. The possible causes are as follows:
-
The file permissions are invalid.
-
The disk does not have free space.
-
An error occurred on the disk.
The processing continues.
-
- Action
-
-
Check the file permissions and the disk status.
-
If the processing result is 0, remove the cause of the error, and then take the following action based on the executed command:
Command name
Action
vmiaccount
create
Delete the added account, and then add that account again.
delete
Add the deleted account, and then delete that account again.
password
Change the password again.
vmiunitadmin
changeowner
Change the owner to the old account, and then change that owner again.
create
Delete the created management unit, and then create that management unit again.
delete
Create the deleted management unit, and then delete that management unit again.
vmiunit
attach
Un-register the registered virtual server, and then register that virtual server again.
detach
Register the un-registered virtual server, and then un-register that virtual server again.
Other than above
Register a new virtual server, and then un-register that virtual server.
-
If the processing result is not 0, remove the cause of the error, and then take action according to the message output just before this message.
-
-
KEOS29623-I (F)
The processing of the virtual server manager command will start now. (client = aa....aa)
aa....aa: Connection source host
- Description
-
The processing of the virtual server manager command will start now.
-
KEOS29624-I (F)
The processing of the virtual server manager command will end now.
- Description
-
The processing of the virtual server manager command will end now.
-
KEOS29626-E (C/F)
An internal error occurred. (details = aa....aa)
aa....aa: Details
- Description
-
An internal error occurred.
The processing will be cancelled.
- Action
-
Contact maintenance personnel.
-
KEOS29627-I (C/F)
A request to process aa....aa was received.
aa....aa: Command name
- Description
-
A request to process the command was received. Command name =aa....aa
-
KEOS29628-I (F)
The processing of the aa....aa command will start now.
aa....aa: Command name
- Description
-
The processing of the command will start.
-
KEOS29629-I (F)
The processing of the aa....aa command terminated. (exit code = bb....bb)
aa....aa: Command name
bb....bb: Exit code
- Description
-
The processing of the command terminated.
-
KEOS29630-E (C/F)
A communication error occurred in the virtual server manager. (details = aa....aa)
aa....aa: Details
- Description
-
A communication error occurred in the virtual server manager. A possible cause is that there is an error in the communication between the virtual server manager and the client that executed the command.
The processing will be cancelled.
- Action
-
Remove the cause of the error based on the details, and then re-execute the command. If the failure is not recovered even after re-executing the command, contact maintenance personnel.
-
KEOS29631-E (C/F)
The user ID or user password is invalid.
- Description
-
The user ID or user password is incorrect.
The processing will be cancelled.
- Action
-
Check the specified user ID and user password.
Specify the correct user ID and user password, and then re-execute the operation.
-
KEOS29632-E (C/F)
Connection cannot be established because the settings for using the virtual server manager functionality are not specified, or the virtual server manager has not yet started.
- Description
-
Connection cannot be established because the settings for operating the Management Server as the virtual server manager are not specified, or the start processing of the virtual server manager is not complete.
The processing will be cancelled.
- Action
-
-
Check whether true is specified in the com.cosminexus.mngsvr.vmi.enabled key of mserver.properties (Management Server configuration file). If false is specified, change the value to true, and then restart the virtual server manager. If true is already specified, wait for some time and then re-execute the command.
-
Check whether the start processing of the virtual server manager is complete.
-
-
KEOS29633-E (F)
The server communication agent returned an error response. (details = aa....aa)
aa....aa: Response code
- Description
-
The server communication agent returned an error response. The possible causes are that the server communication agent does not allow access to the virtual server manager, or there is an error in communication with the server communication agent.
If the virtual server identifier is specified in the following commands, the processing will be cancelled.
-
Commands for starting the management unit or virtual server
-
Commands for stopping the management unit or virtual server
The processing continues in all other cases.
-
- Action
-
Check the sinaviagent.permitted.hosts property of sinaviagent.properties in the server communication agent, and the response code in the details.
Set up the IP address of the virtual server manager in the sinaviagent.permitted.hosts property of sinaviagent.properties to allow access. If access is already allowed, take action according to the response code of the server communication agent.
-
KEOS29634-E (F)
An error occurred while the file was being downloaded. (details = aa....aa)
aa....aa: Exception
- Description
-
An error occurred while the file was being downloaded. A possible cause is an error in communication with the server communication agent.
If the virtual server identifier is specified in the following commands, the processing will be cancelled.
-
Commands for starting the management unit or virtual server
-
Commands for stopping the management unit or virtual server
The processing continues in all other cases.
-
- Action
-
Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.
Also, remove the cause of the error based on the details.
If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.
-
FileNotFoundException
Check whether the directory storing the processing data of the virtual server manager (directory specified in the vmi.spool.dir key of vmi.properties) exists.
-
IOException
Check the access permissions and disk space of the directory storing the processing data of the virtual server manager (directory specified in the vmi.spool.dir key of vmi.properties).
-
SocketIOException
Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):
vmi.serverconnectionagent.connect.timeout
vmi.serverconnectionagent.socket.timeout
-
-
KEOS29635-E (F)
An error occurred in the processing of the server communication agent while a file was being downloaded. (details = aa....aa)
aa....aa: Exception
- Description
-
An error occurred in the processing of the server communication agent while a file was being downloaded. A possible cause is an error in the communication with the server communication agent.
If the virtual server identifier is specified in the following commands, the processing will be cancelled.
-
Commands for starting the management unit or virtual server
-
Commands for stopping the management unit or virtual server
The processing continues in all other cases.
-
- Action
-
Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.
Also, remove the cause of the error based on the details.
If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.
-
DuplicateFileNameException
Check whether the output file or directory, transmitted by the server communication agent, is duplicated.
-
FileNotFoundException
Check whether the output file or directory, transmitted by the server communication agent, exists.
-
IOException
Check the access permissions and disk space for the output file or directory, transmitted by the server communication agent.
-
SocketIOException
Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):
vmi.serverconnectionagent.connect.timeout
vmi.serverconnectionagent.socket.timeout
-
-
KEOS29636-E (F)
The version of the server communication agent is inconsistent.
- Description
-
The version of the server communication agent is inconsistent. A possible cause is an error in the communication with the server communication agent.
If the virtual server identifier is specified in the following commands, the processing will be cancelled.
-
Commands for starting the management unit or virtual server
-
Commands for stopping the management unit or virtual server
The processing continues in all other cases.
-
- Action
-
Check whether the Cosminexus version supported by the virtual server manager is being used for Application Server running on the virtual server.
-
KEOS29637-E (F)
A timeout occurred during command execution. (details = aa....aa)
aa....aa: Process ID
- Description
-
A timeout occurred during command execution. A possible cause is that the processes running on the server communication agent have not terminated or are taking time to terminate.
If the virtual server identifier is specified in the following commands, the processing will be cancelled.
-
Commands for starting the management unit or virtual server
-
Commands for stopping the management unit or virtual server
The processing continues in all other cases.
-
- Action
-
Check the statuses of the processes output in the details. Also, check the statuses of the child processes started from this process.
To check the timeout value, check the settings for the following key in vmi.properties (virtual server manager property file):
vmi.serverconnectionagent.exec.timeout
As and when required , terminate the processes forcibly. If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.
-
KEOS29638-E (C/F)
The specified management unit does not exist. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The specified management unit does not exist. A possible cause is that the specified management unit name is incorrect.
The processing will be cancelled.
- Action
-
Check the management unit name. If the management unit name is correct, contact the virtual server manager administrator to check whether the management unit exists.
Specify the correct management unit name, and then re-execute the command.
-
KEOS29639-E (C/F)
The specified management unit already exists. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The specified management unit already exists. A possible cause is that a management unit has already been created using the specified management unit name.
The processing will be cancelled.
- Action
-
Check the specified management unit name. If the management unit name is correct, contact the virtual server manager administrator to check whether another user has created a management unit with the same name.
Specify a management unit name that is not duplicated with a created management unit, and then re-execute the command.
-
KEOS29640-E (F)
An error occurred while a file was being uploaded. (details = aa....aa)
aa....aa: Exception
- Description
-
An error occurred while a file was being uploaded. A possible cause is an error in the communication with the server communication agent.
If the virtual server identifier is specified in the following commands, the processing will be cancelled.
-
Commands for starting the management unit or virtual server
-
Commands for stopping the management unit or virtual server
The processing continues in all other cases.
-
- Action
-
Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.
Also, remove the cause of the error based on the details.
If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.
-
DuplicateFileNameException
Check whether the output file or directory, transmitted by the virtual server manager, is duplicated.
-
FileNotFoundException
Check whether the output file or directory, transmitted by the virtual server manager, exists.
-
IOException
Check the access permissions and disk space for the directory storing the processing data of the virtual server manager (vmi.spool.dir key of vmi.properties).
-
SocketIOException
Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):
vmi.serverconnectionagent.connect.timeout
vmi.serverconnectionagent.socket.timeout
-
-
KEOS29641-E (F)
An error occurred in the processing of the server communication agent while a file was being uploaded. (details = aa....aa)
aa....aa: Exception
- Description
-
An error occurred in the processing of the server communication agent while a file was being uploaded. A possible cause is an error in the communication with the server communication agent.
If the virtual server identifier is specified in the following commands, the processing will be cancelled.
-
Commands for starting the management unit or virtual server
-
Commands for stopping the management unit or virtual server
The processing continues in all other cases.
-
- Action
-
Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.
Also, remove the cause of the error based on the details.
If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.
-
FileNotFoundException
Check whether the output, transmission destination directory for the server communication agent, exists.
-
IOException
Check the access permissions and disk space for the output, transmission destination directory for the server communication agent.
-
SocketIOException
Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):
vmi.serverconnectionagent.connect.timeout
vmi.serverconnectionagent.socket.timeout
-
-
KEOS29642-E (F)
An error occurred in the processing of the server communication agent. (details = aa....aa)
aa....aa: Exception
- Description
-
An error occurred in the processing of the server communication agent. A possible cause is an error in the communication with the server communication agent.
If the virtual server identifier is specified in the following commands, the processing will be cancelled.
-
Commands for starting the management unit or virtual server
-
Commands for stopping the management unit or virtual server
The processing continues in all other cases.
-
- Action
-
Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.
Also, remove the cause of the error based on the details. Terminate the processes forcibly as and when required
If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.
-
CommandInterruptedException
Check the status of the server communication agent and the status of the running processes.
-
IOException
Check the access permissions of the file that is output.
-
SocketIOException
Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):
vmi.serverconnectionagent.connect.timeout
vmi.serverconnectionagent.socket.timeout
-
-
KEOS29643-E (C/F)
The description cannot be specified in the Easy Setup definition file. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
The description of Easy Setup definition file (DefModel.xml) stored in the specified definition directory is incorrect.
The processing will be cancelled.
- Action
-
Remove the cause of the error based on the details described in the following table, and then re-execute the vmiunit import command.
Table 13‒11: List of error details described in KEOS29643-E Details
Description
Action
An XML namespace that cannot be used is specified in the xmlns attribute of <model-definition>. (value = aa....aa)
aa....aa: Value specified in the xmlns attribute of <model-definition>
An XML namespace that cannot be used is specified in <model-definition> in the Easy Setup definition file.
Change the <model-definition> definition in the Easy Setup definition file.
The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.
The XML namespace is not specified in the xmlns attribute of <model-definition>.
The XML namespace is not specified in the xmlns attribute of <model-definition> in the Easy Setup definition file.
Change the <model-definition> definition in the Easy Setup definition file.
The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.
<model-definition>-<web-system> is not defined.
<model-definition>-<web-system> is not defined in the Easy Setup definition file.
Add the Web system definition (<model-definition>-<web-system>) in the Easy Setup definition file.
Multiple <model-definition>-<web-system> tags are defined.
Multiple <model-definition>-<web-system> tags are defined in the Easy Setup definition file.
Define only one <model-definition>-<web-system> tag in the Easy Setup definition file.
Multiple <web-system>-<tier> tags are defined.
Multiple <web-system>-<tier> tags are defined in the Easy Setup definition file.
Define only one <web-system>-<tier> tag in the Easy Setup definition file.
A value that cannot be specified is specified in <tier>-<tier-type>. (value = aa....aa)
aa....aa: Value specified in <tier-type>
A value that cannot be used as the <tier>-<tier-type> value is specified in the Easy Setup definition file.
Specify a value that can be used in <tier>-<tier-type> in the Easy Setup definition file.
A value other than 1 is specified as the value of <tier>-<j2ee-server-count>. (value = aa....aa)
aa....aa: Value specified in <j2ee-server-count>
A value other than 1 is specified as the value of <tier>-<j2ee-server-count> in the Easy Setup definition file.
Delete the <tier>-<j2ee-server-count> tag in the Easy Setup definition file, or specify 1 as the value of <tier>-<j2ee-server-count>.
Multiple <web-system>-<unit> tags are defined.
Multiple <web-system>-<unit> tags are defined in the Easy Setup definition file.
Define only one <web-system>-<unit> tag in the Easy Setup definition file.
<logical-server-name> is not defined for items wherein the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> is aa....aa.
aa....aa: Logical server type
<logical-server-name> is not defined for items wherein the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> is aa....aa in the Easy Setup definition file.
Add the following <logical-server-name> tag to define the logical server name in the logical server definition where the logical server type is aa....aa in the Easy Setup definition file:
<unit>
<allocated-host>
<define-server>
<logical-server-type>aa....aa</logical-server-type>
<logical-server-name>logical server name</logical-server-name>
A value that cannot be specified is specified in <unit>-<allocated-host>-<define-server>-<logical-server-type>. (value = aa....aa)
aa....aa: Logical server type
A value that cannot be used as the <unit>-<allocated-host>-<define-server>-<logical-server-type> value is specified in the Easy Setup definition file.
Specify a value that can be used as the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file.
Multiple <model-definition>-<host> tags are defined.
Multiple <model-definition>-<host> tags are defined in the Easy Setup definition file.
Define only one <model-definition>-<host> tag in the Easy Setup definition file.
A value other than localhost is specified as the value of <unit>-<allocated-host>-<host-ref>. (value = aa....aa)
aa....aa: Value specified in <host-ref>
A value other than localhost is specified as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.
Specify localhost as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.
A value other than localhost is specified as the value of <model-definition>-<host>-<host-name>. (value = aa....aa)
aa....aa: Value specified in <host-name>
A value other than localhost is specified as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file.
Specify localhost as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file.
A value other than localhost is specified as the value of <model-definition>-<host>-<agent-host>. (value = aa....aa)
aa....aa: Value specified in <agent-host>
A value other than localhost is specified as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file.
Specify localhost as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file.
<web-system>-<load-balancer> is defined.
<web-system>-<load-balancer> is defined in the Easy Setup definition file.
Delete the definition of <web-system>-<load-balancer> from the Easy Setup definition file.
<tier>-<j2ee-server-count> cannot be specified in logical tier aa....aa.
aa....aa: Tier type
<tier>-<j2ee-server-count> is defined in the Easy Setup definition file.
Delete the definition of <tier>-<j2ee-server-count> from the Easy Setup definition file.
In the logical server classification aa....aa, <server-no> cannot be specified.
aa....aa: Logical server classification
In the Easy Setup definition file, <server-no> is defined with the logical server having a logical server classification other than "j2ee-server".
Delete the definition of <server-no> corresponding to the logical server having a logical server classification other than "j2ee-server", in the Easy Setup definition file.
If the specified value of <tier>-<j2ee-server-count> is 0, the logical server classification j2ee-server cannot be specified.
In the Easy Setup definition file, if <tier>-<j2ee-server-count> value is "0", the logical server "j2ee-server" is defined.
Delete definition of the logical server classification "j2ee-server" in the Easy Setup definition file.
In the <server-no> value (aa....aa), a value greater than the <tier>-<j2ee-server-count> value (bb....bb) is specified.
aa....aa: Value specified in <server-no>
bb....bb: Value specified in <j2ee-server-count>
In the Easy Setup definition file, a value greater than the <tier>-<j2ee-server-count> value is defined as the <server-no> value.
Specify a value smaller than the <tier>-<j2ee-server-count> value as the <server-no> value in the Easy Setup definition file.
The definition of <unit>-<allocated-host>-<define-server> corresponding to <tier>-<j2ee-server-count> value (aa....aa) is insuffecient.
aa....aa: Value specified in <j2ee-server-count>
The definition of <unit>-<allocated-host>-<define-server> corresponding to the <tier>-<j2ee-server-count> value is insuffecient in the Easy Setup definition file.
Define <unit>-<allocated-host>-<define-server> having the same count of logical server classification "j2ee-server" as the <tier>-<j2ee-server-count> value, in the Easy Setup definition file.
If <tier>-<j2ee-server-count> is not specified, <server-no> cannot be specified.
If <tier>-<j2ee-server-count> is not defined in the Easy Setup definition file, <server-no> cannot be specified.
Delete the definition of <server-no> from the Easy Setup defiition file.
<server-no> is not specified in the logical server definition having the logical server classification "j2ee-server". (Unit name = aa....aa)
aa....aa: Unit name
In the Easy Setup definition file, <server-no> is not defined corresponding to the logical server definition having logical server classification "j2ee-server".
Define <server-no> in the logical server definition having the logical server classification "j2ee-server", in the Easy Setup definition file.
-
KEOS29644-E (C/F)
There is a syntax error in the Easy Setup definition file. (file name = aa....aa, row number = bb....bb, column number = cc....cc, details = dd....dd)
aa....aa: File name
bb....bb: Row number
cc....cc: Column number
dd....dd: Details
- Description
-
There is a syntax error in the specified Easy Setup definition file (DefModel.xml).
The processing will be cancelled.
- Action
-
Check the contents of the Easy Setup definition file.
Remove the cause of the error based on the details, and then re-execute the command.
-
KEOS29645-E (C/F)
There is a syntax error in the virtual server group information file. (file name = aa....aa, row number = bb....bb, column number = cc....cc, details = dd....dd)
aa....aa: File name
bb....bb: Row number
cc....cc: Column number
dd....dd: Details
- Description
-
There is a syntax error in the virtual server group information file.
The processing will be cancelled.
- Action
-
Check the contents of the virtual server group information file.
Remove the cause of the error based on the details, and then re-execute the command.
-
KEOS29646-E (C/F)
An error occurred while the xml file was being parsed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An error occurred while the xml file was being parsed. There is a critical syntax error in the specified Easy Setup definition file (DefModel.xml).
The processing will be cancelled.
- Action
-
Check the contents of the Easy Setup definition file.
Remove the cause of the error based on the details, and then re-execute the operation.
-
KEOS29647-E (C/F)
The value specified in the argument is invalid. (option = aa....aa, value = bb....bb)
aa....aa: Option name
bb....bb: Value
- Description
-
The value specified in the argument is invalid.
The processing will be cancelled.
- Action
-
Check the character restrictions that can be specified in the argument where the error occurred. For details on the character restrictions that can be specified in the arguments, see 9. Commands Used with Virtual Systems in the manual uCosminexus Application Server Command Reference Guide.
Set up the values that can be specified, and then re-execute the command.
-
KEOS29648-E (C/F)
The specified user ID already exists in the virtual server manager administrator account. (user ID = aa....aa)
aa....aa: User ID
- Description
-
The user ID of the specified system builder account is duplicated with the virtual server manager administrator account.
The processing will be cancelled.
- Action
-
Check the user ID of the virtual server manager administrator account that is being managed.
Specify a different user ID than the virtual server manager administrator account, and then re-execute the command.
-
KEOS29649-E (C/F)
The specified user ID already exists. (user ID = aa....aa)
aa....aa: User ID
- Description
-
The specified user ID is already being used in the system builder account.
The processing will be cancelled.
- Action
-
Execute the vmiaccount list command to check the registered user IDs. Specify a user ID different from the registered user IDs, and then re-execute the command.
-
KEOS29650-I (C/F)
The system builder account was added successfully. (user ID = aa....aa)
aa....aa: User ID
- Description
-
The system builder account was added successfully.
-
KEOS29651-E (C/F)
The operation cannot be executed because the specified user ID is the user ID of the virtual server manager administrator account. (user ID = aa....aa)
aa....aa: User ID
- Description
-
The password cannot be changed or deleted because the specified user ID is for the virtual server manager administrator account.
The processing will be cancelled.
- Action
-
Check the user ID of the virtual server manager administrator account that is being managed. Also, execute the vmiaccount list command to check the registered user IDs.
Specify the correct user ID for the system builder account, and then re-execute the command.
To change the password of the virtual server manager administrator account, use the mngsvrctl command.
-
KEOS29652-E (C/F)
The specified user ID cnanot be deleted because it owns the management unit. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The user ID of the specified system builder account cannot be deleted because it owns the management unit.
The processing will be cancelled.
- Action
-
Execute the vmiunit info command to check the owner.
Change the settings so that the user ID of the specified system builder account is no longer the owner of the management unit, and then re-execute the command.
-
KEOS29653-I (C/F)
The system builder account was deleted successfully. (user ID = aa....aa)
aa....aa: User ID
- Description
-
The system builder account was deleted successfully.
-
KEOS29654-E (C/F)
The command option is incorrect. (details = aa....aa)
aa....aa: Details
- Description
-
The specified option is incorrect.
The processing will be cancelled.
- Action
-
Check the specified command options.
Remove the cause of the error based on the details described in the following table, and then re-execute the command.
Table 13‒12: List of error details described in KEOS29654-E Details
Description
Action
An incorrect option is specified. (option = aa....aa)
aa....aa: Option
The specified command option is incorrect.
Review, and if necessary revise, the command options.
A required option is not specified. (option = aa....aa)
aa....aa: Option
A required option is not specified.
Review, and if necessary revise, the command options.
-
KEOS29655-E (C/F)
The specified user ID does not exist. (user ID = aa....aa)
aa....aa: User ID
- Description
-
The specified user ID does not exist in the system builder account. A possible cause is that the specified user ID is incorrect.
The processing will be cancelled.
- Action
-
Execute the vmiaccount list command to check whether the user ID exists.
Specify an existing system builder user ID, and then re-execute the command.
-
KEOS29656-I (C/F)
The user password of the system builder account was changed successfully. (user ID = aa....aa)
aa....aa: User ID
- Description
-
The user password of the system builder account was changed successfully.
-
KEOS29657-W (C/F)
The specified management unit is the owner of the specified user ID. (management unit name = aa....aa, user ID = bb....bb)
aa....aa: Management unit name
bb....bb: User ID
- Description
-
The specified user ID is already the owner of the management unit.
The command will terminate without processing.
- Action
-
Check the specified management unit name and the owner name. If there is no error, contact the virtual server manager administrator to check the management unit owner.
-
KEOS29658-I (C/F)
The owner of the management unit was changed successfully. (management unit name = aa....aa, owner = bb....bb)
aa....aa: Management unit name
bb....bb: Owner
- Description
-
The owner of the management unit was changed successfully.
-
KEOS29659-E (C/F)
A processing was interrupted while it was at standby. (details = aa....aa)
aa....aa: Details
- Description
-
A processing was interrupted while it was at standby.
The processing will be cancelled.
- Action
-
Check the details.
Remove the cause of the error based on the details, and then re-execute the command.
-
KEOS29660-E (C/F)
The processing could not be started within the specified time.
- Description
-
The processing could not be started within the specified time. A possible cause is that another command was not terminated within the standby time.
The processing will be cancelled.
- Action
-
Check the following standby time values:
-
Value specified in the -wait option of the common arguments.
-
Value specified in the vmi.connect.wait key of .vmirc (client settings property file) or vmiclient.properties (client common configuration file).
Re-execute the command after the other commands terminate or after extending the standby time value.
-
-
KEOS29661-I (C/F)
The management unit was created successfully. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was created successfully.
-
KEOS29662-E (C/F)
The virtual server cannot be deleted because it is registered in the specified management unit. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The virtual server cannot be deleted because it is registered in the specified management unit.
The processing will be cancelled.
- Action
-
Execute the vmiunit list command to check the existence of the virtual server in the management unit.
Execute the vmiunit detach command to unregister all the virtual servers registered in the management unit, and then re-execute the command.
-
KEOS29663-I (C/F)
The management unit was deleted successfully. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was deleted successfully.
-
KEOS29664-W (C/F)
The virtual server is not registered in the specified management unit. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The virtual server is not registered in the specified management unit.
The command will terminate without processing.
- Action
-
Execute the vmiunit list command to check the existence of the virtual server in the management unit.
Register the virtual server, apply the definition to the management unit, and then re-execute the command.
-
KEOS29665-E (C/F)
The virtual server is not registered in the specified management unit. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The virtual server is not registered in the specified management unit.
The processing will be cancelled.
- Action
-
Execute the vmiunit list command to check the existence of the virtual server in the management unit.
Specify the correct management unit name, and then re-execute the command.
-
KEOS29666-I (C/F)
The virtual server has started successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The virtual server started successfully.
-
KEOS29667-I (C/F)
The management unit has started successfully. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully started virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be started
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
The management unit started successfully.
-
KEOS29668-W (C/F)
An attempt to start some of the virtual servers in the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully started virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be started
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
An attempt to start some of the virtual servers in the management unit failed.
The management units contain the following virtual servers:
-
Successfully started virtual servers
-
Virtual servers that could not be started
-
- Action
-
Make sure that the message output before this message contains an information message about the successfully started virtual servers and an error message about the virtual servers that could not be started.
Take action for the error message about the virtual servers that could not be started.
-
KEOS29669-E (C/F)
An attempt to start a management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully started virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be started
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
An attempt to start a management unit failed. The management unit contains virtual servers that could not be started, but does not contain successfully started virtual servers.
The processing will be cancelled.
- Action
-
Make sure that the message output before this message contains an error message about the virtual servers that could not be started.
Take action for the error message about the virtual servers that could not be started.
-
KEOS29670-I (C/F)
The operation to start a virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
A virtual server was not started.
Table 13‒13: List of error details described in KEOS29670-I Details
Description
Action
The virtual server is already running.
The virtual server is already running.
--
Legend:
--: Not applicable.
-
KEOS29673-I (F)
The virtual server will start now. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The virtual server will start.
-
KEOS29674-W (F)
The virtual server will start now. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
The virtual server will start now.
The logical status and real status does not match.
The processing continues.
- Action
-
Execute the vmiunit status command to check the logical status and real status of the virtual server.
Check the details described in the following table. Also, stop the virtual server as and when required.
Table 13‒14: List of error details described in KEOS29674-W Details
Description
Action
The statuses do not match. (logical status = aa....aa, real status = bb....bb)
aa....aa: Logical status
bb....bb: Real status
The logical status and real status of the virtual server does not match.
Execute the vmiunit status command to check the logical status and real status of the virtual server.
To match the statuses, execute the vmiunit start or vmiunit stop commands for this virtual server.
-
KEOS29675-E (C/F)
An attempt to write to the file failed. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
An attempt to write to the file failed. The possible causes are as follows:
-
The user does not have the permission to access the write destination file or directory.
-
The disk space at the write destination has depleted.
-
The write destination directory does not exist.
-
The directory could not be created.
The processing will be cancelled.
-
- Action
-
Check whether the path of the output destination directory is incorrect, or check the access permissions and disk space for the output destination directory. Remove the cause of the error based on the details, and then re-execute the command.
-
KEOS29676-E (C/F)
An attempt to start a virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
An attempt to start a virtual server failed. The possible causes are that an error occurred in the virtual server start processing, or that the conditions for executing the start processing are not satisfied.
The processing will be cancelled if the virtual server identifier is specified. The processing continues if the virtual server identifier is not specified.
- Action
-
Take action based on the details.
To restore the virtual server with a failed logical status, execute the vmiunit detach command to remove the virtual server that could not be started from the management unit, then execute the vmiunit attach command to re-register the virtual server into the management unit, and then execute the vmiunit update command to apply the settings. Re-execute the command thereafter.
Table 13‒15: List of error details described in KEOS29676-E Details
Description
Action
The logical status is not set up.
The logical status is not set up.
Execute the vmiunit status command to check the logical status.
Execute the vmiunit update command to set up the virtual server, and then re-execute the command.
The virtual server definition differs from the management unit definition.
The virtual server definition differs from the management unit definition.
Execute the vmiunit status command to check the scope of change in the definition.
Execute the vmiunit update command to update the definition, and then re-execute the command.
An attempt to start the Administration Agent failed.
An attempt to start the Administration Agent failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Administration Agent settings in the definition file.
Check the following virtual server log, and then remove the cause of the error:
-
Administration Agent log
-
Server communication agent log
An attempt to start the Management Server failed.
An attempt to start the Management Server failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Management Server settings in the definition file.
Check the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
An attempt to start a Web system failed.
An attempt to start a Web system failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Easy Setup definition file settings in the definition file.
Check the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
The logical status is failed.
The operation cannot be executed because the logical status of the virtual server is failed.
Execute the vmiunit status command to check the logical status of the virtual server.
To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.
The logical status does not enable processing. (logical status = aa....aa)
aa....aa: Logical status
The processing cannot be executed because the logical status of the virtual server is Running, Stopping, or Updating.
Execute the vmiunit status command to check the logical status of the virtual server.
To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.
Cannot connect to the virtual server.
A connection cannot be established to the virtual server. A possible cause is an error in the communication with the server communication agent.
Check the status of the virtual server power supply.
-
If the power is ON: Check the server communication agent log on the virtual server, and then remove the cause of the error.
-
If the virtual server power supply is OFF: Switch the power to ON.
An error occurred while a temporary file was being created. (details = aa....aa)
aa....aa: Details
An error occurred while a temporary file was being created. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
The user does not have the permission to access the parent directory of the file or directory to be created.
Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.
An attempt to start the application failed. (J2EE server name = aa....aa, port number = bb....bb, application name = cc....cc)
aa....aa: J2EE server name
bb....bb: Port number of the naming service
cc....cc: Application name
An attempt to start the application failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
There is an error in the application.
Check the details, or the following virtual server log, and then remove the cause of the error:
-
Server management command log
-
Server communication agent log
An attempt to check the Administration Agent operations failed.
An attempt to check the Administration Agent operations failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in an Administration Agent process.
Check the return code, or the following virtual server log, and then remove the cause of the error:
-
Administration Agent log
-
Server communication agent log
An attempt to check the Management Server operations failed.
An attempt to check the Management Server operations failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in a Management Server process.
Check the return code, or the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
An attempt to check the Web system operations failed. (Web system name = aa....aa, service unit name = bb....bb)
aa....aa: Web system name
bb....bb: Service unit name
An attempt to check the Web system operations failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
The disk space of the virtual server has depleted.
-
An attempt to execute the cmx_list_status command failed.
Check the return code, or the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
The application status could not be acquired. (J2EE server name = aa....aa, port number = bb....bb)
aa....aa: J2EE server name
bb....bb: Port number of the naming service
The application status could not be acquired. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
The disk space of the virtual server has depleted.
-
An attempt to execute the cjlistapp command failed.
Check the return code, or the following virtual server log, and then remove the cause of the error.
-
Server management command log
-
Server communication agent log
-
-
KEOS29677-I (C/F)
The virtual server was stopped successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The management unit was stopped successfully.
-
KEOS29678-I (C/F)
The management unit was stopped successfully. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully stopped virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be stopped
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
The management unit was stopped successfully.
-
KEOS29679-W (C/F)
An attempt to stop some of the virtual servers in the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully stopped virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be stopped
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
An attempt to stop some of the virtual servers in the management unit failed. The management unit contains successfully stopped virtual servers and virtual servers that could not be stopped.
- Action
-
Make sure that the message output before this message contains an information message about the successfully stopped virtual servers and an error message about the virtual servers that could not be stopped.
Take action for the error message about the virtual servers that could not be stopped.
-
KEOS29680-E (C/F)
An attempt to stop the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully stopped virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be stopped
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
An attempt to stop the management unit failed. The management unit contains virtual servers that could not be stopped, but does not contain successfully stopped virtual servers.
The processing will be cancelled.
- Action
-
Make sure that the message output before this message contains an error message about the virtual servers that could not be stopped.
Take action for the error message about the virtual servers that could not be stopped.
-
KEOS29681-I (C/F)
The operation to stop a virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
The virtual server was not stopped.
Table 13‒16: KEOS29681-I List of error details described in Details
Description
Action
The virtual server has already been stopped.
The virtual server has already been stopped.
--
Legend:
--: Not applicable.
-
KEOS29684-I (F)
The virtual server will stop now. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The virtual server will stop.
-
KEOS29685-W (F)
The virtual server will stop now. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
The virtual server will stop now. The logical status and real status do not match.
The processing continues.
- Action
-
Execute the vmiunit status command to check the logical status and real status of the virtual server. Then check the details. Stop the virtual server as and when required.
Table 13‒17: List of error details described in KEOS29685-W Details
Description
Action
The real status is invalid. (real status = aa....aa)
aa....aa: Real status
The real status of the virtual server is invalid.
Execute the vmiunit status command to check the real status of the virtual server.
Re-execute the command based on the results of command execution.
The statuses do not match. (logical status = aa....aa, real status = bb....bb)
aa....aa: Logical status
bb....bb: Real status
The logical status and real status of the virtual server does not match.
Execute the vmiunit status command to check the logical status and real status of the virtual server.
To match the statuses, execute the vmiunit start or vmiunit stop commands for this virtual server.
-
KEOS29686-I (C/F)
The load balancer operations were successful. (management unit name = aa....aa, tier identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Tier identifier
- Description
-
The load balancer operations were successful.
-
KEOS29687-E (C/F)
An attempt to stop the virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
An attempt to stop the virtual server failed. The possible causes are that an error occurred in the virtual server stop processing, or that the conditions for executing the stop processing are not satisfied.
The processing will be cancelled if the virtual server identifier is specified. The processing continues if the virtual server identifier is not specified.
- Action
-
Take action based on the details.
To restore the virtual server with a failed logical status, execute the vmiunit detach command to remove the virtual server that could not be stopped from the management unit, then execute the vmiunit attach command to re-register the virtual server into the management unit, and then execute the vmiunit update command to apply the settings.
Table 13‒18: List of error details described in KEOS29687-E Details
Description
Action
The logical status is not set up.
The logical status is not set up.
Execute the vmiunit status command to check the logical status.
Execute the vmiunit update command to set up the virtual server, and then re-execute the command.
An attempt to stop the Administration Agent failed.
An attempt to stop the Administration Agent failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Administration Agent process.
Check the following virtual server log, and then remove the cause of the error:
-
Administration Agent log
-
Server communication agent log
An attempt to stop the Management Server failed.
An attempt to stop the Management Server failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Management Server process.
Check the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
An attempt to stop the Web system failed.
An attempt to stop the Web system failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Web system settings.
Check the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
The logical status does not enable processing. (logical status = aa....aa)
aa....aa: Logical status
The processing cannot be executed because the logical status of the virtual server is Running, Stopping, or Updating.
Execute the vmiunit status command to check the logical status of the virtual server.
To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.
Cannot connect to the virtual server.
A connection cannot be established to the virtual server. A possible cause is an error in the communication with the server communication agent.
Check the status of the virtual server power supply.
-
If the power is ON: Check the server communication agent log on the virtual server, and then remove the cause of the error.
-
If the virtual server power supply is OFF: Switch the power to ON.
An error occurred while a temporary file was being created. (details = aa....aa)
aa....aa: Details
An error occurred while a temporary file was being created. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
The user does not have the permission to access the parent directory of the file or directory to be created.
Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.
An attempt to check the Administration Agent operations failed.
An attempt to check the Administration Agent operations failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in an Administration Agent process.
Check the return code, or the following virtual server log, and then remove the cause of the error.
-
Administration Agent log
-
Server communication agent log
An attempt to check the Management Server operations failed.
An attempt to check the Management Server operations failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in a Management Server process.
Check the return code, or the following virtual server log, and then remove the cause of the error.
-
Management Server log
-
Server communication agent log
An attempt to check the Web system operations failed. (Web system name = aa....aa, service unit name = bb....bb)
aa....aa: Web system name
bb....bb: service unit name
An attempt to check the Web system operations failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
The disk space of the virtual server has depleted.
-
An attempt to execute the cmx_list_status command failed.
Check the return code, or the following virtual server log, and then remove the cause of the error.
-
Management Server log
-
Server communication agent log
-
-
KEOS29688-E (C/F)
A required property is not specified. (aa....aa) (management unit name = bb....bb, tier identifier = cc....cc, file name =dd....dd)
aa....aa: Property key
bb....bb: Management unit name
cc....cc: Tier identifier
dd....dd: File name
- Description
-
A required property is not specified.
The processing will be cancelled.
- Action
-
Check the contents of the file.
Remove the cause of the error, and then re-execute the command.
-
KEOS29689-E (C/F)
The specified virtual server identifier is already being used as the virtual server identifier or business IP address of another virtual server belonging to the specified management unit. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Specified management unit name
bb....bb: Specified virtual server identifier
- Description
-
The specified virtual server identifier is incorrect, or is already registered in the management unit as a virtual server identifier or business IP address.
The processing will be cancelled.
- Action
-
Use the vmiunit list command to check the existence of the specified virtual server identifier or business IP address.
Change the virtual server identifier, and then re-execute the command.
-
KEOS29690-I (C/F)
The virtual server group was registered successfully. (management unit name = aa....aa, number of new virtual server groups = bb....bb, number of new virtual servers = cc....cc)
aa....aa: Management unit name
bb....bb: Number of added virtual server groups
cc....cc: Number of added virtual servers
- Description
-
The virtual server group was registered successfully.
-
KEOS29691-E (C/F)
The specified virtual server does not exist. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The specified virtual server does not exist. The specified virtual server identifier is incorrect, or is not registered in the management unit.
The processing will be cancelled.
- Action
-
Execute the vmiunit list command to check whether the specified virtual server identifier exists. Specify the correct virtual server identifier, and then re-execute the command.
-
KEOS29692-I (C/F)
The virtual server group was un-registered successfully. (management unit name = aa....aa, virtual server group name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server group name
- Description
-
The virtual server group was un-registered successfully.
-
KEOS29693-E (C/F)
The definition directory is not imported into the management unit. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The definition file and business application have not been imported into the management unit.
The processing will be cancelled.
- Action
-
Execute the vmiunit status command to check the definition status.
Execute the vmiunit import command to import the definition directory, and then re-execute the command.
-
KEOS29694-E (C/F)
An error occurred while a temporary file was being created. (management unit name = aa....aa, details = bb....bb)
aa....aa: Management unit name
bb....bb: Details
- Description
-
An error occurred while a temporary file was being created. The possible causes are the file and directory access permissions, or that the disk space at the creation destination has depleted.
The processing will be cancelled.
- Action
-
Check the details, and the access permissions or disk space at the creation destination. Remove the cause of the error, and then re-execute the command.
-
KEOS29695-E (C/F)
An attempt to acquire the application name failed. (management unit name = aa....aa, application file = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Application file name
cc....cc: Details
- Description
-
An attempt to acquire the application name failed. A possible cause is an error in the EAR file for the J2EE application stored in the definition directory.
The processing will be cancelled.
- Action
-
Check the EAR file. Also, remove the cause of the error based on the details, and then re-execute the command.
-
KEOS29696-E (C/F)
The user ID is not the owner of the specified management unit. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The user ID is not the owner of the specified management unit. The specified management unit name or user ID is incorrect.
The processing will be cancelled.
- Action
-
Check the management unit name and user ID.
Specify the correct management unit name and user ID, and then re-execute the command.
-
KEOS29697-I (C/F)
The definition directory was registered successfully. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The definition directory was registered successfully.
-
KEOS29698-E (C/F)
An invalid value is specified for the property. (management unit name = aa....aa, tier identifier = bb....bb, cc....cc = dd....dd) (file name = ee....ee)
aa....aa: Management unit name
bb....bb: Tier identifier
cc....cc: Property key
dd....dd: Value specified for the property (invalid value)
ee....ee: File name
- Description
-
An invalid value is specified for the file property.
The processing will be cancelled.
- Action
-
Check the contents of the file.
Change the value to the correct value, and then re-execute the command.
-
KEOS29699-E (C/F)
An invalid value is specified for the file. (management unit name = aa....aa, tier identifier = bb....bb, cc....cc = dd....dd) (file name = ee....ee)
aa....aa: Management unit name
bb....bb: Tier identifier
cc....cc: Parameter name
dd....dd: Value
ee....ee: File name
- Description
-
An invalid value is specified for the file.
The processing will be cancelled.
- Action
-
Check the contents of the file.
Change the value to the correct value, and then re-execute the command.
-
KEOS29700-E (C/F)
An error occurred while reading the file. (management unit name = aa....aa, tier identifier = bb....bb, file name = cc....cc, details = dd....dd)
aa....aa: Management unit name
bb....bb: Tier identifier
cc....cc: File name
dd....dd: Details
- Description
-
An error occurred while reading the file. A possible cause is an error in the access permissions for the definition directory or the file stored in the definition directory.
The processing will be cancelled.
- Action
-
Check the access permissions for the definition directory and definition file. Remove the cause of the error based on the details, and then re-execute the command.
-
KEOS29701-W (C/F)
The error mark has already been set up. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The virtual server identifier is incorrect, or the error mark has already been set up.
The command will terminate without processing.
- Action
-
Check the virtual server identifier. If there is no error in the virtual server identifier, execute the vmiunit status command to check the error mark setup time and error mark comments.
Specify the correct virtual server identifier, and then re-execute the command.
To change the error mark comments, execute the vmiunit unmark command to remove the error mark, and then re-execute the vmiunit mark command.
-
KEOS29702-I (C/F)
The error mark has been set up. (management unit name = aa....aa, virtual server identifier = bb....bb, setup time = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Setup time
- Description
-
The error mark has been set up.
-
KEOS29703-W (C/F)
The error mark has not been set up. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The virtual server identifier is incorrect, or the error mark has already been removed.
The command will terminate without processing.
- Action
-
Check the virtual server identifier. If there is no error in the virtual server identifier, execute the vmiunit status command to check the error mark setup time and error mark comments.
Specify the correct virtual server identifier, and then re-execute the command.
-
KEOS29704-I (C/F)
The error mark has been removed. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The error mark is removed.
-
KEOS29705-W (F)
An invalid value is specified for the property. (management unit name = aa....aa, tier identifier = bb....bb, cc....cc = dd....dd) The default value (ee....ee) will be used. (file name = ff....ff)
aa....aa: Management unit name
bb....bb: Tier identifier
cc....cc: Property key
dd....dd: Value specified for the property (invalid value)
ee....ee: Default value of property
ff....ff: File name
- Description
-
An invalid value is specified for the property of the file stored in the definition directory. The default value will be used.
The processing continues.
- Action
-
Check the contents of the file.
Remove the cause of the warning as and when required, and then re-execute the command.
-
KEOS29706-I (C/F)
The virtual server was applied successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The virtual server was applied successfully.
-
KEOS29707-I (C/F)
The definitions were successfully applied to the management unit. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully applied virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be applied
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
The definitions were successfully applied to the management unit.
-
KEOS29708-W (C/F)
An attempt to apply some of the definitions to the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully applied virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be applied
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
An attempt to apply some of the definitions to the management unit failed. There are virtual servers that could not be applied.
- Action
-
Check the message output before this message.
Remove the cause of the error, and then re-execute the command.
-
KEOS29709-E (C/F)
An attempt to apply the definitions to the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))
aa....aa: Management unit name
bb....bb: Number of virtual servers belonging to the management unit
cc....cc: Number of successfully applied virtual servers
dd....dd: Number of skipped virtual servers
ee....ee: Number of virtual servers that could not be applied
ff....ff: Number of successful load balancer operations
gg....gg: Number of failed load balancer operations
- Description
-
An attempt to apply the definitions to the management unit failed. There are no successfully applied virtual servers.
The processing will be cancelled.
- Action
-
Check the message output before this message.
Remove the cause of the error, and then re-execute the command.
-
KEOS29710-I (C/F)
The definitions were not applied to the virtual server. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
The definitions were not applied to the virtual server.
Table 13‒19: List of error details described in KEOS29710-I Details
Description
Action
The latest definitions are already applied.
The latest definitions are already applied.
--
Legend:
--: Not applicable.
-
KEOS29712-E (C/F)
An attempt to apply a virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
An attempt to apply a virtual server failed. The possible causes are that there is an error in the virtual server apply processing, or that the conditions for executing the apply processing are not satisfied.
The processing for the other virtual servers continues.
- Action
-
Take action based on the details.
To re-apply a virtual server with a failed logical status, execute the vmiunit detach command to remove the virtual server from the management unit, then execute the vmiunit attach command to re-register the virtual server in the management unit, and then re-execute the command.
Table 13‒20: List of error details described in KEOS29712-E Details
Description
Action
An attempt to start the Administration Agent failed.
An attempt to start the Administration Agent failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Administration Agent settings in the definition file.
Check the following virtual server log, and then remove the cause of the error:
-
Administration Agent log
-
Server communication agent log
An attempt to start the Management Server failed.
An attempt to start the Management Server failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Management Server settings in the definition file.
Check the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
An attempt to start a Web system failed.
An attempt to start a Web system failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Easy Setup definition file settings in the definition file.
Check the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
An attempt to stop the Administration Agent failed.
An attempt to stop the Administration Agent failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Administration Agent process.
Check the following virtual server log, and then remove the cause of the error:
-
Administration Agent log
-
Server communication agent log
An attempt to stop the Management Server failed.
An attempt to stop the Management Server failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Management Server process..
Check the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
An attempt to stop the Web system failed.
An attempt to stop the Web system failed. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
There is an error in the Web system settings.
Check the following virtual server log, and then remove the cause of the error:
-
Management Server log
-
Server communication agent log
The logical status is failed.
The operation cannot be executed because the logical status of the virtual server is failed.
Execute the vmiunit status command to check the logical status of the virtual server.
To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.
The logical status does not enable processing. (logical status = aa....aa)
aa....aa: Logical status
The processing cannot be executed because the logical status of the virtual server is Running, Stopping, or Updating.
Execute the vmiunit status command to check the logical status of the virtual server.
To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.
Cannot connect to the virtual server.
A connection cannot be established to the virtual server. A possible cause is an error in the communication with the server communication agent.
Check the status of the virtual server power supply.
-
If the power is ON: Check the server communication agent log on the virtual server, and then remove the cause of the error.
-
If the virtual server power supply is OFF: Switch the power to ON.
The statuses do not match. (logical status = aa....aa, real status = bb....bb)
aa....aa: Logical status
bb....bb: Real status
The logical status and real status of the virtual server does not match.
Execute the vmiunit status command to check the logical status and real status of the virtual server.
To match the statuses, execute the vmiunit start or vmiunit stop commands for this virtual server.
An error occurred while a temporary file was being created. (details = aa....aa)
aa....aa: Details
An error occurred while a temporary file was being created. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
The user does not have the permission to access the parent directory of the file or directory to be created.
Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.
The logical status is Running.
The logical status of the virtual server is Running.
Execute the vmiunit status command to check the logical status of the virtual server.
To apply this virtual server, execute the vmiunit stop command to stop the virtual server.
An attempt to upload the definition directory failed. (details = aa....aa)
aa....aa: Details
An attempt to upload the definition directory failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
The user does not have the permission to access the parent directory of the upload destination.
-
The disk space of the virtual server has depleted.
Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.
An attempt to set up the Web system failed.
An attempt to set up the Web system failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
There is an error in the contents of the definition directory set up in the management unit.
Also, if JP1 auto-setup is specified using the hook script, the deletion of the file fails because the log file trap functionality is running.
Check the details, or the following virtual server log, and then remove the cause of the error:
-
Log output by the rasetup -vm command
-
Management Server log
-
Server communication agent log
Also, if JP1 auto-setup is specified using the hook script, check whether the log file trap functionality is running in th virtual server.
An attempt to import the application failed. (J2EE server name = aa....aa, port number = bb....bb, file name = cc....cc)
aa....aa: J2EE server name
bb....bb: Port number of the naming service
cc....cc: File name
An attempt to import the application failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
There is an error in the application.
Check the details, or the following virtual server log, and then remove the cause of the error.
-
Server management command log
-
Server communication agent log
An attempt to start the application failed. (J2EE server name = aa....aa, port number = bb....bb, application name = cc....cc)
aa....aa: J2EE server name
bb....bb: Port number of the naming service
cc....cc: Application name
An attempt to start the application failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
There is an error in the application.
Check the details, or the following virtual server log, and then remove the cause of the error.
-
Server management command log
-
Server communication agent log
An attempt to delete the application failed. (J2EE server name = aa....aa, port number = bb....bb, J2EE application name = cc....cc)
aa....aa: J2EE server name
bb....bb: Port number of the naming service
cc....cc: J2EE application name
An attempt to delete the application failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
There is an error in the J2EE server environment or the application.
Check the details, or the following virtual server log, and then remove the cause of the error.
-
Server management command log
-
Server communication agent log
An attempt to stop the application failed. (J2EE server name = aa....aa, port number = bb....bb, J2EE application name = cc....cc)
aa....aa: J2EE server name
bb....bb: Port number of the naming service
cc....cc: J2EE application name
An attempt to stop the application failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
There is an error in the J2EE server environment or the application.
Check the details, or the following virtual server log, and then remove the cause of the error.
-
Server management command log
-
Server communication agent log
An attempt to execute the hook script failed. (return code = aa....aa)
aa....aa: Return code of the hook script
An attempt to execute the hook script failed. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
There is an error in the contents of the hook script.
Check the return code, or server communication agent log of the virtual server, and then remove the cause of the error.
The application status could not be acquired. (J2EE server name = aa....aa, port number = bb....bb)
aa....aa: J2EE server name
bb....bb: Port number of the naming service
The application status could not be acquired. The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
The disk space of the virtual server has depleted.
-
An attempt to execute the cjlistapp command failed.
Check the return code, or the following virtual server log, and then remove the cause of the error.
-
Server management command log
-
Server communication agent log
An attempt to create the Easy Setup definition file failed. (details = aa....aa)
aa....aa: Details
An attempt to create the Easy Setup definition file failed.
There is an error in the directory storing the processing data of the virtual server manager. The possible causes are as follows:
-
The user does not have access permissions.
-
The disk space has depleted.
-
A disk error occurred.
Check the message details. Remove the cause of the error, and then re-execute the command.
-
-
KEOS29713-E (C/F)
A required file does not exist in the definition directory. (file name = aa....aa)
aa....aa: File name
- Description
-
A required file does not exist in the definition directory.
The processing will be cancelled.
- Action
-
Make sure that all the required files have been stored.
Store the missing file in the definition directory, and then re-execute the command.
-
KEOS29714-E (C/F)
The definition directory contains files that cannot be specified at the same time. (file = aa....aa, bb....bb)
aa....aa: File name 1
bb....bb: File name 2
- Description
-
An EAR file with the same name as the specified EAR file exists in the definition directory.
The processing will be cancelled.
- Action
-
Make sure that the definition directory does not contain an EAR file with the same name. Note that the name is not case sensitive. "A" and "a" are treated as the same character.
If an EAR file with the same name exists, review the file name. Specify an EAR file with the changed file name in the definition directory, and then re-execute the command.
-
KEOS29715-E (C/F)
The specified path is not a blank directory. ( path = aa....aa)
aa....aa: path
- Description
-
The specified path is not a blank directory. The possible causes are as follows:
-
The specified path is incorrect.
-
The specified path is a file.
-
The directory in the specified path is not blank.
-
The user does not have the permission to access the specified path.
The processing will be cancelled.
-
- Action
-
Check whether the specified path is a blank directory, or check the path. If there is no error in the path, check whether the user has the access permissions.
Create a blank directory with access permissions, specify the correct path, and then re-execute the command.
-
KEOS29716-E (C/F)
An attempt to fetch the definition directory failed. (management unit name = aa....aa, details = bb....bb)
aa....aa: Management unit name
bb....bb: Details
- Description
-
An attempt to fetch the definition directory failed. The possible causes are as follows. If the file name is output in the details, check the following errors in that file, and if the file name is not output in the details, check the following errors in the directory storing the processing data of the virtual server manager (directory specified in the vmi.spool.dir key of vmi.properties):
-
There is no access permission.
-
The disk space has depleted.
-
The directory does not exist.
-
The directory could not be created.
The processing will be cancelled.
-
- Action
-
Check the access permissions and disk space for the file name output in the details, or the directory storing the processing data of the virtual server manager, remove the cause of the error, and then re-execute the command.
-
KEOS29717-I (C/F)
The definition directory was fetched successfully. (management unit name = aa....aa, output destination directory path = bb....bb)
aa....aa: Management unit name
bb....bb: Output destination directory path
- Description
-
The definition directory was fetched successfully.
-
KEOS29718-I (F)
The virtual server operation will be executed. (management unit name = aa....aa, tier identifier = bb....bb, virtual server identifier = cc....cc, operation type = dd....dd, operation target = ee....ee)
aa....aa: Management unit name
bb....bb: Tier identifier
cc....cc: Virtual server identifier
dd....dd: Operation type (Start, Stop, Run, Setup, Delete, Import)
ee....ee: Operation target (Administration Agent, Management Server, Web system, J2EE application, hook script)
- Description
-
The virtual server operation will be executed.
-
KEOS29719-I (F)
The virtual server operation was successful. (management unit name = aa....aa, tier identifier = bb....bb, virtual server identifier = cc....cc, operation type = dd....dd, operation target = ee....ee)
aa....aa: Management unit name
bb....bb: Tier identifier
cc....cc: Virtual server identifier
dd....dd: Operation type (Start, Stop, Run, Setup, Delete, Import)
ee....ee: Operation target (Administration Agent, Management Server, Web system, J2EE application, hook script)
- Description
-
The virtual server operation was successful.
-
KEOS29720-W (C/F)
The file will be ignored because it is not a valid component as a definition directory. (file name = aa....aa)
aa....aa: Ignored file name
- Description
-
The file will be ignored because it is not a valid component as a definition directory. The possible causes are as follows:
-
The file deployed in the definition directory is incorrect.
-
The configuration of the definition directory is incorrect.
-
Files not required for setting up Application Server have been deployed.
The processing continues.
-
- Action
-
Check the file name output in the message.
If the file name is incorrect, change the name to the correct file name, and if the file storage location is incorrect, move the file to the correct location, and then re-execute the command.
-
KEOS29721-E (C/F)
The load balancer operations failed. (management unit name = aa....aa, tier identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Tier identifier
cc....cc: Details
- Description
-
The load balancer operations failed. A possible cause is an error in the load balancer operations.
The processing will be cancelled.
- Action
-
Check the details. Take action based on the details, and then re-execute the command.
Table 13‒21: List of error details described in KEOS29721-E Details
Description
Action
An attempt to set up the load balancer control script failed. (details =aa....aa)
aa....aa: Details
An attempt to set up the load balancer control script failed.
A possible cause is that the configuration of the load balancer is incorrect.
Check the message details.
Remove the cause of the error, and then re-execute the command.
An attempt to execute the load balancer control script failed. (details =aa....aa)
aa....aa: Details
An attempt to execute the load balancer control script failed.
The possible causes are that the configuration of the load balancer is incorrect, or the load balancer is not operating normally.
Check the operation status of the load balancer. Also, check the message details.
Remove the cause of the error, and then re-execute the command.
An attempt to read the load balancer connection configuration property file failed. (details =aa....aa)
aa....aa: Details
An attempt to read the load balancer connection configuration property file failed.
A possible cause is that the configuration of the load balancer is incorrect.
Check the message details.
Remove the cause of the error, and then re-execute the command.
An attempt to log in to the load balancer failed. (details =aa....aa)
aa....aa: Details
An attempt to log in to the load balancer failed.
A possible cause is that the load balancer account information is incorrect.
Check the lb.user key and lb.password key set in the load balancer connection configuration property file and the message details.
Remove the cause of the error, and then re-execute the command.
An attempt to communicate with the load balancer failed. (details =aa....aa)
aa....aa: Details
An attempt to communicate with the load balancer failed.
The possible causes are that the load balancer is not operating normally, or there is a network error.
Check the network status. Also, check the message details.
Remove the cause of the error, and then re-execute the command.
The load balancer type is incorrect.
The load balancer type is incorrect.
A possible cause is that the specified load balancer type is different from the connected load balancer type.
Check the value of the lb.type key specified in the load balancer connection configuration property file.
Remove the cause of the error, and then re-execute the command.
-
KEOS29722-W (C/F)
The operation for starting the virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
The virtual server was not started. The real status of the virtual server is Running, but the logical status is Stopped.
The command will terminate without processing if the virtual server identifier is specified. The processing continues if the virtual server identifier is not specified.
- Action
-
Execute the vmiunit status command to check the logical status and real status of the virtual server. Take action based on the details, and then re-execute the command.
Table 13‒22: List of error details described in KEOS29722-W details
Description
Action
The statuses do not match. (logical status = aa....aa, real status = bb....bb)
aa....aa: Logical status
bb....bb: Real status
The logical status and real status of the virtual server does not match.
Execute the vmiunit status command to check the logical status and real status of the virtual server.
To match the statuses, execute the vmiunit start or vmiunit stop commands for this virtual server.
-
KEOS29723-E (C/F)
The specified business IP address is already being used as the virtual server identifier or business IP address of another virtual server belonging to the specified management unit. (management unit name = aa....aa, business IP address = bb....bb)
aa....aa: Specified management unit name
bb....bb: Specified business IP address
- Description
-
The specified business IP address is incorrect, or is already registered in the management unit as the virtual server identifier or business IP address.
The processing will be cancelled.
- Action
-
Execute the vmiunit list command to check the existence of the specified virtual server identifier or business IP address.
Change the business IP address, and then re-execute the command.
-
KEOS29724-E (C/F)
The specified virtual server identifier is already being used in another management unit. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Specified management unit name
bb....bb: Specified virtual server identifier
- Description
-
The specified virtual server identifier is incorrect, or is already registered in another management unit as the virtual server identifier or business IP address.
The processing will be cancelled.
- Action
-
Check the virtual server identifier.
If there is no error in the virtual server identifier, then contact the virtual server manager administrator to check whether the specified virtual server identifier exists.
Change the virtual server identifier, and then re-execute the command.
-
KEOS29725-E (C/F)
The specified business IP address is already being used in another management unit. (management unit name = aa....aa, business IP address = bb....bb)
aa....aa: Specified management unit name
bb....bb: Specified business IP address
- Description
-
The specified business IP address is incorrect, or is already registered in another management unit as the virtual server identifier or business IP address.
The processing will be cancelled.
- Action
-
Check the business IP address.
If there is no error in the business IP address, then contact the virtual server manager administrator to check whether the specified business IP address exists.
Change the business IP address, and then re-execute the command.
-
KEOS29726-I (C/F)
The virtual server was locked successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The virtual server was locked successfully.
-
KEOS29727-E (C/F)
An attempt to lock the virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
An attempt to lock the virtual server failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.
The processing will be cancelled.
- Action
-
Execute the vmiunit status command to check the logical status of the virtual server.
Remove the cause of the error based on the details, and then re-execute the command.
Table 13‒23: List of error details described in KEOS29727-E Details
Description
Action
The logical status is not set up.
The logical status is not set up.
A possible cause is that the logical status of the virtual server is Not Setup.
Execute the vmiunit status command to check the logical status.
Execute the vmiunit update command to set up the virtual server, and then re-execute the command.
An attempt to set up the load balancer control script failed. (details =aa....aa)
aa....aa: Details
An attempt to set up the load balancer control script failed.
A possible cause is that the configuration of the load balancer is incorrect.
Check the message details.
Remove the cause of the error, and then re-execute the command.
An attempt to execute the load balancer control script failed. (details =aa....aa)
aa....aa: Details
An attempt to execute the load balancer control script failed.
The possible causes are that the configuration of the load balancer is incorrect, or the load balancer is not operating normally.
Check the operation status of the load balancer. Also, check the message details.
Remove the cause of the error, and then re-execute the command.
An attempt to read the load balancer connection configuration property file failed. (details =aa....aa)
aa....aa: Details
An attempt to read the load balancer connection configuration property file failed.
A possible cause is that the configuration of the load balancer is incorrect.
Check the message details.
Remove the cause of the error, and then re-execute the command.
An attempt to log in to the load balancer failed. (details =aa....aa)
aa....aa: Details
An attempt to log in to the load balancer failed.
A possible cause is that the load balancer account information is incorrect.
Check the lb.user key and lb.password key set in the load balancer connection configuration property file and the message details.
Remove the cause of the error, and then re-execute the command.
An attempt to communicate with the load balancer failed. (details =aa....aa)
aa....aa: Details
An attempt to communicate with the load balancer failed.
The possible causes are that the load balancer is not operating normally, or there is a network error.
Check the network status. Also, check the message details.
Remove the cause of the error, and then re-execute the command.
The load balancer type is incorrect.
The load balancer type is incorrect.
A possible cause is that the specified load balancer type is different from the connected load balancer type.
Check the value of the lb.type key specified in the load balancer connection configuration property file.
Remove the cause of the error, and then re-execute the command.
-
KEOS29728-I (C/F)
The virtual server was unlocked successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The virtual server was unlocked successfully.
-
KEOS29729-E (C/F)
An attempt to unlock the virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
An attempt to unlock the virtual server failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.
The processing will be cancelled.
- Action
-
Execute the vmiunit status command to check the logical status of the virtual server.
Remove the cause of the error based on the details, and then re-execute the command. For the details, see Table 13-23 List of error details described in KEOS29727-E.
-
KEOS29730-I (C/F)
The management unit was locked successfully. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was locked successfully.
-
KEOS29731-E (C/F)
An attempt to lock the management unit failed. (management unit name = aa....aa, details = bb....bb)
aa....aa: Management unit name
bb....bb: Details
- Description
-
An attempt to lock the management unit failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.
The processing will be cancelled.
- Action
-
Execute the vmiunit status command to check the logical status of the virtual server.
Remove the cause of the error based on the details, and then re-execute the command. For the details, see Table 13-23 List of error details described in KEOS29727-E.
-
KEOS29732-I (C/F)
The management unit was unlocked successfully. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
The management unit was unlocked successfully.
-
KEOS29733-E (C/F)
An attempt to unlock the management unit failed. (management unit name = aa....aa, details = bb....bb)
aa....aa: Management unit name
bb....bb: Details
- Description
-
An attempt to unlock the management unit failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.
The processing will be cancelled.
- Action
-
Execute the vmiunit status command to check the logical status of the virtual server.
Remove the cause of the error based on the details, and then re-execute the command. For the details, see Table 13-23 List of error details described in KEOS29727-E.
-
KEOS29734-E (C/F)
The load balancer integration functionality is not enabled. (management unit name = aa....aa)
aa....aa: Management unit name
- Description
-
Load balancer integration is not enabled. A possible cause is that the -lb option is specified in the command, but the connection information of the load balancer to be used is not specified in the tier-wise property file.
The processing will be cancelled.
- Action
-
Check the value of the lb.use key in the tier-wise property file.
Specify the connection information of the load balancer to be used in the tier-wise property file, apply the definition to the management unit, and then re-execute the command.
-
KEOS29735-I (C/F)
The load balancer operations were successful. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
The load balancer operations were successful.
-
KEOS29736-E (C/F)
The load balancer operations failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
The load balancer operations failed. A possible cause is that an error occurred during the load balancer operations.
The processing will be cancelled.
- Action
-
Check the message details.
Remove the cause of the error based on the details, and then re-execute the command.
For the details, see Table 13-21 List of error details described in KEOS29721-E.
-
KEOS29737-W (C/F)
An error mark has been set for a running virtual server. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
A virtual server with an error mark will be operated.
The processing continues.
- Action
-
Execute the vmiunit status command to check the error mark setup time and error mark comments.
Execute the vmiunit unmark command to remove the error mark as and when required, and then re-execute the command.
-
KEOS29738-E (C/F)
An error occurred during authentication. (details = aa....aa)
aa....aa: Details
- Description
-
An error occurred during authentication.
The processing will be cancelled.
- Action
-
Check the details output in the message.
See the details, remove the cause of the error, and then re-execute the command.
Table 13‒24: List of error details described in KEOS29738-E Details
Description
Action
A memory shortage occurred.
A memory shortage occurred. The processing will be cancelled.
Check whether the memory required for execution is available.
Increase the free memory space, and then re-execute the operation.
The authentication processing cannot be started. (details = aa....aa)
aa....aa: Details
The authentication processing cannot be started.
The processing will be cancelled.
Contact maintenance personnel.
Cannot connect to JP1/Base.
A connection could not be established with JP1/Base. The possible causes are as follows:
-
JP1/Base is not running.
-
The host name of the authentication server in the JP1/Base settings is incorrect.
The processing will be cancelled.
Check whether JP1/Base is running. Also, check the host name of the authentication server specified in JP1/Base.
If JP1/Base is not running, start JP1/Base. Also, set up an appropriate host name for the authentication server specified in JP1/Base.
An error occurred in JP1/Base.
An error occurred in JP1/Base.
The processing will be cancelled.
See the JP1/Base log.
Remove the cause of the error based on the log check results.
-
-
KEOS29739-E (C/F)
The processing of the aa....aa command cannot be started because the settings for using the JP1 user authentication integration functionality are specified.
aa....aa: Command name
- Description
-
The processing of the command cannot be started because the settings for using the JP1 user authentication integration functionality are specified.
The processing will be cancelled.
- Action
-
When using the JP1 user authentication integration functionality, manage the accounts by operating the authentication server directly.
If you do not want to use the JP1 user authentication integration functionality, disable the JP1 user authentication integration functionality.
-
KEOS29740-W (C/F)
The virtual server manager administrator account will not be set up because the settings for using the JP1 user authentication integration functionality are specified.
- Description
-
The virtual server manager administrator account will not be set up because the settings for using the JP1 user authentication integration functionality are specified.
The processing continues without setting up the virtual server manager administrator account.
- Action
-
When using the JP1 user authentication integration functionality, manage the accounts by operating the authentication server directly.
If you do not want to use the JP1 user authentication integration functionality, disable the JP1 user authentication integration functionality.
-
KEOS29741-I (C/F)
The user script was executed successfully. (management unit name = aa....aa, result = successful:bb....bb warning:cc....cc failed: dd....dd)
aa....aa: Management unit name
bb....bb: Number of successful results
cc....cc: Number of results terminated with a warning
dd....dd: Number of results terminated with an error
- Description
-
The user script was executed successfully.
-
KEOS29742-W (C/F)
The user script has been executed. (management unit name = aa....aa, result = successful: bb....bb warning: cc....cc failed: dd....dd)
aa....aa: Management unit name
bb....bb: Number of successful results
cc....cc: Number of results terminated with a warning
dd....dd: Number of results terminated with an error
- Description
-
An attempt to delete the distributed user script failed.
-
KEOS29743-E (C/F)
An attempt to execute the user script failed. (management unit name = aa....aa, result = successful:bb....bb warning:cc....cc failed:dd....dd)
aa....aa: Management unit name
bb....bb: Number of successful results
cc....cc: Number of results terminated with a warning
dd....dd: Number of results terminated with an error
- Description
-
An attempt to distribute or execute the user script failed.
The processing will be cancelled.
- Action
-
See the virtual server manager log.
See the virtual server manager log for the virtual servers in which user script execution failed, check the details, remove the cause of the error, and then re-execute the command.
-
KEOS29744-E (C/F)
An error occurred while the user script was being executed. (management unit name = aa....aa, details = bb....bb)
aa....aa: Management unit name
bb....bb: Details
- Description
-
An error occurred while the user script was being executed.
The processing will be cancelled.
- Action
-
Remove the cause of the error based on the details described in the following table, and then re-execute the command.
Table 13‒25: List of error details described in KEOS29744-E Details
Description
Action
The user script does not exist in the user script deployment directory.
The user script does not exist in the user script deployment directory.
Check the file configuration of the user script deployment directory. Assign the user script in the user script deployment directory.
The virtual server executing the user script does not exist.
The virtual server does not exist in the specified management unit.
Check whether the virtual server exists in the management unit. Register the virtual server for executing the user script in the management unit.
An attempt to expand the user script failed.
The user does not have the file operation permissions for Cosminexus-installation-directory/manager/vmi/spool.
Check the directory permissions.
An error occurred while a temporary file was being created. (details = aa....aa)
aa....aa: Details
An error occurred while a temporary file was being created.
The user does not have the permission to access the parent directory of the file or directory to be created.
Check the details. Remove the cause of the error.
Cannot connect to the virtual server. (virtual server name = aa....aa)
aa....aa: Virtual server name
The connection to the virtual server cannot be established.
There is an error in the communication with the server communication agent.
Check the status of the virtual server power supply.
If the power is ON, check the server communication agent log on the virtual server. Remove the cause of the error based on the log information.
If the virtual server power supply is OFF, switch the power to ON.
-
KKEOS29745-I (C/F)
The user script was executed successfully on the virtual server. (management unit name = aa....aa, virtual server name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server name
- Description
-
The user script was executed successfully.
-
KEOS29746-W (C/F)
The user script has been executed on the virtual server. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
The user script has been executed.
- Action
-
Remove the cause of the error based on the details described in the following table, and then re-execute the command.
Table 13‒26: List of error details described in KEOS29746-W details
Description
Action
An attempt to delete the temporary directory on the virtual server failed.
The temporary directory Cosminexus-installation-directory/manager/sinagent/work/vmi on the virtual server cannot be deleted.
Check the directory permissions, and then delete the temporary directory.
An attempt to delete the user script on the virtual server failed.
The user script file Cosminexus-installation-directory/manager/sinagent/work/userscript_dir on the virtual server cannot be deleted.
Check the directory permissions, and then delete the user script.
-
KEOS29747-E (C/F)
The execution of the user script on the virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server name
cc....cc: Details
- Description
-
The execution of the user script failed.
The processing will be cancelled.
- Action
-
Remove the cause of the error based on the details described in the following table, and then re-execute the command.
Table 13‒27: List of error details described in KEOS29747-E Details
Description
Action
An attempt to upload failed. (details = aa....aa)
aa....aa: Details
An attempt to upload the user script failed.
The possible causes are as follows:
-
There is an error in the communication with the server communication agent.
-
The user does not have the permission to access the parent directory at the upload destination.
-
The disk space of the virtual server has depleted.
Check the details or the server communication agent log of the virtual server.
The user script terminated abnormally. (return code = aa....aa)
aa....aa: Return code of the user script
The user script terminated abnormally.
There is an error in the user script contents.
Check the return code.
An error occurred while a temporary file was being created. (details = aa....aa)
aa....aa: Details
An error occurred while a temporary file was being created. The possible causes are as follows:
-
An error occurred in the communication with the server communication agent.
-
The user does not have the permission to access the parent directory of the file or directory to be created.
Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.
-
-
KEOS29748-E (C/F)
The virtual server group information file contains an unspecifiable description. (file name = aa....aa, details = bb....bb)
aa....aa: File name
bb....bb: Details
- Description
-
The description in the specified virtual server group information file is incorrect.
The processing will be cancelled.
- Action
-
Remove the cause of the error based on the details described in the following table, and then re-execute the command.
Table 13‒28: List of error details described in KEOS29748-E Details
Description
Action
Multiple <virtualserver> tags with the same tier identifier are specified in <virtualserver-info>-<group>. (virtual server group name = aa....aa, tier identifier = bb....bb)
aa....aa: Virtual server group name
bb....bb: Tier identifier
Multiple <virtualserver> tags with the same tier identifier are specified in <virtualserver-info>-<group>.
Check the value of <virtualserver-info>-<group>-<virtualserver> in the virtual server group information file, and then specify the correct tier identifier.
A required <virtualserver> tag is not specified. (virtual server group name = aa....aa, tier identifier = bb....bb)
aa....aa: Virtual server group name
bb....bb: Tier identifier
The <virtualserver> tag is not specified.
Check <virtualserver-info>-<group>-<virtualserver> in the virtual server group information file, and then add the settings for <virtualserver>.
The attribute value specified in <virtualserver-info>-<group>-<virtualserver> is invalid. (attribute name = aa....aa, value = bb....bb)
aa....aa: Attribute name
bb....bb: Value
The attribute value specified in <virtualserver-info>-<group>-<virtualserver> of the virtual server group information file is invalid.
Check the attribute value of <virtualserver-info>-<group>-<virtualserver> in the virtual server group information file, and then specify a specifiable value.
The attribute value specified in <virtualserver-info>-<group> is invalid. (attribute name = aa....aa, value = bb....bb)
aa....aa: Attribute name
bb....bb: Value
The attribute value specified in <virtualserver-info>-<group> of the virtual server group information file is invalid.
Check the attribute value of <virtualserver-info>-<group> in the virtual server group information file, and then specify a specifiable value.
Multiple <virtualserver-info>-<group> tags have been specified for the same name attribute. (value of the name attribute = aa....aa)
aa....aa: Value of the name attribute
Multiple <virtualserver-info>-<group> tags have been specified for the same name attribute.
Check the name attribute value in <virtualserver-info>-<group> in the virtual server group information file, and then specify an appropriate value.
The same virtual server group name has been specified using a different case. (virtual server group name 1 = aa....aa, virtual server group name 2 = bb....bb)
aa....aa: Virtual server group name 1
bb....bb: Virtual server group name 2
The same virtual server group name has been specified using a different case in the name attribute of <virtualserver-info>-<group>.
Check the name attribute value in <virtualserver-info>-<group> in the virtual server group information file, and then specify an appropriate value.
The same virtual server group name has already been registered using a different case. (specified virtual server group name = aa....aa, registered virtual server group name = bb....bb)
aa....aa: Specified virtual server group name
bb....bb: Registered virtual server group name
A virtual server group with a virtual server group name has already been registered using a different case than the virtual server group name specified in the name attribute of <virtualserver-info>-<group>.
Check the name attribute value in <virtualserver-info>-<group> in the virtual server group information file, and then specify an appropriate value.
-
KEOS29749-E (C/F)
The specified virtual server group does not exist. (management unit name = aa....aa, virtual server group name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server group name
- Description
-
The specified virtual server group does not exist. The possible causes are that the specified virtual server group name is incorrect or is not registered in the management unit.
The processing will be cancelled.
- Action
-
Execute the vmiunit list command to check whether the virtual server group name exists.
Specify the correct virtual server group name, and then re-execute the command.
-
KEOS29750-E (C/F)
An attempt to lock the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Details
- Description
-
An attempt to lock the virtual server group failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.
The processing will be cancelled.
- Action
-
Execute the vmiunit status command to check the logical status of the virtual server. Also, check the message details.
Remove the cause of the error based on the details, and then re-execute the command.
-
KEOS29751-I (C/F)
The virtual server group was locked successfully. (management unit name = aa....aa, virtual server group name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server group name
- Description
-
The virtual server group was locked successfully.
-
KEOS29752-E (C/F)
The specified definition directory contains an invalid tier-wise definition directory. (management unit name = aa....aa, tier identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Tier identifier
- Description
-
The name of the tier-wise definition directory differs from the tier identifier defined in the management unit.
The processing will be cancelled.
- Action
-
Execute the vmiunit compare command to compare the definition directories.
Specify the correct definition directory, and then re-execute the command.
-
KEOS29753-E (C/F)
The specified definition directory does not contain a required tier-wise definition directory. (management unit name = aa....aa, tier identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Tier identifier
- Description
-
A tier-wise definition directory with the same name as the tier identifier defined in the management unit, does not exist.
The processing will be cancelled.
- Action
-
Execute the vmiunit compare command to compare the definition directories.
Specify the correct definition directory, and then re-execute the command.
-
KEOS29754-E (C/F)
The name of the tier-wise definition directory is inappropriate as the tier identifier. (directory path = aa....aa)
aa....aa: Directory path
- Description
-
The name of the tier-wise definition directory is inappropriate as the tier identifier.
The processing will be cancelled.
- Action
-
Check the name of the tier-wise definition directory displayed in the message.
The possible causes are that the name of the tier-wise definition directory below the definition directory specified in the -dir argument contains characters that cannot be used as a tier identifier, or the length of the string exceeds 31 bytes.
Change the name of the tier-wise definition directory to an appropriate name, and then re-execute the command.
-
KEOS29755-W (C/F)
The error mark has already been set up. (management unit name = aa....aa, virtual server group name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server group name
- Description
-
The virtual server group name is incorrect, or the error mark has already been set up.
The processing will be cancelled.
- Action
-
Check the virtual server group name. If there is no error in the virtual server group name, execute the vmiunit status command to check the error mark setup time and the error mark comments.
Specify the correct virtual server group name, and then re-execute the command.
To change the error mark comments, execute the vmiunit unmark command to remove the error mark, and then re-execute the vmiunit mark command.
-
KEOS29756-I (C/F)
The error mark has been set up. (management unit name = aa....aa, virtual server group name = bb....bb, setup time = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Setup time
- Description
-
The error mark has been set up.
-
KEOS29757-W (C/F)
The error mark has not been set up. (management unit name = aa....aa, virtual server group name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server group name
- Description
-
The virtual server identifier is incorrect, or the error mark has already been removed.
The processing will be cancelled.
- Action
-
Check the virtual server group name. If there is no error in the virtual server group name, execute the vmiunit status command to check the error mark setup time and the error mark comments.
Specify the correct virtual server group name, and then re-execute the command.
-
KEOS29758-I (C/F)
The error mark has been removed. (management unit name = aa....aa, virtual server group name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server group name
- Description
-
The error mark has been removed.
-
KEOS29759-E (C/F)
The load balancer integration functionality is not enabled. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server identifier
- Description
-
Load balancer integration is not enabled.
The -lb option is specified in the command, but the connection information of the load balancer to be used is not specified in the tier-wise property file.
The processing will be cancelled.
- Action
-
Check the value of the lb.use key in the tier-wise property file.
Specify the connection information of the load balancer to be used in the tier-wise property file, apply the definition to the management unit, and then re-execute the command.
-
KEOS29760-I (C/F)
The virtual server group was started successfully. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Number of virtual servers belonging to the virtual server group
dd....dd: Number of successfully started virtual servers
ee....ee: Number of skipped virtual servers
ff....ff: Number of virtual servers that could not be started
gg....gg: Number of successful load balancer operations
hh....hh: Number of failed load balancer operations
- Description
-
The virtual server group was started successfully.
-
KEOS29761-W (C/F)
An attempt to start some of the virtual servers in the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Number of virtual servers belonging to the virtual server group
dd....dd: Number of successfully started virtual servers
ee....ee: Number of skipped virtual servers
ff....ff: Number of virtual servers that could not be started
gg....gg: Number of successful load balancer operations
hh....hh: Number of failed load balancer operations
- Description
-
An attempt to start some of the virtual servers in the virtual server group failed.
A possible cause is that the virtual server group contains successfully started virtual servers and virtual servers that could not be started.
- Action
-
Make sure that the message output before this message contains an information message about the successfully started virtual servers and an error message about the virtual servers that could not be started.
Take action for the error message about the virtual servers that could not be started.
-
KEOS29762-E (C/F)
An attempt to start the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the management unit = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Number of virtual servers belonging to the virtual server group
dd....dd: Number of successfully started virtual servers
ee....ee: Number of skipped virtual servers
ff....ff: Number of virtual servers that could not be started
gg....gg: Number of successful load balancer operations
hh....hh: Number of failed load balancer operations
- Description
-
An attempt to start the virtual server group failed.
A possible cause is that the virtual server group contains virtual servers that could not be started, does not contain successfully started virtual servers.
The processing will be cancelled.
- Action
-
Make sure that the message output before this message contains an error message about the virtual servers that could not be started.
Take action for the error message about the virtual servers that could not be started.
-
KEOS29763-I (C/F)
The virtual server group was stopped successfully. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Number of virtual servers belonging to the virtual server group
dd....dd: Number of successfully stopped virtual servers
ee....ee: Number of skipped virtual servers
ff....ff: Number of virtual servers that could not be stopped
gg....gg: Number of successful load balancer operations
hh....hh: Number of failed load balancer operations
- Description
-
The virtual server group was stopped successfully.
-
KEOS29764-W (C/F)
An attempt to stop some of the virtual servers in the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Number of virtual servers belonging to the virtual server group
dd....dd: Number of successfully stopped virtual servers
ee....ee: Number of skipped virtual servers
ff....ff: Number of virtual servers that could not be stopped
gg....gg: Number of successful load balancer operations
hh....hh: Number of failed load balancer operations
- Description
-
An attempt to stop some of the virtual servers in the virtual server group failed.
A possible cause is that the virtual server group contains successfully stopped virtual servers and virtual servers that could not be stopped.
- Action
-
Make sure that the message output before this message contains an information message about the successfully stopped virtual servers and an error message about the virtual servers that could not be stopped.
Take action for the error message about the virtual servers that could not be stopped.
-
KEOS29765-E (C/F)
An attempt to stop the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Number of virtual servers belonging to the virtual server group
dd....dd: Number of successfully stopped virtual servers
ee....ee: Number of skipped virtual servers
ff....ff: Number of virtual servers that could not be stopped
gg....gg: Number of successful load balancer operations
hh....hh: Number of failed load balancer operations
- Description
-
An attempt to stop the virtual server group failed.
A possible cause is that the virtual server group contains virtual servers that could not be stopped, but does not contain successfully stopped virtual servers.
The processing will be cancelled.
- Action
-
Make sure that the message output before this message contains an error message about the virtual servers that could not be stopped.
Take action for the error message about the virtual servers that could not be stopped.
-
KEOS29766-E (C/F)
An attempt to unlock the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server group name
cc....cc: Details
- Description
-
An attempt to unlock the virtual server group failed.
The possible causes are as follows:
-
The configuration of the load balancer is incorrect.
-
The logical status is not set up.
The processing will be cancelled.
-
- Action
-
Execute the vmiunit status command to check the logical status of the virtual server. Also, check the message details.
Remove the cause of the error based on the details, and then re-execute the command.
-
KEOS29767-I (C/F)
The virtual server group was unlocked successfully. (management unit name = aa....aa, virtual server group name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server group name
- Description
-
The virtual server group was unlocked successfully.
-
KEOS29768-W (C/F)
The information for the virtual server group specified in the virtual server group information file differs from the registered virtual server group information. (file name = aa....aa, virtual server group name = bb....bb, tier identifier = cc....cc, attribute name = dd....dd, registered value = ee....ee, specified value = ff....ff)
aa....aa: File name
bb....bb: Virtual server group name
cc....cc: Tier identifier
dd....dd: Attribute name
ee....ee: Registered value
ff....ff: Specified value
- Description
-
The information for the virtual server group specified in the virtual server group information file differs from the registered virtual server group information.
This virtual server group information is ignored and the processing continues.
- Action
-
Compare the information for the virtual server group specified in the virtual server group information file and the information displayed with the vmiunit list command.
Take one of the following actions, and then re-execute the command.
-
If the information specified in the virtual server group information file is incorrect
Revise the information in the virtual server group information file.
-
If the information displayed with the vmiunit list command is incorrect
Use the vmiunit detach command to delete the incorrect virtual server group information.
-
-
KEOS29769-E (C/F)
The newly registered information is not specified in the virtual server group information file. (file name = aa....aa)
aa....aa: File name
- Description
-
The newly registered information is not specified in the virtual server group information file.
A possible cause is that the specified virtual server group information file is incorrect.
The processing will be cancelled.
- Action
-
Check the path and the contents of the specified virtual server group information file.
Specify the correct virtual server group information file, and then re-execute the command.
-
KEOS29770-E (C/F)
The operation to start a virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
The virtual server is not started because the status does not enable the virtual server to start.
The command will terminate without processing if the virtual server identifier is specified. If the virtual server identifier is not specified, the processing continues.
- Action
-
Execute the vmiunit status command to check the virtual server status.
Remove the cause of the error based on the details, and then re-execute the command.
Table 13‒29: List of error details described in KEOS29770-E Details
Description
Action
An attempt to start the virtual server that should have started before this virtual server failed. (Identifier of virtual server that should have started first = aa....aa)
aa....aa: Virtual server identifier
An attempt to start the virtual server that should have started before this virtual server failed.
Take the action for the message output before this message.
-
KEOS29771-E (C/F)
The operation to stop a virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)
aa....aa: Management unit name
bb....bb: Virtual server identifier
cc....cc: Details
- Description
-
The virtual server is not stopped because the status does not enable the virtual server to stop.
The command will terminate without processing if the virtual server identifier is specified. If the virtual server identifier is not specified, the processing continues.
- Action
-
Execute the vmiunit status command to check the virtual server status.
Remove the cause of the error based on the details, and then re-execute the command.
Table 13‒30: List of error details described in KEOS29771-E Details
Description
Action
An attempt to stop the virtual server that should have stopped before this virtual server failed. (Identifier of virtual server that should have stopped first = aa....aa)
aa....aa: Virtual server identifier
An attempt to stop the virtual server that should have stopped before this virtual server failed.
Take the action for the message output before this message.
-
KEOS29772-E (C/F)
The same tier-wise definition directory has been specified using a different case. (directory path 1 = aa....aa, directory path 2 = bb....bb)
aa....aa: Directory path 1
bb....bb: Directory path 2
- Description
-
The same tier-wise definition directory has been specified using a different case.
The processing will be cancelled.
- Action
-
Check the tier-wise definition directory below the definition directory specified in the -dir argument.
Change the name of the tier-wise definition directory, and then re-execute the command.
-
KEOS29773-E (C/F)
The specified virtual server identifier is already being used as the virtual server identifier or business IP address of another virtual server specified in the virtual server group information file. (management unit name = aa....aa, virtual server identifier = bb....bb)
aa....aa: Specified management unit name
bb....bb: Specified virtual server identifier
- Description
-
The specified virtual server identifier is already being used as the virtual server identifier or business IP address of another virtual server specified in the virtual server group information file.
The possible causes are that the specified virtual server identifier is incorrect, or the virtual server identifier or business IP address of another virtual server is incorrect.
The processing will be cancelled.
- Action
-
Check the contents of the virtual server group information file.
Change the virtual server identifier, and then re-execute the command.
-
KEOS29774-E (C/F)
The specified business IP address is already being used as the virtual server identifier or business IP address of another virtual server specified in the virtual server group information file. (management unit name = aa....aa, business IP address = bb....bb)
aa....aa: Specified management unit name
bb....bb: Specified business IP address
- Description
-
The specified business IP address is already being used as the virtual server identifier or business IP address of another virtual server specified in the virtual server group information file.
The processing will be cancelled.
- Action
-
Check the contents of the virtual server group information file.
Change the business IP address, and then re-execute the command.
-
KEOS29775-W (C/F)
An error mark has been set for a running virtual server group. (management unit name = aa....aa, virtual server group name = bb....bb)
aa....aa: Management unit name
bb....bb: Virtual server group name
- Description
-
A virtual server group with an error mark will be operated.
The processing continues.
- Action
-
Execute the vmiunit status command to check the error mark setup time and the error mark comments.
Execute the vmiunit unmark command to remove the error mark as and when required, and then re-execute the command.
-
KEOS29776-E (C/F)
The OS type defined in the tier-wise property file is not compatible with the virtual server OS. (management unit name = aa....aa, tier identifier = bb....bb, virtual server identifier = cc....cc, defined OS type = dd....dd, virtual server OS name = ee....ee)
aa....aa: Management unit name
bb....bb: Tier identifier
cc....cc: Virtual server identifier
dd....dd: Defined OS type
ee....ee: Virtual server OS name
- Description
-
The OS type defined in the tier-wise property file is not compatible with the virtual server OS.
The processing will be cancelled.
- Action
-
The possible causes are as follows. Take action based on the respective causes, and then re-execute the command.
-
The OS type specified in tier.target.os in the tier-wise property file is incorrect.
Revise the value specified for tier.target.os in the tier-wise property file, and then execute the vmiunit import command to re-import the definition.
-
The virtual server OS is incorrect.
Re-install the virtual server OS.
-