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.


Code Severity Message Cause/Action
128005 ERROR END failed %s of "%s" on server "%s" due to a "%s" signal

Cause: The quickCheck of {resource} on {server} failed due to an operating system signal {signal}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128008 ERROR Usage: quickCheck -t <tag name> -i <id>

Cause: Incorrect arguments have been supplied to the dmmp device quickCheck command preventing it from running.

Action: Make sure all software components are properly installed and at the correct version. Rerun the command and supply the correct argument list: -t <Resource Tag> and -i <Resource ID> that identifies the dmmp device resource to be quickChecked.

128010 ERROR quickCheck for "%s" failed checks of underlying paths, initiate recovery. retry count=%s.

Cause: The dmmp kit failed to quickCheck a device after {count} times of retries. A recovery of the protected dmmp resource will be executed.

Action: Check adjacent log messages for further details and related messages.

128021 ERROR unable to find device for uuid "%s".

Cause: The device could not be found by unique id during a restore operation.

Action: Verify that the resource is configured properly. Rerun the command and supply the correct device id that identifies the dmmp device resource to be restored.

128025 ERROR Device "%s" failed to unlock.

Cause: A non working {device} was detected and could not be unlocked during the restore operation.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128026 ERROR Device "%s" failed to lock.

Cause: The {device} could not be locked during the resotre.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128031 ERROR unable to find device for uuid "%s".

Cause: The device could not be found by unique id during the remove operation.

Action: Verify that the resource is configured properly. Rerun the command and supply the correct device id that identifies the dmmp device resource to be removed.

128034 ERROR Device "%s" failed to unlock.

Cause: The {device} could not be unlocked during the remove.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128036 ERROR unable to load existing information for device with uuid "%s".

Cause: The device information could not be loaded by unique id.

Action: Make sure the resource is configured properly. Rerun the command and supply the correct device id that identifies the dmmp device resource.

128037 ERROR unable to load existing information for device "%s".

Cause: The device information could not be loaded by name.

Action: Make sure the resource is configured properly. Rerun the command and supply the correct device name that identifies the dmmp device resource.

128038 ERROR unable to load existing information for device, no dev or uuid defined.

Cause: The device information could not be loaded since neither a unique device id nor name of the device were defined.

Action: Make sure the resource is configured properly. Rerun the command and supply the correct device id or name that identifies the dmmp device resource.

128041 ERROR unable to load existing information for device with uuid "%s".

Cause: The device information could not be loaded by unique id.

Action: Make sure the resource is configured properly. Rerun the command and supply the correct device id that identifies the dmmp device resource.

128057 ERROR All paths are failed on "%s".

Cause: LifeKeeper detected all paths listed to the protected dmmp device are in the failed state.

Action: Check adjacent log messages for further details and related messages.

128058 ERROR could not determine registrations for "%s"! All paths failed.

Cause: LifeKeeper could not determine registrations for protected dmmp {device}. All paths to the dmmp {device} are in the failed state.

Action: Check adjacent log messages for further details and related messages.

128059 WARN path "%s" no longer configured for "%s", remove from path list.

Cause: LifeKeeper detected listed {path} to protected {device} is not valid anymore and will remove it from the path list.

Action: Check adjacent log messages for further details and related messages.

128060 WARN registration failed on path "%s" for "%s".

Cause: LifeKeeper failed the registration on {path} for protected dmmp {device}.

Action: Check adjacent log messages for further details and related messages.

128062 ERROR all paths failed for "%s".

Cause: LifeKeeper failed to verify a valid path to protected dmmp {device}.

Action: Check adjacent log messages for further details and related messages.

128072 ERROR The daemon "%s" does not appear to be running and could not be restarted. Path failures may not be correctly handled without this daemon.

Cause: LifeKeeper failed to verify dmmp daemon is running and could not restart it.

Action: Check adjacent log messages for further details and related messages.

128078 ERROR "%s" resource type is not installed on "%s".

Cause: The Device Mapper Multipath Recovery Kit for dmmp device support is not installed on the system.

Action: Install the steeleye-lkDMMP Device Mapper Multipath Recovery Kit rpm on the system.

128083 ERROR This script must be executed on "%s".

Cause: An incorrect system name has been supplied as an argument to the devicehier script used to create the dmmp device resource.

Action: Make sure the cluster nodes and comm-paths are properly configured. Supply the correct system name to the devicehier script. The name must match the name of the system on which the command is run.

