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 | An error occurred during internal processing. | Please contact our Support Team. |
| 18224 | INFO | curl response error. (HTTP status=[$http_status], response=[$response] | Access to Amazon S3 objects is temporarily unavailable. | No action is generally required, but if this occurs frequently, please contact support. |
| 18225 | INFO | curl call failed. (err=$ret)(output=$response) | Access to Amazon S3 objects is temporarily unavailable. | No action is generally required, but if this occurs frequently, please contact support. |
| 18227 | ERROR | Abandon retrying curl: max attempts reached | The maximum number of access attempts to an Amazon S3 QWK object has been reached. | If this message appears frequently, adjust QWK_CURL_RETRY. |
| 18228 | ERROR | Abandon retrying curl: timeout exceeded | Accessing Amazon S3 QWK objects is taking too long. | If this message appears frequently, adjust QWK_CURL_RETRY_TIMEOUT. |
| 18230 | ERROR | Unexpected error in retry_curl | An error occurred during internal processing. | Please contact our Support Team. |
| 141000 | ERROR | Config value is invalid (key=”%s”, value=”%s”, rc=%d) | The property setting value is invalid. | Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141001 | ERROR | Config key “%s” is invalid. | The specified property name is invalid. | Please contact support. |
| 141002 | ERROR | The value of config “%s” is empty. | The specified property’s setting value is empty. | Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141003 | ERROR | The value of config “%s” is not numeric. | The specified property’s setting value is not a numeric value. | 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”. | The specified property’s setting value is out of range. | Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141005 | ERROR | Failed to init the object. | The App type or Res type is invalid. | Please contact support. |
| 141006 | ERROR | The component “%s” is unknown. | The specified JP1 component is invalid. | 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. | The logical host name is not specified. | 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. | Failed to call the resource shutdown procedure executed when an error occurs during resource startup. | Please check the logs on the corresponding JP1 side. |
| 141014 | ERROR | Cannot be stopped. | Failed to execute the resource shutdown procedure when an error occurs during resource startup. | Please check the logs on the corresponding JP1 side. |
| 141018 | ERROR | %s | When an exception occurs during the startup process of the JP1 processes due to resource initiation, the exception details are output. | Please check the logs on the corresponding JP1 side. |
| 141025 | ERROR | %s | When an exception occurs during the termination process of the JP1 process due to resource stoppage, the exception details are output. | Please check the logs on the corresponding JP1 side. |
| 141028 | ERROR | QuickCheck failed. | Resource monitoring detected an anomaly. | Please check the logs on the corresponding JP1 side. |
| 141029 | ERROR | %s | When an exception occurs during the process of verifying the status of JP1 processes through resource monitoring, the details of that exception are output. | Please check the logs on the corresponding JP1 side. |
| 141303 | ERROR | Failed to stop “JP1_Base_%s”, rc=%d | Failed to stop the JP1/Base Windows service (“JP1_Base_logical_hostname”). | Please check the logs on the corresponding JP1 side. |
| 141305 | ERROR | Failed to stop “JP1_Base_Event %s”, rc=%d | Failed to stop the JP1/Base Event Windows service (“JP1_Base_Event logical_hostname”). | Please check the logs on the corresponding JP1 side. |
| 141307 | ERROR | Failed to start “JP1_Base_Event %s”, rc=%d | Failed to start the JP1/Base Event Windows service (“JP1_Base_Event logical_hostname”). | Please check the logs on the corresponding JP1 side. |
| 141309 | ERROR | Failed to start “JP1_Base_%s”, rc=%d | Failed to start the JP1/Base Windows service (“JP1_Base_logical_hostname”). | Please check the logs on the corresponding JP1 side. |
| 141312 | ERROR | Failed to stop “JP1_AJS2_%s”, rc=%d | Failed to stop the JP1/AJS3 Windows service (“JP1_AJS2_logical_hostname”). | Please check the logs on the corresponding JP1 side. |
| 141314 | ERROR | Failed to start “JP1_AJS2_%s”, rc=%d | Failed to start the JP1/AJS3 Windows service (“JP1_AJS2_logical_hostname”). | Please check the logs on the corresponding JP1 side. |
| 141401 | ERROR | Not found childTag(“%s”) | The specified child resource does not exist. | Confirm that the child resources specified when creating the resource (IP resource, Volume resource resource, or JP1/Base resource) are correct. |
| 141402 | ERROR | Failed to execute command=[%s], rc=%d | The command to retrieve resource dependencies failed. | Please check the command line output in the log. |
| 141404 | ERROR | Failed to create dependency parentTag=[%s], childTag=[%s], rc=%d | Failed to create resource dependencies. | Please confirm the existence of parent and child resources. |
| 141406 | ERROR | Resource should be created on the local node. (local=%s, sys=%s) | The name does not match the local node. | Please contact support. |
| 141408 | ERROR | Invalid component label. (label=%s) | The JP1 component name specified during resource creation is invalid. | 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”’ | Failed to start the created resource. | Please check the logs on the corresponding JP1 side. |
| 141503 | ERROR | A resource with the specified tag name “%s” already exists on the target machine “%s”. | The tag of the resource you attempted to extend already exists on the target node. | Please delete the corresponding resource hierarchy of the target node before performing the expansion process. |
| 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>] |
The usage message was displayed because there was an error in the arguments for the config.pl script, which performs property setting-related operations. | Check the log output and execute with the correct arguments. |
| 141552 | ERROR | resource “%s” not found on %s | The tag specified in the property settings-related command does not exist. | Please specify the tag name of the existing resource. |
| 141553 | ERROR | “%s” is an unknown configuration. | The property name specified in the property settings-related command is invalid. | Confirm the property name using the —list-configs option and specify the correct property name. |
| 141554 | ERROR | The —set option must be in the format “<cfg>=<value>”. | The format of the property name and value specified in the property settings command is invalid. | Please execute according to the appropriate format. |
| 141602 | WARN | Could not resolve hostname “%s”. | Failed to resolve the logical host name. | Configure the network so that virtual IP addresses can be obtained using logical host names. |
| 141603 | WARN | Not found IP resource of “%s (%s)”. | There is no IP resource in ISP corresponding to the logical host’s IP address. | Ensure that an IP resource corresponding to the logical host’s IP address exists and that the server creating the resource is in ISP state. |
| 141606 | WARN | Not found FS resource (logical host: “%s”, shared file directory: “%s”). | The Volume resource corresponding to the storage location for shared files used by the logical host does not exist. | Ensure that a Volume resource exists, corresponding to the storage location for shared files used by the logical host, and that the server creating the resource enters ISP state. |
| 141611 | ERROR | usage: depResources.pl <ip|ip-tag|fs|fs-tag|jp1ajsbase|jp1ajsbase-tag> <logicalHost> | The usage message was displayed because the arguments for depResources.pl, the script that retrieves dependencies, were invalid. | Please specify the correct arguments based on the usage information. |
| 141650 | ERROR | usage: %s —list-event-server|—directory <event-server> | The usage message was displayed because the arguments for parse-index.pl, a script that retrieves logical host information from the JP1 event server index file (*1), were invalid. | Please specify the correct arguments based on the usage information. |
| 141652 | ERROR | Cannot open file “%s” | Failed to open the JP1 event server index file (*1). | Please check the status of the event server index file. |
| 141654 | ERROR | No logical host candidates were found in the index file. | The JP1 event server index file (*1) does not contain any candidate logical hosts. | Please configure the logical host for JP1. |
| 141656 | ERROR | There is no event-server “%s” entry in the index file. | The JP1 event server index file (*1) does not contain an entry for the event server matching the specified logical host. | Check the configuration of the JP1 logical host and specify an existing logical host. |
*1 : This is the configuration file which maps logical host names to the paths where the event server stores its settings and data. For details, please refer to the JP1 manual .
Post your comment on this topic.