Combined Message Catalog

Cause: Unable to establish valid login credentials for user {user}. The pam_setcred call returned: {retval}.

Action: Check /var/log/security and /var/log/messages for more information.

Cause: Unable to clear login credentials for user {user}. The pam_setcred call returned: {retval}.

Action: Check /var/log/security and /var/log/messages for more information.

Cause: System name did not get removed from /etc/hosts file.

Action: Remove system name manually then restart the GUI server, then enter the following:
run <action name>

Cause: The GUI server terminated due to an abnormal condition.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: LifeKeeper was unable to find the resource {tag} on {server}.

Cause: LifeKeeper was unable to run pre-extend checks because it was unable to find the script CANEXTEND on {server}.

Action: Check your LifeKeeper configuration.

Cause: LifeKeeper was unable to extend the resource {resource} on {server}.

Cause: LifeKeeper was unable to extend the resource hierarchy because it was unable to the find the script EXTEND on {server}.

Action: Check your LifeKeeper configuration.

Cause: LifeKeeper was unable to extend the resource {resource} on {server}.

Cause: The name provided for a resource is already in use.

Action: Either choose a different name for the resource, or use the existing resource.

Cause: The name or id provided for a resource is already in use.

Action: Either choose a different name or id for the resource or use the existing resource.

Cause: An unexpected failure occurred while creating a resource.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The IP address provided is neither an IPv4 nor an IPv6 address.

Action: Please check the name or address provided and try again.
If a name was provided, verify that name resolution returns a valid IP address.

Cause: LCD failed to fetch resource information for resource id {id} during resource recovery.

Action: Verify the input resource id and retry the recovery operation.

Cause: Local recovery failed for resource {resource}.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: Remotely removing a resource from service failed while attempting to find the resource by tag name {tag}.

Action: Check input tag name and retry the recovery operation.

Cause: Remotely removing a resource from service failed given that the tag name {tag} is not a shared resource.

Action: Check input tag name and retry the recovery operation.

Cause: Remote transfer of an in service resource failed given tag name {tag}.

Action: Check input tag name and retry the recovery operation.

Cause: LifeKeeper failed to find a shared resource by {tag} name during remote transfer of a resource in service from a remote {machine}.

Action: Check input tag name and retry the recovery operation.

Cause: Parallel recovery failed to initialize the list of resources in the hierarchy.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: Parallel recovery failed to fork a new process attempting to restore a single resource.

Cause: Parallel recovery failed to reserve a single resource from the collective hierarchy.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A single sub process of a resource recovery is hung during parallel recovery of a whole resource hierarchy.

Action: A kill of the hanging sub process will be executed automatically.

Cause: Failed to kill the hung sub process.

Cause: Writing an on-disk version of an in-memory data object failed attempting to create the intermediate folder. This is a system error.

Action: Check log for the error information in detail and determine why the intermediate folder is not created.

Cause: Writing an on-disk version of an in-memory data object failed while attempting to open a temporary file. This is a system error.

Action: Check log for the error information in detail and determine why the file is not successfully opened.

Cause: Writing an on-disk version of an in-memory data object failed while attempting to write to a temporary file. This is a system error.

Action: Check log for the error information in detail and determine why the file writing is failed.

Cause: Writing an on-disk version of an in-memory data object failed while attempting to fsync a temporary file. This is a system error.

Action: Check log for the error information in detail and determine why the "fsync" is failed.

Cause: Writing an on-disk version of an in-memory data object failed while attempting to close a temporary file. This is a system error.

Action: Check log for the error information in detail and determine why the file closing is failed.

Cause: Writing an on-disk version of an in-memory data object failed while attempting to rename a temporary file {file} to original file {file}. This is a system error.

Action: Check log for the error information in detail and determine why the file renaming is failed.

Cause: Writing an on-disk version of an in-memory data object failed while attempting to open an intermediate directory {directory}. This is a system error."

Action: Check log for the error information in detail and determine why the directory open is failed.

Cause: Writing an on-disk version of an in-memory data object failed while attempting to fsync an intermediate directory {directory}. This is a system error.

Action: Check log for the error information in detail and determine why the directory "fsync" is failed.

Cause: Writing an on-disk version of an in-memory data object failed while attempting to close an intermediate directory {directory}. This is a system error.

Action: Check log for the error information in detail and determine why the directory close is failed.

Cause: Writing an on-disk version of an in-memory data object failed as the final size {size} bytes of written data is less than the requested number {number} of bytes.

Action: Check log for the related error information in detail and determine why the data writing is failed.

Cause: Attempting to open a data file failed during the reading of an on-disk version of the data object into the buffer. This is a system error.

Action: Check log for the error information in detail and determine why the file open is failed.

Cause: Attempting to open a temporary data file failed during the reading of an on-disk version of the data object into the buffer. This is a system error.

Action: Check log for the error information in detail and determine why the file open is failed.

Cause: Reading a data file failed during the loading of an on-disk version of the data object into the buffer. This is a system error.

Action: Check log for the error information in detail and determine why the file reading is failed.

Cause: The read buffer limit {max} was reached while attempting to read an on-disk version of the data object into the buffer.

Action: Check the LifeKeeper configuration and restart the LifeKeeper.

Cause: Failed to close a data file during reading an on-disk version of the data object into the buffer. This is a system error.

Action: Check log for the error information in detail and determine why the file close is failed.

Cause: Failed to rename a temporary data file during reading an on-disk version of the data object into the buffer. This is a system error.

Action: Check log for the error information in detail and determine why the file renaming is failed.

Cause: Failed to open a directory {directory} with error {error} during reading an on-disk version of the application and resource type information into the buffer. This is a system error.

Action: Check log for the error information in detail and determine why the open directory is failed.

Cause: The command "lcdrcp" failed during a file copy because the input source path is missing.

Action: Check the input source path and retry "lcdrcp".

Cause: The "lcdrcp" command failed during a file copy because the input destination path is missing.

Action: Check the input destination path and retry "lcdrcp".

Cause: Input destination path was empty during file copy when using "lcdrcp".

Action: Check the input destination path and retry "lcdrcp".

Cause: Failed to open source file path during file copy using "lcdrcp". This is a system error.

Action: Check the existence/availability of the input source path and retry "lcdrcp". Also check the related log for error information in detail.

Cause: Failed to fetch file attributes using "fstat" during file copy by "lcdrcp". This is a system error.

Action: Check the log for error information in detail.

Cause: Detected source file as a none ordinary file during file copy using "lcdrcp".

Action: Check the input source file path and retry "lcdrcp".

Cause: Failed to allocate memory with requested size in shared memory.

Action: A fatal error will be produced.

Cause: Adding the requested dependency would produce a loop of dependent relationship.

Action: Correct the requested dependency and retry the dependency creation.

Cause: The priorities for {resource1} and {resource2} do not match.

Action: Resource priorities must match. Change one or both priorities to the same value and retry creating the dependency.

Cause: The command "doabort" failed to create the {directory} for writing the core file. This is a system error.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: Received signal {signum}.

Cause: In function {function}, attempting to receive message within timeout {timeout} seconds failed due to a non-idle status of incoming mailbox {mailbox}.

Action: Check the status of the connections inside the cluster and retry the process.

Cause: In function {function}, attempting to receive message within timeout {timeout} seconds failed with incoming mailbox {mailbox}.

Action: Check the status of the connections inside the cluster and retry the process.

Cause: Sending message failed due to a illegal message.

Cause: Sending message failed due to an unknown destination system name {system}.

Action: Check the configuration and status of the system and check the logs for related errors. Retry the same process after the system is full initialized.

Cause: Sending message failed due to an unknown mailbox {mailbox} on destination system name {system}. This error may be caused by sending a message before the LCD is fully initialized.

Action: Check the configuration and status of the system and check the logs for related errors. Retry the same process after the system is full initialized.

Cause: Sending message failed. The network connection to destination system {system} is alive but the contact to the destination mailbox is lost.

Action: Check the configuration and status of the system and check the logs for related errors. Retry the same process after the system is full initialized.

Cause: Sending message failed due to losing connection with the destination system {system}.

Action: Check the configuration and status of the system and check the logs for related errors. Retry the same process after the system is full initialized.

