uCosminexus Application Server, Messages

[Contents][Back][Next]

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