uCosminexus Application Server, Messages

[Contents][Back][Next]

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.