Cause: Sending message to destination system {system} failed due to internal error {error}.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: Sending message failed due to losing connection with the destination system {system}.

Action: Check the configuration and status of the system and check the logs for related errors. Retry the same process after the system is full initialized.

Cause: Sending message failed due to losing connection with the destination system {system}.

Action: Check the configuration and status of the system and check the logs for related errors. Retry the same process after the system is full initialized.

Cause: Creating network object failed due to a failure when getting host name using "getaddrinfo()".

Action: Check the configuration and status of the system. Do the same process again.

Cause: Creating network object failed due to the IP address pair {pair} is already used for a TCP communication path.

Action: Check the input IP address pair and do the network creation again.

Cause: Communication to system {system} by communication path {path} failed.

Action: Check system configuration and network connection.

Cause: A failover from system {system} will be started due to all the communications path are down.

Action: Check system configuration and network connection status. Confirm the system status when failover is done.

Cause: A resource could not be brought in service because its current state is unknown.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A resource could not be brought into service because its current state disallows it.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The resource’s related recovery kit requires a license.

Action: Install a license for the recovery kit on the server where the resource was to be brought into service.

Cause: A resource {resource} could not be brought into service on machine {machine} because its secondary remote resource {resource} is already in service on machine {machine}.

Action: Manually change the remote resource out of service and do in service on local resource again.

Cause: A resource could not be brought into service.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A resource could not be put out of service due to the current state being {state}.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A resource {resource} could not be put out of service.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A global action script failed with the specified error code.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A resource action failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: Creating of a {eqvtype} equivalency failed due to the two input tag names exist on the same system.

Action: Correct the inputs resource tag names and do the same process again.

Cause: The LCM daemon did not become available within a reasonable time and the LCD cannot operate without the LCM.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A shared memory segment could not be initialized.

Action: Check the logs for related errors and try to resolve the reported problem. Review the product documentation and ensure that the server meets the minimum requirements and that the operating system is configured properly.

Cause: Your license has expired.

Action: Contact Support to obtain a new license.

Cause: Your license is about to expire.

Action: Contact Support to obtain a new license.

Cause: The specified system name is not known.

Action: Verify the system name, and try the operation again.

Cause: The specified system name is not recognized.

Action: Verify the system name, and try the operation again.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An action or event script produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: An error occured on the remote machine.

Action: Check the logs on the remote machine for additional details.

Cause: An attempt was made to put a resource in an illegal state.

Action: Do not try to put a resource into an illegal state.

Cause: Changing resource {resource} to state {state} failed since its SHARED equivalent resource {resource} on machine {machine} is in state {state}.

Action: A split brain situation has occurred. The failover operation has been aborted. You should manually put the split brain resources (ISP on multiple systems) in the proper state.

Cause: No resource with the provided tag exists.

Action: Provide a valid tag, or check the logs for related errors and try to resolve the reported problem.

Cause: No resource exists with the provided identifier.

Action: Provide a valid identifier, or check the logs for related errors and try to resolve the reported problem.

Cause: The provided tag name already exists.

Action: Choose a different tag name.

Cause: The provided identifier already exists.

Action: Choose a different identifier to use for this resource.

Cause: Tag name is too long.

Action: Provide a tag name that is less than 256 characters.

Cause: Tag name contains an illegal character.

Action: Specify a tag name that does not include one of these characters: _-./

Cause: Both a tag and an identifier were specified.

Action: Provide only one of tag or identifier.

Cause: The utility "lkexterrlog" can not be accessed for collecting system information.

Action: Check the installation of package "steeleye-lk" and make sure the utility "lkexterrlog" is accessible.

Cause: The execution of utility "lkexterrlog" failed when collecting system information.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The resource is already in service. Recovery will not be attempted.

Cause: A resource was not in an appropriate state to allow recovery.

Action: Put the resource in the ISP state if recovery is still needed.

Cause: An error occured why attempting to recover a resource.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A error occur that prevented a resource from being taken out of service during a recovery. The system has been restarted to ensure the resource is not active on two systems.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A failure occured while transfering a resource and it’s dependencies to another system.

Action: Check the logs for related errors and try to resolve the reported problem. Check the log on the other system for related errors.

Cause: There was an error while restoring a resource.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: Parallel recovery failed. Check the logs for related errors and try to resolve the reported problem.

Action: No action is required. The system will continue to recover serially. If the recovery fails, check for error messages related to the resources which failed to recover to find out what further actions to take.

Cause: The opening of the temporal recovery log file {file} in preparation for loading into it into memory failed with the error {error}.

Action: Check system log files and correct any reported errors before retying the operation.

Cause: Loading the temporal recovery log information into memory failed when attempting to acquire memory to store the log information.

Action: Check system log files and correct any reported errors before retying the operation.

Cause: Loading the temporal recovery log information into memory failed when attempting to increase the amount of memory required to store the log information.

Action: Check system log files and correct any reported errors before retrying the operation.

Cause: The update of the temporal recovery log file was terminated when the open of the temporary file {temporary name} failed.

Action: Check system log files and correct any reported errors before retrying the operation.

Cause: The update of the temporal recovery log file was terminated when the rename of the temporary file {temporary name} to the real log file {real name} failed.

Action: Check system log files and correct any reported errors before retrying the operation.

Cause: The modification of semaphore ID {semaphore} failed with error {err} and error message description {perror}.

Action: Check adjacent log messages for more details. Also, check the system log files and correct any reported errors before retrying the operation.

Cause: The attempt to generate an IPC key for use in semaphore operations for resource {tag} using path {path} failed. This is a system error.

Action: Check adjacent log messages for more details. Also check system log files and correct any reported errors before retrying the operation.

Cause: The attempt to retrieve the semaphore identification associated with the instances files has failed. This is a system error.

Action: Check adjacent log messages for more details. Also check system log files and correct any reported errors before retying the operation.

Cause: The attempt to create and initialize a semaphore used during the recovery process has failed with the error {error number}. This is a system error.

Action: Check adjacent log messages for more details. Also, check system log files and correct any reported errors before retying the operation.

Cause: The attempt to set a semaphore used during the recovery process has failed with the error {error number}. This is a system error.

Action: Check adjacent log messages for more details. Also, check system log files and correct any reported errors before retying the operation.

Cause: The attempt to release a semaphore used during the recovery process has failed with the error {error number}. This is a system error.

Action: Check adjacent log messages for more details. Also, check system log files and correct any reported errors before retying the operation.

Cause: The attempt to bring resource {tag} In Service has failed.

Action: Check adjacent log messages for more details. Correct any reported errors and retry the operation.

Cause: The request to take resource {tag} Out of Service on {server} for transfer to the local system has failed.

Action: Check adjacent log messages for more details on the local system. Also, check the log messages on {server} for further details on the failure to remove the resource.

Cause: The request to take resource {tag} Out of Service on {server} for transfer to the local system has failed.

Action: Check adjacent log messages for more details on the local system. Also, check the log messages on {server} for further details on the failure to remove the resource.

Cause: The request to take resource {tag} Out of Service on {server} for transfer to the local system has failed.

Action: Check adjacent log messages for more details on the local system. Also, check the log messages on {server} for further details on the failure to remove the resource.

Cause: A network connection could not be properly configured.

Action: Verify that all network hardware and drivers are properly configured. If this message continues and resources cannot be put into service, contact Support.

Cause: A network connection could not be properly configured.

Action: Verify that all network hardware and drivers are properly configured. If this message continues and resources cannot be put into service, contact Support.

Cause: A network connection could not be properly configured.

Action: Verify that all network hardware and drivers are properly configured. If this message continues and resources cannot be put into service, contact Support.

Cause: A pipe could not be opened or created.

Action: Check adjacent log messages for more details.

Cause: A message failed to be sent or received.

Action: Check adjacent log messages for more details. This may be a temporary error but if this error continues and servers can’t communicate then verify the network configuration on the servers.

Cause: A message failed to be sent or received.

Action: Check adjacent log messages for more details. This may be a temporary error but if this error continues and servers can’t communicate then verify the network configuration on the servers.

Cause: A message failed to be sent or received.

Action: Check adjacent log messages for more details. This may be a temporary error but if this error continues and servers can’t communicate then verify the network configuration on the servers.

Cause: A message failed to be sent or received.

