Use Control F to search for a specific error code in each catalog. To search for any error code, select the Search button at the top right of the screen.
For a complete list of all the messages you may encounter while using LifeKeeper for Linux, please refer to the Combined Message Catalog.
Code | Severity | Message | Cause/Action |
---|---|---|---|
139000 | ERROR | Cannot find the "oci" command in directories of the PATH. Please confirm that it is installed and the PATH is set correctly. |
Cause: Unable to get PATH for "oci" Action: Make sure that the |
139012 | ERROR | \"oci\" command(request-id:%s) failed with code %s, message \"%s\" and status %s |
Cause: Failed to execute the Action: Configure the |
139013 | ERROR | Failed to assign $ip, error:\"$result\" |
Cause: Failed to allocate $ip. Action: Resolve the cause of the error based on the $result details. |
139022 | ERROR | \"oci\" command(request-id:%s) failed with code %s, message \"%s\" and status %s |
Cause: Failed to execute the Action: Configure the |
139023 | ERROR | Failed to unassign $ip, error:\"$result\" |
Cause: Failed to allocate $ip. Action: Resolve the cause of the error based on the $result details. If $ip was unallocated before the remove process was performed, make sure that the resource state is OSU and that $ip is not allocated to the target VNIC on the OCI console. |
139032 | ERROR | \"oci\" command(request-id:%s) failed with code %s, message \"%s\" and status %s |
Cause: Failed to execute the Action: Configure the |
139033 | ERROR | Failed to \"$ocicmdstr\", unknown error:\"$ip_list\" |
Cause: The Action: Unknown error: Please take action based on the "$ip_list". |
139034 | ERROR | There is no secondary IPs on $device. |
Cause: No secondary IP address has been assigned to $device. Action: If local recovery is enabled, make sure that local recovery was performed and therefore it recovered from the failure. |
139035 | ERROR | $ip is not assigned to $device. |
Cause: $ip is not assigned to $device. Action: If local recovery is enabled, make sure that local recovery was performed and therefore it recovered from the failure. |
139042 | ERROR | \"oci\" command(request-id:%s) failed with code %s, message \"%s\" and status %s |
Cause: Failed to execute the Action: Configure the |
139043 | ERROR | Failed to assign $ip, error:\"$result\" |
Cause: Failed to allocate $ip. Action: Resolve the cause of the error based on the $result details. |
139060 | ERROR | $cmd is invalid. |
Cause: $cmd is invalid. Action: Please contact us. |
139061 | ERROR | OCIVIP does not support IPv6. |
Cause: OCIVIP resources do not support use with IPv6. Action: Please use IPv4. |
139062 | ERROR | $cmd is invalid. |
Cause: $cmd is invalid. Action: Please contact us. |
139063 | ERROR | IPv$ipversion is unknown version. |
Cause: The IP address version is incorrect. Action: Please use IPv4. |
139070 | ERROR | Failed to access the $IMDS_URL with the curl command, status code is $status_code. |
Cause: Command curl to $IMDS_URL failed. Action: Make sure that curl to $IMDS_URL completes successfully. |
139071 | ERROR | Failed to decode JSON, error:\"$e\". |
Cause: Failed to decode JSON. Action: Make sure that the result obtained from Instance Meta Data Service is in JSON format. |
139073 | ERROR | Cannot find the vnicId of $device. |
Cause: The vnicId corresponding to $device could not be obtained. Action: Check if vnicId exists in the JSON record of Instance Meta Data Service. |
139074 | ERROR | Cannot find the subnetcidr of $device. |
Cause: The subnetCidrBlock corresponding to $device could not be obtained. Action: Check if subnetcidr exists in the JSON record of Instance Meta Data Service. |
139075 | ERROR | Cannot find the vRouterIp of $device. |
Cause: The virtualRouterIp corresponding to $device could not be obtained. Action: Check if virtualRouterIp exists in the JSON record of Instance Meta Data Service. |
139080 | ERROR | \"oci\" command(request-id:%s) failed with code %s, message \"%s\" and status %s |
Cause: Failed to execute the Action: Configure the |
139081 | ERROR | Failed to get subnet id, error:\"$subnetid\" |
Cause: Failed to obtain the subnet id. Action: Check if the information can be obtained correctly with the following command. The $vnicid corresponds to the VNIC-ID (OCID) of each VNIC assigned to the node. |
139100 | ERROR | IP address is not specified. |
Cause: IP address is not specified. Action: Make sure the IP address is specified. |
139101 | ERROR | Device is not specified. |
Cause: Device is not specified. Action: Make sure the device is specified. |
139105 | ERROR | Cannot bring OCIVIP resource $Tag in service on server $SysName. |
Cause: Failed to restore the OCIVIP resource $Tag on $SysName. Action: Please refer to the log related to the restore process. |
139111 | ERROR | IP-$ip already exists, and device and netmask are inconsistent with those of $ocivipTag. |
Cause: An IP resource corresponding to the IP address of the OCIVIP resource exists, but the device information and netmask information are inconsistent. Action: Change the configuration of the existing IP resource to have the same settings as the OCIVIP resource and create a dependency with the OCIVIP resource. |
139112 | ERROR | Cannot bring IP resource $iptag in service on server $SysName. |
Cause: Failed to restore the IP resource $iptag corresponding to the OCIVIP resource on $SysName. Action: Review the configuration of the IP resource and make sure that restoring of the IP resource is successful. Then create a dependency with the OCIVIP resource. |
139200 | ERROR | A resource with the specified tag name "%s" already exists on the target machine "%s". |
Cause: A resource with the specified tag name already exists on the extended node. Action: Please use a different tag name or delete the resource with the target tag name of the extended node. |
139201 | ERROR | Template resource "%s" does not exist on the server "%s". |
Cause: The resource specified as the extension source does not exist on the node. Action: Please specify the tag name correctly. |
139250 | ERROR | Failed to valuenetOnOCI, error: \"$stderr_log\". |
Cause: Action: The full error message is in $stderr_log. Please take action based on it. |
Post your comment on this topic.