Control F を使用して、各カタログの特定のエラーコードを検索します。エラーコードの検索には、画面右上の検索ボックスをご利用ください。
| コード | 重大度 | メッセージ | 原因/処置 |
|---|---|---|---|
| 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: Refer to the “Property Name” column of the Properties table in Operation for Properties of JP1/AJS Resource . |
| 141002 | ERROR | The value of config “%s” is empty. |
Cause: The 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 shutdown procedure executed when an error occurs during resource startup. Action: Please check the logs on the corresponding JP1 side. |
| 141014 | ERROR | Cannot be stopped. |
Cause: Failed to execute the resource shutdown procedure when an error occurs during resource startup. Action: Please check the logs on the corresponding JP1 side. |
| 141018 | ERROR | %s |
Cause: When an exception occurs during the startup process of the JP1 processes due to resource initiation, the exception details are output. Action: Please check the logs on the corresponding JP1 side. |
| 141025 | ERROR | %s |
Cause: When an exception occurs during the termination process of the JP1 process due to resource stoppage, the exception details are output. Action: Please check the logs on the corresponding JP1 side. |
| 141028 | ERROR | QuickCheck failed. |
Cause: Resource monitoring detected an anomaly. Action: Please check the logs on the corresponding JP1 side. |
| 141029 | ERROR | %s |
Cause: When an exception occurs during the process of verifying the status of JP1 processes through resource monitoring, the details of that exception are output. Action: Please check the logs on the corresponding JP1 side. |
| 141401 | ERROR | Not found childTag(“%s”) |
Cause: The specified child resource does not exist. Action: Confirm that the child resources specified when creating the resource (IP resource, File System resource, or JP1/Base resource) 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 confirm the existence of 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 logs on the corresponding JP1 side. |
| 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 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>] |
Cause: The usage message was displayed because there was an error in the arguments for the config.pl script, which performs property setting-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 settings-related 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 settings-related command is invalid. Action: 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>”. |
Cause: The format of the property name and value specified in the property settings command is invalid. Action: Please execute according to the appropriate 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 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”). |
Cause: The File System resource corresponding to the storage location for shared files used by the logical host does not exist. Action: Ensure that a File System 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> |
Cause: The usage message was displayed because the arguments for depResources.pl, the script that retrieves dependencies, were invalid. Action: Please specify the correct arguments based on the usage information. |
| 141650 | ERROR | usage: %s —list-event-server|—directory <event-server> |
Cause: 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. 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: The JP1 event server index file (*1) does not contain any candidate logical hosts. Action: Please configure the logical host for JP1. |
| 141656 | ERROR | There is no event-server “%s” entry in the index file. |
Cause: The JP1 event server index file (*1) does not contain an entry for the event server matching the specified logical host. Action: 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 .
このトピックへフィードバック