Action: Check adjacent log messages for more details. This may be a temporary error but if this error continues and servers can’t communicate then verify the network configuration on the servers.

Cause: A message failed to be sent or received.

Action: Check adjacent log messages for more details. This may be a temporary error, but if this error continues and servers cannot communicate, verify the network configuration on the servers.

Cause: A quickCheck script is probably taking too long or hanging.

Action: Perform the steps listed in the message text.

Cause: lkcheck was not able to check all resources within the LKCHECKINTERVAL.

Action: Check if any quickCheck is running longer than expected. This may indicate a problem with a resource. Increase the LKCHECKINTERVAL parameter if needed.

Cause: This is output from a "sendevent "(event generator) command.

Action: Check adjacent log messages for more details.

Cause: This is output from a "sendevent" (event generator) command.

Action: Check adjacent log messages for more details.

Cause: This is output from a "sendevent" (event generator) command.

Action: Check adjacent log messages for more details.

Cause: A SCSI device couldn’t be reserved or have its status checked. This may be because the storage is malfunctioning or because the disk has been reserved by another server.

Action: Check adjacent log messages for more details and verify that resources are being handled properly.

Cause: A SCSI device couldn’t be reserved or have its status checked. This may be because the storage is malfunctioning or because the disk has been reserved by another server.

Action: Check adjacent log messages for more details and verify that resources are being handled properly.

Cause: A SCSI device couldn’t be reserved or have its status checked. This may be because the storage is malfunctioning or because the disk has been reserved by another server. THE SERVER WILL BE REBOOTED/HALTED.

Action: Verify that the storage is functioning properly and, if so, that resources were handled properly and have been put in service on another server.

Cause: The protected SCSI device could not be opened. The device may be failing or may have been removed from the system.

Action: The system will be halted or a failover to the backup node will be initiated. The default action in this case is a failover, but this can be modified with the SCSIERROR tunable.

Cause: The protected SCSI device could not be opened. The device may be failing or may have been removed from the system.

Action: This error is not critical. The operation will be retried in 5 seconds. If the problem persists, the system will perform a halt or resource failover.

Cause: A SCSI device couldn’t be reserved due to a conflict with another server. This may be because the storage is malfunctioning or because the disk has been reserved by another server.

Action: Check adjacent log messages for more details and verify that resources are handled properly.

Cause: A SCSI device couldn’t be reserved or have its status checked. This may be because the storage is malfunctioning or because the disk has been reserved by another server.

Action: Check adjacent log messages for more details and verify that resources are handled properly.

Cause: A SCSI device couldn’t be reserved or have its status checked. This may be because the storage is malfunctioning or because the disk has been reserved by another server.

Action: Check adjacent log messages for more details and verify that resources are handled properly.

Cause: This message indicates an incomplete process that will be retried.

Action: Check adjacent log messages for repeated errors.

Cause: This message is part of the output from an "ins_remove" command.

Action: Check adjacent log messages for more details. This may not be a true error.

Cause: A flag list operation on a server took much longer than expected. There may be a problem communicating with the other server.

Action: Check adjacent log messages for more details.

Cause: One of the servers in the cluster could not be told to disallow failover operations from the current server.

Action: Check adjacent log messages for more details and monitor the cluster for unexpected behavior.

Cause: A process is incomplete but will be retried.

Action: Check adjacent log messages for more details and for repeated warnings/errors.

Cause: There was a fatal error while attempting to start LifeKeeper.

Action: Check adjacent log messages for more details.

Cause: A suitable tag during the create process for a storage resource could not be automatically generated.

Action: Check adjacent log messages for more details. Retry the operation if there are no other errors.

Cause: A core component of the software could not be started.

Action: Check adjacent log messages for more details and try to resolve the reported problem.

Cause: Some parts of the software are taking longer than expected to start up.

Action: Perform the steps listed in the message text.

Cause: Some parts of the software are taking longer than expected to start up.

Action: Perform the steps listed in the message text.

Cause: A dependency relationship could not be created on the given server.

Action: Check the logs for related errors and try to resolve the reported problem

Cause: A command to request data to backup from another server failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The resource was not switched back over as expected.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: Invalid parameters were specified for the "getlocks" operation.

Action: Verify the parameters and retry the operation. If this error happens during normal operation, contact Support.

Cause: A lock was ignored because the system for which the lock was created is not alive.

Action: Check the logs for related errors. This may be a harmless error.

Cause: Acquiring a lock tool longer than expected/allowed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The software failed to acquire a lock that is required to manage resources.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A file could not be copied to another server.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A flag could not be set to indicate that the server is being stopped by user request.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The execution of utility "lkexterrlog" failed when opening the extended log file.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: One or more resources in the hierarchy with $loctag are not able to switchback.

Action: Manually switch the hierarchy back when all resources are able.

Cause: Switchback can not be completed at this time and will be retried in time specified in the message.

Action: None if retry should be retried. To stop delayed retry cancel the "at" job.

Cause: Unable to open the file /opt/LifeKeeper/config/.reservation_id to retrieve the unique id used for SCSI 3 persistent reservations.

Action: None. An attempt will be made to regenerate the ID and update the file.

Cause: The reservation id defined for the system is not unique within the cluster and cannot be used.

Action: Take all resources out of service on this node and then run "/opt/LifeKeeper/bin/genresid -g" to generate a unique reservation id.

Cause: Unable to open the file /opt/LifeKeeper/config.reservation_id to store the unique id used for SCSI 3 persistent reservations.

Action: Correct the error listed as the reason the open failed and then take all resources out of service on this node and then run "/opt/LifeKeeper/bin/genresid -g" to generate a new unique reservation id.

Cause: The generated reservation id is already defined on another node in the cluster and must be unique within the cluster.

Action: Take all resources out of service on this node and then run "/opt/LifeKeeper/bin/genresid -g" to generate a new unique reservation id.

Cause: A SCSI device that appeared to be reserved was not released as expected.

Action: Check the logs for related errors and try to resolve any reported problems. This error may be benign if the system is functioning properly.

Cause: A reservation on a SCSI device could not be acquired.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The "lklogmsg" tool failed to execute a sub-command {command}.

Action: Check the logs for related errors and try to resolve any reported problems. Verify that the sub-command exists and is a valid command or program. If this message happens during normal operation, contact Support.

Cause: When in LifeKeeper Single Server Protection operation, a resource could not be recovered and VMware-HA is about to be triggered to handle the failure (if VMware-HA is enabled).

Action: No action is required. VMware should handle the failure.

Cause: This is the output from an "snmptrap" command that may have failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: When in LifeKeeper Single Server Protection operation, a resource could not be recovered and a reboot is about to be triggered to handle the failure.

Action: No action is required.

Cause: This indicates a notification email could not be sent via the "mail" command.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: This is the output from a "mail" command that may have failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: This is the output from a "mail" command that may have failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: Invalid arguments were specified for the "comm_down" event.

Action: Check your LifeKeeper configuration and retry the operation.

Cause: During the handling of a communication failure with another node, a local lock could not be acquired. This will likely stop a failover from proceeding.

Action: Check the logs for related errors and try to resolve the reported problem. If failovers are not taking place properly, contact Support.

Cause: Invalid arguments were specified for the "comm_up" event.

Action: Check your LifeKeeper configuration and retry the operation.

Cause: "flg_list" command reached its timeout value {delay} seconds.

Cause: "flg_list" command reached its timeout value.

Action: Switch back the resource tree if unintended switchover occurs.

Cause: One of other servers looked dead to this server {server}, but witness servers did not agree.

Action: Ensure other server is dead and switch over the resource manually.

Cause: An unexpected failure occurred during "COMM_UP" event.

Action: Check adjacent log messages for more details.

Cause: "lcdrecover" took too long or errored out.

Cause: Failed 5 times to perform "lcdrecover."

Action: Switch over the resource tree manually.

Cause: An error occurred during extend.

Action: Check the LifeKeeper log.

Cause: Hierarchy is on one server.

Action: Extend the hierarchy to a second server.

Cause: A resource hierarchy failed to be unextended from a server.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: A hierarchy cannot be unextended because the target server does not have adequate communication with the other servers in the cluster.

Action: Check the logs for related errors and try to resolve the reported problem. Ensure that all servers have communication paths to each other.

