uCosminexus Application Server, Messages

[Contents][Back][Next]

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.