128084 ERROR The device %s is not active.

Cause: LifeKeeper failed to find the specified {device} as a valid device on the system during resource creation.

Action: Check adjacent log messages for further details and related messages. Rerun the command and supply the correct argument list: -t <Resource Tag> and -i <Resource ID> that identifies the dmmp device resource to be created.

128086 ERROR Failed to create "%s" hierarchy.

Cause: LifeKeeper failed to create resource hierarchy for {device}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128088 ERROR Error creating resource "%s" on server "%s"

Cause: LifeKeeper failed to create the resource with {tagname} on {server}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128090 ERROR Failed to create dependency "%s"-"%s" on system "%s".

Cause: LifeKeeper failed to create dependency {resource tag name} – {resource tag name} on {system} during creation.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128091 ERROR Error creating resource "%s" on server "%s"

Cause: LifeKeeper failed to create {resource} on {system}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128101 ERROR "%s" constructor requires a valid argument.

Cause: LifeKeeper failed to create an object for the dmmp resouce during construction.

Action: Rerun the command and supply the correct argument list: -t <Resource Tag> and -i <Resource ID> that identifies the dmmp device resource.

128102 ERROR Invalid tag "%s".

Cause: A resource instance could not be found for the given tag name.

Action: Make sure the resource is configured properly. Rerun the command and supply the correct argument list: -t <Resource Tag> and -i <Resource ID> that identifies the dmmp device resource.

128111 ERROR Failed to get registrations for "%s": %s. Verify the storage supports persistent reservations.

Cause: LifeKeeper failed to get the registrations of {device} with the message, "bad field in Persistent reservation in cdb".

Action: Verify if the storage supports persistent reservations. Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128112 ERROR Failed to get registrations for "%s": %s. Verify the storage supports persistent reservations.

Cause: LifeKeeper failed to get the registrations of {device} with the message, "illegal request".

Action: Verify if the storage supports persistent reservations. Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128136 ERROR A previous quickCheck with PID "%s" running for device "%s" has been terminated.

Cause: LifeKeeper detected that a previous quickCheck operation is still running during the dmmp resource restore operation. It has been terminated by LifeKeeper.

Action: Check adjacent log messages for further details and related messages.

128137 ERROR SCSI reservation conflict on %s during LifeKeeper resource initialization. Manual intervention required.

Cause: LifeKeeper detected a SCSI reservation conflict on {device} during dmmp resource restore.

Action: Check adjacent log messages for further details and related messages. Manual intervention and fix of the reservation conflict on {device} is required.

128138 ERROR unable to clear registrations on %s.

Cause: LifeKeeper failed to clear all the registrations on {device}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128140 WARN registration failed on path %s for %s.

Cause: LifeKeeper failed to make the registration on {path} for {device}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128143 ERROR reserve failed (%d) on %s.

Cause: LifeKeeper failed to make reservation for {resource} on {device}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128145 ERROR The server ID "%s" returned by "%s" is not valid.

Cause: LifeKeeper failed to generate a valid host {ID}.

Action: The ID used to register a device is made up of 1 to 12 Hex digits that uniquely identifies the server in the cluster. Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128146 ERROR device failure on %s. SYSTEM HALTED.

Cause: LifeKeeper detected failure on {device} and will reboot the server.

Action: Check adjacent log messages for further details and related messages.

128148 ERROR device failure on %s. SYSTEM HALTED DISABLED.

Cause: LifeKeeper detected a failure on {device}. The reboot was skipped due to LifeKeeper configuration.

Action: Check adjacent log messages for further details and related messages. Turn on the configuration "SCSIHALT" to make the reboot available for any detected device failure.

128149 ERROR device failure or SCSI Error on %s. SENDEVENT DISABLED.

Cause: LifeKeeper detected a failure on {device}. The event generation was skipped due to LifeKeeper configuration.

Action: Check adjacent log messages for further details and related messages. Turn on the configuration "SCSIEVENT" to make the sendevent available for any detected device failure.

128150 ERROR %s does not have EXCLUSIVE access to %s, halt system.

Cause: LifeKeeper detected a reservation conflict for {device} on {server} and will reboot the server.

Action: Check adjacent log messages for further details and related messages.

128151 ERROR %s does not have EXCLUSIVE access to %s, halt system DISABLED.

Cause: LifeKeeper detected a reservation conflict for {device} on {server}. The reboot was skipped due to LifeKeeper configuration.