Cause: Internal error.

Action: Try restarting the product.

Cause: Internal error.

Action: Try restarting the product.

Cause: Internal error.

Action: Try restarting the product.

Cause: Internal error.

Action: Try restarting the product.

Cause: This will not occur under normal circumstances.

Cause: Internal error.

Action: Try restarting the product.

Cause: Internal error.

Action: Try restarting the product.

Cause: LifeKeeper could not get IPC key.

Action: Check adjacent log messages for more details.

Cause: LifeKeeper could not get semaphore set id.

Action: Check adjacent log messages for more details.

Cause: System could not allocate a shared memory segment.

Action: Check adjacent log messages for more details.

Cause: A system error has occurred while accessing /opt/LifeKeeper/out.

Action: Determine why /opt/LifeKeeper/out is not accessible.

Cause: You are running a demo license.

Action: Contact Support to obtain a new license.

Cause: You have a license for LifeKeeper Single Server Protection but you do not have LifeKeeper Single Server Protection installed.

Action: Either install LifeKeeper Single Server Protection or obtain a license that matches the product you are running.

Cause: License manager initialization failed.

Action: Check adjacent log messages for more details.

Cause: License manager initialization failed.

Action: Check adjacent log messages for more details.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: LifeKeeper could not find valid license keys.

Action: Ensure license keys are valid for the server and retry the operation.

Cause: There is an unknown problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: A message failed to be sent.

Action: Check adjacent log messages for more details. This may be a temporary error.

Cause: A message failed to be sent.

Action: Check adjacent log messages for more details. This may be a temporary error.

Cause: A system error has occurred while accessing temporary file /tmp/OUT.{pid}.

Action: Determine why /tmp/OUT.{pid} is not accessible.

Cause: A system error has occurred while accessing temporary file /tmp/ERR.{pid}.

Action: Determine why /tmp/ERR.{pid} is not accessible.

Cause: This message is for information only.

Cause: LifeKeeper could not find the {id} resource.

Action: Verify the parameters and retry the "sendevent" operation.

Cause: A system error has occurred while reading /opt/LifeKeeper/config/flg.

Action: Determine why /opt/LifeKeeper/config/flg is not readable.

Cause: A system error has occurred while writing /opt/LifeKeeper/config/flg.

Action: Determine why /opt/LifeKeeper/config/flg is not writable.

Cause: A system error has occurred while writing /opt/LifeKeeper/config/flg.

Action: Determine why /opt/LifeKeeper/config/flg is not writable.

Cause: A system error has occurred while renaming /opt/LifeKeeper/config/.flg to /opt/LifeKeeper/config/flg.

Action: Determine why /opt/LifeKeeper/config/flg was not able to be renamed.

Cause: A system error has occurred while changing permissions in /opt/LifeKeeper/config/flg.

Action: Determine why LifeKeeper could not change permissions in /opt/LifeKeeper/config/flg.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: A system error has occurred while writing /opt/LifeKeeper/subsys/scsi/resources/disk/disk.reserve.

Action: Determine why /opt/LifeKeeper/subsys/scsi/resources/disk/disk.reserve is not writable.

Cause: The system could not allocate memory for LifeKeeper.

Action: Increase the process limit for the data segment.

Cause: A system error has occurred while writing /tmp/LK_IS_UNAVAIL.

Action: Determine why /tmp/LK_IS_UNAVAIL is not writable.

Cause: A system error has occurred while writing /opt/LifeKeeper/config/LK_IS_ON.

Action: Determine why /opt/LifeKeeper/config/LK_IS_ON is not writable.

Cause: A system error has occurred while writing /tmp/LCM_IS_UNAVAI.

Action: Determine why /tmp/LCM_IS_UNAVAI is not writable.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: A message failed to be received.

Action: Check adjacent log messages for more details. This may be a temporary error, but if this error continues and servers cannot communicate, verify the network configuration on the servers.

Cause: A system error has occurred while accessing /opt/LifeKeeper/config/LK_START_TIME.

Action: Determine why /opt/LifeKeeper/config/LK_START_TIME is not accessible.

Cause: A message failed to be received.

Action: Check adjacent log messages for more details. This may be a temporary error, but if this error continues and servers cannot communicate, verify the network configuration on the servers.

Cause: A message failed to be received.

Action: Check adjacent log messages for more details. This may be a temporary error, but if this error continues and servers cannot communicate, verify the network configuration on the servers.

Cause: LifeKeeper was unable to fail over the given resource during shutdown.

Action: Switch over the resource tree to other server manually.

Cause: LifeKeeper was unable to fail over the given resource during start up.

Action: Switch over the resource tree manually after LifeKeeper starts up.

Cause: An error occurred while running the "rlslocks" command.

Action: Check adjacent messages for more details.

Cause: An error occurred while running the "getlocks" command.

Action: Check adjacent log messages for more details.

Cause: Internal error.

Action: Increase the process limit for the data segment.

Cause: A system error has occurred while invoking ksh.

Action: Make sure the pdksh (v8.0 and earlier) or the steeleye-pdksh (v81 and later) package is installed.

Cause: A system error has occurred while removing /tmp/LCM_IS_UNAVAIL.

Action: Determine why /tmp/LCM_IS_UNAVAIL is not removable.

Cause: A system error has occurred while trying to unlink /tmp/LK_IS_UNAVAIL.

Action: Determine why /tmp/LK_IS_UNAVAIL is not removable.

Cause: A system error has occurred while accessing /opt/LifeKeeper.

Action: Determine why /opt/LifeKeeper is not accessible.

Cause: A system error has occurred while removing a semaphore.

Action: Try to remove the semaphore manually.

Cause: A system error has occurred while removing a shared memory segment.

Action: Try to remove the shared memory segment manually.

Cause: A system error has occurred while removing a semaphore.

Action: Try to remove the semaphore manually.

Cause: A system error has occurred while removing a shared memory segment.

Action: Try to remove the shared memory segment manually.

Cause: The remote {node} is down, inaccessible via the network or some other system problem occurred on the remote node.

Action: Bring the remote node back online, or check adjacent messages for additional information, or check the logs on the remote node for additional information.

Cause: Internal error.

Action: Perform the steps listed in the message text.

Cause: This will not occur under normal circumstances.

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

Cause: The {action} for resource {tag} has failed.

Action: See adjacent error messages for further details.

Cause: LifeKeeper could not find the network device.

Action: Check your LifeKeeper configuration.

Cause: Internal error.

Action: Try restarting the product.

Cause: Internal error.

Action: Try restarting the product.

Cause: An invalid system name was provided.

Action: Recheck the system name and rerun the command.

Cause: Internal error.

Action: Try restarting the product.

Cause: Internal error.

Action: Try restarting the product.

Cause: Internal error.

Action: Try restarting the product.

Cause: Command execution failed.

Action: See message details to determine the problem.

Cause: The command {command} produced unexpected output.

Action: Action should be determined by the content of adjacent error messages.

Cause: There is a problem with your demo license.

Action: Contact Support to obtain a new license.

Cause: You have a demo license and clock tampering has been detected.

Action: Contact Support to obtain a new license.

Cause: You have a demo license and clock tampering has been detected.

Action: Contact Support to obtain a new license.

Cause: The demo license for this product has expired.

Action: Contact Support to obtain a new license.

Cause: You have a demo license and clock tampering has been detected.

Action: Contact Support to obtain a new license.

Cause: You are running a demo license.

Action: Contact Support to obtain a new license.

Cause: You are running a demo license.

Action: Contact Support to obtain a new license.

Cause: An Application Recovery Kit license for {kit} was not found.

Action: Contact Support to obtain a new license.

Cause: The command "eventslcm" produced unexpected output.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: This version of the LifeKeeper core package is restricted to being used within the territories of the People’s Republic of China or Japan.

Cause: There was a mis-match between your locale and the locale for which the product license was created.

Action: Contact Support to obtain a new license which matches your locale.

Cause: You have a license for LifeKeeper Single Server Protection but you do not have LifeKeeper Single Server Protection installed.

Action: Either install LifeKeeper Single Server Protection or obtain a license that matches the product you are running.

Cause: Your license key for this product has expired.

Action: Contact Support to obtain a new license.

Cause: Your license key for this product has expired.

Action: Contact Support to obtain a new license.

