Use Control F to search for a specific error code.
| Code | Severity | Message | Cause/Action |
|---|---|---|---|
| 18100 | DEBUG | qwk_global_lock: file=%s, line=%d | |
| 18101 | DEBUG | qwk_global_unlock: file=%s, line=%d | |
| 18102 | ERROR | Periodic storage quorum check has not been done for %lld ms, which exceeds 2*QWK_STORAGE_HBEATTIME (%lld) ms. | |
| 18104 | ERROR | usage: %s | |
| 18105 | INFO | starting %s | |
| 18106 | ERROR | qwk_config() failed. | |
| 18107 | ERROR | thread_initialize() failed. | |
| 18108 | ERROR | state_monitor_initialize() failed. | |
| 18109 | ERROR | state_monitor() failed. | |
| 18110 | ERROR | start_server() failed. | |
| 18111 | INFO | shutdown %s | |
| 18112 | ERROR | ‘fopen’ for %s failed: %d | |
| 18113 | ERROR | ‘qwk_object_path=’ line cannot be found for %s. | |
| 18114 | ERROR | ‘%s’ is unknown config. | |
| 18115 | ERROR | configuration of hbeattime ‘%d’ is incorrect. | |
| 18116 | ERROR | configuration of numhbeats ‘%d’ is incorrect. | |
| 18117 | ERROR | configuration of timeout_multiplier ‘%d’ is incorrect. | |
| 18118 | ERROR | configuration of lcmhbeattime ‘%d’ is incorrect. | |
| 18119 | ERROR | configuration of lcmnumhbeats ‘%d’ is incorrect. | |
| 18120 | ERROR | configuration of qwk_object_type is incorrect. | |
| 18121 | ERROR | configuration of my_node is incorrect. | |
| 18122 | ERROR | configuration of number_of_node ‘%d’ is incorrect. | |
| 18123 | ERROR | configuration of number_of_object ‘%d’ is incorrect. | |
| 18124 | ERROR | configuration of object node is incorrect. | |
| 18125 | ERROR | configuration of object path is incorrect. | |
| 18126 | ERROR | my_node is not include in qwk_objects. | |
| 18127 | ERROR | ‘CreateFile’ for %s failed: %d | |
| 18128 | ERROR | ‘ReadFile’ for %s failed: %d | |
| 18129 | ERROR | ‘popen’ for %s failed: %d | |
| 18130 | ERROR | ‘CreateFile’ for %s failed: %d | |
| 18131 | ERROR | ‘WriteFile’ for %s failed: %d | |
| 18132 | ERROR | ‘popen’ for %s failed: %d | |
| 18133 | ERROR | (bug) buffer overflow | |
| 18134 | ERROR | (bug) data is corrupted | |
| 18135 | ERROR | ‘signature=’ line cannot be found. | |
| 18136 | ERROR | signature ‘%s’ does not match. | |
| 18137 | ERROR | ‘local_node=’ line cannot be found. | |
| 18138 | ERROR | local_node ‘%s’ does not match. | |
| 18139 | ERROR | ‘time=’ line cannot be found. | |
| 18140 | ERROR | ‘sequence=’ line cannot be found. | |
| 18141 | ERROR | sequence ‘%s’ scan failed. | |
| 18142 | WARN | ‘node=’ line cannot be found. index=%d | |
| 18143 | ERROR | ‘commstat=’ line cannot be found. index=%d | |
| 18144 | ERROR | ‘checksum=’ line cannot be found. | |
| 18145 | ERROR | checksum ‘%s’ scan failed. | |
| 18146 | ERROR | checksum does not match. | |
| 18147 | INFO | valid qwk object was found. sequence=%llu | |
| 18148 | INFO | invalid qwk object was found. initializing to sequence 0. | |
| 18149 | ERROR | qwk object was not found. | |
| 18150 | DEBUG | write sequence %llu | |
| 18151 | ERROR | failed to read qwk object. | |
| 18152 | ERROR | failed to decode node_info. | |
| 18153 | DEBUG | read sequence %llu | |
| 18154 | WARN | sequence backed down from %llu to %llu. | |
| 18155 | ERROR | ‘malloc’ for %zu failed: %d | |
| 18156 | ERROR | thread_create() failed. index=%d | |
| 18157 | INFO | lcd sys state: %s (It looks the same from its own node and from the target node.) | |
| 18158 | INFO | lcd sys state of target node seen from own node: %s | |
| 18159 | INFO | lcd sys state of own node seen from target node: %s | |
| 18160 | DEBUG | remote node is DOWN. quiet_period=%lld | |
| 18161 | INFO | timeout (status=CR4) | |
| 18162 | INFO | quorum failed (status=CR3) | |
| 18163 | INFO | remote node up (status=CR1) | |
| 18164 | INFO | remote node down (status=CR2) | |
| 18165 | DEBUG | Quorum check in progress: %d / %d | |
| 18166 | INFO | quorum_verify(%s, %s): %s | |
| 18167 | DEBUG | target_node ‘%s’ is unknown. | |
| 18168 | INFO | witness_verify(%s, %s): %s | |
| 18169 | INFO | terminate() | |
| 18170 | ERROR | (bug) data is corrupted | |
| 18171 | ERROR | format error in request. | |
| 18172 | ERROR | format error in quorum_verify request. lkevent cannot be found. | |
| 18173 | ERROR | format error in witness_verify request. lkevent cannot be found. | |
| 18174 | ERROR | format error in witness_verify request. target_node cannot be found. | |
| 18175 | ERROR | ‘%s’ is unknown command. | |
| 18176 | DEBUG | process_each_request_thread | |
| 18177 | ERROR | qwk_receive() did not receive full header. Close connection. | |
| 18178 | ERROR | Request is too long. Close connection. | |
| 18179 | ERROR | qwk_receive() did not receive full request. Close connection. | |
| 18180 | ERROR | do_request() failed. | |
| 18181 | ERROR | qwk_send() did not send full header. Close connection. | |
| 18182 | ERROR | qwk_send() did not send full response. Close connection. | |
| 18183 | DEBUG | process_each_request_thread() exit. | |
| 18184 | ERROR | ConnectNamedPipe() failed. – error 0x%x | |
| 18185 | ERROR | thread_create() failed. | |
| 18186 | ERROR | CreateNamedPipe() failed. – error 0x%x | |
| 18189 | ERROR | create_named_pipe() failed. | |
| 18190 | ERROR | thread_create() failed. | |
| 18193 | ERROR | ‘CreateThread’ failed. - error 0x%x | |
| 18194 | ERROR | requst is too long. header.size=%zu | |
| 18195 | ERROR | qwk_send() failed for header. | |
| 18196 | ERROR | qwk_send() failed for request. | |
| 18197 | ERROR | qwk_send() failed for termination. | |
| 18198 | ERROR | qwk_receive() did not receive full header. | |
| 18199 | ERROR | Response buffer is not enough large. Server sent %zu bytes. | |
| 18200 | ERROR | qwk_receive() did not receive full response. | |
| 18201 | ERROR | ‘%s’ is unknown command. | |
| 18202 | ERROR | Usage: %s … | |
| 18203 | ERROR | Cannot create named pipe. - error 0x%x | |
| 18205 | ERROR | request_send() failed. | |
| 18206 | ERROR | request_receive() failed. | |
| 18207 | ERROR | ‘%s’ is unknown lkevent. | |
| 18208 | ERROR | ‘%s’ is unknown qwktype. | |
| 18209 | ERROR | ‘%s’ is unknown node state. | |
| 18210 | ERROR | ‘%s’ is unknown quorum state. | |
| 18211 | INFO | qwk object was restored. | |
| 18212 | INFO | quorum state changed to %s. | |
| 18213 | INFO | quorum state changed to %s. | |
| 18215 | ERROR | %s is empty | |
| 18216 | ERROR | qwk_storage_s3get for %s failed: %d (%s) | |
| 18217 | ERROR | qwk_storage_s3put for %s failed: %d (%s) | |
| 18218 | WARN | The first cycle did not complete before timeout (%lld ms). completed_num=%d | |
| 18219 | ERROR | Cannot find the configuration for node ‘%s’ in the configuration file. If the configuration of the cluster is changed after the initialization, it needs to be initialized again. Please see the SIOS product documentation for information on how to reinitialize using qwk_storage_init command. | |
| 18223 | ERROR | Abandon retrying: only curl commands are allowed | Cause: An error occurred during internal processing. Action: Please contact our Support Team. |
| 18224 | INFO | curl response error. (HTTP status=[$http_status], response=[$response] | Cause: Access to Amazon S3 objects is temporarily unavailable. Action: No action is generally required, but if this occurs frequently, please contact support. |
| 18225 | INFO | curl call failed. (err=$ret)(output=$response) | Cause: Access to Amazon S3 objects is temporarily unavailable. Action: No action is generally required, but if this occurs frequently, please contact support. |
| 18227 | ERROR | Abandon retrying curl: max attempts reached | Cause: The maximum number of access attempts to an Amazon S3 QWK object has been reached. Action: If this message appears frequently, adjust QWK_CURL_RETRY. |
| 18228 | ERROR | Abandon retrying curl: timeout exceeded | Cause: Accessing Amazon S3 QWK objects is taking too long. Action: If this message appears frequently, adjust QWK_CURL_RETRY_TIMEOUT. |
| 18230 | ERROR | Unexpected error in retry_curl | Cause: An error occurred during internal processing. Action: Please contact our Support Team. |
| 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” command. Action: Make sure that the “oci” command is installed and that the installation directory for the “oci” command is added to your PATH. |
| 139011 | ERROR | \"oci\" command(request-id:%s) failed with code %s, message \"%s\" and status %s | Cause: Failed to execute the oci command. Action: Configure the oci command to end successfully based on the status code and message. |
| 139012 | ERROR | Failed to assign $ip, error:\”$result\” | Cause: Failed to allocate $ip. Action: Resolve the cause of the error based on the $result details. |
| 139021 | ERROR | \"oci\" command(request-id:%s) failed with code %s, message \"%s\" and status %s | Cause: Failed to execute the oci command. Action: Configure the oci command to end successfully based on the status code and message. |
| 139022 | 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. |
| 139031 | ERROR | \"oci\" command(request-id:%s) failed with code %s, message \"%s\" and status %s | Cause: Failed to execute the oci command. Action: Configure the oci command to end successfully based on the status code and message. |
| 139032 | ERROR | Failed to \”$ocicmdstr\”, unknown error:\”$ip_list\” | Cause: The oci command terminated abnormally due to a cause other than code 139032. 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. |
| 139036 | ERROR | A message equivalent to any of the codes 139070 to 139075. | Cause: Refer to 139070 to 139075 Action: Refer to 139070 to 139075. |
| 139037 | ERROR | A message equivalent to any of the codes 139060 to 139063. | Cause: Refer to 139060 to 139063. Action: Refer to 139060 to 139063. |
| 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. |
| 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 oci command. Action: Configure the oci command to end successfully based on the status code and message. |
| 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: valuentOnOCI failed. Action: The full error message is in $stderr_log. Please take action based on it. |
| 140201 | INFO | Daemon already started. | The daemon is already running at the time of restore. |
| 140202 | ERROR | Daemon already started but the pidfile does not match. | Cause: Indicates that the daemon is already running at the time of restore but the pidfile does not match. Action: Stop the running daemon and then try to restore. |
| 140203 | INFO | Health check received. | A probe from the load balancer was received during restore. |
| 140205 | INFO | Daemon not started, the pidfile ($pidfile) is already removed. | The daemon is not already running at the time of remove. The pidfile has also been removed. |
| 140206 | INFO | Daemon not started. | The daemon is not already running at the time of remove. |
| 140208 | WARN | Resource out of service | Cause: The quickCheck is running but the resource was not ISP (In-Service, Protected). |
| 140209 | ERROR | Daemon not running. | Cause: Daemon is stopped with quickCheck. Action: Attempt a local recovery. |
| 140210 | ERROR | Daemon is running but the pidfile does not match. | Cause: Daemon is started with quickCheck but pidfile doesn’t match. Action: Attempt a local recovery. |
| 140211 | ERROR | flg $id-hc-hg is on | Cause: The $id-hc-hg flag was detected by quickCheck. Action: Attempt failover. |
| 140250 | FATAL | Socket open failed. Check if the port \”$port\” is in use by ‘ss -anp’. | Cause: Could not open the socket. Action: Check to see if the port is in use with ‘ss -anp’ and kill the process that is using it. |
| 140251 | ERROR | Health probe not received. Check that the probe from the load balancer is set correctly, including the firewall. | Cause: A probe from the load balancer was not received within $HC_TIMEOUT seconds. Action: Make sure the probe from the load balancer is configured correctly, including the firewall. |
| 141000 | ERROR | Config value is invalid (key=”%s”, value=”%s”, rc=%d) | Cause: The property setting value is invalid. Action: Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141001 | ERROR | Config key “%s” is invalid. | Cause:The specified property name is invalid. Action: Please contact support. |
| 141002 | ERROR | The value of config “%s” is empty. | CauseThe specified property’s setting value is empty. Action: Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141003 | ERROR | The value of config “%s” is not numeric. | Cause: The specified property’s setting value is not a numeric value. Action: Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141004 | ERROR | The value of config “%s” must be in the range from “%d” to “%d”. | Cause: The specified property’s setting value is out of range. Action: Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141005 | ERROR | Failed to init the object. | Cause: The App type or Res type is invalid. Action: Please contact support. |
| 141006 | ERROR | The component “%s” is unknown. | Cause: The specified JP1 component is invalid. Action: Please verify the specified JP1 component name. For a list of available JP1 components, refer to the JP1 component field in Creating a JP1/AJS Resource Hierarchy . |
| 141007 | ERROR | The logical host is empty. | Cause: The logical host name is not specified. Action: Please verify the specified logical host name. For acceptable logical host names, refer to the logical host name field in Creating a JP1/AJS Resource Hierarchy . |
| 141013 | ERROR | Stop failed. | Cause: Failed to call the resource stop operation, which is executed when an error occurs during resource startup. Action: Please check the corresponding JP1 logs. |
| 141014 | ERROR | Cannot be stopped. | Cause: The resource stop operation, executed when an error occurs during resource startup, failed. Action: Please check the corresponding JP1 logs. |
| 141018 | ERROR | %s | Cause: If an error occurs while starting JP1 processes during resource startup, the details of the exception will be output. Action: Please check the corresponding JP1 logs. |
| 141025 | ERROR | %s | Cause: If an error occurs while stopping JP1 processes during resource termination, the details of the exception will be output. Action: Please check the corresponding JP1 logs. |
| 141028 | ERROR | QuickCheck failed. | Cause: An abnormality was detected during resource monitoring. Please check the corresponding JP1 logs. |
| 141029 | ERROR | %s | Cause: If an error occurs while checking JP1 process status during resource monitoring, the details of the exception will be output. Action: Please check the corresponding JP1 logs. |
| 141303 | ERROR | Failed to stop “JP1_Base_%s”, rc=%d | Cause: Failed to stop the JP1/Base Windows service (“JP1_Base_logical_hostname”). Action: Please check the corresponding JP1 logs. |
| 141305 | ERROR | Failed to stop “JP1_Base_Event %s”, rc=%d | Cause: Failed to stop the JP1/Base Event Windows service (“JP1_Base_Event logical_hostname”). Action: Please check the corresponding JP1 logs. |
| 141307 | ERROR | Failed to start “JP1_Base_Event %s”, rc=%d | Cause: Failed to start the JP1/Base Event Windows service (“JP1_Base_Event logical_hostname”). Action: Please check the corresponding JP1 logs. |
| 141309 | ERROR | Failed to start “JP1_Base_%s”, rc=%d | Cause: Failed to start the JP1/Base Windows service (“JP1_Base_logical_hostname”). Action: Please check the corresponding JP1 logs. |
| 141312 | ERROR | Failed to stop “JP1_AJS2_%s”, rc=%d | Cause: Failed to stop the JP1/AJS3 Windows service (“JP1_AJS2_logical_hostname”). Action: Please check the corresponding JP1 logs. |
| 141314 | ERROR | Failed to start “JP1_AJS2_%s”, rc=%d | Cause: Failed to start the JP1/AJS3 Windows service (“JP1_AJS2_logical_hostname”). Action: Please check the corresponding JP1 logs. |
| 141401 | ERROR | Not found childTag(“%s”) | Cause: The specified child resource does not exist. Action: Please verify that the child resources (IP, Volume, or JP1/Base resources) specified during resource creation are correct. |
| 141402 | ERROR | Failed to execute command=[%s], rc=%d | Cause: The command to retrieve resource dependencies failed. Action: Please check the command line output in the log. |
| 141404 | ERROR | Failed to create dependency parentTag=[%s], childTag=[%s], rc=%d | Cause: Failed to create resource dependencies. Action: Please verify the existence of the parent and child resources. |
| 141406 | ERROR | Resource should be created on the local node. (local=%s, sys=%s) | Cause: The name does not match the local node. Action: Please contact support. |
| 141408 | ERROR | Invalid component label. (label=%s) | Cause: The JP1 component name specified during resource creation is invalid. Action: Please verify the specified JP1 component name. For a list of available JP1 components, refer to the JP1 component field in Creating a JP1/AJS Resource Hierarchy . |
| 141409 | ERROR | Error bringing resource “%s” in service on server “%s”’ | Cause: Failed to start the created resource. Action: Please check the corresponding JP1 logs. |
| 141503 | ERROR | A resource with the specified tag name “%s” already exists on the target machine “%s”. | Cause: The tag of the resource you attempted to extend already exists on the target node. Action: Please delete the corresponding resource hierarchy of the target node before extending a resource. |
| 141550 | ERROR | usage: %s [--server <server>] --tag <tag> <sub-command> sub-command: --set <cfg>=<value> --get <cfg> --default-get <cfg> --list-configs --show [--format <text|json>] |
Cause: The usage information was displayed because of an error in the arguments for the config.pl script, which handles property-related operations. Action: Check the log output and execute with the correct arguments. |
| 141552 | ERROR | resource “%s” not found on %s | Cause: The tag specified in the property configuration command does not exist. Action: Please specify the tag name of the existing resource. |
| 141553 | ERROR | “%s” is an unknown configuration. | Cause: The property name specified in the property configuration command is invalid. Action: Verify the property name using the --list-configs option, and then specify the correct property name. |
| 141554 | ERROR | The --set option must be in the format “<cfg>=<value>”. | Cause: The format of the property name and value specified in the property configuration command is invalid. Action: Please execute the command with the correct format. |
| 141602 | WARN | Could not resolve hostname “%s”. | Cause: Failed to resolve the logical host name. Action: Configure the network so that virtual IP addresses can be obtained using logical host names. |
| 141603 | WARN | Not found IP resource of “%s (%s)”. | Cause: There is no IP resource in ISP corresponding to the logical host’s IP address. Action: Ensure that the IP resource corresponding to the logical host’s IP address exists, and that it is in the ISP state on the server where the resource is being created. |
| 141606 | WARN | Not found FS resource (logical host: “%s”, shared file directory: “%s”). | Cause: The volume resource corresponding to the storage location for shared files used by the logical host does not exist. Action: Ensure that the volume resource corresponding to the storage location for the shared files used by the logical host exists, and that it is in the ISP state on the server where the resource is being created. |
| 141611 | ERROR | usage: depResources.pl <ip|ip-tag|fs|fs-tag|jp1ajsbase|jp1ajsbase-tag> <logicalHost> | Cause: The usage information was displayed because of invalid arguments for depResources.pl, a script that retrieves dependency information. Action: Please specify the correct arguments based on the usage information.. |
| 141650 | ERROR | usage: %s --list-event-server|--directory <event-server> | Cause: The usage information was displayed because of invalid arguments for parse-index.pl, a script that retrieves logical host information from the JP1 event server index file (*1) Action: Please specify the correct arguments based on the usage information. |
| 141652 | ERROR | Cannot open file “%s” | Cause: Failed to open the JP1 event server index file (*1). Action: Please check the status of the event server index file. |
| 141654 | ERROR | No logical host candidates were found in the index file. | Cause: No logical host candidates were found in the JP1 event server index file (*1). Action: Please configure the logical host for JP1. |
| 141656 | ERROR | There is no event-server “%s” entry in the index file. | Cause: No event-server entry matching the specified logical host was found in the JP1 event server index file (*1). Action: Check the configuration of the JP1 logical host and specify an existing logical host. |
| 142000 | Error | Resource should be created on the local node. (local=<local node name>, sys=<Execution node name>) | Cause: The node you attempted to create the resource on is not the local node. Action: Create the resource on the local node. |
| 142002 | Error | hulname "<Windows service name>" is invalid. create error | Cause: The specified Windows service does not exist. Action: Specify the appropriate HULFT Windows service name. |
| 142003 | Error | hulexep "<folder path>" is invalid. create error | Cause: The specified folder path does not exist. Action: Specify the path to the appropriate folder containing the HULFT executable module. |
| 142004 | Error | hulpath "<folder path>" is invalid. create error | Cause: The specified folder path does not exist. Action: Specify the path to the folder containing the appropriate HULFT system operating environment settings files. |
| 142005 | Error | Failed to bring resource "<HULFT resource tag name>" in service on server "<server name>" | Cause: Failed to start the resource on the specified server. Action: Check the configuration parameters, including hulname, hulexep, and hulpath. |
| 142006 | Error | Failed to create dependency with IP resource "<IP Address resource tag name>" | Cause: Failed to create a dependency with the specified IP address resource. Action: Verify that the specified IP address resource exists. |
| 142007 | Error | Failed to create dependency with Volume resource "<volume resource tag name>" | Cause:Failed to create a dependency on the specified volume resource. Action: Verify that the specified volume resource exists. |
| 142011 | Error | A resource with the specified tag name "<HULFT resource tag name>" already exists on the target machine "<target node name>". | Cause: A tag with the same name already exists on the resource extension target node. Action: Ensure that tag names do not conflict. |
| 142013 | Error | Config value is invalid (key="<property name>", value="<value>", rc=<return value>) | Cause:The value for the key is incorrect. Action: Specify the appropriate value to change the settings. |
| 142018 | Error | [<HULFT Windows service name>] failed to start. | Cause: Failed to start the displayed HULFT Windows service. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142019 | Error | [<HULFT Windows service name>] is not alive. | Cause: The displayed HULFT Windows service is not running. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142020 | Error | <Exception Information> | Cause: An exception occurred during the restore process. Action: Check the displayed exception information. |
| 142022 | Error | [<HULFT Windows service name>] failed to stop | Cause: Failed to stop the displayed HULFT Windows service. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142023 | Error | <Exception Information> | Cause: An exception occurred during the remove process. Action: Check the displayed exception information. |
| 142025 | Error | <Exception Information> | Cause: An exception occurred during the quickCheck process. Action: Check the displayed exception information. |
| 142026 | Error | Path [$path] is not directory. | Cause: The path specified in hulexep or hulpath is not an actual folder path. Action: Specify the correct folder path for HULEXEP or HULPATH. |
| 142027 | Error | [<Property name>] must be a positive integer. (value=<Input value>) | Cause: The entered property value is not a positive integer. Action: Enter a positive integer. |
| 142028 | Error | [<Property name>] must be greater than or equal to <minimum value> and less than or equal to <maximum value>. (value=<Input value>) | Cause: The entered property value is outside the specified range. Action: Enter a value within the range. |
| 142029 | Error | Failed to find ‘myhostname’ entry in hulenv.conf. (rc=<command execution result>, path=[<hulenv.cnf path>]) | Cause: The command to search for the entry ‘myhostname’ in hulenv.cnf under the HULPATH folder failed. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142030 | Error | Not found ‘myhostname’ entry in hulenv.conf. (path=[%s]) | Cause: The entry for ‘myhostname’ cannot be found in the hulenv.cnf file under the HULPATH folder. Action: Check the contents of hulenv.cnf. Also, check the following items in the error log 142032 output immediately before this error: |
| 142031 | Error | Failed to get volume (hulpath=[<HULPATH folder path>]) | Cause: Failed to retrieve volume label information from hulpath. Action: Check the folder path information in hulpath. |
| 142032 | Error* | command=[<Command executed>], expected=<Expected return code>, rc=<Actual return code> <Execution result output (multiple lines)> |
Cause: The executed command failed. (*If the command executes successfully, this log is output at the info level. It is output at the error level only when execution fails.) |
| 142033 | Error | [<HULFT Windows service name>] does not exist as a Windows Service. | Cause: The Windows service specified in hulname does not exist. Action: Check the Windows service name specified in hulname. |
| 142034 | Error | Config [<HULFT Windows service name>] does not exist. | Cause: There are no lines containing "BINARY_PATH_NAME" in the output of the sc command. Action: Check the following items in the log 142032 output immediately before this error: |
| 142035 | Error | [<HULFT Windows service name>] does not exist as a Windows Service. | Cause: The Windows service specified in hulname does not exist. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142036 | Error | Failed to get HULFT windows service list. (rc=%d) | Cause: The command to retrieve a list of HULFT Windows services failed to execute. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142037 | Error | Failed to get HULEXEP path. | Cause: Failed to retrieve the folder path for HULEXEP. Action: Check the log output (142033 or 142034) immediately before this error. |
| 142038 | Error | Not found [PATH] section in [%s] | Cause: The [PATH] section could not be found in the hulft.ini configuration file in the HULEXEP folder. Action: Check the hulft.ini file. |
| 142039 | Error | Not found ‘HULPATH’ entry. (End of [PATH] section in [%s]) | Cause: The HULPATH entry could not be found in the [PATH] section of the hulft.ini configuration file in the HULEXEP folder. Action: Check the hulft.ini file. |
| 142040 | Error | Not found ‘HULPATH’ entry. (End of hulft.ini) | Cause: The HULPATH entry could not be found in the [PATH] section of the hulft.ini configuration file in the HULEXEP folder. (Scanned to the end of the file) Action: Check the hulft.ini file. |
| 142041 | Error | Failed to get HULEXEP. (serviceName=[<HULFT Windows service name>]) | Cause: Failed to retrieve the folder path for HULEXEP. Action: Check the log output 142037 immediately before this error. |
| 142042 | Error | Failed to get HULPATH. (serviceName=[<HULFT Windows service name>], HULEXEP=[<HULEXEP folder path>]) | Cause: Failed to retrieve the folder path for HULPATH Action: Check the log output (142038, 142039 or 142040) immediately before this error. |
| 142043 | Error | Invalid operation string. (operation=<Processing type string>) | Cause: The argument passed to the utlsvcctl.exe command is invalid. Action: Please contact support. |
| 142044 | Error | [<HULFT Windows service name>] is not running. | Cause: The HULFT Windows service is not running. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142045 | Error | [<HULFT Windows service name>] failed to extract port information from [<hulenv.cnf path>] file. (rc=<Command execution result>) | Cause: The command to extract the Receive Port (rcvport), Command Acknowledge Port (sddport), and Observe Port (obsport) from hulenv.cnf failed. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142046 | Error | [<HULFT Windows service name>] failed to check the port "<port number>". (rc=<Command execution result>) | Cause: The command to check the specified port failed to execute. Action: Check the following items in the error log 142032 output immediately before this error: |
| 142048 | Error | [%s] failed to change startup type. | Cause: The startup type for the target HULFT Windows service could not be changed to "Manual". Action: Check the following items in the error log 142032 output immediately before this error: |
| 142050 | Error | usage: service.pl <sub-command> | Cause: The usage message was displayed because invalid arguments were passed to the script service.pl (which retrieves HULFT Windows service names). Action: This is an internal error; please contact support. |
| 142053 | Error | Failed to get myhostname from hulenv.conf. | Cause: Failed to retrieve information set in the myhostname entry in the hulenv.cnf file. Action: Check the log output (142029 or 142030) immediately before this error. |
| 142056 | Warning | Could not resolve hostname "%s". | Cause: Failed to convert the hostname set in myhostname to an IP address. Action: Check the mapping between the hostname and the virtual IP address. |
| 142057 | Error | Failed to get mountpoint. | Cause: Failed to retrieve volume information from the HULPATH folder path. Action: Check the log output (142031) immediately before this error. |
| 142060 | Error | usage: getDependentCandidates.pl <ip|fs> [<hulpath>] | Cause: The usage message was displayed because invalid arguments were passed to the script getDependentCandidates.pl (which retrieves candidate resources for creating dependencies). Action: This is an internal error; please contact support. |
| 142061 | Error | usage: config.pl [--server <server>] --tag <tag> <sub-command> | Cause: The usage message was displayed because invalid arguments were passed to the script config.pl (which operates properties). Action: This is an internal error; please contact support. |
| 142063 | Error | resource "<tag name>" not found on %s | Cause: The resource for the tag specified in the config.pl script (which operates properties) does not exist. Action: This is an internal error; please contact support. |
| 142064 | Error | "%s" is an unknown configuration. | Cause: The property name specified in the config.pl script (which operates properties) does not exist. Action: This is an internal error; please contact support. |
| 142065 | Error | The --set option must be in the format "<cfg>=<value>". | Cause: The format of the "--set" option specified in the config.pl script (which operates properties) is invalid. Action: This is an internal error; please contact support. |
*1: This is the configuration file which maps logical hostnames to their respective settings and data storage paths used by the event server. For details, please refer to the JP1 documentation .
Post your comment on this topic.