Action: Check adjacent log messages for further details and related messages. Turn on the configuration "RESERVATIONCONFLICT" to make the reboot available for any detected reservation conflicts.

128154 WARN unable to flush buffers on %s.

Cause: LifeKeeper failed to flush the buffers for {device} during dmmp resource remove.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128157 WARN %s utility not found, limited healthcheck for %s.

Cause: LifeKeeper failed to find "dd" utility for the health check of {device}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128160 ERROR %s failed to read %s.

Cause: LifeKeeper failed a disk I/O test for {device} when using {utility}.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128163 ERROR Registration ID "%s" for "%s" is not valid.

Cause: LifeKeeper failed to generate a valid registration {ID} for {device}.

Action: The ID used to register a device is made up of 4 Hex digits derived from the path to the device. Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128170 ERROR Usage: canextend <Template system name> <Template tag name>
128173 ERROR Usage error OSUquickCheck
128174 ERROR both tag and id name not specified
128175 ERROR Failed multipath check.
128500 ERROR Usage error

Cause: Incorrect arguments have been supplied to the dmmp device restore command preventing it from running.

Action: Rerun the command and supply the correct argument list: -t <Resource Tag> and -i <Resource ID> that identifies the dmmp device resource to be restored.

128504 ERROR "%s" resource type is not installed on "%s".

Cause: The Device Mapper Multipath Recovery Kit for dmmp device support is not installed on the system.

Action: Install the steeleye-lkDMMP Device Mapper Multipath Recovery Kit rpm on the system.

128506 ERROR Usage error

Cause: Incorrect arguments have been supplied to the dmmp device devShared command preventing it from running.

Action: Rerun the command and supply the correct argument list: <Template Resource System Name> and <Template Resource Tag> that identifies the dmmp device resource to be created.

128507 FATAL This script must be executed on "%s".

Cause: An incorrect system name has been supplied as an argument to the devicehier script used to create the dmmp device resource.

Action: Supply the correct system name to the devicehier script. The name must match the name of the system on which the command is run.

128511 ERROR Failed to get the ID for the device "%s". Hierarchy create failed.

Cause: The devicehier script used to create the dmmp device resource was unable to determine the SCSI ID for the supplied device.

Action: Check that the supplied device path exists and that is for a supported SCSI storage array.

128512 ERROR Failed to get the disk ID for the device "%s". Hierarchy create failed.

Cause: The devicehier script used to create the dmmp disk resource was unable to determine the SCSI ID for the supplied disk.

Action: Check that the supplied device path exists and that is for a supported SCSI storage array.

128513 ERROR Failed to create the underlying resource for device "%s". Hierarchy create failed.

Cause: The creation of the underlying dmmp disk resource failed.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128515 ERROR Error creating resource "%s" on server "%s"

Cause: The creation of the dmmp device resource failed.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128517 ERROR Failed to create dependency "%s"-"%s" on system "%s".

Cause: The parent child dependency creation between the dmmp device and dmmp disk resources failed.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128519 ERROR Error creating resource "%s" on server "%s"

Cause: The attempt to bring the newly created dmmp device resource in service has failed.

Action: Check adjacent log messages for further details and related messages. You must correct any reported errors before retrying the operation.

128521 ERROR Either TEMPLATESYS or TEMPLATETAG argument missing

Cause: Incorrect arguments have been supplied to the extend command for the dmmp device resource.

Action: Rerun the dmmp device resource extend and supply the correct template system and tag names.

128540 ERROR Usage error

Cause: Incorrect arguments have been supplied to the dmmp device getId command used to retrieve the SCSI ID.

Action: Rerun the command and supply the correct argument list: -i <device path> or -b <device ID>.

128541 ERROR Usage error

Cause: Incorrect arguments have been supplied to the command used to delete the dmmp device resource.

Action: Rerun the command and supply the correct argument list: -t <dmmp device resource tag>.

128543 ERROR device node \"$dev\" does not exist.

Cause: The device node required for restoring the dmmp device resource does not exist. The allocated wait time in restore for udev device creation has been exceed.

Action: Rerun the dmmp device resource restore once udev has created the device.

128544 ERROR Usage error

Cause: Incorrect arguments have been supplied to the remove command used to take the dmmp device resource out of service.

Action: Rerun the command and supply the correct argument list: -t <dmmp device resource tag>.

Feedback

Thanks for your feedback.

Post your comment on this topic.

Post Comment