Cause: You have a license for LifeKeeper Single Server Protection but you do not have LifeKeeper Single Server Protection installed.

Action: Either install LifeKeeper Single Server Protection or obtain a license that matches the product you are running.

Cause: Your license key for this product has expired.

Action: Please contact Support to obtain a permanent license key for your product.

Cause: An error has ocurred with the "steeleye-lighttpd" process. Specific details of the error are included in the actual log message.

Action: Correct the configration and "steeleye-lighttpd" will automatically be restarted.

Cause: The db2nodes.cfg does not contain any server names.

Action: Ensure the db2nodes.cfg is valid.

Cause: "db2level" command did not return DB2 version.

Action: Check your DB2 configuration.

Cause: The DB2 Application Recovery Kit was unable to find any nodes for the DB2 instance.

Action: Check your DB2 configuration.

Cause: Failed to get resource information.

Action: Check your LifeKeeper configuration.

Cause: Failed to get resource information.

Action: Check your LifeKeeper configuration.

Cause: Failed to get the instance information.

Action: Check your LifeKeeper configuration.

Cause: Failed to get the instance home directory path.

Action: Check your LifeKeeper configuration.

Cause: The DB2 Application Recovery Kit found invalid instance type.

Action: Check your LifeKeeper configuration.

Cause: There was an unexpected error running "db2 get db cfg for $DB" command.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The requested startup of the DB2 instance failed.

Action: Check the logs for related errors and try to resolve the reported problem. Correct any reported errors before retrying the "restore" operation.

Cause: The requested startup of the DB2 instance failed.

Action: Check the logs for related errors and try to resolve the reported problem. Correct any reported errors before retrying the "restore" operation.

Cause: The home directory of instance of Multiple Partition database should exist in "/etc/fstab".

Action: Ensure the home directory exists in "/etc/fstab".

Cause: Failed to mount the home directory of instance of Multiple Partition database.

Action: Ensure the home directory is mounted and retry the operation.

Cause: Failed to get the instance nodes.

Action: Check your LifeKeeper configuration.

Cause: The requested startup of the DB2 instance failed.

Action: Check the logs for related errors and try to resolve the reported problem. Correct any reported errors before retrying the "restore" operation.

Cause: The requested shutdown of the DB2 instance failed.

Action: Check the logs for related errors and try to resolve the reported problem. Correct any reported errors before retrying the "remove" operation.

Cause: The requested shutdown of the DB2 instance failed.

Action: Check the logs for related errors and try to resolve the reported problem. Correct any reported errors before retrying the "remove" operation.

Cause: Failed to get the instance nodes.

Action: Check your LifeKeeper configuration.

Cause: The requested shutdown of the DB2 instance failed.

Action: Check the logs for related errors and try to resolve the reported problem. Correct any reported errors before retrying the "remove" operation.

Cause: Failed to get the instance nodes.

Action: Check your LifeKeeper configuration.

Cause: Invalid parameters were specified for the create operation.

Action: Verify the parameters and retry the operation.

Cause: The DB2 Application Recovery Kit was unable to determine the DB2 instance home directory.

Action: Ensure the instance owner name is same as the instance name and retry the operation.

Cause: The DB2 Application Recovery Kit was unable to determine the DB2 instance type.

Action: Check your DB2 configuration.

Cause: The DB2 Application Recovery Kit was unable to find any nodes for the DB2 instance.

Action: Check your DB2 configuration.

Cause: The instance home directory should be on a shared filesystem.

Action: Ensure the path is on shared filesystem and retry the create operation.

Cause: LifeKeeper could not determine the location of the database table space containers or verify that they are located in a path which is on a mounted filesystem.

Action: Check the logs for related errors and try to resolve the reported problem. Correct any reported errors before retrying the "create" operation.

Cause: The path of database table space container should be on a shared filesystem.

Action: Ensure database table space container is on a shared filesystem and retry the operation.

Cause: An attempt was made to protect the DB2 instance that is already under LifeKeeper protection.

Action: You must select a different DB2 instance for LifeKeeper protection.

Cause: The file system which the DB2 resource depends on should be in service.

Action: Ensure the file system resource is in service and retry the "create" operation.

Cause: LifeKeeper was unable to create the resource {raw device} .

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

Cause: LifeKeeper was unable to find the raw resource {tag} .

Action: Check your LifeKeeper configuration.

Cause: The requested dependency creation between the parent DB2 resource and the child Raw resource failed.

Action: Check adjacent log messages for further details and related messages. Correct any reported errors before retrying the "create" operation.

Cause: An unexpected error occurred while attempting to update the DB2 setting.

Action: The DB2AUTOSTART will need to be updated manually to turn off the automatic startup of the instance at system boot.

Cause: LifeKeeper could not find DB2 installed location.

Action: Check your DB2 configuration.

Cause: An attempt to retrieve the DB2 instance owner from template server during a "canextend" or "extend" operation failed.

Action: Verify the DB2 instance owner exists on the specified server. If the user does not exist, it should be created with the same uid and gid on all servers in the cluster.

Cause: The user id on the target server {target server} for the DB2 instance owner {user} does not match the value of the user {user} on the template server {template server}.

Action: The user ids for the DB2 instance owner {user} must match on all servers in the cluster. The user id mismatch should be corrected manually on all servers before retrying the "canextend" operation.

Cause: The group id on the target server {target server} for the DB2 instance owner {user} does not match the value of the user {user} on the template server {template server}.

Action: The group ids for the DB2 instance owner {user} must match on all servers in the cluster. The group id mismatch should be corrected manually on all servers before retrying the "canextend" operation.

Cause: The home directory location of the user {user} on the target server {target server} does not match the DB2 instance owner’s home directory on the template server {template server}.

Action: The home directory location of the DB2 instance owner {user} must match on all servers in the cluster. The location mismatch should be corrected manually on all servers before retrying the "canextend" operation.

Cause: There was an unexpected error running "db2 get dbm cfg" command.

Action: Check your DB2 configuration.

Cause: The DB2 "SVCENAME" parameter is set to null.

Action: Check your DB2 configuration.

Cause: "/etc/services" on the template server does not contain the service names for the DB2 instance.

Action: The service names in "/etc/services" for the DB2 instance must match on all servers in the cluster. The service names mismatch should be corrected manually on all servers before retrying the "canextend" operation.

Cause: "/etc/services" on the target server does not contain the service names for the DB2 instance.

Action: The service names in "/etc/services" for the DB2 instance must match on all servers in the cluster. The service names mismatch should be corrected manually on all servers before retrying the "canextend" operation.

Cause: The "/etc/services" entries for the instance are mismatched.

Action: The service names in "/etc/services" for the DB2 instance must match on all servers in the cluster. The service names mismatch should be corrected manually on all servers before retrying the "canextend" operation.

Cause: LifeKeeper could not find db2nodes.cfg for Multiple Partition instance.

Action: Ensure the home directory is mounted and retry the operation.

Cause: Failed to get resource information from the template server.

Action: Check your LifeKeeper configuration.

Cause: There was an unexpected error running "db2iset" command.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The DB2 Application Recovery Kit was unable to determine the DB2 instance type.

Action: Check your DB2 configuration.

Cause: The DB2 Application Recovery Kit was unable to find any nodes for the DB2 instance.

Action: Check your DB2 configuration.

Cause: The DB2 Application Recovery Kit was unable to determine the DB2 instance home directory.

Action: Ensure the instance owner name is same as the instance name and retry the operation.

Cause: The DB2 Application Recovery Kit was unable to determine the DB2 instance type.

Action: Check your DB2 configuration.

Cause: The DB2 Application Recovery Kit was unable to find the node for the DB2 instance.

Action: Check your DB2 configuration.

Cause: The DB2 Application Recovery Kit was unable to find DB2 for the instance.

Action: Check your DB2 configuration.

Cause: Invalid parameters were specified for the "nodes" command.

Action: Verify the parameters and retry the operation.

Cause: LifeKeeper was unable to find the resource {tag}.

Action: Verify the parameters and retry the operation.

Cause: The resource {tag} is single partition instance.

Action: Verify the parameters and retry the operation.

Cause: Invalid parameters were specified for the "nodes" command.

Action: Verify the parameters and retry the operation.

