8.1.4 Error messages

Switcher failed to switch because it failed to get the virtual server identifier or event type. (event_id=event_id, system_id=system_id, event_type=event_type)

Content:

Switching failed because acquisition of virtual server identifier or event type failed.

Corrective action:

Collect the survey information and contact our company service representative (SE).

Switcher failed to switch because it failed to get the virtual server information. (event_id=event_id, system_id=system_id, instance_id=instance_id)

Content:

Switching failed because acquisition of virtual server information failed.

However, this message may appear if the instance with the instance ID (instance _id) included in the message is not an instance of a cluster node. If it is not a cluster node, no action is required.

For cluster nodes, an instance of a cluster node may no longer function properly, and recovery is required depending on the state of the instance.

An instance of a cluster node is one that meets all of the following conditions:

The tag "fujitsu.pclswr.id" of the instance is the same value as the tag "fujitsu.pclswr.id" set in "Creating Cluster Node Instance" in "Using the Smart Workload Recovery Feature" in the "PRIMECLUSTER Installation and Administration Guide Cloud Services" when the system was deployed.
The environment variable "PCLSWR _ SYSTEM _ LIST" for the Lambda function in use on your system contains an integer value that identifies the cluster node for the tag "fujitsu.pclswr.id" of the instance.
Instance tag "fujitsu.pclswr.is _recovery _target" is true.

See

For more information about how to determine the tags for an instance, see "Point" in "8.1 Lambda Function Messages".

Corrective action:

Perform recovery according to the instance status.

For information about how to recover, refer to "Recovering According to Instance State" in "Using the Smart Workload Recovery Feature" in the "PRIMECLUSTER Installation and Administration Guide Cloud Services".

Switcher failed to switch because it failed to update the execution management object. (event_id=event_id, system_id=system_id, instance_id=instance_id, state=state)

Content:

Switch failed because update of the execution management object failed.

Because an instance on a cluster node may no longer function properly, recovery is required depending on the state of the instance.

Corrective action:

Perform recovery according to the instance status.

For information about how to recover, see "Recovering According to Instance State" in "Using the Smart Workload Recovery Feature" in the "PRIMECLUSTER Installation and Administration Guide Cloud Services".

Switcher failed to switch because it failed to both apply the blackhole security group and destroy the virtual server. (event_id=event_id, system_id=system_id, instance_id=instance_id, bhsg_id=security_group_id)

Content:

Switch failed because both applying Blackhole Security Group and destroying virtual server failed.

Because an instance on a cluster node may no longer function properly, recovery is required depending on the state of the instance.

Corrective action:

Perform recovery according to the instance status.

Switcher failed to switch because it failed to create a virtual server. (event_id=event_id, system_id=system_id, instance_id=instance_id, new_instance_id=new_instance_id)

Content:

Switching failed because the virtual server creation failed.

Because an instance on a cluster node may no longer function properly, recovery is required depending on the state of the instance.

If the following log is output in addition to this message, creation of the switching destination instance has failed due to AZ resource exhaustion.

botocore.exceptions.ClientError: An error occurred (InsufficientInstanceCapacity) when calling the RunInstances operation (reached max retries: 3): We currently do not have sufficient ＜instance_type＞ capacity in the Availability Zone you requested (＜availability_zone＞). Our system will be working on provisioning additional capacity. You can currently get ＜instance_type＞ capacity by not specifying an Availability Zone in your request or choosing ＜availability_zone＞.

The < instance _ type > and < availability _ zone > in the logs vary from system to system.

Corrective action:

Perform recovery according to the instance status.

For the recovery method, take appropriate action in the following cases:

When AZ resources are depleted
When you create a destination instance, specify a different AZ that has not run out of resources, and then create the destination instance, according to "Changing the settings of the switch destination AZ" in "Using the Smart Workload Recovery Feature" in the "PRIMECLUSTER Installation and Administration Guide Cloud Services".
AZ resources are not depleted
Refer to "Recovering According to Instance State" in "Using the Smart Workload Recovery Feature" in the "PRIMECLUSTER Installation and Administration Guide Cloud Services" to create the target instance.

Switcher failed to switch because it failed to find the subnet for switching. (event_id=event_id, system_id=system_id, instance_id=instance_id)

Content:

Switch failed because destination subnet does not exist.

Because an instance on a cluster node may no longer function properly, recovery is required depending on the state of the instance.

Corrective action:

Do the following:

Add a key to the tag of the switched subnet to indicate the target of switching.
For information about setting up subnets, see "Creating VPC and Subnet" in "Using the Smart Workload Recovery Feature" in the "PRIMECLUSTER Installation and Administration Guide Cloud Services".
Perform recovery according to the instance status.
For information about how to recover, see "Recovering According to Instance State" in "Using the Smart Workload Recovery Feature" in the "PRIMECLUSTER Installation and Administration Guide Cloud Services".

Switcher failed to switch because of internal error. (event_id=event_id, system_id=system_id, instance_id=instance_id)

Content:

Switching failed because an internal error occurred.

Because an instance on a cluster node may no longer function properly, recovery is required depending on the state of the instance.

Corrective action:

Perform recovery according to the instance status.

Switcher failed to switch because Amazon Machine Image does not exist. (event_id=event_id, system_id=system_id, instance_id=instance_id, ami_id=ami_id)

Content:

Switch failed because the AMI does not exist.

Corrective action:

Create an AMI to use for switching from a healthy instance, and then re-create the cluster node instance from the AMI you created.

For instructions on creating an AMI, creating a cluster node, and operating it as a cluster node, see "Procedure for Getting AMI in Operation" in "Using the Smart Workload Recovery Feature" in the "PRIMECLUSTER Installation and Administration Guide Cloud Services".