Cause: Invalid parameters were specified for the "nodes" command.

Action: Verify the parameters and retry the operation.

Cause: There was an unexpected error running "nodes" command.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: There was an unexpected error running "nodes" command.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: There was an unexpected error running "nodes" command.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The DB2 Application Recovery Kit was unable to determine the DB2 instance type.

Action: Check your DB2 configuration.

Cause: The DB2 Application Recovery Kit was unable to determine the DB2 instance home directory.

Action: Ensure the instance owner name is same as the instance name and retry the operation.

Cause: A process check for the DB2 instance did not find any processes running.

Action: The DB2 instance must be started.

Cause: The DB2 Application Recovery Kit was unable to find any nodes for the DB2 instance.

Action: Check your DB2 configuration.

Cause: All database partition servers should be running.

Action: Ensure all database partition servers are running and retry the operation.

Cause: An unexpected error occurred attempting to create a flag for controlling DB2 local recovery processing.

Action: Check the adjacent log messages for further details and related messages. Correct any reported errors.

Cause: An unexpected error occurred attempting to remove a flag for controlling DB2 local recovery processing.

Action: Check the adjacent log messages for further details and related messages. Correct any reported errors.

Cause: The DB2 Application Recovery Kit was unable to determine the DB2 instance home directory.

Action: Ensure the instance owner name is same as the instance name and retry the operation.

Cause: This message indicates an internal software error.

Action: The stack trace indicates the source of the error.

Cause: A data replication action was attempted on a non data replication resource.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The bitmap merge operation has failed.

Action: The target server may have the mirror and/or protected filesystem mounted, or the bitmap file may be missing on the target. Check the target server.

Cause: The "mdadm" command has failed to add a device into the mirror.

Action: This is usually a temporary condition.

Cause: The message contains the output of the "mdadm" command.

Cause: The system failed to start the ‘mdadm -F’ monitor process. This should not happen under normal circumstances.

Action: Reboot the system to ensure that any potential conflicts are resolved.

Cause: The mirror device could not be created.

Action: Ensure the device is not already in use and that all other parameters for the mirror creation are correct.

Cause: This message contains the "mdadm" command output.

Cause: The device was busy for an abnormally long period of time.

Action: Reboot the system to be sure that the device is no longer busy.

Cause: The nbd-server process could not be started on the target server.

Action: Ensure that the target disk device is available and that its Device ID has not changed.

Cause: The system was unable to start the ‘balance’ tunnel process or there was a network problem.

Action: Ensure that the network is operating properly and that TCP ports in the range 10000-10512 are opened and unused. Ensure that the software is installed properly on all systems.

Cause: The nbd-client process has failed to start on the source server.

Action: Look up the reported errno value and try to resolve the problem reported. For example, an errno value of 110 means "Connection timed out", which may indicate a network or firewall problem.

Cause: This is usually a temporary condition.

Action: If this error persists, reboot the system to resolve any potential conflicts.

Cause: The mirror device could not be stopped.

Action: Ensure that the device is not busy or mounted. Try running "mdadm —stop" manually to stop the device.

Cause: The process could not be signalled. This may indicate that the process has already died.

Action: Ensure that the process in question is no longer running. If it is, then reboot the system to clear up the unkillable process.

Cause: The system failed to set a ‘mirrorinfo’ file setting.

Action: Check the network and systems and retry the mirror setting operation.

Cause: The mount point became unmounted.

Action: Ensure that the mount point is mounted and retry the operation.

Cause: The filesystem or device was not available on the target server. The mirrored data will not be available on the target server until the mirror is paused and resumed again.

Action: Reboot the target server to resolve any potential conflicts.

Cause: The filesystem could not be unmounted on the target server.

Action: Ensure that the filesystem and device are not busy on the target server. Reboot the target server to resolve any potential conflicts.

Cause: The target disk could not be identified.

Action: Ensure that the appropriate storage recovery kits are installed on the target server. Ensure that the Device ID of the target disk has not changed.

Cause: A unique ID could not be found for the target disk device.

Action: Ensure that the appropriate storage recovery kits are installed on the target server. Ensure that the Device ID of the target disk has not changed.

Cause: An attempt was made to create a mirror with invalid parameters.

Action: A bitmap file parameter must be specified or synchronous writes must be specified.

Cause: The hierarchy extend operation failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The hierarchy extend operation failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The in-service operation has failed on the target server.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: There is no storage recovery kit that recognizes the underlying disk device that you are attempting to use for the mirror.

Action: Make sure the appropriate storage recovery kits are installed. If necessary, place your device name in the /opt/LifeKeeper/subsys/scsi/resources/DEVNAME/device_pattern file.

Cause: The "mkfs" command failed.

Action: Ensure that the disk device is writable and free of errors and that the filesystem tools for the selected filesystem are installed.

Cause: This message contains the output of the "mkfs" command.

Cause: The resource creation failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The data corrupt flag file has been set as a precaution to prevent accidental data corruption. The mirror cannot be restored on this server until the file is removed.

Action: If you are sure that the data is valid on the server in question, you can either: 1) remove the file and restore the mirror, or 2) force the mirror online using the LifeKeeper GUI or ‘mirror_action force’ command.

Cause: The hierarchy switchover operation has failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The hierarchy unextend operation failed.

Action: Reboot the target server to resolve any potential conflicts and retry the operation.

Cause: The bitmap merge command failed on the target server. This may be caused by one of two things: 1) The bitmap file may be missing or corrupted, or 2) the mirror (md) device may be active on the target.

Action: Make sure that the mirror and protected filesystem are not active on the target. If the target’s bitmap file is missing, pause and resume the mirror to recreate the bitmap file.

Cause: Invalid parameters were specified for the mirror create operation.

Cause: Invalid parameters were specified for the mirror create operation.

Cause: A unique ID could not be determined for the disk device.

Action: Ensure that the appropriate storage recovery kits are installed on the server. Ensure that the Device ID of the disk has not changed.

Cause: Invalid parameters were specified for the mirror create operation.

Cause: Invalid parameters were specified for the mirror create operation.

Cause: Invalid parameters were specified for the mirror create operation.

Cause: Invalid parameters were specified for the mirror create operation.

Cause: Invalid parameters were specified for the mirror create operation.

Cause: Invalid parameters were specified for the mirror create operation.

Cause: The mount point is busy.

Action: Make sure the filesystem is not busy. Stop any processes or applications that may be accessing the filesystem.

Cause: An invalid parameter was specified for the mirror create operation.

Cause: A temporary communication failure (split-brain scenario) has occurred between the source and target servers.

Action: Perform the steps listed in the message text.

Cause: The specified command failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: This message contains the output of the command that was reported as failing in message 104125.

Cause: The netraid.down script was called without specifying the communication path or the server name. This script is called internally so should always have the proper parameters.

Action: Report this error to SIOS support.

Cause: The replication connection for the mirror is down.

Action: Check the network.

Cause: The mirror resize operation has failed to update the mirror metadata on the listed system.

Action: You must successfully complete the resize before using the mirror. Re-run mirror_resize (possibly using -f to force the operation if necessary).

Cause: The partition or disk chosen for mirror creation has an odd number of disk sectors and will have to be resized to be used with DataKeeper.

Action: Resize the partition using the ‘parted’ command or resize the disk (is possible) using platform (VMware, AWS) tools. Caution: data may be lost if this is not done carefully.

Cause: The hierarchy extend operation failed.

Action: Check the logs for related errors and try to resolve the reported problem.

Cause: The mirror could not be established.

Action: Check the logs for related errors and try to resolve the reported problems.

Cause: The mirror device created on the target node when the mirror was paused could not be stopped.

Action: Ensure that the device is not busy or mounted. Try running "mdadm —stop" manually to stop the device.

Cause: A full resync could not be done by dirtying the full bitmap. The fullsync flag will be used instead. This is a non-fatal error as a full synchronization will still be done.

Action: None

Cause: The mirror is configured on the target system.

Action: The target system should be rebooted. DataKeeper should then be able to resync the mirror.

Cause: The mirror disk is mounted on the target system.

Action: The mirror disk should be unmounted on the target system, in order to initiate a full mirror resync. A full resync is required because untracked changes have occurred on the disk.

Cause: The disk chosen for mirroring does not provide a UUID to the operating system. DataKeeper cannot mirror a disk without a UUID.

Action: You may be able to create a GPT partition table on the disk to provide a UUID for the disk partitions.

Cause: The SNMP trap 142 to notify when DataKeeper has paused the mirror and mounted the target disk failed. The details of the error will be displayed following this message.

Cause: The SNMP trap 142 to notify when DataKeeper has paused the mirror and mounted the target disk failed. The details of the error is displayed in this message.

Cause: The email to notify when DataKeeper has paused the mirror and mounted the target disk failed. The details of the error will be displayed following this message.

Cause: The email to notify when DataKeeper has paused the mirror and mounted the target disk failed. The details of the error will be displayed in this message.

Cause: You have mounted the underlying mirrored disk on the target system.

Action: You must unmount the disk immediately in order to avoid data corruption.

Cause: The resynchronization of the md device is detected in PENDING state.

Action: LifeKeeper will try to fix the issue by forcing a resynchronization. Check the logs for related errors. When successful assure that the PENDING state has been cleared in /proc/mdstat and the resynchronization is in progress or has been completed for the datarep resource.

Cause: Unable to make changes in /etc/sysconfig/raid-check to add or remove an entry to the list of MD devices to skip (SKIP_DEVS).

Action: Check system logs for any errors related to raid-check or SKIP_DEVS. Manually add or remove md listed.

Cause: The local device for a mirror failed. The recovery action has been set to "nothing" in LKDR_FAILURE requiring manual intervention to recover.

Action: Check system logs and LifeKeeper logs for errors related to the local disk.

Cause: The mirror is being forced online, overriding the data_corrupt flag. The data on the specified system will be treated as the latest data. If this is not correct then this can lead to data corruption or data loss.

Action: None

Cause: The data_corrupt flag exists for one or more mirrors in the hierarchy. To avoid corrupting additional data none of the mirrors are brought in-service until all of the data_corrupt flags are resolved.

Action: Check the LifeKeeper logs to determine where each mirror was last in-service, aka where the latest data for each mirror resides. The mirrors should be brought in-service on the "previous source" where the full hierarchy was in-service and allow the mirrors to synchronize with all targets.

Cause: The mirror is being forced online, overriding the data_corrupt flag. The data on the specified system will be treated as the correct data to be synchronized with all targets. This can lead to data corruption or data loss if this is not the latest data.

Action: None

Cause: The ‘source’ flag file was not created on the specified system to track the mirror source.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘source’ flag file was not created on the specified system to track the mirror source.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘source’ flag file should contain the system name of a previous source but the name listed was not found in the list of systems configured.

Action: Report this problem to SIOS support.

Cause: The ‘source’ flag file was not created on the specified system to track the mirror source

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘previous_source’ flag file was not created on the mirror source to track the mirror’s previous source.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘data_corrupt’ flag file was not created on the target listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘source’ flag file should exist on the system and without it the consistency of the mirror can not be verified. A full resync is required to assure data reliability.

Action: Check the LKROOT (/opt/LifeKeeper) file system for error or that it is full.

Cause: The amount of time waiting for the previous source could not be determined. Targets will be added with a full resync if the previous source is not found.

Action: none

Cause: The source flag file on the target is updated when it is in-sync and stopped so the the next in-service does not require the previous source.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The local system name should not be in the previous_source flag file.

Action: Report this error to SIOS support.

Cause: There are no targets waiting for a previous source to merge.

Action: Report this error to SIOS support.

Cause: The ‘source’ flag file was not created on the target listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘last_owner’ flag file was not created on the source.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The system listed had the mirror in-service last.

Action: The system listed has the last_owner file that indicates it has the most recent data and is most likely the best system to in-service the mirror to avoid losing data.

Cause: The system listed is not alive.

Action: Since the system listed is not alive, it cannot be determined whether that system was a more recent mirror source than the local system. Therefore the local system should not automatically be allowed to bring the mirror in-service.

Cause: The email to notify when DataKeeper resynchronization is complete failed. The details of the error will be displayed following this message.

Cause: The email to notify when DataKeeper resynchronization is complete failed. The details of the error is displayed in this message.

Cause: SNMP trap 143 to notify when DataKeeper resynchronization is complete failed. The details of the error will be displayed following this message.

Cause: SNMP trap 143 to notify when DataKeeper resynchronization is complete failed. The details of the error are given in this message.

Cause: The kernel does not support async replication. The message will provide more details on the failure.

Action: Do not configure asynchronous replication while using this kernel per the details in the message.

Cause: The is_async_supported returned a warning message specifying some conditions to be aware when replicating asynchronously.

Action: Verify that the condition of the warning does not apply to this configuration. Synchronous replication may be necessary.

Cause: In a multi-target configuration targets will not be configured until the previous source is available to merge its bitmap so that all targets will be able to partially resynchronize. The LKDR_WAIT_ON_PREVIOUS_SOURCE_TIMEOUT entry in /etc/defaults/LifeKeeper is set to “-1” to wait indefinitely.

Action: Check on the status of the previous source listed in the message and resolve any issues that are preventing it from rejoining the cluster.

Cause: In a multi-target configuration targets are not being configured, waiting on the previous source to rejoin the cluster.

Action: Run the command listed in the message to force an immediate full resynchronization to this target and any remaining targets waiting to be resynchronized.

Cause: In a multi-target configuration targets will not be configured until the previous source is available to merge its bitmap so that all targets will be able to partially resynchronize. The LKDR_WAIT_ON_PREVIOUS_SOURCE_TIMEOUT entry in /etc/defaults/LifeKeeper is set to the number of seconds to wait. If the previous source does not join the cluster in that time then targets will be added with a full resynchronization.

Action: Check on the status of the previous source listed in the message and resolve any issues that are preventing it from rejoining the cluster.

Cause: In a multi-target configuration targets are not being configured, waiting on the previous source to rejoin the cluster.

Action: Run the command listed in the message to force an immediate full resynchronization to this target and any remaining targets waiting to be resynchronized.
Note: Run this command to stop waiting even if the target listed is deleted and never returning.

Cause: The ‘data_corrupt’ flag file was not created on the source listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘data_corrupt’ flag file was not created on the target listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘data_corrupt’ flag file was not created on the source listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘data_corrupt’ flag file was not created on the target listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘data_corrupt’ flag file was not created on the target listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘source’ flag file should exist on the system and without it the consistency of the mirror can not be verified. A full resync is required to assure data reliability. All targets not already being mirrored will require a full resync.

Action: Check the LKROOT (/opt/LifeKeeper) file system for error or that it is full.

Cause: The ‘source’ flag file was not created on the specified system to track the mirror source.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘data_corrupt’ flag file was not created on the target listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘source’ flag file was not created on the specified system to track the mirror source.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘data_corrupt’ flag file was not created on the target listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full

Cause: The ‘last_owner’ flag file was not created on the target listed.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘last_owner’’ flag file is used to know where the mirror was last in-service.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘last_owner’’ flag file is used to know where the mirror was last in-service.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: The ‘previous_source’ flag file was not created. This is needed to merge the previous source bitmap to avoid a full resync.

Action: Check the LKROOT (/opt/LifeKeeper) file system for errors or that it is full.

Cause: This message indicates a failure to set a sysfs parameter for the nbd driver (/sys/block/nbdX).

Action: It may be necessary to adjust one or more of:

NBD_NR_REQUESTS
NBD_SCHEDULER
LKDR_ASYNC_LIMIT

in /etc/default/LifeKeeper to avoid this error.

Cause: The mirror resize operation failed.

Cause: The mirror resize operation failed.

Cause: The mirror resize operation failed.

Cause: The mirror resize operation failed.

Cause: The specified resource is OSF. This prevents replication until this resource is repaired. The LKDR_WAIT_TO_RESYNC setting in /etc/default/LifeKeeper determines what resources must be in-service before replication is allowed.

Action: Determine the cause of the corruption and repair. This may involve bringing the resource in-service on another node. A full resync is most likely required once the data is repaired.

Cause: The specified resource is not in-service and is required before replication is resumed during a restore operation.

Action: Bring the required resources in-service to resume replication. Replication can also resume using the GUI command to resume or using the mirror_action command.

Cause: The /sys/module/nbd/taint file could not be opened for reading.

Action: Verify that the /sys/module/nbd/taint file exists and is read-enabled.

Cause: At least one kernel module required by SIOS DataKeeper failed to load.

Action: Verify that the current running kernel is supported by this version of SIOS Protection Suite for Linux. If the kernel was recently updated, re-run the SIOS Protection Suite for Linux setup script located on the SIOS installation media to install kernel modules that are compatible with the current running kernel.

Cause: Unable to read /proc/modules.

Action: Verify that the /proc/modules file exists and is read-enabled.

Cause: The given script or routine was called for an unsupported kernel module.

Action: This is an internal error. Please contact SIOS Customer Support.

Cause: Failed to load the given kernel module using the modprobe command.

Action: Inspect the output provided in the log message from the failed modprobe attempt and resolve any issues found there.

Cause: The given tag does not correspond to a LifeKeeper protected resource on the given system.

Action: Verify that the resource tag and system name are correct.

Cause: The scsi/netraid-specific canfailover script was called for a non-scsi/netraid resource.

Action: Use the canfailover script, if it exists, corresponding to the appropriate app and type of the given resource.

Cause: Invalid parameters passed to the SAP create script.

Action: Please provide appropriate parameters for the SAP create script.

Cause: Invalid parameters were specified when trying to create an internal SAP object.

Action: Provide either the SID and instance or the LifeKeeper resource tag name.

Cause: The sapservices file either does not exist or is not readable.

Action: Verify that the sapservices file exists and is readable.

Cause: Unable to find information about the given resource on the given server.

Action: Verify that the given resource exists and that all necessary file systems are mounted on the given server.

Cause: Unable to update the LifeKeeper resource information field for the given resource on the given server.

Action: Verify that the resource exists and that LifeKeeper is running on the given server.

Cause: Unable to find the given IP address or host name on the given server.

Action: Verify that the IP address or DNS name exists in DNS or in the local hosts file.

Cause: At least one NFS shared file system listed in the SAP_NFS_CHECK_DIRS parameter is currently unavailable.

Action: Verify that the NFS server is alive, all necessary NFS-related services are running, and that all necessary file systems are being exported.

Cause: Unable to find information about the given resource on the given server.

Action: Verify that the given resource exists and that all necessary file systems are mounted on the given server.

Cause: The SAP canextend script either does not exist or is not executable.

Action: Verify that the SAP canextend script exists and is executable.

Cause: Unable to create an internal SAP object to represent the given SAP instance.

Action: Verify that the SAP instance is properly installed and configured and that all necessary file systems are mounted.

Cause: The given SAP installation directory does not exist on the given server.

Action: Verify that the SAP software is properly installed and that all necessary file systems are mounted.

Cause: The saphostexec or saposcol utility either could not be found or is not executable.

Action: Verify that the SAP Host Agent package is installed correctly and that all necessary file systems are mounted.

Cause: The saphostexec or saposcol utility either could not be found or is not executable.

Action: Verify that the SAP Host Agent package is installed correctly and that all necessary file systems are mounted.

Cause: The given SAP instance is already protected by LifeKeeper on the given server.

Action: Choose an SAP instance which is not already under LifeKeeper protection.

Cause: Unable to determine the location of the SAP Mount (sapmnt) directory.

Action: Verify that all necessary file systems are mounted and that the all necessary SAP instance profiles are accessible.

Cause: Multiple virtual IPs or hostnames were detected for the given SAP instance on the given server.

Action: Verify that the virtual IP or hostname associated to the instance is configured correctly.

Cause: The given host name parameter is set to a physical server host name on the given server.

Action: Set the given host name parameter to a virtual host name.

Cause: Multiple SAP instances with the same instance number were detected under the same SAP SID.

Action: Reconfigure the SAP environment so that each instance under a given SAP SID has a unique instance number.

Cause: The NFS export for the given file system is not currently protected by LifeKeeper.

Action: Create a LifeKeeper NFS hierarchy for the given exported file system and reattempt SAP resource creation.

Cause: Unable to create a LifeKeeper file system resource hierarchy to protect the given file system on the given server.

Action: Check the LifeKeeper and system logs for more information.

Cause: Unable to create a LifeKeeper dependency between the given resources on the given server.

Action: Check the LifeKeeper logs for more information.

Cause: Unable to recover the given SAP resource on the given server.

Action: A failover of the SAP resource hierarchy will be attempted automatically. No user intervention is required.

Cause: The template and target servers provided during SAP resource extension are the same.

Action: Provide the correct names for the template and target servers and reattempt the extend operation.

Cause: Unable to find the home directory for the given SAP user on the given server.

Action: Verify that the SAP software is installed correctly and that the appropriate SAP administrative user for the given SID exists on the server.

Cause: The given SAP administrative user does not exist on the given server.

Action: Verify that the SAP software is properly installed and create the required SAP administrative user if necessary.

Cause: The group ID’s for the given SAP administrative user on the template and target servers do not match.

Action: Modify the group ID of the given SAP administrative user so that it is the same on the template and target servers.

Cause: The user ID’s for the given SAP administrative user on the template and target servers do not match.

Action: Modify the user ID of the given SAP administrative user so that it is the same on the template and target servers.

Cause: Unable to locate necessary SAP executables or the SAP instance profile.

Action: Verify that the SAP software is properly installed and configured and that all necessary file systems are mounted.

Cause: The given command was not found in the sap perl module on the given server.

Action: If this error resulted from a user-initiated command line action, verify that the correct routine name was provided to the remoteControl script. If this error occurred during normal LifeKeeper operation, please submit an issue report to SIOS customer support.

Cause: The given file does not have read/write permissions enabled on the given server.

Action: Enable read/write permissions on the given file.

Cause: Unable to create an internal SAP object to represent the given SAP instance.

Action: Verify that the SAP instance is properly installed and configured and that all necessary file systems are mounted.

Cause: The Autostart parameter is enabled in the given instance profile on the given server.

Action: Disable Autostart for the given SAP instance by setting ‘Autostart = 0’ in the instance profile.

Cause: Unable to start the SAP Start Service (sapstartsrv) process for the given SAP instance.

Action: Verify that the sapservices file contains the appropriate command to start the sapstartsrv process and that the process can be started manually.

Cause: Unable to stop the SAP Start Service (sapstartsrv) process for the given SAP instance.

Action: Verify that the sapservices file contains the appropriate command to start the sapstartsrv process and that the process can be stopped manually.

Cause: Unable to extend an SAP resource representing an ERSv1 instance to three or more nodes.

Action: In order to extend an SAP resource representing an ERS instance to three or more nodes, upgrade to ERSv2. Upgrade instructions are provided in the online product documentation.

Cause: The versions of the enqueue server and enqueue replication server do not match.

Action: Consult the online product documentation for instructions on how to modify the instance profiles so that the enqueue server and enqueue replication server are using the same version.

Cause: An in-service operation was attempted for an ASCS/SCS resource while its corresponding ERS instance was running and storing a backup enqueue table on a different server in the cluster.

Action: Bring the ASCS/SCS resource in-service on the server where its corresponding ERS instance is running in order for it to retrieve the backup enqueue table. If the ASCS/SCS resource must be forced in-service on the given node, either (i) run the command ‘/opt/LifeKeeper/bin/flg_create -f sap_cs_force_restore_<ASCS/SCS Tag>’ and reattempt the in-service operation, or (ii) take the corresponding ERS resource out of service on the remote server. Both of these actions will result in a loss of the backup enqueue table.

Cause: The GetEnqVersion routine was called for an unsupported SAP instance type. Only instance types 1 (TYPE_CS), 2 (TYPE_ERS), and 5 (TYPE_NEW_ERS) are supported.

Action: This is an internal error. Please submit an issue report to SIOS customer support.

Cause: The given instance profile either does not exist or cannot be read on the given server.

Action: Verify that the file exists and is read-enabled

Cause: The given resource could not be created on the given server.

Action: Verify that the SAP software is properly installed and that all necessary file systems are mounted and accessible on the given server.

Cause: While attempting to create a dependency, the given resource was not in-service on the given server.

Action: Bring the resource in-service on the given server and retry the operation.

Cause: Unable to find information about the given resource on the given server.

Action: Verify that the given resource exists and that all necessary file systems are mounted on the given server.