SteelEye Protection Suite for Linux
Version 8.1.1

Message Catalog
Core Messages
File System Kit Messages
Gen/App Kit Messages
IP Kit Messages
Oracle Listener Kit Messages
Oracle Kit Messages
SCSI Kit Messages
DataKeeper Messages

Core Message Catalog
Use Control F to search for a specific error code in each catalog.

Code

Severity

MessageCause/Action

000200

ERROR

pam_start() failed

000201

ERROR

pam_authenticate() failed

000202

ERROR

pam_end() failed?!?!

000203ERROR

Did not find expected group 'lkguest'

000204ERROR

Did not find expected group 'lkoper'

000205ERROR

Did not find expected group 'lkadmin'

000902

ERROR

Error removing system name from loopback address line in Cause: System name did not get removed from /etc/hosts/etc/hosts file. You must do this manually before starting
file.
the GUI server.
Action: Remove system name manually then restart the
GUI server, then enter the following: run <action name>000918ERROR

LifeKeeper GUI Server error during Startup

Cause: The GUI server terminated due to an abnormal
condition.
Action: Check the logs for related errors and try to resolve
the reported problem.

001052FATAL

Template resource "%s" on server "%s" does not exist

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

001053

ERROR

Cannot access canextend script "%s" on server "%s"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.

Page 2 of 69

SPS Message Catalog continued

Code

Severity

MessageCause/Action

001054

ERROR

Cannot extend resource "%s" to server "%s"Cause: LifeKeeper was unable to extend the resource{resource} on {server}.

001055

ERROR

Cannot access extend script "%s" on server "%s"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.

001057

ERROR

Cannot extend resource "%s" to server "%s"Cause: LifeKeeper was unable to extend the resource{resource} on {server}.

001059ERROR

Resource with tag "%s" already exists

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.

001060ERROR

Resource with either matching tag "%s" or id "%s" alreadyexists on server "%s" for App "%s" and Type "%s"Cause: The name or id provided for a resource is already inuse.
Action: Either choose a different name or id for the
resource or use the existing resource.

001061

ERROR

Error creating resource "%s" on server "%s"Cause: An unexpected failure occurred while creating a
resource.
Action: Check the logs for related errors and try to resolve
the reported problem.

001081WARN

IP address is neither v4 nor v6

Cause: The IP address provided is neither an IPv4 nor an
IPv6 address.
Action: Please check the name or address provided andtry again. If a name was provided, verify that nameresolution returns a valid IP address.

Page 3 of 69

SPS Message Catalog continued

Code004024

Severity

MessageCause/Action

ERROR

Cause: LCD failed to fetch resource information forresource id {id} during resource recovery.
Action: Verify the input resource id and retry the recovery
operation.

004028ERROR%s occurred to resource \"%s\"Cause: Local recovery failed for resource {resource}.
Action: Check the logs for related errors and try to resolve
the reported problem.

004055

ERROR

attempt to remote-remove resource \"%s\" that can't be
foundCause: 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.

004056

ERROR

attempt to remote-remove resource \"%s\" that is not ashared resource

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.

004060

ERROR

attempt to transfer-restore resource \"%s\" that can't be
foundCause: Remote transfer of an in service resource failed
given tag name {tag}.
Action: Check input tag name and retry the recovery
operation.

004061

ERROR

attempt to transfer-restore resource \"%s\" that is not ashared resource with machine \"%s\"Cause: LifeKeeper failed to find a shared resource by {tag}name during remote transfer of a resource in service from aremote {machine}.
Action: Check input tag name and retry the recovery
operation.

Page 4 of 69

SPS Message Catalog continued

Code004089Severity
ERROR

MessageCause/Action

ERROR: Parallel recovery initialization failed.\n

Cause: Parallel recovery failed to initialize the list ofresources in the hierarchy.
Action: Check the logs for related errors and try to resolve
the reported problem.

004093ERROR

ERROR: reserve failed. continuing to next resource\nCause: Parallel recovery failed to reserve a single resourcefrom the collective hierarchy.
Action: Check the logs for related errors and try to resolve
the reported problem.

004096ERROR

ERROR: clone %d is hung, attempting to kill it\nCause: A single sub process of a resource recovery ishung during parallel recovery of a whole resource hierarchy.
Action: A kill of the hanging sub process will be executed
automatically.

004097ERROR

ERROR: Could not kill clone %d\nCause: Failed to kill the hung sub process.

004116

ERROR%s

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 anddetermine why the intermediate folder is not created.

004117

ERROR

open(%s

Cause: Writing an on-disk version of an in-memory data
object failed while attempting to open a temporary file. Thisis a system error.
Action: Check log for the error information in detail anddetermine why the file is not successfully opened.

Page 5 of 69

SPS Message Catalog continued

Code004118Severity
ERROR

MessageCause/Action

write(%sCause: 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 anddetermine why the file writing is failed.

004119ERROR

fsync(%sCause: Writing an on-disk version of an in-memory data
object failed while attempting to fsync a temporary file. Thisis a system error.
Action: Check log for the error information in detail anddetermine why the "fsync" is failed.

004120

ERROR

close(%sCause: Writing an on-disk version of an in-memory data
object failed while attempting to close a temporary file. Thisis a system error.
Action: Check log for the error information in detail anddetermine why the file closing is failed.

004121

ERROR

rename(%s, %s

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 anddetermine why the file renaming is failed.

004122

ERROR

open(%s

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 anddetermine why the directory open is failed.

Page 6 of 69

SPS Message Catalog continued

Code004123Severity
ERROR

MessageCause/Action

fsync(%sCause: 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 anddetermine why the directory "fsync" is failed.

004124

ERROR

close(%sCause: 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 anddetermine why the directory close is failed.

004125

ERROR

wrote only %d bytes of requested %d\nCause: Writing an on-disk version of an in-memory data
object failed as the final size {size} bytes of written data isless than the requested number {number} of bytes.
Action: Check log for the related error information in detailand determine why the data writing is failed.

004126

ERROR

open(%s

Cause: Attempting to open a data file failed during thereading of an on-disk version of the data object into thebuffer. This is a system error.
Action: Check log for the error information in detail anddetermine why the file open is failed.

004127

ERROR

open(%s

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 anddetermine why the file open is failed.

Page 7 of 69

SPS Message Catalog continued

Code004128Severity
ERROR

MessageCause/Action

read(%s

Cause: Reading a data file failed during the loading of an
on-disk version of the data object into the buffer. This is asystem error.
Action: Check log for the error information in detail anddetermine why the file reading is failed.

004129

ERROR

read buffer overflow (MAX=%d)\nCause: 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.

004130

ERROR

close(%sCause: Failed to close a data file during reading an on-disk
version of the data object into the buffer. This is a systemerror.
Action: Check log for the error information in detail anddetermine why the file close is failed.

004131

ERROR

rename(%s, %s

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 anddetermine why the file renaming is failed.

004132

ERROR

Can't open %s : %s

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 asystem error.
Action: Check log for the error information in detail anddetermine why the open directory is failed.

Page 8 of 69

SPS Message Catalog continued

Code004133Severity
ERROR

MessageCause/Action

path argument may not be NULL

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".

004134

ERROR

destination path argument may not be NULL

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".

004135

ERROR

destination path can't be zero length string

Cause: Input destination path was empty during file copy
when using "lcdrcp".
Action: Check the input destination path and retry "lcdrcp".

004136

ERROR

open(%s

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.

004137

ERROR

fstat(%sCause: 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.

004138

ERROR

file \"%s\" is not an ordinary file (mode=0%o

Cause: Detected source file as a none ordinary file during
file copy using "lcdrcp".
Action: Check the input source file path and retry "lcdrcp".

004152

ERROR

having \"%s\" depend on \"%s\" would produce a loop

Cause: Adding the requested dependency would produce aloop of dependent relationship.
Action: Correct the requested dependency and retry thedependency creation.

Page 9 of 69

SPS Message Catalog continued

Code004164

Severity
ERROR

MessageCause/Action

Priority mismatch between resources %s and %s. Depend- Cause: The priorities for {resource1} and {resource2} do notency creation failed.
match.
Action: Resource priorities must match. Change one orboth priorities to the same value and retry creating thedependency.

004176

ERROR%s

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.

004190ERROR%s: ::receive(%d) did not receive message within %d seconds on incoming_mailbox %s

Cause: In function {function}, attempting to receive
message within timeout {timeout} seconds failed withincoming mailbox {mailbox}.
Action: Check the status of the connections inside thecluster and retry the process.

004205

ERROR

destination system \"%s\" is unknown

Cause: Sending message failed due to an unknown
destination system name {system}.
Action: Check the configuration and status of the systemand check the logs for related errors. Retry the sameprocess after the system is full initialized.

004206

ERROR

destination mailbox \"%s\" at system \"%s\" is unknown

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 systemand check the logs for related errors. Retry the sameprocess after the system is full initialized.

Page 10 of 69

SPS Message Catalog continued

Code004208Severity
ERROR

MessageCause/Action

destination system \"%s\" is alive but the mailbox process
is not listening.

Cause: Sending message failed. The network connection
to destination system {system} is alive but the contact tothe destination mailbox is lost.
Action: Check the configuration and status of the systemand check the logs for related errors. Retry the sameprocess after the system is full initialized.

004209

ERROR

destination system \"%s\" is dead.

Cause: Sending message failed due to losing connection
with the destination system {system}.
Action: Check the configuration and status of the systemand check the logs for related errors. Retry the sameprocess after the system is full initialized.

004211

ERROR

can't send to destination \"%s\" error=%dCause: 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.

004217

ERROR

destination system \"%s\" is out of service.

Cause: Sending message failed due to losing connection
with the destination system {system}.
Action: Check the configuration and status of the systemand check the logs for related errors. Retry the sameprocess after the system is full initialized.

004221

ERROR

destination system \"%s\" went out of service.

Cause: Sending message failed due to losing connection
with the destination system {system}.
Action: Check the configuration and status of the systemand check the logs for related errors. Retry the sameprocess after the system is full initialized.

Page 11 of 69

SPS Message Catalog continued

Code004228Severity
ERROR

MessageCause/Action

Can't get host name from getaddrinfo(

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.

004234ERROR

IP address pair %s already in use

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.

004258

WARN

Communication to %s by %s FAILED

Cause: Communication to system {system} bycommunication path {path} failed.
Action: Check system configuration and network
connection.

004261WARN

COMMUNICATIONS failover from system \"%s\" will bestarted.

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.

004292

ERROR

resource \"%s\" %sCause: 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.

004293

ERROR

resource \"%s\" %sCause: 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.

Page 12 of 69

SPS Message Catalog continued

Code004294

Severity
ERROR

MessageCause/Action

resource \"%s\" requires a license (for Kit %s/%s) but none Cause: The resource's related recovery kit requires ais installed
license.
Action: Install a license for the recovery kit on the serverwhere the resource was to be brought into service.

004297

ERROR

secondary remote resource \"%s\" on machine \"%s\" isalready in-service, so resource \"%s\" on machine \"%s\"can't be brought in-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 ofservice and do in service on local resource again.

004300

ERROR

restore of resource \"%s\" has failed

Cause: A resource could not be brought into service.
Action: Check the logs for related errors and try to resolve
the reported problem.

004311

ERROR

can't perform \"remove\" action on resources in state\"%s\"

Cause: A resource could not be put out of service due tothe current state being {state}.
Action: Check the logs for related errors and try to resolve
the reported problem.

004313

ERROR

remove of resource \"%s\" has failed

Cause: A resource {resource} could not be put out ofservice.
Action: Check the logs for related errors and try to resolve
the reported problem.

004318ERROR%s,priv_globact(%d,%s): script %s FAILED returning %d

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.

Page 13 of 69

SPS Message Catalog continued

Code004332

Severity
ERROR

MessageCause/Action

action \"%s\" has failed on resource \"%s\"Cause: A resource action failed.
Action: Check the logs for related errors and try to resolve
the reported problem.

004351ERROR

a \"%s\" equivalency must have one remote resource

Cause: Creating of a {eqvtype} equivalency failed due tothe two input tag names exist on the same system.
Action: Correct the inputs resource tag names and do thesame process again.

004376

FATAL

wait period of %u seconds for LCM to become available
has been exceeded (lock file \"%s\" not removed

Cause: The LCM daemon did not become available withina reasonable time and the LCD cannot operate without the
LCM.
Action: Check the logs for related errors and try to resolve
the reported problem.

004386

ERROR

initlcdMalloc;shmget

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 documentationand ensure that the server meets the minimum
requirements and that the operating system is configured
properly.

004444

WARN

License key (for Kit %s/%s) has EXPIRED

Cause: Your license has expired.
Action: Contact Support to obtain a new license.

004445004466

WARN

ERROR

License key (for Kit %s/%s) will expire at midnight in %ld
days

Cause: Your license is about to expire.

system \"%s\" not defined on machine \"%s\".

Cause: The specified system name is not known.

Action: Contact Support to obtain a new license.

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

Page 14 of 69

SPS Message Catalog continued

Code004467

Severity
ERROR

MessageCause/Action

system \"%s\" unknown on machine \"%s\"Cause: The specified system name is not recognized.
Action: Verify the system name, and try the operation
again.

004494

ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004495ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004496ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004497

ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004498ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

Page 15 of 69

SPS Message Catalog continued

Code004499Severity
ERROR

MessageCause/Action

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004500ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004501ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004502ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004503

ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004504

ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

Page 16 of 69

SPS Message Catalog continued

Code004505

Severity
ERROR

MessageCause/Action

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004506ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004507

ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004508ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004509ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004510ERROR

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

Page 17 of 69

SPS Message Catalog continued

Code004511

Severity
ERROR

MessageCause/Action

COMMAND OUTPUT: %s

Cause: An action or event script produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

004512

ERROR

Cause: An error occured on the remote machine.
Action: Check the logs on the remote machine for
additional details.

004565

ERROR

can't set resource state type to ILLSTATE

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.

004567

ERROR

resource \"%s\" can't be changed to \"%s\" state because Cause: Change resource {resource} to state {state} failed
it is a primary resource of a SHARED equivalency tosince its SHARED equivalency primary resource
resource \"%s\" on machine \"%s\" which is in state \"%s\" {resource} on machine {machine} is in state {state}.
Action: Check the input or manually put the primaryresource out of service and try the same process again.

004607

ERROR

no resource instance has tag \"%s\"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.

004608

ERROR

no resource instance has identifier \"%s\"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.

004619

ERROR

resource with tag \"%s\" already exists with identifier\"%s\"

Page 18 of 69

Cause: The provided tag name already exists.
Action: Choose a different tag name.

SPS Message Catalog continued

Code004620004643004646

Severity
ERROR

ERROR

ERROR

MessageCause/Action

resource with identifier \"%s\" already exists with tag\"%s\"

Cause: The provided identifier already exists.

Instance tag name is too long. It must be shorter than %dcharacters.

Cause: Tag name is too long.

Tag name contains illegal characters

Cause: Tag name contains an illegal character.

Action: Choose a different identifier to use for thisresource.

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

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

ERROR

can't set both tag and identifier at same time

Cause: Both a tag and an identifier were specified.
Action: Provide only one of tag or identifier.

004782

ERROR

Resource \"%s\" was in state \"%s\" before event occurred Cause: The resource is already in service. Recovery will
- recovery will not be attempted
not be attempted.

004783

ERROR

Resource \"%s\" was already in state \"%s\" before event
occurred

Cause: A resource was not in an appropriate state to allow
recovery.
Action: Put the resource in the ISP state if recovery is stillneeded.

004786

ERROR%s on failing resource \"%s\"Cause: An error occured why attempting to recover aresource.
Action: Check the logs for related errors and try to resolve
the reported problem.

Page 19 of 69

SPS Message Catalog continued

Code004788Severity
EMERG

MessageCause/Action

failed to remove resource '%s'. SYSTEM HALTED.

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.

004793ERROR

lcdsendremote transfer resource \"%s\" to \"%s\" onmachine \"%s\" failed (rt=%d

Cause: A failure occured while transfering a resource andit'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.

004797

ERROR

Restore of SHARED resource \"%s\" has failed

Cause: There was an error while restoring a resource.
Action: Check the logs for related errors and try to resolve
the reported problem.

004806

ERROR

Restore in parallel of resource \"%s\" has failed; will re-try
serially

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 torecover 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.

004819ERROR

read_temporal_recovery_log(): failed to fopen file: %s.
fopen() %s.

Cause: The opening of the temporal recovery log file {file} inpreparation for loading into it into memory failed with theerror {error}.
Action: Check system log files and correct any reported
errors before retying the operation.

Page 20 of 69

SPS Message Catalog continued

Code004820

Severity
ERROR

MessageCause/Action

read_temporal_recovery_log(): failed to malloc initial buf for Cause: Loading the temporal recovery log information into
temporal_recovery_stamp.
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.

004821

ERROR

read_temporal_recovery_log(): failed to reallocate buffer for Cause: Loading the temporal recovery log information into
temporal_recovery_stamp.
memory failed when attempting to increase the amount ofmemory required to store the log information.
Action: Check system log files and correct any reported
errors before retrying the operation.

004822

ERROR

write_temporal_recovery_log(): failed to open file: %s.

Cause: The update of the temporal recovery log file wasterminated when the open of the temporary file {temporaryname} failed.
Action: Check system log files and correct any reported
errors before retrying the operation.

004823

ERROR

rename(%s, %s) failed.

Cause: The update of the temporal recovery log file wasterminated 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.

004829FATAL

err=%s line=%d Semid=%d numops=%u perror=%s

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.

Page 21 of 69

SPS Message Catalog continued

Code004860

Severity
ERROR

MessageCause/Action

restore ftok failed for resource %s with path %s

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.

004861

ERROR

semget failed with error %d

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.

004862

ERROR

semctl SEMSET failed with error %d

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.

004863

ERROR

semop failed with error %d

Cause: The attempt to set a semaphore used during therecovery 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.

Page 22 of 69

SPS Message Catalog continued

Code004864

Severity
ERROR

MessageCause/Action

semctl SEMSET failed with error %d

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.

004865

ERROR

restore action failed for resource %s

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.

004872

ERROR

Remote remove of resource \"%s\" on machine \"%s\"failed (rt=%d

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.

004875

ERROR

remote remove of resource \"%s\" on machine \"%s\" failed 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.

004876

ERROR

remote remove of resource \"%s\" on machine \"%s\" failed 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.

Page 23 of 69

SPS Message Catalog continued

Code005045

Severity
ERROR

MessageCause/Action

tli_fdget_i::execute unable to establish a listener port

Cause: A network connection could not be properly
configured.
Action: Verify that all network hardware and drivers areproperly configured. If this message continues andresources cannot be put into service, contact Support.

005055

ERROR

tli_fdget_o::execute - async connect failure

Cause: A network connection could not be properly
configured.
Action: Verify that all network hardware and drivers areproperly configured. If this message continues andresources cannot be put into service, contact Support.

005061

ERROR

tli_fdget_o::execute - bind socket

Cause: A network connection could not be properly
configured.
Action: Verify that all network hardware and drivers areproperly configured. If this message continues andresources cannot be put into service, contact Support.

005145

ERROR

opening the file

Cause: A pipe could not be opened or created.
Action: Check adjacent log messages for more details.

005225006012

WARN

ERROR

so_driver::handle_error: sending/receiving data message
errno %d: %s

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.

quickCheck script '%s' failed to exit after %u seconds. For- Cause: A quickCheck script is probably taking too long or
cibly terminated. Please examine the script or adjust thehanging.
LKCHECKINTERVAL parameter in %s.
Action: Perform the steps listed in the message text.

Page 24 of 69

SPS Message Catalog continued

Code006102

Severity
ERROR

MessageCause/Action

COMMAND OUTPUT: $LKROOT/bin/sendevent

Cause: This is output from a "sendevent "(event generator)
command.
Action: Check adjacent log messages for more details.

006103

ERROR

COMMAND OUTPUT: $LKROOT/bin/sendevent

Cause: This is output from a "sendevent" (event generator)
command.
Action: Check adjacent log messages for more details.

006104

ERROR

COMMAND OUTPUT: $LKROOT/bin/sendevent

Cause: This is output from a "sendevent" (event generator)
command.
Action: Check adjacent log messages for more details.

007058ERROR%s: %s failed on '%s', result:%d, Sense Key = %d.

Cause: A SCSI device couldn't be reserved or have its
status checked. This may be because the storage ismalfunctioning or because the disk has been reserved byanother server.
Action: Check adjacent log messages for more details andverify that resources are being handled properly.

007059ERROR%s: %s failed on '%s', result:%d.

Cause: A SCSI device couldn't be reserved or have its
status checked. This may be because the storage ismalfunctioning or because the disk has been reserved byanother server.
Action: Check adjacent log messages for more details andverify that resources are being handled properly.

Page 25 of 69

SPS Message Catalog continued

Code007060

Severity
EMERG

MessageCause/Action%s: failure on device '%s'. SYSTEM HALTED.

Cause: A SCSI device couldn't be reserved or have its
status checked. This may be because the storage ismalfunctioning or because the disk has been reserved byanother 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.

007072ERROR%s: failed to open SCSI device '%s', initiate recovery.
errno=0x%x, retry count=%d.

Cause: The protected SCSI device could not be opened.
The device may be failing or may have been removed fromthe system.
Action: The system will be halted or a failover to the
backup node will be initiated. The default action in this caseis a failover, but this can be modified with the
SCSIERROR tunable.

007073ERROR%s: failed to open SCSI device '%s', RETRY. errno=%d,retry count=%d.

Cause: The protected SCSI device could not be opened.
The device may be failing or may have been removed fromthe 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.

007075ERROR%s: RESERVATION CONFLICT on SCSI device '%s'.
ret=%d, errno=0x%x, retry count=%d.

Cause: A SCSI device couldn't be reserved due to aconflict with another server. This may be because thestorage is malfunctioning or because the disk has been
reserved by another server.
Action: Check adjacent log messages for more details andverify that resources are handled properly.

Page 26 of 69

SPS Message Catalog continued

Code007077

Severity
ERROR

MessageCause/Action%s: DEVICE FAILURE on SCSI device '%s', initiate
recovery. ret=%d, errno=0x%x, retry count=%d.

Cause: A SCSI device couldn't be reserved or have its
status checked. This may be because the storage ismalfunctioning or because the disk has been reserved byanother server.
Action: Check adjacent log messages for more details andverify that resources are handled properly.

007078ERROR%s: DEVICE FAILURE on SCSI device '%s', RETRY.
ret=%d, errno=0x%x, retry count=%d.

Cause: A SCSI device couldn't be reserved or have its
status checked. This may be because the storage ismalfunctioning or because the disk has been reserved byanother server.
Action: Check adjacent log messages for more details andverify that resources are handled properly.

010002

WARN

flag $flag not present, send message again.

Cause: This message indicates an incomplete processthat will be retried.
Action: Check adjacent log messages for repeated errors.

010003

ERROR

COMMAND OUTPUT: $LKBIN/ins_remove

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.

010004

EMERG

Cannot find the $LKROOT/config/lkstart-hook file. You
must install the LifeKeeper Distribution Enabling package
before starting $PRODUCT.

Cause: This error may be caused by installing LifeKeeper
directly using the rpms, or perhaps by inadvertently
removing an rpm from the system.
Action: You should reinstall LifeKeeper using the 'setup'
script on the installation media.

Page 27 of 69

SPS Message Catalog continued

Code
010006

Severity
WARN

MessageCause/Action

flg_list -d $i took more than $pswait seconds to complete... Cause: A flag list operation on a server took much longer
than expected. There may be a problem communicatingwith the other server.
Action: Check adjacent log messages for more details.

010007

ERROR

flag $flag not present, switchovers may occur.

Cause: One of the servers in the cluster could not be told todisallow failover operations from the current server.
Action: Check adjacent log messages for more details andmonitor the cluster for unexpected behavior.

010008WARN

flag $flag not present, send message again.

Cause: A process is incomplete but will be retried.
Action: Check adjacent log messages for more details andfor repeated warnings/errors.

010023FATAL

LifeKeeper failed to initialize properly.

Cause: There was a fatal error while attempting to start
LifeKeeper.
Action: Check adjacent log messages for more details.

010025

ERROR`printf 'Unable to get a unique tag name on server "%s" fortemplate resource "%s"' $MACH $DISK`

Cause: A suitable tag during the create process for astorage resource could not be automatically generated.
Action: Check adjacent log messages for more details.
Retry the operation if there are no other errors.

010034FATAL

Unable to start lcm.

Cause: A core component of the software could not be
started.
Action: Check adjacent log messages for more details andtry to resolve the reported problem.

010038

WARN

Waiting for LifeKeeper core components to initialize has
exceeded 10 seconds. Continuing anyway, check logs forfurther details.

Page 28 of 69

Cause: Some parts of the software are taking longer than
expected to start up.
Action: Perform the steps listed in the message text.

SPS Message Catalog continued

Code010039010046

Severity
WARN

ERROR

MessageCause/Action

Waiting for LifeKeeper core components to initialize has
exceeded 10 seconds. Continuing anyway, check logs forfurther details.

Cause: Some parts of the software are taking longer than
expected to start up.
Action: Perform the steps listed in the message text.

The dependency creation failed on server $SERVER:" `cat Cause: A dependency relationship could not be created on$TEMP_FILE`
the given server.
Action: Check the logs for related errors and try to resolve
the reported problem

010063

ERROR$REMSH error

Cause: A command to request data to backup from anotherserver failed.
Action: Check the logs for related errors and try to resolve
the reported problem.

010085

ERROR

lkswitchback($MACH): Automatic switchback of \"$loctag\" failed

Cause: The resource was not switched back over as
expected.
Action: Check the logs for related errors and try to resolve
the reported problem.

010102

ERROR

admin machine not specified

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.

010107

WARN

Lock for $m is ignored because system is OOS

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 aharmless error.

Page 29 of 69

SPS Message Catalog continued

Code010108Severity
ERROR

MessageCause/Action

lock acquisition timeout

Cause: Acquiring a lock tool longer than expected/allowed.
Action: Check the logs for related errors and try to resolve
the reported problem.

010109

ERROR

could not get admin locks." `cat /tmp/ER$$`

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.

010112

ERROR

lcdrcp failed with error no: $LCDRCPRES

Cause: A file could not be copied to another server.
Action: Check the logs for related errors and try to resolve
the reported problem.

010116

ERROR

unable to set !lkstop flag

Cause: A flag could not be set to indicate that the server isbeing stopped by user request.
Action: Check the logs for related errors and try to resolve
the reported problem.

010222

ERROR

scsifree(%s): LKSCSI_Release(%s) unsuccessful

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 thesystem is functioning properly.

010231

ERROR

scsiplock(%s): reserve failed.

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.

Page 30 of 69

SPS Message Catalog continued

Code010250

Severity
ERROR

MessageCause/Action

Failed to exec command '%s'

Cause: The "lklogmsg" tool failed to execute a subcommand {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.

010402

EMERG

local recovery failure on resource $opts{'N'}, trigger
VMware HA...

Cause: When in "single-node" operation (vAppKeeper), a
resource could not be recovered and VMware-HA is about
to be triggered to handle the failure (if VMware-HA isenabled).
Action: No action is required. VMware should handle thefailure.

010413

ERROR

COMMAND OUTPUT: cat /tmp/err$$

Cause: This is the output from an "snmptrap" commandthat may have failed.
Action: Check the logs for related errors and try to resolve
the reported problem.

010440ERROR[$SUBJECT event] mail returned $err

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.

010443

ERROR

COMMAND OUTPUT: cat /tmp/err$$

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.

Page 31 of 69

SPS Message Catalog continued

Code010445

Severity
ERROR

MessageCause/Action

COMMAND OUTPUT: cat /tmp/err$$

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.

010463

ERROR

LifeKeeper: name of machine is not specified,
ARGS=$ARGS

Cause: Invalid arguments were specified for the "comm_down" event.
Action: Check your LifeKeeper configuration and retry theoperation.

010471

ERROR

COMM_DOWN: Attempt to obtain local comm_down lock
flag failed

Cause: During the handling of a communication failure withanother 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.

010482ERROR

LifeKeeper: name of machine is not specified,
ARGS=$ARGS

Cause: Invalid arguments were specified for the "comm_up" event.
Action: Check your LifeKeeper configuration and retry theoperation.

010484

WARN

flg_list -d $MACH check timed-out ($delay seconds).

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

010487

WARN

flg_list -d $MACH check timed-out, unintended switchovers may occur.

Cause: "flg_list" command reached its timeout value.

Page 32 of 69

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

SPS Message Catalog continued

Code010492

Severity
WARN

MessageCause/Action$m

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.

010494

ERROR

LifeKeeper: COMM_UP to machine $MACH completedwith errors.

Cause: An unexpected failure occurred during "COMM_
UP" event.
Action: Check adjacent log messages for more details.

010503

ERROR

lcdrecover hung or returned error, attempting kill of process Cause: "lcdrecover" took too long or errored out.
$FPID

010506ERROR

Intelligent Switchback Check Failed

Cause: Failed 5 times to perform "lcdrecover."Action: Switch over the resource tree manually.

010508ERROR[$SUBJECT] sent to $LK_NOTIFY_ALIAS

010600

ERROR

removing hierarchy remnants

010627

WARN

Equivalency Trim: does not have a full complement ofequivalencies. Hierarchy will be unextended from

010629WARN

Your hierarchy exists on only one server. Your application
has no protection until you extend it to at least one otherserver.

010712

ERROR

Unextend hierarchy failed

Cause: This message is for information only.

Cause: A resource hierarchy failed to be unextended from aserver.
Action: Check the logs for related errors and try to resolve
the reported problem.

Page 33 of 69

SPS Message Catalog continued

Code010746

Severity
ERROR

MessageCause/Action$ERRMSG Target machine \"$TARGET_MACH\" does
not have an active LifeKeeper communication path tomachine \"$aMach\" in the hierarchy." >&2

Cause: A hierarchy cannot be unextended because thetarget server does not have adequate communication withthe other servers in the cluster.
Action: Check the logs for related errors and try to resolve
the reported problem. Ensure that all servers havecommunication paths to each other.

011000

ERROR

appremote: unknown command type %d('%c')\nCause: Internal error.
Action: Try restarting the product.

011001

ERROR

depremote: unknown command type %d('%c')\nCause: Internal error.
Action: Try restarting the product.

011002

ERROR

eqvremote: unknown command type %d('%c')\nCause: Internal error.
Action: Try restarting the product.

011003

ERROR

flgremote: unknown command type %d('%c')\nCause: Internal error.
Action: Try restarting the product.

011004

WARN

Illegal creation of resource

Cause: This will not occur under normal circumstances.

011011FATAL%sCause: LifeKeeper could not get IPC key.
Action: Check adjacent log messages for more details.

011012FATAL

semget(%s,%cCause: LifeKeeper could not get semaphore set id.
Action: Check adjacent log messages for more details.

011013FATAL

shmget(%s,%cCause: System could not allocate a shared memory
segment.
Action: Check adjacent log messages for more details.

Page 34 of 69

SPS Message Catalog continued

Code011014

Severity
FATAL

MessageCause/Action

prefix_lkroot("out"Cause: A system error has occurred while accessing/opt/LifeKeeper/out.
Action: Determine why /opt/LifeKeeper/out is notaccessible.

011015

ERROR

DEMO_UPGRADE_MSG

Cause: You are running a demo license.
Action: Contact Support to obtain a new license.

011016

ERROR

lic_single_node_msg

Cause: You have a license for vAppKeeper, but you do nothave vAppKeeper installed.
Action: Either install vAppKeeper, or obtain a license thatmatches the product you are running.

011017

ERROR

lic_init_fail_msg, "flex_init failed"

Cause: License manager initialization failed.
Action: Check adjacent log messages for more details.

011018ERROR

lic_init_fail_msg, lc_errstring(lm_job

Cause: License manager initialization failed.
Action: Check adjacent log messages for more details.

011019EMERG

lic_init_fail_msg, "flex_init failed"

Cause: License manager initialization failed.
Action: Check adjacent log messages for more details.

011020EMERG

lic_init_fail_msg, lc_errstring(lm_job

Cause: License manager initialization failed.
Action: Check adjacent log messages for more details.

011021

EMERG

lic_error_msg, lc_errstring(lm_job

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011022

EMERG

lic_error_msg, lc_errstring(lm_job

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

Page 35 of 69

SPS Message Catalog continued

Code011023Severity
EMERG

MessageCause/Action

lic_no_rest_suite, ""Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011024

EMERG

lic_error_msg, lc_errstring(lm_job

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011025

EMERG

lic_no_license, ""Cause: LifeKeeper could not find valid license keys.
Action: Ensure license keys are valid for the server andretry the operation.

011026

EMERG

lic_error_msg, lc_errstring(lm_job

Cause: There is an unknown problem with your license.
Action: Contact Support to obtain a new license.

011027

EMERG

lic_no_license, ""Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011028

ERROR

lang_error_msg

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011029FATAL

can't set reply system

Cause: A message failed to be sent.
Action: Check adjacent log messages for more details.
This may be a temporary error.

011030

FATAL

can't set reply mailbox

Cause: A message failed to be sent.
Action: Check adjacent log messages for more details.
This may be a temporary error.

011031

ERROR

Failure reading output of '%s' on behalf of %s

Cause: A system error has occurred while accessing
temporary file /tmp/OUT.{pid}.
Action: Determine why /tmp/OUT.{pid} is not accessible.

Page 36 of 69

SPS Message Catalog continued

Code011032

Severity
ERROR

MessageCause/Action

Failure reading output of '%s'

Cause: A system error has occurred while accessing
temporary file /tmp/ERR.{pid}.
Action: Determine why /tmp/ERR.{pid} is not accessible.

011033

ERROR

event \"%s,%s\" already posted for resource with id \"%s\" Cause: This message is for information only.

011034

ERROR

no resource has id of \"%s\"Cause: LifeKeeper could not find the {id} resource.
Action: Verify the parameters and retry the "sendevent"
operation.

011044

ERROR

flagcleanup:fopen(%sCause: A system error has occurred while reading/opt/LifeKeeper/config/flg.
Action: Determine why /opt/LifeKeeper/config/flg is notreadable.

011045

ERROR

flagcleanup:fopen(%sCause: A system error has occurred while writing/opt/LifeKeeper/config/flg.
Action: Determine why /opt/LifeKeeper/config/flg is notwritable.

011046

ERROR

flagcleanup:fputs(%sCause: A system error has occurred while writing/opt/LifeKeeper/config/flg.
Action: Determine why /opt/LifeKeeper/config/flg is notwritable.

011047

ERROR

flagcleanup:rename(%s,%s

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 notable to be renamed.

Page 37 of 69

SPS Message Catalog continued

Code011048Severity
ERROR

MessageCause/Action

flagcleanup:chmod(%sCause: 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.

011049

ERROR

License check failed with error code %d

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011051

ERROR

lcdinit: clearing Disk Reserve file failed

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.

011052FATAL

malloc() failed

Cause: The system could not allocate memory for
LifeKeeper.
Action: Increase the process limit for the data segment.

011053FATAL

lcm_is_unavail

Cause: A system error has occurred while writing /tmp/LK_
IS_UNAVAIL.
Action: Determine why /tmp/LK_IS_UNAVAIL is notwritable.

011054FATAL

lk_is_unavail

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.

Page 38 of 69

SPS Message Catalog continued

Code011055

Severity
FATAL

MessageCause/Action

usr_alarm_config_LK_IS_ON

Cause: A system error has occurred while writing/tmp/LCM_IS_UNAVAI.
Action: Determine why /tmp/LCM_IS_UNAVAI is notwritable.

011056

ERROR

License check failed with error code %d

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011057

ERROR

lcdremote: unknown command type %d('%c')\nCause: 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.

011059FATAL

Could not write to: %s

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.

011060FATAL

received NULL message

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.

011061

ERROR

unknown data type %d('%c') on machine \"%s\"\nCause: 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.

Page 39 of 69

SPS Message Catalog continued

Code011062

Severity
WARN

MessageCause/Action

LifeKeeper shutdown in progress. Unable to perform failover recovery processing for %s\nCause: LifeKeeper was unable to fail over the given
resource during shutdown.
Action: Switch over the resource tree to other server
manually.

011063

WARN

LifeKeeper resource initialization in progress. Unable to per- Cause: LifeKeeper was unable to fail over the given
form failover recovery processing for %s\nresource during start up.
Action: Switch over the resource tree manually after
LifeKeeper starts up.

011068ERROR

ERROR on command %s

Cause: An error occurred while running the "rlslocks"
command.
Action: Check adjacent messages for more details.

011070ERRORERROR on command %s

Cause: An error occurred while running the "getlocks"
command.
Action: Check adjacent log messages for more details.

011081FATAL

Failed to ask ksh to run: %s

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.

011082

ERROR

Failed to remove: %s

Cause: A system error has occurred while removing/tmp/LCM_IS_UNAVAIL.
Action: Determine why /tmp/LCM_IS_UNAVAIL is notremovable.

011083

ERROR

Failed to remove: %s

Cause: A system error has occurred while trying to unlink/tmp/LK_IS_UNAVAIL.
Action: Determine why /tmp/LK_IS_UNAVAIL is notremovable.

Page 40 of 69

SPS Message Catalog continued

Code011084

Severity
FATAL

MessageCause/Action

Failed to generate an IPC key based on: %s

Cause: A system error has occurred while accessing/opt/LifeKeeper.
Action: Determine why /opt/LifeKeeper is not accessible.

011085

ERROR

semget(%s,%c) failed

Cause: A system error has occurred while removing asemaphore.
Action: Try to remove the semaphore manually.

011086

ERROR

shmget(%s,%c) failed

Cause: A system error has occurred while removing ashared memory segment.
Action: Try to remove the shared memory segment
manually.

011087

ERROR

semctl(IPC_RMID) failed

Cause: A system error has occurred while removing asemaphore.
Action: Try to remove the semaphore manually.

011088

ERROR

shmctl(IPC_RMID) failed

Cause: A system error has occurred while removing ashared memory segment.
Action: Try to remove the shared memory segment
manually.

011089FATAL

Execution of lcdstatus on remote system <%s> failed\nCause: 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 checkadjacent messages for additional information, or check thelogs on the remote node for additional information.

011091

WARN

Cause: This will not occur under normal circumstances.

Page 41 of 69

SPS Message Catalog continued

Code011092

Severity

MessageCause/Action

FATAL

Cause: There is a problem with your license.
Action: Perform the steps listed in the message text.

011093FATAL

Cause: There is a problem with your license.
Action: Perform the steps listed in the message text.

011094FATAL

Cause: There is a problem with your license.
Action: Perform the steps listed in the message text.

011095FATAL

Cause: There is a problem with your license.
Action: Perform the steps listed in the message text.

011096FATAL

Cause: There is a problem with your license.
Action: Perform the steps listed in the message text.

011097FATAL

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011098FATAL

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011099FATAL

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011100FATAL

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011101FATAL

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

Page 42 of 69

SPS Message Catalog continued

Code011102

Severity

MessageCause/Action

FATAL

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011103FATAL

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011104FATAL

Cause: There is a problem with your license.
Action: Contact Support to obtain a new license.

011105FATAL

Cause: There is a problem with your license.
Action: Perform the steps listed in the message text.

011111

ERROR

action \"%s\" on resource with tag \"%s\" has failed

Cause: The {action} for resource {tag} has failed.
Action: See adjacent error messages for further details.

011112

ERROR

Cause: LifeKeeper could not find the network device.
Action: Check your LifeKeeper configuration.

011117

ERROR

sysremote: system \"%s\" not found on \"%s\"Cause: An invalid system name was provided.
Action: Recheck the system name and rerun thecommand.

011129

ERROR

Failure during run of '%s' on behalf of %s

Cause: Command execution failed.
Action: See message details to determine the problem.

011130

ERROR%s

Cause: The command {command} produced unexpected
output.
Action: Action should be determined by the content ofadjacent error messages.

Page 43 of 69

SPS Message Catalog continued

Code011131

Severity
EMERG

MessageCause/Action

demo_update_msg

Cause: There is a problem with your demo license.
Action: Contact Support to obtain a new license.

011132

EMERG

demo_tamper_msg

Cause: You have a demo license and clock tampering has
been detected.
Action: Contact Support to obtain a new license.

011133

EMERG

demo_tamper_msg

Cause: You have a demo license and clock tampering has
been detected.
Action: Contact Support to obtain a new license.

011134

EMERG

demo_expire_msg

Cause: The demo license for this product has expired.
Action: Contact Support to obtain a new license.

011135

EMERG

demo_tamper_msg

Cause: You have a demo license and clock tampering has
been detected.
Action: Contact Support to obtain a new license.

011136

EMERG

buf

Cause: You are running a demo license.
Action: Contact Support to obtain a new license.

011138

EMERG

buf

Cause: You are running a demo license.
Action: Contact Support to obtain a new license.

011142WARN

LifeKeeper Recovery Kit %s license key NOT FOUND

Cause: An Application Recovery Kit license for {kit} was
not found.
Action: Contact Support to obtain a new license.

Page 44 of 69

SPS Message Catalog continued

Code011150

Severity
ERROR

MessageCause/Action

COMMAND OUTPUT: %s

Cause: The command "eventslcm" produced unexpected
output.
Action: Check the logs for related errors and try to resolve
the reported problem.

011151

EMERG&localebuf[3]Cause: This version of the LifeKeeper core package isrestricted to being used within the territories of the People's
Republic of China or Japan.

011152

EMERG

Localized license failure

Cause: There was a mis-match between your locale andthe locale for which the product license was created.
Action: Contact Support to obtain a new license whichmatches your locale.

011154EMERG

Single Node flag check failed.

Cause: You have a license for vAppKeeper but you do nothave vAppKeeper installed.
Action: Either install vAppKeeper or obtain a license thatmatches the product you are running.

011155

EMERG

lic_master_exp_msg, ""Cause: Your license key for this product has expired.
Action: Contact Support to obtain a new license.

011162

EMERG

lic_restricted_exp_msg, ""Cause: Your license key for this product has expired.
Action: Contact Support to obtain a new license.

011163

EMERG

Single Node license check failed

Cause: You have a license for vAppKeeper but you do nothave vAppKeeper installed.
Action: Either install vAppKeeper or obtain a license thatmatches the product you are running.

Page 45 of 69

SPS Message Catalog continued

Code011164

Severity
EMERG

MessageCause/Action

demo_expire_msg, DEMO_UPGRADE_MSG

Cause: Your license key for this product has expired.
Action: Please contact Support to obtain a permanent
license key for your product.

015000ERROR

COMMAND OUTPUT: /opt/LifeKeeper/sbin/steeleyelighttpdCause: An error has ocurred with the "steeleye-lighttpd"
process. Specific details of the error are included in theactual log message.
Action: Correct the configration and "steeleye-lighttpd" willautomatically be restarted.

DB2 Kit Message Catalog
Use Control F to search for a specific error code in each catalog.

Code103001103002103003103004

Severity
ERROR

ERROR

ERROR

ERROR

MessageCause/Action

LifeKeeper has detected an error while trying to determine
the node number(s) of the DB partition server(s) for the
instance

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

LifeKeeper was unable to get the version for the requested
instance "%s"Cause: "db2level" command did not return DB2 version.

LifeKeeper has detected an error while trying to determine
the node number(s) of the DB partition server(s) for the
instance

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

Unable to get the information for resource "%s"Cause: Failed to get resource information.

Action: Ensure the db2nodes.cfg is valid.

Action: Check your DB2 configuration.

Action: Check your DB2 configuration.

Action: Check your LifeKeeper configuration.

Page 46 of 69

SPS Message Catalog continued

Code103005

Severity
ERROR

MessageCause/Action

Unable to get the information for resource "%s"Cause: Failed to get resource information.
Action: Check your LifeKeeper configuration.

103006

ERROR

Unable to get the instance information for resource "%s"Cause: Failed to get the instance information.
Action: Check your LifeKeeper configuration.

103007103008

ERROR

ERROR

Unable to get the instance home directory information forresource "%s"Cause: Failed to get the instance home directory path.

Unable to get the instance type information for resource"%s"Cause: The DB2 Application Recovery kit found invalid
instance type.

Action: Check your LifeKeeper configuration.

Action: Check your LifeKeeper configuration.
103009ERROR

LifeKeeper has encountered an error while trying to get the
database configuration parameters for database \"$DB\"

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.

103012103013103015

ERROR

ERROR

ERROR

LifeKeeper was unable to start the database server for
instance "%s"Cause: The requested start up of the DB2 instance failed.

LifeKeeper was unable to start the database server for
instance "%s"Cause: The requested start up 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.

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

An entry for the home directory "%s" of instance "%s" does Cause: The home directory of instance of Multiple Partition
not exist in "/etc/fstab"database should exist in "/etc/fstab".
Action: Ensure the home directory exist in "/etc/fstab".

Page 47 of 69

SPS Message Catalog continued

Code103016

Severity
ERROR

MessageCause/Action

LifeKeeper was unable to mount the home directory for theDB2 instance "%s"Cause: Failed to mount the home directory of instance ofMultiple Partition database.
Action: Ensure the home directory is mounted and retry theoperation.

103017103018103020

ERROR

ERROR

ERROR

Unable to get the instance nodes information for resource"%s"Cause: Failed to get the instance nodes.

LifeKeeper was unable to start database partition server"%s" for instance "%s"Cause: The requested start up of the DB2 instance failed.

LifeKeeper was unable to stop the database server for
instance "%s"Cause: The requested shutdown of the DB2 instancefailed.

Action: Check your LifeKeeper configuration.

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

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

LifeKeeper was unable to stop the database server for
instance "%s"Cause: The requested shutdown of the DB2 instancefailed.
Action: Check the logs for related errors and try to resolve
the reported problem. Correct any reported errors before
retrying the "remove" operation.

103023

ERROR

Unable to get the instance nodes information for resource"%s"Page 48 of 69

Cause: Failed to get the instance nodes.
Action: Check your LifeKeeper configuration.

SPS Message Catalog continued

Code103024

Severity
ERROR

MessageCause/Action

LifeKeeper was unable to stop database partition server"%s" for instance "%s"Cause: The requested shutdown of the DB2 instancefailed.
Action: Check the logs for related errors and try to resolve
the reported problem. Correct any reported errors before
retrying the "remove" operation.

103026103027

ERROR

FATAL

Unable to get the instance nodes information for resource"%s"Cause: Failed to get the instance nodes.

The argument for the DB2 instance is empty

Cause: Invalid parameters were specified for the create
operation.

Action: Check your LifeKeeper configuration.

Action: Verify the parameters and retry the operation.
103028FATAL

Unable to determine the DB2 instance home directory

Cause: The DB2 Application Recovery Kit was unable todetermine the DB2 instance home directory.
Action: Ensure the instance owner name is same as theinstance name and retry the operation.

103029FATAL

Unable to determine the DB2 instance type

Cause: The DB2 Application Recovery Kit was unable todetermine the DB2 instance type.
Action: Check your DB2 configuration.

103030103031

FATAL

ERROR

LifeKeeper has detected an error while trying to determine
the node number(s) of the DB partition server(s) for the
instance

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

The path "%s" is not on a shared filesystem

Cause: The instance home directory should be on a sharedfilesystem.

Action: Check your DB2 configuration.

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

Page 49 of 69

SPS Message Catalog continued

Code103032

Severity
ERROR

MessageCause/Action

LifeKeeper was unable to get the DB tablespace containers Cause: LifeKeeper could not determine the location of thefor instance "%s" or the log path for one of its databases
database table space containers and verify that they arelocated 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.

103033

ERROR

The path "%s" is not on a shared filesystem

Cause: The path of database table space container should
be on a shared filesystem.
Action: Ensure database table space container is on ashared filesystem and retry the operation.

103034ERROR

A DB2 Hierarchy already exists for instance "%s"Cause: An attempt was made to protect the DB2 instancethat is already under LifeKeeper protection.
Action: You must select a different DB2 instance for
LifeKeeper protection.

103035ERROR

The file system resource "%s" is not in-service

Cause: The file system which the DB2 recource depends
on should be in-service.
Action: Ensure the file system resource is in-service andretry the "create" operation.

103036

ERROR

Unable to create the hierarchy for raw device "%s"Cause: LifeKeeper was unable to create the resource {rawdevice} .
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the "create" operation.

103037ERROR

A RAW hierarchy does not exist for the tag "%s"Cause: LifeKeeper was unable to find the raw resource{tag} .
Action: Check your LifeKeeper configuration.

Page 50 of 69

SPS Message Catalog continued

Code103038Severity
ERROR

MessageCause/Action

LifeKeeper was unable to create a dependency between
the DB2 hierarchy "%s" and the Raw hierarchy "%s"Cause: The requested dependency creation between theparent 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.

103039ERROR

LifeKeeper could not disable the automatic startup featureof DB2 instance "%s"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 start up of the instance at
system boot.

103040ERROR

DB2 version "%s" is not installed on server "%s"Cause: LifeKeeper could not find DB2 installed location.
Action: Check your DB2 configuration.

103041ERROR

The instance owner "%s" does not exist on target server"%s"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 thespecified server. If the user does not exist, it should becreated with the same uid and gid on all servers in thecluster.

103042ERROR

The instance owner "%s" uids are different on target server Cause: The user id on the target server {target server} for"%s" and template server "%s"the DB2 instance owner {user} does not match the value ofthe 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.

Page 51 of 69

SPS Message Catalog continued

Code103043Severity
ERROR

MessageCause/Action

The instance owner "%s" gids are different on target server Cause: The group id on the target server {target server} for"%s" and template server "%s"the DB2 instance owner {user} does not match the value ofthe 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.

103044ERROR

The instance owner "%s" home directories are different on
target server "%s" and template server "%s"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 instanceowner {user} must match on all servers in the cluster. The
location mismatch should be corrected manually on allservers before retrying the "canextend" operation.

103045ERROR

LifeKeeper was unable to get the DB2 "SVCENAME"
parameter for the DB2 instanceCause: There was an unexpected error running "db2 get
dbm cfg" command.
Action: Check your DB2 configuration.

103046103047

ERROR

ERROR

Unable to get the value of the DB2 "SVCENAME" parameter for the DB2 instance %s.

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

LifeKeeper was unable to get the contents of the "/etc/services" file on the server "%s"Cause: "/etc/services" on the template server does notcontain the service names for the DB2 instance.

Action: Check your DB2 configuration.

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

Page 52 of 69

SPS Message Catalog continued

Code103048Severity
ERROR

MessageCause/Action

LifeKeeper was unable to get the contents of the "/etc/services" file on the server "%s"Cause: "/etc/services" on the target server does notcontain 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
services names mismatch should be corrected manually on
all servers before retrying the "canextend" operation.

103049ERROR

The "/etc/services" entries for the instance "%s" are different on target server "%s" and template server "%s"Cause: The "/etc/services" entries for the instance aremismatch.
Action: The service names in /etc/services for the DB2
instance must match on all servers in the cluster. The
services names mismatch should be corrected manually on
all servers before retrying the "canextend" operation.

103050ERROR

The home directory "%s" for instance "%s" is not mounted
on server "%s"Cause: LifeKeeper could not find db2nodes.cfg for Multiple
Partition instance.
Action: Ensure the home directory is mounted and retry theoperation.

103051

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: Failed to get resource information from thetemplate server.
Action: Check your LifeKeeper configuration.

103052ERROR

LifeKeeper was unable to add instance "%s" and/or its var- Cause: There was an unexpected error running "db2iset"iables to the DB2 registrycommand.
Action: Check the logs for related errors and try to resolve
the reported problem.

103054

ERROR

Unable to determine the DB2 instance type

Cause: The DB2 Application Recovery Kit was unable todetermine the DB2 instance type.
Action: Check your DB2 configuration.

Page 53 of 69

SPS Message Catalog continued

Code103055103060

Severity
ERROR

ERROR

MessageCause/Action

LifeKeeper has detected an error while trying to determine
the node number(s) of the DB partition server(s) for the
instance

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

Unable to determine the DB2 instance home directory

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

Action: Check your DB2 configuration.

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

ERROR

Unable to determine the DB2 instance type

Cause: The DB2 Application Recovery Kit was unable todetermine the DB2 instance type.
Action: Check your DB2 configuration.

103062103063

ERROR

ERROR

LifeKeeper has detected an error while trying to determine
the node number(s) of the DB partition server(s) for the
instance

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

Unable to determine the DB2 install path

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

Action: Check your DB2 configuration.

Action: Check your DB2 configuration.
103065

ERROR

Invalid input provided for "%s" utility operation, characters
are not allowed.

Cause: Invalid parameters were specified for the "nodes"
command.
Action: Verify the parameters and retry the operation.

103066

ERROR

Unable to get the information for resource "%s"Cause: LifeKeeper was unable to find the resource {tag}.
Action: Verify the parameters and retry the operation.

103067ERROR

The DB2 instance "%s" is not a EEE or Multiple Partition
instance

Page 54 of 69

Cause: The resource {tag} is single partition instance.
Action: Verify the parameters and retry the operation.

SPS Message Catalog continued

Code103069Severity
ERROR

MessageCause/Action

Node "%s" is already protected by this hierarchy

Cause: Invalid parameters were specified for the "nodes"
command.
Action: Verify the parameters and retry the operation.

103070

ERROR

Node number "%s" is the last remaining node protected byresource "%s". Deleting all nodes is not allowed.

Cause: Invalid parameters were specified for the "nodes"
command.
Action: Verify the parameters and retry the operation.

103071ERROR

LifeKeeper is unable to get the equivalent instance forresource "%s"Cause: There was an unexpected error running "nodes"
command.
Action: Check the logs for related errors and try to resolve
the reported problem.

103072

ERROR

Unable to set NodesInfo for resource "%s" on "%s"Cause: There was an unexpected error running "nodes"
command.
Action: Check the logs for related errors and try to resolve
the reported problem.

103073

ERROR

Unable to set NodesInfo for resource "%s" on "%s"Cause: There was an unexpected error running "nodes"
command.
Action: Check the logs for related errors and try to resolve
the reported problem.

103076

ERROR

Unable to determine the DB2 instance type

Cause: The DB2 Application Recovery Kit was unable todetermine the DB2 instance type.
Action: Check your DB2 configuration.

103077

ERROR

Unable to determine the DB2 instance home directory

Cause: The DB2 Application Recovery Kit was unable todetermine the DB2 instance home directory.
Action: Ensure the instance owner name is same as theinstance name and retry the operation.

Page 55 of 69

SPS Message Catalog continued

Code103078Severity
ERROR

MessageCause/Action

The database server is not running for instance "%s"Cause: A process check for the DB2 instance did not findany processes running.
Action: The DB2 instance must be started.

103079103080103082

ERROR

ERROR

ERROR

LifeKeeper has detected an error while trying to determine
the node number(s) of the DB partition server(s) for the
instance

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

One or more of the database partition servers for instance"%s" is down

Cause: All database partition servers should be running.

Failed to create flag "%s"Cause: An unexpected error occurred attempting to createa flag for controlling DB2 local recovery processing.

Action: Check your DB2 configuration.

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

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

ERROR

Failed to remove flag "%s"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.

103084

ERROR

Unable to determine the DB2 instance \"$Instance\" home
directory

Cause: The DB2 Application Recovery Kit was unable todetermine the DB2 instance home directory.
Action: Ensure the instance owner name is same as theinstance name and retry the operation.

DMMP Kit Message Catalog
Use Control F to search for a specific error code in each catalog.

Page 56 of 69

SPS Message Catalog continued

Code128005

Severity
ERROR

MessageCause/Action

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: The quickCheck of {resource} on {server} failed due
to an operating system signal {signal}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128008

ERROR

Usage: quickCheck -t <tag name> -i <id>Cause: Incorrect arguments have been supplied to thedmmp device quickCheck command preventing it fromrunning.
Action: Make sure all software components are properly
installed and at the correct version. Rerun the commandand supply the correct argument list: -t <Resource Tag>and -i <Resource ID> that identifies the dmmp device
resource to be quickChecked.

128010

ERROR

quickCheck for "%s" failed checks of underlying paths, ini- Cause: The dmmp kit failed to quickCheck a device after
tiate recovery. retry count=%s.
{count} times of retries. A recovery of the protected dmmp
resource will be executed.
Action: Check adjacent log messages for further details
and related messages.

128021

ERROR

unable to find device for uuid "%s".

Cause: The device could not be found by unique id during a
restore operation.
Action: Verify that the resource is configured properly.
Rerun the command and supply the correct device id that
identifies the dmmp device resource to be restored.

Page 57 of 69

SPS Message Catalog continued

Code128025

Severity
ERROR

MessageCause/Action

Device "%s" failed to unlock.

Cause: A non working {device} was detected and could not
be unlocked during the restore operation.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128026

ERROR

Device "%s" failed to lock.

Cause: The {device} could not be locked during the resotre.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128031

ERROR

unable to find device for uuid "%s".

Cause: The device could not be found by unique id during
the remove operation.
Action: Verify that the resource is configured properly.
Rerun the command and supply the correct device id that
identifies the dmmp device resource to be removed.

128034

ERROR

Device "%s" failed to unlock.

Cause: The {device} could not be unlocked during theremove.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128036

ERROR

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

Cause: The device information could not be loaded byunique id.
Action: Make sure the resource is configured properly.
Rerun the command and supply the correct device id that
identifies the dmmp device resource.

Page 58 of 69

SPS Message Catalog continued

Code128037

Severity
ERROR

MessageCause/Action

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

Cause: The device information could not be loaded by
name.
Action: Make sure the resource is configured properly.
Rerun the command and supply the correct device namethat identifies the dmmp device resource.

128038

ERROR

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

Cause: The device information could not be loaded sinceneither a unique device id nor name of the device were
defined.
Action: Make sure the resource is configured properly.
Rerun the command and supply the correct device id orname that identifies the dmmp device resource.

128041

ERROR

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

Cause: The device information could not be loaded byunique id.
Action: Make sure the resource is configured properly.
Rerun the command and supply the correct device id that
identifies the dmmp device resource.

128057

ERROR

All paths are failed on "%s".

Cause: LifeKeeper detected all paths listed to the protecteddmmp device are in the failed state.
Action: Check adjacent log messages for further details
and related messages.

128058

ERROR

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

Cause: LifeKeeper could not determine registrations forprotected dmmp {device}. All paths to the dmmp {device}
are in the failed state.
Action: Check adjacent log messages for further details
and related messages.

Page 59 of 69

SPS Message Catalog continued

Code128059Severity
WARN

MessageCause/Action

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

Cause: LifeKeeper detected listed {path} to protected{device} is not valid anymore and will remove it from thepath list.
Action: Check adjacent log messages for further details
and related messages.

128060

WARN

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

Cause: LifeKeeper failed the registration on {path} forprotected dmmp {device}.
Action: Check adjacent log messages for further details
and related messages.

128062

ERROR

all paths failed for "%s".

Cause: LifeKeeper failed to verify a valid path to protecteddmmp {device}.
Action: Check adjacent log messages for further details
and related messages.

128072ERROR

The daemon "%s" does not appear to be running and could Cause: LifeKeeper failed to verify dmmp daemon is runningnot be restarted. Path failures may not be correctly handled and could not restart it.
without this daemon.
Action: Check adjacent log messages for further details
and related messages.

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

Cause: The Device Mapper Multipath Recovery Kit for
dmmp device support is not installed on the system.
Action: Install the steeleye-lkDMMP Device Mapper
Multipath Recovery Kit rpm on the system.

Page 60 of 69

SPS Message Catalog continued

Code128083Severity
ERROR

MessageCause/Action

This script must be executed on "%s".

Cause: An incorrect system name has been supplied as anargument to the devicehier script used to create the dmmp
device resource.
Action: Make sure the cluster nodes and comm-paths areproperly configured. Supply the correct system name to thedevicehier script. The name must match the name of thesystem on which the command is run.

128084ERROR

The device %s is not active.

Cause: LifeKeeper failed to find the specified {device} as avalid device on the system during resource creation.
Action: Check adjacent log messages for further details
and related messages. Rerun the command and supply thecorrect argument list: -t <Resource Tag> and -i <Resource
ID> that identifies the dmmp device resource to be created.

128086

ERROR

Failed to create "%s" hierarchy.

Cause: LifeKeeper failed to create resource hierarchy for{device}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128088

ERROR

Error creating resource "%s" on server "%s"Cause: LifeKeeper failed to create the resource with{tagname} on {server}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

Page 61 of 69

SPS Message Catalog continued

Code128090

Severity
ERROR

MessageCause/Action

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

Cause: LifeKeeper failed to create dependency {resource
tag name} - {resource tag name} on {system} during
creation.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128091

ERROR

Error creating resource "%s" on server "%s"Cause: LifeKeeper failed to create {resource} on {system}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

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

Cause: LifeKeeper failed to create an object for the dmmp
resouce during construction.
Action: Rerun the command and supply the correct
argument list: -t <Resource Tag> and -i <Resource ID>
that identifies the dmmp device resource.

128102

ERROR

Invalid tag "%s".

Cause: A resource instance could not be found for the
given tag name.
Action: Make sure the resource is configured properly.
Rerun the command and supply the correct argument list: -t<Resource Tag> and -i <Resource ID> that identifies the
dmmp device resource.

Page 62 of 69

SPS Message Catalog continued

Code128111

Severity
ERROR

MessageCause/Action

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

Cause: LifeKeeper failed to get the registrations of {device}with the message, "bad field in Persistent reservation in
cdb".
Action: Verify if the storage supports persistentreservations. Check adjacent log messages for further
details and related messages. You must correct any
reported errors before retrying the operation.

128112

ERROR

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

Cause: LifeKeeper failed to get the registrations of {device}with the message, "illegal request".
Action: Verify if the storage supports persistentreservations. Check adjacent log messages for further
details and related messages. You must correct any
reported errors before retrying the operation.

128136ERROR

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

Cause: LifeKeeper detected that a previous quickCheck
operation is still running during the dmmp resource restore
operation. It has been terminated by LifeKeeper.
Action: Check adjacent log messages for further details
and related messages.

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

Cause: LifeKeeper detected a SCSI reservation conflict on{device} during dmmp resource restore.
Action: Check adjacent log messages for further details
and related messages. Manual intervention and fix of thereservation conflict on {device} is required.

Page 63 of 69

SPS Message Catalog continued

Code128138Severity
ERROR

MessageCause/Action

unable to clear registrations on %s.

Cause: LifeKeeper failed to clear all the registrations on{device}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128140

WARN

registration failed on path %s for %s.

Cause: LifeKeeper failed to make the registratioin on {path}for {device}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128143

ERROR

reserve failed (%d) on %s.

Cause: LifeKeeper failed to make reservation for {resource}on {device}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128145ERROR

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

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

128146

ERROR

device failure on %s. SYSTEM HALTED.

Cause: LifeKeeper detected failure on {device} and will
reboot the server.
Action: Check adjacent log messages for further details
and related messages.

Page 64 of 69

SPS Message Catalog continued

Code128148Severity
ERROR

MessageCause/Action

device failure on %s. SYSTEM HALTED DISABLED.

Cause: LifeKeeper detected a failure on {device}. The
reboot was skipped due to LifeKeeper configuration.
Action: Check adjacent log messages for further details
and related messages. Turn on the configuration"SCSIHALT" to make the reboot available for any detected
device failure.

128149

ERROR

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

Cause: LifeKeeper detected a failure on {device}. The
event generation was skipped due to LifeKeeper
configuration.
Action: Check adjacent log messages for further details
and related messages. Turn on the configuration"SCSIEVENT" to make the sendevent available for any
detected device failure.

128150

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

Cause: LifeKeeper detected a reservation conflict for{device} on {server} and will reboot the server.
Action: Check adjacent log messages for further details
and related messages.

128151ERROR%s does not have EXCLUSIVE access to %s, halt system Cause: LifeKeeper detected a reservation conflict for
DISABLED.
{device} on {server}. The reboot was skipped due to
LifeKeeper configuration.
Action: Check adjacent log messages for further details
and related messages. Turn on the configuration"RESERVATIONCONFLICT" to make the reboot available
for any detected reservation conflicts.

Page 65 of 69

SPS Message Catalog continued

Code128154

Severity
WARN

MessageCause/Action

unable to flush buffers on %s.

Cause: LifeKeeper failed to flush the buffers for {device}
during dmmp resource remove.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

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

Cause: LifeKeeper failed to find "dd" utility for the healthcheck of {device}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128160

ERROR%s failed to read %s.

Cause: LifeKeeper failed a disk I/O test for {device} whenusing {utility}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128163

ERROR

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

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

128170ERROR

Usage: canextend <Template system name> <Template
tag name>

Page 66 of 69

SPS Message Catalog continued

Code128500

Severity
ERROR

MessageCause/Action

Usage error

Cause: Incorrect arguments have been supplied to thedmmp device restore command preventing it from running.
Action: Rerun the command and supply the correct
argument list: -t <Resource Tag> and -i <Resource ID>
that identifies the dmmp device resource to be restored.

128504

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

Cause: The Device Mapper Multipath Recovery Kit for
dmmp device support is not installed on the system.
Action: Install the steeleye-lkDMMP Device Mapper
Multipath Recovery Kit rpm on the system.

128506

ERROR

Usage error

Cause: Incorrect arguments have been supplied to thedmmp device devShared command preventing it fromrunning.
Action: Rerun the command and supply the correct
argument list: <Template Resource System Name> and<Template Resource Tag> that identifies the dmmp device
resource to be created.

128507FATAL

This script must be executed on "%s".

Cause: An incorrect system name has been supplied as anargument to the devicehier script used to create the dmmp
device resource.
Action: Supply the correct system name to the devicehierscript. The name must match the name of the system on
which the command is run.

128511ERROR

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

Cause: The devicehier script used to create the dmmp
device resource was unable to determine the SCSI ID forthe supplied device.
Action: Check that the supplied device path exists andthat is for a supported SCSI storage array.

Page 67 of 69

SPS Message Catalog continued

Code128512

Severity
ERROR

MessageCause/Action

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

Cause: The devicehier script used to create the dmmp disk
resource was unable to determine the SCSI ID for the
supplied disk.
Action: Check that the supplied device path exists andthat is for a supported SCSI storage array.

128513

ERROR

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

Cause: The creation of the underlying dmmp disk resource
failed.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128515

ERROR

Error creating resource "%s" on server "%s"Cause: The creation of the dmmp device resource failed.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128517

ERROR

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

Cause: The parent child dependency creation between thedmmp device and dmmp disk resources failed.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

128519

ERROR

Error creating resource "%s" on server "%s"Cause: The attempt to bring the newly created dmmp
device resource in service has failed.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

Page 68 of 69

SPS Message Catalog continued

Code128521

Severity
ERROR

MessageCause/Action

Either TEMPLATESYS or TEMPLATETAG argument miss- Cause: Incorrect arguments have been supplied to theingextend command for the dmmp device resource.
Action: Rerun the dmmp device resource extend andsupply the correct template system and tag names.

128540ERROR

Usage error

Cause: Incorrect arguments have been supplied to thedmmp device getId command used to retrieve the SCSI ID.
Action: Rerun the command and supply the correct
argument list: -i <device path> or -b <device ID>.

128541ERROR

Usage error

Cause: Incorrect arguments have been supplied to thecommand used to delete the dmmp device resource.
Action: Rerun the command and supply the correct
argument list: -t <dmmp device resource tag>.

128543

ERROR

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

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

128544

ERROR

Usage error

Cause: Incorrect arguments have been supplied to theremove command used to take the dmmp device resourceout of service.
Action: Rerun the command and supply the correct
argument list: -t <dmmp device resource tag>.

Page 69 of 69

File System Kit Message Catalog
Use Control F to search for a specific error code in each catalog.

Code124004

Severity
FATAL

MessageCause/Action

resource tag name not specified

Cause: Invalid arguments were specified for the"quickCheck" operation.
Action: Ensure that the correct arguments are passed.

124005

FATAL

resource id not specified

Cause: Invalid arguments were specified for the"quickCheck" operation.
Action: Ensure that the correct arguments are passed.

124007

FATAL

Failed to get resource information

Cause: The filesystem resource's info field does notcontain the correct information.
Action: Put the correct information in the resource's info
field or restore the system from a recent "lkbackup" torestore the original info field.

124008

ERROR

getId failed

Cause: The filesystem resource could not find theunderlying disk device.
Action: Check adjacent log messages for further details.
Verify that the resource hierarchy is valid and that all
required storage kits are installed.

124009ERROR

LifeKeeper protected filesystem is in service but quickCheck detects the following error

Cause: The filesystem kit has found something wrong withthe resource.
Action: Check the messages immediately following thisone for more details.

Page 1 of 79

SPS Message Catalog continued

Code124010

Severity
ERROR

MessageCause/Action\"$id\" is not mounted

Cause: The filesystem resource is no longer mounted.
Action: No action is required. Allow local recovery toremount the resource.

124011

ERROR\"$id\" is mounted but with the incorrect mount options (cur- Cause: The filesystem resource is mounted incorrectly.
rent mount option list: $mntopts, expected mount option
Action: No action is required. Allow local recovery tolist: $infoopts
remount the resource.

124012

ERROR\"$id\" is mounted but on the wrong device (current mountdevice: $tmpdev, expected mount device: $dev

Cause: The filesystem resource has the wrong device
mounted.
Action: No action is required. Allow local recovery toremount the resource.

124015ERROR

LifeKeeper protected filesystem \"$tag\" ($id) is $percent% Cause: The filesystem is getting full.
full ($blocksfree free blocks).
Action: Remove or migrate data from the filesystem.

124016WARN

LifeKeeper protected filesystem \"$tag\" ($id) is $percent%% full ($blocksfree free blocks).

Cause: The filesystem is getting full.

cannot find device information for filesystem $id

Cause: The filesystem resource could not find theunderlying disk device.

124020FATAL

Action: Remove or migrate data from the filesystem.

Action: Check adjacent log messages for further details.
Verify that the resource hierarchy is valid and that all
required storage kits are installed.
124029

ERROR

Failed to find child resource.

Cause: The filesystem resource could not determine its
underlying disk resource.
Action: Ensure that the resource hierarchy is correct.

Page 2 of 79

SPS Message Catalog continued

Code124032

Severity
FATAL

MessageCause/Action

Script has hung. Exiting.

Cause: Processes had files open on a mounted filesystemthat needed to be unmounted. Killing those processes hastaken too long.
Action: If this error continues, try to temporarily stop all
software that may be using the mount point to allow it to beunmounted. If the filesystem still cannot be unmounted,
contact Support.

124042

ERROR

file system $fsname failed unmount; will try again

Cause: Processes had files open on a mounted filesystemthat needed to be unmounted. It can take multiple attempts
to clear those processes.
Action: No action is required. Allow the process tocontinue.

124046

ERROR

file system $fsname failed unmount

Cause: A filesystem could not be unmounted.
Action: If this error continues, try to temporarily stop all
software that may be using the mount point to allow it to beunmounted. If the filesystem still cannot be unmounted,
contact Support.

124049

ERROR

Local recovery of resource has failed (err=$err

Cause: A filesystem resource has a problem that cannot be
repaired locally.
Action: No action is required. Allow the resource to be
failed over to another system.

124103ERROR$ERRMSG Script was terminated for unknown reason

Cause: This message should not occur under normal
circumstances.
Action: Check adjacent log messages for further details.

Page 3 of 79

SPS Message Catalog continued

Code124104

Severity
ERROR

MessageCause/Action$ERRMSG Required template machine name is null

Cause: Invalid arguments were specified for the canextend
operation.
Action: Ensure that the arguments are correct. If this error
happens during normal operation, please contact Support.

124105ERROR$ERRMSG Required template resource tag name is null

Cause: Invalid arguments were specified for the canextend
operation.
Action: Ensure that the arguments are correct. If this error
happens during normal operation, please contact Support.

124106ERROR$ERRMSG Unable to access template resource \"$TemplateTagName\

Cause: The resource's underlying disk information cannot
be determined.
Action: Ensure the hierarchy is correct on the templatesystem before extending.

124107ERROR$ERRMSG Resource \"$TemplateTagName\" must haveone and only one device resource dependency

Cause: The resource has too many underlying devices in
the hierarchy.
Action: Ensure the hierarchy is correct on the templatesystem before extending.

124108ERROR$ERRMSG Unable to access template resource \"$TemplateTagName\

Cause: The resource cannot be found on the templatesystem.
Action: Ensure the hierarchy is correct on the templatesystem before extending.

124109ERROR$ERRMSG Can not access canextend for scsi/$DeviceResType resources on machine \"$TargetSysName\

Cause: The target system is missing some requiredcomponents.
Action: Ensure that the target system has all the correctkits installed and licensed.

Page 4 of 79

SPS Message Catalog continued

Code124110

Severity
ERROR

MessageCause/Action$ERRMSG Either filesystem \"$TemplateLKId\" is notmounted on \"$TemplateSysName\" or filesystem is notshareable with \"$TargetSysName\

Cause: The filesystem isn't in service on the templatesystem or doesn't meet the requirements for extending to
the target system.
Action: Make sure the resource is in service on thetemplate system and review the product documentation
regarding the requirements for extending filesystems.

124111124112

ERROR

ERROR

$ERRMSG File system type \"${FSType}\" is not supported by the kernel currently running on \"${TargetSysName}\

Cause: The filesystem's type cannot be mounted on thetarget system due to lack of kernel support.

must specify machine name containing primary hierarchy

Cause: Invalid arguments were specified for the creFShieroperation.

Action: Ensure that the target system has all its kernel
modules configured correctly before extending theresource.

Action: If this error happens during normal operation,please contact Support.
124113

ERROR

must specify primary ROOT tag

Cause: Invalid arguments were specified for the creFShieroperation.
Action: If this error happens during normal operation,please contact Support.

124114

ERROR

must specify primary mount point

Cause: Invalid arguments were specified for the creFShieroperation.
Action: If this error happens during normal operation,please contact Support.

124115

ERROR

must specify primary switchback type

Cause: Invalid arguments were specified for the creFShieroperation.
Action: If this error happens during normal operation,please contact Support.
Page 5 of 79

SPS Message Catalog continued

Code

Severity

MessageCause/Action

124118ERROR

dep_remove failure on machine \""$PRIMACH"\" for parent Cause: Cleanup after a dependency creation failed.
\"$PRITAG\" and child \"$DEVTAG.\
Action: Check adjacent log messages for further details.

124119ERROR

ins_remove failure on machine \""$PRIMACH"\" for \"$PRITAG.\

Cause: Cleanup after an instance creation failed.

ins_remove failure on machine \""$PRIMACH"\

Cause: Cleanup after a resource creation failed.

124121ERROR

Action: Check adjacent log messages for further details.

Action: Check adjacent log messages for further details.
124122ERROR$ERRMSG Script was terminated for unknown reason

Cause: This message should not occur under normal
circumstances.
Action: Check adjacent log messages for further details.

124123ERROR$ERRMSG Required template machine name is null

Cause: Invalid arguments were specified for thedepstoextend operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124124ERROR$ERRMSG Required template resource tag name is null

Cause: Invalid arguments were specified for thedepstoextend operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124125ERROR$ERRMSG Unable to access template resource \"$TemplateTagName\

Cause: The resource was unable to locate its underlying
disk resource.
Action: Ensure the hierarchy and all dependencies arecorrect before extending.

Page 6 of 79

SPS Message Catalog continued

Code124126

Severity
ERROR

MessageCause/Action

unextmgr failure on machine \""$PRIMACH"\

Cause: The cleanup, after a failed resource extend
operation, failed.
Action: Manually clean up any remaining resources andcheck adjacent log messages for further details.

124128

ERROR

unextmgr failure on machine \""$PRIMACH"\" for \"$PRITAG.\

Cause: The cleanup, after a failed resource extend
operation, failed.
Action: Manually clean up any remaining resources andcheck adjacent log messages for further details.

124129ERROR$ERRMSG Script was terminated for unknown reason

Cause: This message should not occur under normal
circumstances.
Action: Look for additional log messages for more details.

124130ERROR$ERRMSG Required template machine name is null

Cause: Invalid arguments were specified for the extend
operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124131ERROR$ERRMSG Required template resource tag name is null

Cause: Invalid arguments were specified for the extend
operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124132ERROR$ERRMSG Required target mount point is null

Cause: Invalid arguments were specified for the extend
operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

Page 7 of 79

SPS Message Catalog continued

Code124133Severity
ERROR

MessageCause/Action$ERRMSG Unable to access template resource \"$TemplateTagName\

Cause: The tag being extended doesn't exist on thetemplate system.
Action: Ensure that the hierarchy is correct on the templatesystem before extending.

124134ERROR$ERRMSG Detected conflict in expected tag name \"$TargetTagName\" on target machine.

Cause: A resource already exists on the target system withthe same tag as the resource being extended.
Action: Recreate one of the conflicting resources with adifferent tag.

124135124136

ERROR

ERROR

$ERRMSG Resource \"$TemplateTagName\" does nothave required device resource dependency or unable toaccess this resource on template machine.

Cause: The resource or its underlying disk resource cannot
be found on the template system.

$ERRMSG Resource \"$TemplateTagName\" must haveone and only one device resource dependency

Cause: The resource has multiple underlying devices in thehierarchy on the template system.

Action: Ensure that the hierarchy is correct on the templatesystem before extending.

Action: Ensure the hierarchy is correct before extending
and that the filesystem resource only depends on a single
disk resource.
124137ERROR$ERRMSG Can not access extend for scsi/$DeviceResType resources on machine \"$TargetSysName\

Cause: The files required to support the given storage typearen't available on the target system.
Action: Ensure that the required kits are installed on thetarget system and licensed.

124138ERROR$ERRMSG Unable to access target device resource\"$DeviceTagName\" on machine \"$TargetSysName\

Cause: The required underlying disk resource doesn't exist
on the target system.
Action: Check adjacent log messages for further details
and ensure that the target system is properly configured for
hosting the resources being extended.

Page 8 of 79

SPS Message Catalog continued

Code124139Severity
ERROR

MessageCause/Action$ERRMSG Unable to access template \"/etc/mtab\" file

Cause: The target system cannot read the templatesystem's /etc/mtab file.
Action: Check adjacent log messages for further details.
Ensure that the /etc/mtab file exists on the templatesystem.

124140124141

ERROR

ERROR

$ERRMSG Unable to find mount point entry \"$TemplateLKId\" in template \"/etc/mtab\" file. Is template
resource in-service?

Cause: The resource doesn't appear to be mounted on thetemplate system.

$ERRMSG Unable to find mount point \"$TemplateLKId\"
mode on template machine

Cause: The details of the mount point on the templatesystem cannot be determined.

Action: Make sure the resource is in service before
extending.

Action: Ensure that the resource is in service andaccessible on the template system before extending.
124142ERROR$ERRMSG Unable to create or access mount point \"$TargetLKId\" on target machine

Cause: The mount point could not be created on the target
system.
Action: Ensure that the mount point's parent directory
exists and is accessible on the target system.

124143ERROR$ERRMSG Two or more conflicting entries found in/etc/fstab on \"$TargetSysName\

Cause: The device or mount point appears to be mounted
more than once on the target system.
Action: Ensure that the mount point is not mounted on thetarget system before extending.

124144ERROR$ERRMSG Failed to create resource instance on \"$TargetSysName\

Page 9 of 79

Cause: The resource creation on the target system failed.
Action: Check adjacent log messages for further details.
Make sure to check the logs on the target server.

SPS Message Catalog continued

Code124145

Severity
ERROR

MessageCause/Action$ERRMSG Failed to set resource instance state for \"$TargetTagName\" on \"$TargetSysName\

Cause: The source state could not be changed to OSU on
the target system.
Action: Check adjacent log messages for further details.

124146

ERROR

must specify machine name containing primary hierarchy

Cause: Invalid arguments were specified for the filesyshieroperation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124147

ERROR

must specify primary mount point

Cause: Invalid arguments were specified for the filesyshieroperation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124149

ERROR

create file system hierarchy failure

Cause: The process of finding the resource instance failed.
Action: Check adjacent log messages for further details.

124150

ERROR

create file system hierarchy failure

Cause: The system failed to read the /etc/mtab file.
Action: Check adjacent log messages for further details.

124151

ERROR

create file system hierarchy failure

Cause: The mount point could not be found in the /etc/mtab
file.
Action: Check adjacent log messages for further details.

124152

ERROR

create file system hierarchy failure

Cause: The underlying disk resource could not be found.
Action: Check adjacent log messages for further details.

124153

ERROR

create file system hierarchy failure

Cause: Creating the filesystem resource failed.
Action: Check adjacent log messages for further details.

Page 10 of 79

SPS Message Catalog continued

Code124154

Severity
ERROR

MessageCause/Action

create file system hierarchy failure

Cause: The info field for the resource could not be updated.
Action: Check adjacent log messages for further details.

124155

ERROR

create file system hierarchy failure

Cause: The switchback strategy could not be set on the
resource.
Action: Check adjacent log messages for further details.

124157

ERROR

create file system hierarchy failure \(conflicting entries in/etc/fstab\

Cause: The mount point could not be removed from the/etc/fstab file.
Action: Check adjacent log messages for further details.

124160

ERROR

Unknown error in script filesysins, err=$err

Cause: This message should not occur under normal
circumstances.
Action: Check adjacent log messages for further details.

124161

ERROR

create filesys instance - existid - failure

Cause: This message should not occur under normal
circumstances.
Action: Check adjacent log messages for further details.

124163

ERROR

create filesys instance - ins_list - failure

Cause: Checking for an existing resource failed.
Action: Check adjacent log messages for further details.

124164

ERROR

create filesys instance - newtag - failure

Cause: The system failed to generate a suggested tag forthe resource.
Action: If this error happens during normal operation,
contact Support.

124168

ERROR

create filesys instance - ins_create - failure

Cause: The filesystem resource could not be created.
Action: Check adjacent log messages for further details.

Page 11 of 79

SPS Message Catalog continued

Code124169Severity
ERROR

MessageCause/Action

filesys instance - ins_setstate - failure

Cause: The new filesystem resource's state could not be
initialized.
Action: Check adjacent log messages for further details.

124173

ERROR

create filesys instance - dep_create - failure

Cause: The resource's dependency relationship with its
underlying disk could not be created.
Action: Check adjacent log messages for further details.

124174

ERROR

machine not specified

Cause: Invalid arguments were specified for the rmenu_mp
operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124175

ERROR

mount point not specified

Cause: Invalid arguments were specified for the rmenu_mp
operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124177

ERROR

unexpected multiple matches foundCause: One or more systems show a filesystem or mountpoint used more than once.
Action: Verify filesystem devices and mount points andensure that filesystems are only mounted once. Look for
additional log messages for more details.

124178

ERROR

machine name not specified

Cause: Invalid arguments were specified for the rmenump
operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

Page 12 of 79

SPS Message Catalog continued

Code124180

Severity
ERROR

MessageCause/Action

must specify filesystem type

Cause: Invalid arguments were specified for thevalidfstype operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124181

ERROR

mount point not specified

Cause: Invalid arguments were specified for the validmp
operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124182ERROR

The mount point $MP is not an absolute path

Cause: A mount point was specified that isn't an absolute
path (doesn't start with a '/').
Action: Specify a mount point as an absolute path startingwith a '/'.

124183ERROR$MP is already mounted on $MACH

Cause: The requested mount point is already in use on thesystem.
Action: Specify a mount point that isn't in use or unmount it
before retrying the operation.

124184ERROR

The mount point $MP is already protected by LifeKeeper on Cause: The system is already protecting the specified$MACH
mount point.
Action: Choose a different mount point that isn't alreadybeing protected.

124185ERROR

The mount point $MP is not a directory on $MACH

Cause: The mount point refers to a non-directory such as aregular file.
Action: Choose a mount point that refers to a directory.

Page 13 of 79

SPS Message Catalog continued

Code124186

Severity
ERROR

MessageCause/Action

The mount point directory $MP is not empty on $MACH

Cause: The specified mount point refers to a directory that
isn't empty.
Action: Choose a mount point that is empty or remove thecontents of the specified directory before retrying theoperation.

124187

ERROR

server name not specified

Cause: Invalid arguments were specified for the valuepmp
operation.
Action: Ensure the script is called correctly. If this error
happens during normal operation, please contact Support.

124188

ERROR

There are no mount points on server $MACH

Cause: There are no possible mount points for filesystem
resource on the server.
Action: Check adjacent log messages for further details.

124194

WARN

Please correct conflicting \"/etc/fstab\" entries on server$UNAME for: $FSDEV, $FSNAME

Cause: After deleting a filesystem resource, some entries
in /etc/fstab need to me manually cleaned up.
Action: Manually clean up the /etc/fstab file.

124195

ERROR

getchildinfo found no $OKAPP child for $PTAG

Cause: The system could not find a child resource in thehierarchy.
Action: Check adjacent log messages for further details
and ensure that the hierarchy is correct before retrying theoperation.

124196

ERROR

enablequotas - quotacheck may have failed for $FS_
NAME

Page 14 of 79

Cause: The quota operation failed.
Action: Check adjacent log messages for further details inboth the lifekeeper log and in /var/log/messages.

SPS Message Catalog continued

Code124198124200

Severity
ERROR

ERROR

MessageCause/Action

enablequotas - quotaon failed to turn on quotas for $FS_
NAME, reason

Cause: The quota operation failed.

The device node $dev was not found or did not appear in
the udev create time limit of $delay seconds

Cause: A device node (/dev/...) was not created by udev.
This may indicate an issue with the storage or the server's
connection to the storage.

Action: Check adjacent log messages for further details inboth the lifekeeper log and /var/log/messages.

Action: Check adjacent log messages for further details inboth the lifekeeper log and in /var/log/messages.
124201

WARN

Device $device not found. Will retry wait to see if itappears.

Cause: This can happen under normal conditions while
udev creates device node entries for storage. Thismessage should not happen repeatedly.
Action: Check adjacent log messages for further details inboth the lifekeeper log and in /var/log/messages.

124202

ERROR

Command \"$commandwithargs\" failed. Retrying ....

Cause: The given command failed but may have failed
temporarily. This failure may happen during normal
operations but should not keep failing.
Action: Check adjacent log messages for further details if
this message continues.

124204

WARN

cannot make file system $FSNAME mount point

Cause: The mount point directory could not be created.
Action: Ensure that the mount point can be created. Thismay be due to filesystem permissions, mount options, etc.

124207

ERROR\"fsck\"ing file system $FSNAME failed, trying alternative
superblock

Cause: This message indicates that the typical filesystem
check failed. This message may be ok for ext2 filesystems
or other filesystems where an alternative superblock
location is used.
Action: Check adjacent log messages for further details.

Page 15 of 79

SPS Message Catalog continued

Code124209Severity
ERROR

MessageCause/Action\"fsck\"ing file system $FSNAME with alternative superblock failed

Cause: This indicates that an ext2 filesystem (or otherfilesystem where an alternative superblock location isused) check failed with the alternative superblock location.
Action: Check adjacent log messages for further details
and instructions on how to proceed.

124210WARNPOSSIBLE FILESYSTEM CORRUPTION ON $FSNAME Cause: A filesystem was put in service or failed over when($FPNAME
it was out of sync with its mirror source.
Action: Check adjacent log messages for further details
and review the product documentation for information on
how to bring the filesystem in service safely.

124211

ERROR

Reason for fsck failure ($retval): $ret

Cause: This log message is part of a series of messages
and gives the actual exit code from the fsck process.
Action: Check adjacent log messages for further details
and instructions on how to proceed.

124212

ERROR\"fsck\" of file system $FSNAME failed

Cause: The check of the filesystem failed. This is usually
due to the filesystem having corruption.
Action: Check adjacent log messages for further details.
Review the product documentation for instructions on how
to handle possible filesystem corruption.

124213WARN

POSSIBLE FILESYSTEM CORRUPTION ON $FSNAME Cause: The system or user tried to bring into service a($FPNAME
filesystem that may be corrupted. This can happen if afilesystem is switched or failed over when it was out ofsync with its mirror source.
Action: Check adjacent log messages for further details
and review the product documentation for instructions on
how to bring the resource into service safely.

Page 16 of 79

SPS Message Catalog continued

Code124214

Severity
ERROR

MessageCause/Action

Reason for fsck failure ($retval)

Cause: This message should follow a previous log
message about a filesystem check failure and gives theprocess exit code of the fsck process.
Action: Check adjacent log messages for further details.

124218

ERROR

File system $FSNAME was found to be alreadyCause: This message is part of a series of messages.
Action: Check adjacent log messages for further details.

124219ERROR

mounted after initial mount attempt failed.

Cause: This message is part of a series of messages. Thisshould not happen under normal circumstances but may
not be fatal if the resource can be put in service.
Action: Check adjacent log messages for further details inboth the lifekeeper log and in /var/log/messages.

124220

ERROR

File system $FSNAME failed to mount.

Cause: The filesystem could not be mounted.
Action: Check adjacent log messages for further details.

124221

WARN

Protected Filesystem $ID is full

Cause: The filesystem is full.
Action: Remove unused data from the filesystem or
migrate to a larger filesystem.

124222

WARN

Dependent Applications may be affected <>Cause: This indicates that an operation on a resource islikely to cause operation on other resources based on the
resource hierarchy.
Action: Make sure it's acceptable for the indicatedresources to be affected before continuing.

124223

ERROR

Put \"$t\" Out-Of-Service Failed By Signal

Cause: This message should not occur under normal
circumstances.
Action: Check adjacent log messages for further details.

Page 17 of 79

SPS Message Catalog continued

Code124227

Severity
ERROR

MessageCause/Action

Put \"$i\" Out-Of-Service Failed

Cause: The operation failed.
Action: Check adjacent log messages for further details.

124230

ERROR

Put \"$t\" In-Service Failed By Signal

Cause: This message should not occur under normal
circumstances.
Action: Check adjacent log messages for further details.

124231

ERROR

Put \"$t\" In-Service Failed

Cause: The operation failed.
Action: Check adjacent log messages for further details.

124234

ERROR

Put \"$t\" In-Service Failed

Cause: The operation failed.
Action: Check adjacent log messages for further details.

Page 18 of 79

Gen/App Kit Message Catalog
Use Control F to search for a specific error code in each catalog.

Code126105

Severity
ERROR

MessageCause/Action

script not specified - $PTH is a directory

Cause: The specified script path is a directory.
Action: Correct the path of the script.

126110

ERROR

script $PTH does not exist

Cause: The specified script path does not exist.
Action: Correct the path of the script.

126115

ERROR

script $PTH is a zero length file

Cause: The specified script is an empty file.
Action: Correct the script's file path and check thecontents inside the script.

126117

ERROR

script $PTH is not executable

Cause: The specified script is not executable.
Action: Correct the script's file path, check the contents
inside the script file and make sure it has the proper
execute permissions.

126125

ERROR

required template machine name is null

Cause: The input template machine name is null.
Action: Correct the input template machine name.

126130

ERROR

required template resource tag name is null

Cause: The input template resource {tag} is null.
Action: Correct the input template resource tag name.

Page 19 of 79

SPS Message Catalog continued

Code126135

Severity
ERROR

MessageCause/Action

Unable to generate a new tag

Cause: Failed to generate a new tag as the same as the
template tag name on the target node using the "newtag"
script during the extension. The tag name is alreadyexisting.
Action: Avoid using duplicate tag name on the same nodeand check the log for detail.

126140

ERROR

Unable to generate a new tag

Cause: Failed to generate a new tag as input target tag
name on the target node using the "newtag" script during
the extension. The tag name is already existing.
Action: Avoid using duplicate tag name on the same nodeand check log for detail.

126150

ERROR

unable to remote copy template \"$_lscript\" script file

Cause: Failed to remote copy template script file. The
cause may be due to the non-existence/availability of
template script file on template node or any transaction
failure during "lcdrcp" process.
Action: Check the existence/availability of template script
and the connection to template node. Also check the logs
for related errors and try to resolve the reported problem.

126155

ERROR

failed to create resource instance on \"$TargetSysName\

Cause: Failed to create resource instance using "ins_create".
Action: Check the logs for related errors and try to resolve
the reported problem.

126160

ERROR

failed to set resource instance state for \"$TargetTagName\" on \"$TargetSysName\

Cause: Failed to set resource instance state using "ins_setstate" during GenApp resource extension.
Action: Check the logs for related errors and try to resolve
the reported problem.

Page 20 of 79

SPS Message Catalog continued

Code126170

Severity
ERROR

MessageCause/Action

getlocks failure

Cause: Failed to get the administrative lock when creatinga resource hierarchy.
Action: Check the logs for related errors and try to resolve
the reported problem.

126175

ERROR

instance create failed

Cause: Failed to create a GenApp instance using "appins".
Action: Check the logs for related errors and try to resolve
the reported problem.

126180

ERROR

unable to set state to OSU

Cause: Failed to set resource instance state using "ins_setstate" during GenApp resource creation.
Action: Check the logs for related errors and try to resolve
the reported problem.

126190

ERROR

resource restore has failed

Cause: Failed to restore GenApp resource.
Action: Check the logs for related errors and try to resolve
the reported problem.

126200

ERROR

create application hierarchy rlslocks failure

Cause: Failed to release lock after GenApp resource
created.
Action: Check the logs for related errors and try to resolve
the reported problem.

126210

ERROR

copy $ltype script $lscript failure

Cause: Failed to copy user provided script to appropriate
GenApp directory during resource creation.
Action: Check the existence/availability of user provided
script and the GenApp directory as well. Also check thelogs for related errors and try to resolve the reported
problem.

Page 21 of 79

SPS Message Catalog continued

Code126215

Severity
ERROR

MessageCause/Action

no $ltype script specified

Cause: Missing user defined script during GenApp
resource creation.
Action: Check the input action script and run resource
creation again.

126220

ERROR

no machine name specified

Cause: Missing specified machine name during GenApp
resource creation. Failed to copy specified user script due
to missing the input for machine name.
Action: Check the input for machine name and run
resource creation again.

126225

ERROR

no resource tag specified

Cause: Missing specified tag name during resource
creation.
Action: Check the input for source tag name and run
resource creation again.

126230ERROR$ERRMSG Script was terminated for unknown reason

Cause: Failed to extend GenApp resource due to unknown
reason.
Action: Check the logs for related errors and try to resolve
the reported problem.

126235ERROR$ERRMSG Required template machine name is null

Cause: Missing the input for template machine nameduring GenApp resource extension.
Action: Check the input for template machine name and do
the resource extension again.

126240ERROR$ERRMSG Required template resource tag name is null

Cause: Missing the input for template resource tag nameduring GenApp resource extension.
Action: Check the input for template resource tag nameand do the resource extension again.

Page 22 of 79

SPS Message Catalog continued

Code126245

Severity
ERROR

MessageCause/Action$ERRMSG Can not access extend for $AppType/$ResType resources on machine \"$TargetSysName\

Cause: Failed to locate "extend" script during GenApp
resource extension on target node.
Action: Check the existence/availability of "extend" scriptand do GenApp resource extension again.

126250

ERROR

create application failure - ins_list failed

Cause: Failed when calling "ins_list" during GenApp
resource creation.
Action: Check the logs for related errors and try to resolve
the reported problem.

126255

ERROR

create application failure - unable to generate a new tag

Cause: Failed to generate a new tag during the GenApp
resource creation.
Action: Avoid using duplicate tag name on the same node.
Also check the logs for related errors and try to resolve thereported problem.

126270

ERROR

create application failure - ins_create failed

Cause: Failed using "ins_create" to create GenApp
instance.
Action: Check the logs for related errors and try to resolve
the reported problem.

126275

ERROR

create application failure - copy_actions failed

Cause: Failed using "copy_actions" to copy user specified
template script file.
Action: Check the existence/availability of template script.
Also check the logs for related errors and try to resolve thereported problem.

Page 23 of 79

SPS Message Catalog continued

Code126290

Severity
ERROR

MessageCause/Action

Unable to obtain tag for resource with id $ID

Cause: Failed to fetch GenApp resource tag name by input
ID during recovery.
Action: Check the correctness of input ID andexistance/availability of GenApp resource in LCD. Alsocheck the logs for related errors and try to resolve thereported problem.

126300

ERROR

generic application recover script for $TAG was not foundor was not executable

Cause: Failed to locate the user defined script for GenApp
resource during recovery.
Action: Check the existence/availability of the user
defined script and do the GenApp recovery process again.

126310

ERROR-t flag not specified

Cause: Missing the input for resource tag name during
GenApp resource restore.
Action: Check the input for resource tag name and doresource restore again.

126315ERROR-i flag not specified

Cause: Missing the input for resource internal id during
GenApp resource restore.
Action: Check the input for resource internal id and doresource restore again.

126335

ERROR

restore script \"$LCDAS/$APP_RESTOREDIR/$TAG\"
was not found or is not executable

Cause: Failed to locate the user defined script for GenApp
resource during restore.
Action: Check the existence/availability of the user
defined script and do the GenApp restore process again.

126340

ERROR-t flag not specified

Cause: Missing the input for resource tag name during
GenApp resource remove.
Action: Check the input for resource tag name and doresource remove again.

Page 24 of 79

SPS Message Catalog continued

Code126345

Severity
ERROR

MessageCause/Action-i flag not specified

Cause: Missing the input for resource internal id during
GenApp resource remove.
Action: Check the input for resource internal id and doresource remove again.

126365

ERROR

remove script \"$LCDAS/$APP_REMOVEDIR/$TAG\"
was not found or was not executable

Cause: Failed to locate the user defined script for GenApp
resource during remove.
Action: Check the existence/availability of the user
defined script and do the GenApp remove process again.

126375

ERROR

Script has hung checking \"$tag\". Forcibly terminating.

Cause: The "quickCheck" Script will be forcibly terminatedfor GenApp resource with tag name {tag} due to a waitingtime over the user defined timeout.
Action: Check the GenApp resource performance andrestart quickChecking. Also check the logs for related
errors and try to resolve the reported problem.

126380ERROR

Usage error: no tag specified

Cause: Missing the input for resource tag name during
GenApp resource quickCheck.
Action: Check the input for resource tag name and retry
resource quickCheck.

126385ERROR

Internal error: ins_list failed on $tag.

Cause: Failed using "ins_list" to fetch the GenApp
resource information by input tag name during thequickCheck process.
Action: Correct the input tag name and do the quickCheckprocess again. Also check the logs for related errors and try
to resolve the reported problem.

Page 25 of 79

SPS Message Catalog continued

Code126390

Severity
FATAL

MessageCause/Action

Failed to fork process to execute $userscript: $!

Cause: Failed to fork process to execute user defined"quickCheck" script during the GenApp resource"quickCheck" process.
Action: Check the existency/availability of the user
defined "quickCheck" script and do the "quickCheck"process again.

126391

ERROR

quickCheck has failed for \"$tag\". Starting recovery.

Cause: The GenApp resource with tag name {tag} isdetermined to be failed by using the user defined healthmonitoring script - "quickCheck" and the recovery process
will be initiated.
Action: Check the performance of the GenApp resource
when local recovery finished. Also check the logs for
related errors and try to resolve the reported problem.

126400

ERROR-t flag not specified

Cause: Missing the input for resource tag name during
GenApp resource deletion process.
Action: Check the input for resource tag name and doresource deletion process again.

126405ERROR-i flag not specified

Cause: Missing the input for resource internal id during
GenApp resource deletion process.
Action: Check the input for resource internal id and doresource deletion process again.

Page 26 of 79

IP Kit Message Catalog
Use Control F to search for a specific error code in each catalog.

Code
123006

Severity
FATAL

MessageCause/Action

Unknown version %s of IP address

Cause: The IP address does not appear to be valid for
either IPv4 or IPv6.
Action: Provide a valid IP address.

123008ERROR

No pinglist found for %s.

Cause: Problem while opening the pinglist for this IP
address.
Action: Make sure you have provided a pinglist for this IP
address.

123009

ERROR

List ping test failed for virtual IP %s

Cause: No response was received from any of theaddresses in the ping list.
Action: Check network connectivity of this node and thesystems on which the IPs in the ping list reside.

123013

ERROR

Link check failed for virtual IP %s on interface %s.

Cause: The requested interface is showing 'NOCARRIER' indicating that no link is present on the phycial
layer connection.
Action: Check the physical connections for the interface
and bring the physical layer link up.

123015

ERROR

Link check failed for virtual IP %s on interface %s.

Cause: The requested interface is a bonded interface, andone of the slaves is showing 'NO-CARRIER' indicatingthat no link is present on the phycial layer connection.
Action: Check the physical connections for the slaveinterface and bring the physical layer link up.

Page 27 of 79

SPS Message Catalog continued

Code123024

Severity
ERROR

MessageCause/Action

IP address seems to still exist somewhere else.

Cause: The IP address appears to be in use elsewhere on
the network.
Action: Either select a different IP address to use or locateand disable the current use of this IP address.

123027

ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: The quickCheck of a virtual IP ended due to atimeout.
Action: Correct the condition or provide a more appropriate
value for IP_QUICKCHECK_TIMEOUT in/etc/default/LifeKeeper.

123037

ERROR

must specify machine name containing primary hierarchy

Cause: Not enough arguments were provided to creIPhier.
Action: Supply all of the needed arguments to creIPhier.

123038

ERROR

must specify IP resource nameCause: Not enough arguments were passed to creIPhier.
Action: Supply all of the needed arguments to creIPhier.

123039

ERROR

must specify primary IP Resource tag

Cause: The argument specifying the primary IP Resource
tag was missing from the "creIPhier" command.
Action: Supply all of the needed arguments.

123042ERROR

An unknown error has occurred in utility validmask on
machine %s.

Cause: There was an unexpected error running the"validmask" utility.
Action: Check adjacent log messages for additional
details.

123045ERROR

An unknown error has occurred in utility getlocks.

Cause: There was an unexpected error running the"getlocks" utility.
Action: Check adjacent log messages for additional
details.

Page 28 of 79

SPS Message Catalog continued

Code123053Severity
ERROR

MessageCause/Action

Cannot resolve hostname %s

Cause: A hostname was provided for the IP address, but
the system was unable to resolve the name to an IP
address.
Action: Check the correctness of the hostname and verify
that name resolution (DNS or /etc/hosts) is working
correctly and returns the IP for the hostname.

123055123056

ERROR

ERROR

An unknown error has occurred in utility %s on machine%s.

Cause: There was a failure while creating the IP resource.

create ip hierarchy failure: perform_action failed

Cause: Unexpected error trying to restore the IP address
during creation.

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

Action: Check adjacent log messages for additional
details.
123059ERROR

Resource already exists on machine %s

Cause: Attempted to create an IP address that alreadyexists.
Action: Reuse the existing resource or manually remove
the IP address if it exists or use a different IP address.

123060

ERROR

ins_create failed on machine %s

Cause: An unexpected failure occurred while creating an IP
resource.
Action: Check adjacent log messages for further details.

123064

ERROR

An unknown error has occurred in utility %s on machine%s.

Cause: There was a failure while creating a dependency for
the IP resource.
Action: Check the logs for related errors and try to resolve
the reported problem.

Page 29 of 79

SPS Message Catalog continued

Code123066123068123091

Severity
ERROR

ERROR

ERROR

MessageCause/Action

An error occurred during creation of LifeKeeper application=comm on %s.

Cause: A failure occured while calling "app_create."

An error occurred during creation of LifeKeeper resource
type=ip on %s.

Cause: A failure occured while calling "typ_create."the link for interface %s is down

Cause: The requested interface is showing 'NOCARRIER' indicating that no link is present on the phycial
layer connection.

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

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

Action: Check the physical connections for the interface
and bring the physical layer link up.
123093

ERROR

the ping list check failed

Cause: No response was received from any of theaddresses in the ping list.
Action: Check network connectivity of this node and thesystems on which the IPs in the ping list reside.

123095

ERROR

broadcast ping failed

Cause: No replies were received from a broadcast ping.
Action: Verify that at least one host on the subnet will
respond to broadcast pings. Verify that virtual IP is on thecorrect network interface. Consider using a pinglist insteadof a broadcast ping.

123096

ERROR

$msg

Cause: The broadcast ping used to determine the viabilityof the virtual IP failed.
Action: Please ensure that the ping list for this resource isproperly configured in the properties panel or that broadcast
ping checking is disabled by adding NOBCASTPING=1 to
the /etc/default/LifeKeeper configuration file.

Page 30 of 79

SPS Message Catalog continued

Code123097

Severity
ERROR

MessageCause/Action

exec_list_ping(): broadcast ping failed.

Cause: The broadcast ping used to determine the viabilityof the virtual IP failed.
Action: Ensure that the ping list for this resource isproperly configured in the properties panel or that broadcast
ping checking is disabled by adding NOBCASTPING=1 to
the /etc/default/LifeKeeper configuration file.

Page 31 of 79

Oracle Kit Message Catalog
Use Control F to search for a specific error code in each catalog.

Code122501

Severity
ERROR

MessageCause/Action

DB instance "%s" is already protected on "%s".

Cause: An attempt was made to protect an Oracle
database instance {sid} that is already under LifeKeeper
protection on {server}.
Action: You must select a different database instance {sid}for LifeKeeper protection.

122502

ERROR

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

122503

ERROR

Unable to locate the oratab file "%s" on "%s".

Cause: The oratab file was not found at the default or
alternate locations on {server}.
Action: Verify the oratab file exists and has proper
permissions for the Oracle user. A valid oratab file isrequired to complete the "create" operation.

122504

ERROR

Unable to determine Oracle user for "%s" on "%s".

Cause: The Oracle Application Recovery Kit was unable todetermine the ownership of the Oracle database installation
binaries.
Action: The owner of the Oracle binaries must be a valid
non-root user on {server}. Correct the permissions andownership of the Oracle database installation and retry theoperation.

Page 32 of 79

SPS Message Catalog continued

Code122505

Severity
ERROR

MessageCause/Action

The Oracle database "%s" is not running or no open connections are available on "%s".

Cause: The database instance {sid} was not running or
connections to the database were not available via thecredentials provided.
Action: The database instance {sid} must be started on{server} and the proper credentials must be provided for thecompletion of the "create" operation.

122506

ERROR

Unable to determine Oracle dbspaces and logfiles for "%s" Cause: A query to determine the location of requiredon "%s".
tablespaces, logfiles and related database files failed. Thismay have been caused by an internal database error.
Action: Check the adjacent log messages for further
details and related errors. Check the Oracle log (alert.log)
and related trace logs (*.trc) for additional information andcorrect the reported problem(s).

122507

ERROR

Unknown chunk type found for "%s" on "%s".

Cause: The specified tablespace, logfile or other required
database file is not one of the LifeKeeper supported file orcharacter device types.
Action: The specified file {database_file} must reference
an existing character device or file. Consult the Oracle
installation documentation to recreate the specified file{database_file} as a supported file or character device type.

Page 33 of 79

SPS Message Catalog continued

Code122508Severity
ERROR

MessageCause/Action

DB Chunk "%s" for "%s" on "%s" does not reside on ashared file system.

Cause: The specified tablespace, logfile or other required
database file {database_file} does not reside on a filesystem that is shared with other systems in the cluster.
Action: Use the LifeKeeper UI or "lcdstatus (1M)" to verify
that communication paths have been properly created. Use"rpm" to verify that the necessary Application Recovery
Kits for storage protection have been installed. Verify thatthe file is, in fact, not on shared storage, and if not, move it
to a shared storage device.

122510

ERROR

File system create failed for "%s" on "%s". Reason

Cause: LifeKeeper was unable to create the resource{filesystem} on the specified server {server}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the "create" operation.

122511

ERROR%s

Cause: The message contains the output of the"filesyshier" command.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors.

122513

ERROR

Dependency creation between Oracle database "%s (%s)" Cause: LifeKeeper was unable to create a dependency
and the dependent resource "%s" on "%s" failed. Reason
between the database resource {tag} and the necessary
child resource {childtag}.
Action: Check adjacent log messages for further details
and related messages. Once any problems have beencorrected, it may be possible to create the dependency
between {tag} and {childtag} manually.

Page 34 of 79

SPS Message Catalog continued

Code122514

Severity
ERROR

MessageCause/Action

Unable to "%s" on "%s" during resource create.

Cause: The Oracle Application Recovery Kit was unable torelease the administrative lock using the "rlslocks"
command.
Action: Check adjacent log messages for further details
and related messages.

122516

ERROR

Raw device resource created failed for "%s" on "%s". Rea- Cause: LifeKeeper was unable to create the resource {rawsondevice} on the specified server {server}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the "create" operation.

122519ERROR

In-service attempted failed for tag "%s" on "%s".

Cause: The "perform_action" command for {tag} on {server}
failed to start the database {sid}. The in-service operation
has failed.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the "create" operation.

122521ERROR

Create of app "%s" on "%s" failed with return code of "%d". Cause: There was an error running the command "app_create" to create the internal application type.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

122522

ERROR

Create of typ "%s" for app "%s" on "%s" failed with returncode of "%d".

Cause: There was an error running the command "typ_create" to create the internal resource type.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

Page 35 of 79

SPS Message Catalog continued

Code122524

Severity
ERROR

MessageCause/Action

Setting "resstate" for resource "%s" on "%s" failed withreturn code of "%d".

Cause: There was an error running the command "ins_setstate" to set the resource state to {state}.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

122525ERROR

The values specified for the target and the template servers Cause: The value specified for the target and template
are the same: "%s".
servers for the "extend" operation were the same.
Action: You must specify the correct parameter for the{target server} and {template server}. The {target server} isthe server where the {tag} will be extended.

122526

ERROR

Unable to locate the oratab file in "/etc" or in "%s" on "%s". Cause: The oratab file was not found at the default or
alternate locations on {server}.
Action: Verify the oratab file exists and has proper
permissions for the Oracle user. A valid oratab file isrequired to complete the "extend" operation.

122527

ERROR

Unable to retrieve the Oracle user on "%s".

Cause: An attempt to retrieve the Oracle user from{template server} during a "canextend" or "extend"
operation failed.
Action: The owner of the Oracle binaries must be a valid
user on {target server} and {template server}. Correct thepermissions and ownership of the Oracle databaseinstallation and retry the operation.

Page 36 of 79

SPS Message Catalog continued

Code122528Severity
ERROR

MessageCause/Action

The Oracle user and/or group information for user "%s"does not exist on the server "%s".

Cause: LifeKeeper is unable to find the Oracle user and/or
group information for the Oracle user {user} on the server{server}.
Action: Verify the Oracle user {user} exists on thespecified {server}. If the user {user} does not exist, it shouldbe created with the same uid and gid on all servers in thecluster.

122529ERROR

The id for user "%s" is not the same on template server"%s" and target server "%s".

Cause: The user id on the target server {target server} forthe Oracle user {user} does not match the value of the user
{user} on the template server {template server}.
Action: The user ids for the Oracle user {user} must matchon all servers in the cluster. The user id mismatch should
be corrected manually on all servers before retrying the"extend" operation.

122530

ERROR

The group id for user "%s" is not the same on templateserver "%s" and target server "%s".

Cause: The group id on the target server {target server} forthe Oracle user {user} does not match the value of the user
{user} on the template server {template server}.
Action: The group ids for the Oracle user {user} mustmatch on all servers in the cluster. The group id mismatchshould be corrected manually on all servers before retrying
the "extend" operation.

122532ERROR

No file system or raw devices found to extend for "%s" on"%s".

Cause: There were no dependent file system or raw device
resources found for the Oracle resource {tag} on server{template server}.
Action: Check adjacent log messages for further details
and related messages.

Page 37 of 79

SPS Message Catalog continued

Code122533Severity
WARN

MessageCause/Action

A RAMDISK (%s) was detected in the ORACLE Databaseconfiguration for "%s" on "%s". LifeKeeper cannot protect
RAMDISK. This RAMDISK resource will not be protectedby LifeKeeper! ORACLE hierarchy creation will continue.

Cause: The specified tablespace, logfile or other databasefile {database_file} was detected as a ramdisk. No
protection is available for this type of resource in the current
LifeKeeper product.
Action: The ramdisk will not be protected. You must
manually ensure that the required database file {database_file} will be available during all Oracle database operations.

122534

ERROR

Failed to initialize object instance for Oracle sid "%s" on"%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

122537

ERROR

Update of instance info field for "%s" on "%s" failed (%s).

Cause: There was an error while running the command"ins_setinfo" to update the internal resource information
field.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

122538

ERROR

Initial connect with query buffer to database "%s" on "%s"failed, testing output.

Cause: A connection attempt to the Oracle database {sid}to determine the database status has failed.
Action: The connection attempt failed with the specified
credentials. Check the adjacent log messages for further
details and related errors. Check the Oracle log (alert.log)
and related trace logs (*.trc) for additional information andcorrect the reported problem(s).

Page 38 of 79

SPS Message Catalog continued

Code122542

Severity
ERROR

MessageCause/Action

The "%s [ %s ]" attempt of the database "%s" appears tohave failed on "%s".

Cause: The attempted Oracle action {action} using method{action_method} for the database instance {sid} failed on
the server {server}.
Action: Check the adjacent log messages for further
details and related errors. Check the Oracle log (alert.log)
and related trace logs (*.trc) for additional information andcorrect the reported problem(s).

122543ERROR

All attempts to "%s" database "%s" on "%s" failed

Cause: All efforts to perform the action {action} on the
Oracle database {sid} on server {server} have failed.
Action: Check the adjacent log messages for further
details and related errors. Check the Oracle log (alert.log)
and related trace logs (*.trc) for additional information andcorrect the reported problem(s).

122544

ERROR

Update of "%s" sid "%s" on "%s" failed. Reason: "%s""%s" failed: "%s".

Cause: An unexpected error occurred while attempting to
update the oratab entry for the database {sid}. The error
occurred while attempting to open the oratab file.
Action: The oratab file entry for {sid} will need to be
updated manually to turn off the automatic start up of thedatabase at system boot.

122545

ERROR

Unable to locate the oratab file in "/etc" or in "%s" on "%s". Cause: The oratab file was not found at the default or
alternate locations on {server}.
Action: Verify the oratab file exists and has proper
permissions for the oracle user. A valid oratab file isrequired to complete the "extend" operation.

Page 39 of 79

SPS Message Catalog continued

Code122546

Severity
ERROR

MessageCause/Action

Unable to open file "%s" on "%s" (%s).

Cause: The specified file {file} could not be opened oraccessed on the server {server} due to the error {error}.
Action: Verify the existence and permissions on thespecified file {file}. Check adjacent log messages for further
details and related errors. You must correct any reported
errors before retrying the operation.

122547

ERROR(cleanUpPids):Forcefully killing hung pid(s):pid(s)="%s"Cause: The process {pid} failed to respond to the request to
terminate gracefully. The process {pid} will be forcefully
terminated.
Action: Use the command line to verify that the process{pid} has been terminated. Check the adjacent log
messages for further details and related messages.

122548

ERROR

Unable to locate the DB utility (%s/%s) on this host.

Cause: The Oracle binaries and required database utility{utility} located at {path/utility} were not found on this server{server}.
Action: Verify that the Oracle binaries and required
software utilities are installed and properly configured on
the server {server}. The Oracle binaries must be installed
locally on each node or located on shared storage available
to all nodes in the cluster.

122549

ERROR

Oracle internal error or non-standard Oracle configuration
detected. Oracle User and/or Group set to "root".

Cause: The detected ownership of the Oracle databaseinstallation resolves to the root user and/or root group.
Ownership of the Oracle installation by root is a nonstandard configuration.
Action: The owner of the Oracle binaries must be a valid
non-root user on {server}. Correct the permissions andownership of the Oracle database installation and retry theoperation.

Page 40 of 79

SPS Message Catalog continued

Code122550

Severity
ERROR

MessageCause/Action

Initial inspection of "%s" failed, verifying failure or successof received output.

Cause: The previous Oracle query {query} or command{cmd} failed to return success.
Action: Check the adjacent log messages for further
details and related errors. Check the Oracle log (alert.log)
and related trace logs (*.trc) for additional information andcorrect the reported problem(s).

122551

ERROR

Logon failed with "%s" for "%s" on "%s". Please check
username/password and privileges.

Cause: The logon with the credentials {credentials} for the
database instance {sid} on server {server} failed. An invalid
user {user} or password was specified.
Action: Verify that the Oracle database user {user} andpassword {password} are indeed valid. In addition, theOracle database user {user} must have sufficient privileges
for the attempted action.

122552

ERROR%s

Cause: The message contains the output of the "sqlplus"
command.
Action: Check adjacent log messages for further details
and related messages.

122553

ERROR

Unable to open file "%s" on "%s" (%s).

Cause: The specified file {file} could not be opened oraccessed on the server {server} due to the error {error}.
Action: Verify the existence and permissions on thespecified file {file}. Check adjacent log messages for further
details and related errors. You must correct any reported
errors before retrying the operation.

Page 41 of 79

SPS Message Catalog continued

Code122554

Severity
ERROR

MessageCause/Action

The tag "%s" on "%s" is not an Oracle instance or it does
not exist.

Cause: The specified tag {tag} on server {server} does notrefer to an existing and valid Oracle resource instance.
Action: Use the UI or "lcdstatus (1M)" to verify theexistence of the resource tag {tag}. The resource tag {tag}must be an Oracle resource instance to use the command"ora-display."122555

ERROR

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected while
attempting to update the authorized user, password anddatabase role for the Oracle resource instance.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

122557

ERROR

Update of user and password failed for "%s" on "%s".

Cause: A request to update the user and password for the
resource tag {tag} failed. The specified credentials failed
the initial validation/connection attempt on server {server}.
Action: Verify the correct credentials {user/password}
were specified for the attempted operation. Check adjacentlog messages for further details and related messages. You
must correct any reported errors before retrying theoperation.

122559

ERROR

Update of user and password failed for "%s" on "%s".

Cause: The update of the user and password information
for the resource tag {tag} on server {server} failed.
Action: Verify the correct credentials {user/password}
were specified for the attempted operation. Check adjacentlog messages for further details and related messages. You
must correct any reported errors before retrying theoperation.

Page 42 of 79

SPS Message Catalog continued

Code122562

Severity
ERROR

MessageCause/Action

Unable to find the Oracle executable "%s" on "%s".

Cause: The required Oracle executable {exe} was notfound on this server {server}.
Action: Verify that the Oracle binaries and required
software utilities are installed and properly configured on
the server {server}. The Oracle binaries must be installed
locally on each node or located on shared storage available
to all nodes in the cluster.

122566

ERROR

Unable to find Oracle home for "%s" on "%s".

Cause: The Oracle home directory {Oracle home} does notappear to contain files necessary for the proper operation of
the Oracle instance {sid}.
Action: Verify using the command line that the Oracle
home directory {Oracle home} contains the Oracle binaries,
a valid spfile{sid}.ora or init{sid}.ora file.

122567

ERROR

Oracle SID mismatch. The instance SID "%s" does notmatch the SID "%s" specified for the command.

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected. The
specified internal ID {id} does not match the expected SID{sid}.
Action: Verify the parameters are correct. Check adjacentlog messages for further details and related messages. You
must correct any reported errors before retrying theoperation.

122568ERROR

DB Processes are not running on "%s".

Cause: A process check for the Oracle instance did not
find any processes running on server {server}.
Action: If local recovery is enabled, the Oracle instancewill be restarted locally. Check adjacent log messages forfurther details and related messages.

Page 43 of 79

SPS Message Catalog continued

Code122572

Severity
ERROR

MessageCause/Action

Failed to create flag "%s" on "%s".

Cause: An unexpected error occurred attempting to createa flag for controlling Oracle local recovery processing
causing a failover to the standby node.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors.

122574

ERROR

all attempts to shutdown the database %s failed on "%s".

Cause: The shutdown of the Oracle database failed during
a local recovery process most likely caused because themaximum number of database connections has beenreached.
Action: Check the Oracle logs for connection failurescaused by the maximum number of available connections
being reached, and if found, consider increasing the value.
Additionally, set the tunable LK_ORA_NICE to 1 to prevent
connection failures from causing a quickCheck failure
followed by a local recovery attempt.

122597

ERROR

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protectedduring pre-extend checking.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors
before retrying the pre-extend.

122598

ERROR

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being created while
attempting to determine the validity of the Oracle home
directory.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors
before retrying the "create."

Page 44 of 79

SPS Message Catalog continued

Code122599Severity
ERROR

MessageCause/Action

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected while
attempting to look up the Oracle user on the templatesystem.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors
before retrying the extend.

122600

ERROR

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected while
attempting to display the resource properties.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors
before retrying the display of the resource properties.

122601ERROR

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected while
attempting to check for valid database authorization.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors
before retrying the command.

122603

ERROR

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected while
attempting to perform health checks on the Oracle resource
instance.
Action: Check that correct arguments were passed to thequickCheck command and also check the adjacent log
messages for further details and related messages. Correct
any reported errors before retrying the restore.

Page 45 of 79

SPS Message Catalog continued

Code122604

Severity
ERROR

MessageCause/Action

Failed to create object instance for Oracle on "%s".

Cause: There was an unexpected error creating an internal
representation of the Oracle instance being protected while
attempting to perform a local recovery on the Oracle
resource instance.
Action: Check that correct arguments were passed to the"recover" command, and also check the adjacent log
messages for further details and related messages. Correct
any reported errors before retrying the recover.

122606ERROR

The Oracle database "%s" is not running or no open connections are available on "%s".

Cause: The database instance {sid} was not running or
connections to the database are not available via thecredentials provided.
Action: The database instance {sid} must be started on{server} and the proper credentials must be provided for thecompletion of the selected operation.

122607ERROR

The Oracle database "%s" is not running or no open connections are available on "%s".

Cause: The database instance {sid} was not running or
connections to the database are not available via thecredentials provided.
Action: The database instance {sid} must be started on{server} and the proper credentials must be provided for thecompletion of the selected operation.

122608

ERROR

Failed to create object instance for Oracle on "%s".

Cause: The "remove" operation failed to create theresource object instance required to take the Oracle
resource Out of Service.
Action: Check that correct arguments were passed to the"remove" command and also check the adjacent log
messages for further details and related messages. Correct
any reported errors before retrying the restore.

Page 46 of 79

SPS Message Catalog continued

Code122609Severity
ERROR

MessageCause/Action

Failed to create object instance for Oracle on "%s".

Cause: The "restore" operation failed to create the resource
object instance required to put the Oracle resource In
Service.
Action: Check that correct arguments were passed to the"restore" command and also check the adjacent log
messages for further details and related messages. Correct
any reported errors before retrying the "restore."

122610

ERROR

Unable to "%s" on "%s" during resource create.

Cause: The Oracle Application Recovery Kit was unable tocreate the administrative lock using the "getlocks"
command during resource creation.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors before
retrying the create.

122611

ERROR%s

Cause: The requested dependency creation between theparent Oracle resource and the child File System resource
failed.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors before
retrying the create operation.

122612

ERROR%s

Cause: The requested dependency creation between theparent Oracle 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.

Page 47 of 79

SPS Message Catalog continued

Code122613Severity
ERROR

MessageCause/Action%sCause: The requested dependency creation between theparent Oracle 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.

122614

ERROR%s

Cause: The requested dependency creation between theparent Oracle resource and the child Listener resource
failed.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors before
retrying the create operation.

122616

ERROR%s

Cause: The requested start up or shutdown of the Oracle
database failed.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors before
retrying the "restore" or "remove" operation.

122618

ERROR

Dependency creation between Oracle database "%s (%s)" Cause: LifeKeeper was unable to create a dependency
and the dependent resource "%s" on "%s" failed. Reason
between the database resource {tag} and the necessary
child resource {childtag}.
Action: Check adjacent log messages for further details
and related messages. Once any problems have beencorrected, it may be possible to create the dependency
between {tag} and {childtag} manually.

Page 48 of 79

SPS Message Catalog continued

Code122619Severity
ERROR

MessageCause/Action

Dependency creation between Oracle database "%s (%s)" Cause: LifeKeeper was unable to create a dependency
and the dependent resource "%s" on "%s" failed. Reason
between the database resource {tag} and the necessary
child resource {childtag}.
Action: Check adjacent log messages for further details
and related messages. Once any problems have beencorrected, it may be possible to create the dependency
between {tag} and {childtag} manually.

122625

ERROR

Unable to find the Oracle executable "%s" on "%s".

Cause: The quickCheck process was unable to find the
Oracle executable "sqlplus."
Action: Check the Oracle configuration and also checkadjacent log messages for further details and related
messages. Correct any reported problems.

122626

ERROR

Unable to find the Oracle executable "%s" on "%s".

Cause: The remove process was unable to find the Oracle
executable "sqlplus."
Action: Check the Oracle configuration and also checkadjacent log messages for further details and related
messages. Correct any reported problems.

122627

ERROR

Unable to find the Oracle executable "%s" on "%s".

Cause: The restore process was unable to find the Oracle
executable "sqlplus."
Action: Check the Oracle configuration and also checkadjacent log messages for further details and related
messages. Correct any reported problems.

122628

ERROR

Unable to find the Oracle executable "%s" on "%s".

Cause: The recover process was unable to find the Oracle
executable "sqlplus."
Action: Check the Oracle configuration and also checkadjacent log messages for further details and related
messages. Correct any reported problems.

Page 49 of 79

SPS Message Catalog continued

Code122632

Severity
ERROR

MessageCause/Action

Oracle SID mismatch. The instance SID "%s" does notmatch the SID "%s" specified for the command.

Cause: During a remove, the resource instance {sid}passed to the remove process does not match internal
resource instance information for the {sid}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122633

ERROR

Oracle SID mismatch. The instance SID "%s" does notmatch the SID "%s" specified for the command.

Cause: During a restore, the resource instance {sid}passed to restore does not match internal resource
instance information for the {sid}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122634

ERROR

Oracle SID mismatch. The instance SID "%s" does notmatch the SID "%s" specified for the command.

Cause: During resource recovery, the resource instance{sid} passed to recovery does not match internal resource
instance information for the {sid}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122636ERROR

END failed hierarchy "%s" of resource "%s" on server"%s" with return value of %d

Cause: The create of the Oracle resource hierarchy {tag}failed on {server}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122638ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: The create action for the Oracle database resource{tag} on server {server} failed. The signal {sig} was received
by the create process.
Action: Check adjacent log messages for further details
and related messages. You must correct any reported
errors before retrying the operation.

Page 50 of 79

SPS Message Catalog continued

Code122640

Severity
ERROR

MessageCause/Action

Error creating resource "%s" on server "%s"Cause: An unexpected error occurred attempting to create
the Oracle resource instance {tag} on {server}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122641

ERROR

Error creating resource "%s" on server "%s"Cause: An unexpected error occurred attempting to create
the Oracle resource instance {tag} on {server}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122642

ERROR

Error creating resource "%s" on server "%s"Cause: An unexpected error occurred attempting to create
the Oracle resource instance {tag} on {server}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122643

ERROR

Cannot extend resource "%s" to server "%s"Cause: LifeKeeper was unable to extend the resource{resource} on {server}.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors.

122644

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: An unexpected error occurred attempting to retrieve
resource instance information for {tag} on {server}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors andretry the extend.

122645

ERROR

Cannot access canextend script "%s" on server "%s"Cause: LifeKeeper was unable to run pre-extend checks
because it was unable to find the "canextend" script on{server} for a dependent child resource.
Action: Check your LifeKeeper configuration.

Page 51 of 79

SPS Message Catalog continued

Code122646

Severity
ERROR

MessageCause/Action

Error getting resource information for resource "%s" onserver "%s"Cause: An unexpected error occurred attempting to retrieve
resource instance information for {tag} on {server}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors andretry the extend.

122647

ERROR

Cannot extend resource "%s" to server "%s"Cause: LifeKeeper was unable to extend the resource{resource} on {server}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122648ERROR

Resource with either matching tag "%s" or id "%s" alreadyexists on server "%s" for App "%s" and Type "%s"Cause: During the database resource extension, a
resource instance was found using the same {tag} and/or{id} but with a different resource application and type.
Action: Resource IDs must be unique. The resource
instance with the ID matching the Oracle resource instancemust be removed.

122649

ERROR

Error creating resource "%s" on server "%s"Cause: An unexpected error occurred attempting to create
the Oracle resource instance {tag} on {server}.
Action: Check adjacent log messages for further details
and related messages. Correct any reported errors.

122650

ERROR

Cannot access extend script "%s" on server "%s"Cause: The request to extend the database resource{resource} to {server} failed because it was unable to thefind the script {extend} on {server} for a dependent childresource.
Action: Check your LifeKeeper configuration.

Page 52 of 79

SPS Message Catalog continued

Code122651

Severity
ERROR

MessageCause/Action

Cannot extend resource "%s" to server "%s"Cause: The request to extend the database resouce{resource} to {server} failed because of an error attempting
to extend a dependent child resource.
Action: Check the adjacent log messages for further
details and related messages. Correct any reported errors.

122654ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: The health check for the database {sid} was
terminated because the quickCheck process received asignal. This is most likely caused by the quickCheckprocess requiring more time to complete than was allotted.
Action: The health check time for an Oracle resource iscontrolled by the tunable value ORACLE_QUICKCHECK_TIMEOUT. Set it to a value greater than 45 seconds toallow more time for the health check process to complete.

122655ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: The request to take database {sid} "Out of Service"
was terminated because the remove process received asignal. This is most likely caused by the remove process
requiring more time to complete than was allotted.
Action: The remove time for an Oracle resource iscontrolled by the tunable value ORACLE_REMOVE_TIMEOUT. Set the tunable to a value greater than 240
seconds to allow more time for the remove process tocomplete.

Page 53 of 79

SPS Message Catalog continued

Code122659Severity
ERROR

MessageCause/Action

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: The request to place database {sid} "In Service"
was terminated because the restore process received asignal. This is most likely caused by the restore process
requiring more time to complete than was allotted.
Action: The restore time for an Oracle resource iscontrolled by the tunable value ORACLE_RESTORE_TIMEOUT. Set the tunable to a value greater than 240
seconds to allow more time for the restore process tocomplete.

122663

ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: The recovery of the failed database was terminatedbecause the recovery process received a signal. This ismost likely caused by the recovery process requiring moretime to complete than was allotted.
Action: The recovery time for an Oracle resource iscontrolled by the tunable values ORACLE_RESTORE_TIMEOUT and ORACLE_REMOVE_TIMEOUT. Set one
or both of these to a value greater than 240 seconds toallow more time for a recovery to complete.

122670

ERROR

Update of "%s" sid "%s" on "%s" failed. Reason: "%s""%s" failed: "%s".

Cause: An unexpected error occurred while attempting to
update the oratab entry for the database {sid}. The error
occurred while attempting to open the temporary file used in
the update process.
Action: The oratab file entry for {sid} will need to be
updated manually to turn off the automatic start up of thedatabase at system boot.

Page 54 of 79

SPS Message Catalog continued

Code122671

Severity
ERROR

MessageCause/Action

Update of "%s" sid "%s" on "%s" failed. Reason: "%s""%s" failed: "%s".

Cause: An unexpected error occurred while attempting to
update the oratab entry for the database {sid}. The error
occurred while attempting to close the temporary file usedin the update process.
Action: The oratab file entry for {sid} will need to be
updated manually to turn off the automatic start up of thedatabase at system boot.

122672

ERROR

Update of "%s" sid "%s" on "%s" failed. Reason: "%s""%s" failed: "%s".

Cause: An unexpected error occurred while attempting to
update the oratab entry for the database {sid}. The error
occurred while attempting to rename the temporary fileback to oratab.
Action: The oratab file entry for {sid} will need to be
updated manually to turn off the automatic start up of thedatabase at system boot.

122673

ERROR

Unable to log messages queued while running as oracle
user %s on %s. Reason: $!

Cause: An unexpected error {reason} occurred while
attempting to add messages to the log file. Thesemessages were generated while running as the Oracle
user.
Action: Review the reason for the failure and takecorrective action.

122674

ERROR

Unable to open %s Reason: %s.

Cause: An unexpected error occurred while attempting toopen a connection to the Oracle database and run the
database {cmd}.
Action: Check adjacent log messages for further details
and related messages. Additionally, check the Oracle log(alert.log) and related trace logs (*.trc) for additional
information and correct any reported problems.

Page 55 of 79

Oracle Listener Kit Message Catalog
Use Control F to search for a specific error code in each catalog.

Code
122005

Severity
ERROR

MessageCause/Action

Unable to "%s" on "%s"Cause: There was an unexpected error running "getlocks".
Action: Check the logs for related errors and try to resolve
the reported problem.

122007

ERROR

Unable to "%s" on "%s"Cause: There was an unexpected error running "rlslocks".
Action: Check the logs for related errors and try to resolve
the reported problem.

122009ERROR

The path %s is not a valid file.

Cause: There is no listener.ora file.
Action: Ensure the file exists and retry the operation.

122010ERROR

The listener user does not exist on the server %s.

Cause: "Stat" command could not get user id.
Action: Retry the operation.

122011ERROR

The listener user does not exist on the server %s.

Cause: UID is not in passwd file.
Action: Ensure the UID exists in passwd file and retry theoperation.

122012ERROR

The listener user does not exist on the server %s.

Cause: User name is not in passwd file.
Action: Ensure the user name exists in passwd file; retry
the operation.

Page 56 of 79

SPS Message Catalog continued

Code122023Severity
ERROR

MessageCause/Action

The %s command failed (%dCause: This message contains the return code of the"lsnrctl" command.
Action: Check the logs for related errors and try to resolve
the reported problem.

122024

ERROR

$line

Cause: The message contains the output of the "lsnrctl"
command.
Action: Check the logs for related errors and try to resolve
the reported problem.

122039

ERROR

Usage error

Cause: Invalid parameters were specified for the restore
operation.
Action: Verify the parameters and retry the operation.

122040

ERROR

Script $cmd has hung on the restore of \"$opt_t\". Forcibly
terminating.

Cause: The listener restore script reached its timeout
value.
Action: Ensure listener.ora is valid and that LSNR_
START_TIME (default 35 seconds) in/etc/default/LifeKeeper is set to a value greater than orequal to the time needed to start the listener.

122041ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: LifeKeeper was unable to restore the resource{resource} on {server}.
Action: Check the logs for related errors and try to resolve
the reported problem.

122045

ERROR

Error getting resource information for resource "%s" onserver "%s"Page 57 of 79

Cause: Failed to get resource information.
Action: Check your LifeKeeper configuration.

SPS Message Catalog continued

Code122046

Severity
ERROR

MessageCause/Action

Usage error

Cause: Invalid parameters were specified for the restore
operation.
Action: Verify the parameters and retry the operation.

122049ERROR

The script $cmd has hung on remove of \"$opt_t\". Forcibly Cause: The listener remove script reached its timeout
terminating.
value.
Action: Ensure listener.ora is valid and that LSNR_STOP_TIME (default 35 seconds) in /etc/default/LifeKeeper is set
to a value greater than or equal to the time needed to stop
the listener.

122051

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: LifeKeeper was unable to find the resource {tag} on{server}.
Action: Check your LifeKeeper configuration.

122055ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: LifeKeeper was unable to quickCheck the resource{resource} on {server}.
Action: Check the logs for related errors and try to resolve
the reported problem.

122057

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: LifeKeeper was unable to find the resource {tag} on{server}.
Action: Check your LifeKeeper configuration.

122064WARN

The %s level is set to %s a %s will not occur.

Cause: The minimal Listener protection level is Start andMonitor.
Action: Start the listener manually.

Page 58 of 79

SPS Message Catalog continued

Code122066

Severity
ERROR

MessageCause/Action

Script has hung checking \"$tag\". Forcibly terminating.

Cause: The listener quickCheck script reached its timeout
value.
Action: Ensure listener.ora is valid and that LSNR_STATUS_TIME (default 15 seconds) in/etc/default/LifeKeeper is set to a value greater than orequal to the time needed to check the listener.

122067

ERROR

Usage error

Cause: Invalid parameters were specified for thequickCheck operation.
Action: Verify the parameters and retry the operation.

122069

ERROR

Usage error

Cause: Invalid parameters were specified for the delete
operation.
Action: Verify the parameters and retry the operation.

122072ERROR%s: resource "%s" not found on local server

Cause: Invalid parameters were specified for the recover
operation.
Action: Verify the parameters and retry the operation.

122074WARN

The local recovery attempt has failed but %s level is set to Cause: The optional listener recovery level is set to local%s preventing a failover to another node in the cluster.
recovery only.
With %s recovery set all local recovery failures will exit sucAction: Switch over the resource tree manually.
cessfully to prevent resource failovers.

122078ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: LifeKeeper was unable to recover the resource{resource} on {server}.
Action: Check the logs for related errors and try to resolve
the reported problem.

Page 59 of 79

SPS Message Catalog continued

Code122082

Severity
ERROR

MessageCause/Action

Error getting resource information for resource "%s" onserver "%s"Cause: LifeKeeper was unable to find the resource {tag} on{server}.
Action: Check your LifeKeeper configuration.

122083

ERROR$cmd has hung checking \"$tag\". Forcibly terminating

Cause: The recover script was stopped by signal.
Action: Ensure listener.ora is valid.

122084

ERROR

Cannot extend resource "%s" to server "%s"Cause: LifeKeeper was unable to extend the resource{resource} on {server}.
Action: Verify the parameters and retry the operation.

122085

ERROR

Usage: %s %s

Cause: Invalid parameters were specified for thecanextend operation.
Action: Verify the parameters and retry the operation.

122086ERROR

The values specified for the target and the template servers Cause: The values specified for the target and the template
are the same. Please specify the correct values for the tar- servers are the same.
get and template servers.
Action: Perform the steps listed in the message text.

122087

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: LifeKeeper was unable to find the resource {tag} on{server}.
Action: Check your LifeKeeper configuration.

122088

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: Failed to get listener user name from resource
information.
Action: Ensure the resource info field is valid then retry theoperation.

122089ERROR

The listener user %s does not exist on the server %s.

Cause: User name is not in passwd file.
Action: Ensure the user name exists in passwd file andretry the operation.

Page 60 of 79

SPS Message Catalog continued

Code122090

Severity
ERROR

MessageCause/Action

The id for user %s is not the same on template server %s
and target server %s.

Cause: User ID should be same on both servers.
Action: Trim user ID to the same.

122091ERROR

The group id for user %s is not the same on template server Cause: Group ID should be same on both servers.
%s and target server %s.
Action: Trim group ID to the same.

122092

ERROR

Cannot access canextend script "%s" on server "%s"Cause: LifeKeeper was unable to run pre-extend checks
because it was unable to find the "canextend" script on{server}.
Action: Check your LifeKeeper configuration.

122097

ERROR

Usage: %s %s

Cause: Invalid arguments were specified for the"configActions" operation.
Action: Verify the arguments and retry the operation.

122098

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: LifeKeeper was unable to find the resource {tag} on{server}.
Action: Check your LifeKeeper configuration.

122099

ERROR

Unable to update the resource %s to change the %s to %s
on %s.

Cause: LifeKeeper failed to put information into the info
field.
Action: Restart LifeKeeper and retry the operation.

122100

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: LifeKeeper was unable to find the resource {tag} on{server}.
Action: Check your LifeKeeper configuration.

122101

ERROR

Unable to update the resource %s to change the %s to %s
on %s.

Cause: LifeKeeper failed to put information to info field on{server}.
Action: Restart LifeKeeper on {server} and retry theoperation.

Page 61 of 79

SPS Message Catalog continued

Code122103Severity
ERROR

MessageCause/Action

Usage: %s %s

Cause: Invalid parameters were specified for the create
operation.
Action: Verify the parameters and retry the operation.

122124ERROR

END failed hierarchy "%s" of resource "%s" on server"%s" with return value of %d

Cause: LifeKeeper was unable to create the resource{resource} on {server}.
Action: Check the logs for related errors and try to resolve
the reported problem.

122126

ERROR

Unable to "%s" on "%s

Cause: There was an unexpected error running "rlslocks".
Action: Check the logs for related errors and try to resolve
the reported problem.

122127

ERROR

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: LifeKeeper was unable to create the resource{resource} on {server}.
Action: Check the logs for related errors and try to resolve
the reported problem.

122129

ERROR

Unable to "%s" on "%s

Cause: There was an unexpected error running "getlocks."
Action: Check the logs for related errors and try to resolve
the reported problem.

122131

ERROR

Error creating resource "%s" on server "%s"Cause: LifeKeeper was unable to create the resource{resource} on {server}.
Action: Check your LifeKeeper configuration.

122133

ERROR

Unable to create a file system resource hierarchy for the
file system %s.

Cause: There was an unexpected error running"filesyshier."
Action: Check adjacent log messages for further details.

Page 62 of 79

SPS Message Catalog continued

Code122135

Severity
ERROR

MessageCause/Action

Unable to create a dependency between parent tag %s and Cause: There was an unexpected error running "dep_child tag %s.
create."Action: Check the logs for related errors and try to resolve
the reported problem.

122140ERROR

Resource "%s" is not ISP on server "%s" Manually bring
the resource in service and retry the operation

Cause: IP resource {tag} which the listener resource
depends on should be ISP.
Action: Perform the steps listed in the message text.

122141

ERROR

Unable to create a dependency between parent tag %s and Cause: There was an unexpected error running "dep_child tag %s.
create."Action: Check the logs for related errors and try to resolve
the reported problem.

122144

ERROR

Usage: %s %s

Cause: Invalid parameters were specified for the "create_ins" operation.
Action: Verify the parameters and retry the operation.

122145

ERROR

An error has occurred in utility %s on server %s. View the
LifeKeeper logs for details and retry the operation.

Cause: There was an unexpected error running "app_create."Action: Check the logs for related errors and try to resolve
the reported problem.

122146

ERROR

An error has occurred in utility %s on server %s. View the
LifeKeeper logs for details and retry the operation.

Cause: There was an unexpected error running "typ_create."Action: Check the logs for related errors and try to resolve
the reported problem.

122147

ERROR

An error has occurred in utility %s on server %s. View the
LifeKeeper logs for details and retry the operation.

Page 63 of 79

Cause: There was an unexpected error running "newtag."
Action: Check the logs for related errors and try to resolve
the reported problem.

SPS Message Catalog continued

Code122148Severity
ERROR

MessageCause/Action

Error creating resource "%s" on server "%s"Cause: LifeKeeper was unable to create the resource{resource} on {server}.
Action: Check your LifeKeeper configuration.

122149ERROR

An error has occurred in utility %s on server %s. View the
LifeKeeper logs for details and retry the operation.

Cause: There was an unexpected error running "ins_setstate."
Action: Check the logs for related errors and try to resolve
the reported problem.

122150

ERROR

Error creating resource "%s" on server "%s"Cause: LifeKeeper was unable to create the resource{resource} on {server}.
Action: Check your LifeKeeper configuration.

122151ERROR

Usage: %s %s

Cause: Invalid arguments were specified for the"depstoextend" operation.
Action: Verify the arguments and retry the operation.

122152

ERROR

Usage: %s %s

Cause: Invalid parameters were specified for the "extend"
operation.
Action: Verify the parameters and retry the operation.

122153

ERROR

Error getting resource information for resource "%s" onserver "%s"Cause: LifeKeeper was unable to find the resource {tag} on{server}.
Action: Check your LifeKeeper configuration.

122154

ERROR

Cannot extend resource "%s" to server "%s"Page 64 of 79

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

SPS Message Catalog continued

Code122155

Severity
ERROR

MessageCause/Action

Resource with either matching tag "%s" or id "%s" alreadyexists on server "%s" for App "%s" and Type "%s"Cause: During the Listener resource extension, a resource
instance was found using the same {tag} and/or {id} but witha different resource application and type.
Action: Resource IDs must be unique. The resource
instance with the ID matching the Oracle Listener resource
instance must be removed.

122156

ERROR

Cannot access extend script "%s" on server "%s"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.

122157

ERROR

Usage: %s %s

Cause: Invalid arguments were specified for the"getConfigIps" operation.
Action: Verify the arguments and retry the operation.

122158122159

ERROR

ERROR

The file %s is not a valid listener file. The file does not contain any listener definitions.

Cause: Failed to find any listener definitions.

Usage: %s %s

Cause: Invalid arguments were specified for the"getSidListeners" operation.

Action: Ensure listener definition is in the listener.ora andretry the operation.

Action: Verify the arguments and retry the operation.
122160122161

ERROR

ERROR

The file %s is not a valid listener file. The file does not contain any listener definitions.

Cause: Failed to find any listener definitions.

Usage: %s %s

Cause: Invalid arguments were specified for the "lsndisplay" operation.

Action: Ensure listener definition is in the listener.ora andretry the operation.

Action: Verify the arguments and retry the operation.

Page 65 of 79

SPS Message Catalog continued

Code122162

Severity
ERROR

MessageCause/Action

Error getting resource information for resource "%s" onserver "%s"Cause: LifeKeeper was unable to find the resource {tag} on{server}.
Action: Check your LifeKeeper configuration.

122163

ERROR

Usage: %s %s

Cause: Invalid parameters were specified for the
updateHelper operation.
Action: Verify the parameters and retry the operation.

122164ERROR

END failed hierarchy "%s" of resource "%s" on server"%s" with return value of %d

Cause: LifeKeeper was unable to update the resource{resource} on {server}.
Action: Check the logs for related errors and try to resolve
the reported problem.

122166

ERROR

Usage: %s %s

Cause: Invalid parameters were specified for the"updateHelper" operation.
Action: Verify the parameters and retry the operation.

122170

ERROR

Unable to create a dependency between parent tag %s and Cause: There was an unexpected error running "dep_child tag %s.
create."Action: Check the logs for related errors and try to resolve
the reported problem.

122171

ERROR

Unable to create a dependency between parent tag %s and Cause: There was an unexpected error running "dep_child tag %s.
create."Action: Check the logs for related errors and try to resolve
the reported problem.

122172

ERROR

Usage: %s %s

Cause: Invalid arguments were specified for the"updIPDeps" operation.
Action: Verify the arguments and retry the operation.

Page 66 of 79

SPS Message Catalog continued

Code122173Severity
ERROR

MessageCause/Action

END failed hierarchy "%s" of resource "%s" on server"%s" with return value of %d

Cause: LifeKeeper was unable to update the resource{resource} on {server}.
Action: Check the logs for related errors and try to resolve
the reported problem.

122175

ERROR

Unable to "%s" on "%s

Cause: There was an unexpected error running "rlslocks."
Action: Check the logs for related errors and try to resolve
the reported problem.

122177

ERROR

Unable to "%s" on "%s

Cause: There was an unexpected error running "getlocks."
Action: Check the logs for related errors and try to resolve
the reported problem.

122180

ERROR

Unable to create a dependency between parent tag %s and Cause: There was an unexpected error running "dep_child tag %s.
create."Action: Check the logs for related errors and try to resolve
the reported problem.

122181

ERROR

Unable to create a dependency between parent tag %s and Cause: There was an unexpected error running "dep_child tag %s.
create."Action: Check the logs for related errors and try to resolve
the reported problem.

122183

ERROR

The path %s is not a valid file.

Cause: There is no listener.ora file.
Action: Ensure the file exists and retry the operation.

122185ERROR

The file %s is not a valid listener file. The file does not contain any listener definitions.

Cause: LifeKeeper failed to find any valid listener
definitions.
Action: Ensure there are valid listener definitions in thelistener.ora and retry the operation.

Page 67 of 79

SPS Message Catalog continued

Code122186122187

Severity
ERROR

ERROR

MessageCause/Action

The value specified for %s cannot be empty. Please specify a value for this field.

Cause: The config and/or executable {path} field is empty.

The path %s is not a valid file or directory.

Cause: The defined {path} is invalid.

Action: Input a non-empty value for {path} and retry theoperation.

Action: Ensure the {path} exists and retry the operation.
122188ERROR

The path %s is not a valid file or directory.

Cause: There is no {path}.
Action: Ensure the {path} exists and retry the operation.

122189122190

ERROR

ERROR

The value specified for %s cannot be empty. Please specify a value for this field.

Cause: The config and/or executable Path field is empty.

Usage: %s %s

Cause: Invalid arguments were specified for the "valid_
rpath" operation.

Action: Input path for the field.

Action: Verify the arguments and retry the operation.
122191ERROR

The values specified for the target and the template servers Cause: Invalid argument of valid_rpath.
are the same.
Action: Ensure arguments and retry the operation.

122192

ERROR

Unable to find the configuration file "oratab" in its default
locations, /etc/oratab or %s on "%s"Cause: There is no oratab file in /etc/oratab or {path}.

Unable to find the configuration file "oratab" in its default
locations, /etc/oratab or %s on "%s"Cause: There is no oratab file in /etc/oratab or {path}.

122193

ERROR

Page 68 of 79

Action: Ensure oratab file exists in {path} or ORACLE_
ORATABLOC in /etc/default/Lifekeeper is set to a valid
path.

Action: Ensure oratab file exists in {path} or ORACLE_
ORATABLOC in /etc/default/Lifekeeper is set to a valid
path.

SPS Message Catalog continued

Code122194122195122196

Severity
ERROR

ERROR

ERROR

MessageCause/Action

Unable to find the configuration file "oratab" in its default
locations, /etc/oratab or %s on "%s"Cause: There is no oratab file in /etc/oratab or {path}.

Unable to find the configuration file "oratab" in its default
locations, /etc/oratab or %s on "%s"Cause: There is no oratab file in /etc/oratab or {path}.

Action: Ensure oratab file exists in {path} or ORACLE_
ORATABLOC in /etc/default/Lifekeeper is set to a valid
path.

Action: Ensure oratab file exists in {path} or ORACLE_
ORATABLOC in /etc/default/Lifekeeper is set to a validpath.

END failed %s of "%s" on server "%s" due to a "%s" signal Cause: LifeKeeper was unable to remove the resource{resource} on {server}.
Action: Check the logs for related errors and try to resolve
the reported problem.

122197

ERROR

Unable to find the configuration file \"oratab\" in its default
locations, /etc/oratab or $listener::oraTab on \"$me\"

Page 69 of 79

Cause: There is no oratab file in /etc/oratab or {path}.
Action: Ensure oratab file exists in {path} or ORACLE_
ORATABLOC in /etc/default/Lifekeeper is set to a valid
path.

SCSI Kit Message Catalog
Use Control F to search for a specific error code in each catalog.

Code

Severity

MessageCause/Action

125102

ERROR`printf 'Template resource "%s" on server "%s" does notexist' $TemplateTagName $TemplateSysName`

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

125103

ERROR`printf '%s is not shareable with any machine.' $DEV`

Cause: The device does not appear to be shared with anyother systems.
Action: Verify that the device is accessible from all servers
in the cluster. Ensure that all relevant storage drivers andsoftware are installed and configured properly.

125104

ERROR`printf 'Failed to create disk hierarchy for "%s" on "%s"'$PRIMACH $DEV`

Cause: The creation of a resource to protect a physicaldisk failed.
Action: Check adjacent log messages for more details andtry to resolve the reported problem.

125107

ERROR`printf 'Template resource "%s" on server "%s" does notexist' $TemplateTagName $TemplateSysName`

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

125114

ERROR`printf 'Template resource "%s" on server "%s" does notexist' $TemplateTagName $TemplateSysName`

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

125120

ERROR`printf 'Template resource "%s" on server "%s" does notexist' $TemplateTagName $TemplateSysName`

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

125123

ERROR`printf 'Cannot access depstoextend script "%s" on server"%s"' $depstoextend $TargetSysName`

Cause: LifeKeeper was unable to run pre-extend checks on
the resource hierarchy because it was unable to find thescript "DEPSTOEXTEND" on {server}.
Action: Check your LifeKeeper configuration.

Page 70 of 79

SPS Message Catalog continued

Code

Severity

MessageCause/Action

125126

ERROR`printf 'Template resource "%s" on server "%s" does notexist' $ChildTag $TemplateSysName`

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

125129

ERROR`printf 'Template resource "%s" on server "%s" does notexist' $TemplateTagName $TemplateSysName`

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

125155ERRORSCSI $DEV failed to lock.

Cause: There was a problem locking a SCSI device.
Action: Check adjacent log messages for more details andtry to resolve the reported problem.

125164ERRORSCSI $INFO failed to unlock.

Cause: There was a problem unlocking a SCSI device.
Action: Check adjacent log messages for more details andtry to resolve the reported problem.

125181

ERROR`printf 'Template resource "%s" on server "%s" does notexist' $TemplateTag $TemplateSysName`

Page 71 of 79

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

DataKeeper Message Catalog
Use Control F to search for a specific error code in each catalog.

Code104002

Severity
FATAL

MessageCause/Action$msg

Cause: This message indicates an internal software error.
Action: The stack trace indicates the source of the error.

104003FATAL$self->Val('Tag') . " is not an SDR resource"

Cause: A data replication action was attempted on a nondata replication resource.
Action: Check the logs for related errors and try to resolve
the reported problem.

104010

ERROR$self->{'md'}: bitmap merge failed, $action

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.

104022

ERROR$argv[1]: mdadm failed ($ret

Cause: The "mdadm" command has failed to add a device
into the mirror.
Action: This is usually a temporary condition.

104023

ERROR$_

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

104025

ERROR

failed to spawn monitor

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.

Page 72 of 79

SPS Message Catalog continued

Code104026

Severity
ERROR

MessageCause/Action

cannot create $md

Cause: The mirror device could not be created.
Action: Ensure the device is not already in use and that allother parameters for the mirror creation are correct.

104027

ERROR$_

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

104035ERROR

Too many failures. Aborting resync of $md

Cause: The device was busy for an abnormally long periodof time.
Action: Reboot the system to be sure that the device is nolonger busy.

104036

ERROR

Failed to start nbd-server on $target (error $port

Cause: The nbd-server process could not be started on thetarget server.
Action: Ensure that the target disk device is available andthat its Device ID has not changed.

104037

ERROR

Failed to start compression (error $port

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 andthat TCP ports in the range 10000-10512 are opened andunused. Ensure that the software is installed properly on all
systems.

104038

ERROR

Failed to start nbd-client on $source (error $ret

Cause: The nbd-client process has failed to start on thesource 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.

Page 73 of 79

SPS Message Catalog continued

Code104039Severity
ERROR

MessageCause/Action

Failed to add $nbd to $md on $source

Cause: This is usually a temporary condition.
Action: If this error persists, reboot the system to resolve
any potential conflicts.

104045

ERROR

failed to stop $self->{'md'}

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.

104048

WARN

failed to kill $proc, pid $pid

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 theunkillable process.

104050

ERROR

Setting $name on $dest failed: $ret. Please try again.

Cause: The system failed to set a 'mirrorinfo' file setting.
Action: Check the network and systems and retry the mirror
setting operation.

104052FATAL

Specified existing mount point "%s" is not mounted

Cause: The mount point became unmounted.
Action: Ensure that the mount point is mounted and retry
the operation.

104055

ERROR

Failed to set up temporary $type access to data for $self-> Cause: The filesystem or device was not available on the{'tag'}. Error: $ret
target server. The mirrored data will not be available on thetarget server until the mirror is paused and resumed again.
Action: Reboot the target server to resolve any potential
conflicts.

Page 74 of 79

SPS Message Catalog continued

Code

Severity

MessageCause/Action

104057

ERROR

Failed to undo temporary access for $self->{'tag'} on $self- Cause: The filesystem could not be unmounted on the>{'sys'}. Error: $ret. Please verify that $fsid is not mounted target server.
on server $self->{'sys'}.
Action: Ensure that the filesystem and device are not busyon the target server. Reboot the target server to resolve any
potential conflicts.

104062FATAL

Cannot find a device with unique ID "%s"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 IDof the target disk has not changed.

104066

FATAL

Cannot get the hardware ID of device "%s"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 IDof the target disk has not changed.

104067FATAL

Asynchronous writes cannot be enabled without a bitmap
file

Cause: An attempt was made to create a mirror with invalid
parameters.
Action: A bitmap file parameter must be specified orsynchronous writes must be specified.

104068104070

FATAL

FATAL

Failed to extend dependent resource %s to system %s.
Error %s

Cause: The hierarchy extend operation failed.

Unable to extend the mirror "%s" to system "%s"Cause: The hierarchy extend operation failed.

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

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

Page 75 of 79

SPS Message Catalog continued

Code104071

Severity
ERROR

MessageCause/Action

Failed to restore target device resources on $target->{'sys'} : $err

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.

104073EMERG

WARNING: A temporary communication failure has
Cause: A temporary communication failure (split-brain
occurred between systems %s and %s. In order to avoid scenario) has occurred between the source and target
data corruption, data resynchronization will not occur.
servers.
MANUAL INTERVENTION IS REQUIRED. In order to iniAction: Perform the steps listed in the message text.
tiate data resynchronization, you should: 1) Take one of
the following resources out of service (this resource will
become the mirror target): %s on %s or %s on %s. 2)
Take the other resource out of service (this resource will
become the mirror source). 3) Run %s/bitmap -d %s on
the system that will become mirror source. 4) Bring the mirror in service on the source system. A full resync will
occur.

104074

FATAL

Cannot get the hardware ID of device "%s"Cause: There is no storage recovery kit that recognizes theunderlying 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.

104081FATAL

Cannot make the %s filesystem on "%s" (%d)

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.

Page 76 of 79

SPS Message Catalog continued

Code

Severity

MessageCause/Action

104082FATAL%sCause: This message contains the output of the "mkfs"
command.

104083

FATAL

Cannot create filesys hierarchy "%s"Cause: The resource creation failed.
Action: Check the logs for related errors and try to resolve
the reported problem.

104086

ERROR

The "%s_data_corrupt" flag is set in "%s/subsys/scsi/resources/netraid/" on system "%s". To avoid
data corruption, LifeKeeper will not restore the resource

Cause: The data corrupt flag file has been set as aprecaution 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 inquestion, you can either: 1) remove the file and restore themirror, or 2) force the mirror online using the LifeKeeper GUI
or 'mirror_action force' command.

104092

ERROR

Mirror target resource movement to system %s : status%s

Cause: The hierarchy switchover operation has failed.
Action: Check the logs for related errors and try to resolve
the reported problem.

104099

ERROR

Unable to unextend the mirror for resource "%s" from sys- Cause: The hierarchy unextend operation failed.
tem "%s"
Action: Reboot the target server to resolve any potential
conflicts and retry the operation.

104106

ERROR

remote 'bitmap -m' command failed on $target->{'sys'}:$rangesCause: 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 ismissing, pause and resume the mirror to recreate the bitmap
file.

Page 77 of 79

SPS Message Catalog continued

Code

Severity

MessageCause/Action

104107

ERROR

Asynchronous writes cannot be enabled without a bitmap
file

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

104108

ERROR

Local Partition not available

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

104109

ERROR

Cannot get the hardware ID of device "%s"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 thedisk has not changed.

104111FATAL

Insufficient input parameters for "%s" creation

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

104112FATAL

Insufficient input parameters for "%s" creation

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

104113FATAL

Insufficient input parameters for "%s" creation

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

104114FATAL

Insufficient input parameters for "%s" creation

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

104115FATAL

Insufficient input parameters for "%s" creation

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

104117FATAL

Insufficient input parameters for "%s" creation

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

104118FATAL

Cannot unmount existing Mount Point "%s"Cause: The mount point is busy.
Action: Make sure the filesystem is not busy. Stop any
processes or applications that may be accessing thefilesystem.

Page 78 of 79

SPS Message Catalog continued

Code

Severity

MessageCause/Action

104119FATAL

Invalid data replication resource type requested ("%s"Cause: An invalid parameter was specified for the mirror
create operation.

104124EMERG

WARNING: A temporary communication failure has
Cause: A temporary communication failure (split-brain
occurred between systems %s and %s. In order to avoid scenario) has occurred between the source and target
data corruption, data resynchronization will not occur.
servers.
MANUAL INTERVENTION IS REQUIRED. In order to initiate data resynchronization, you should take one of the fol- Action: Perform the steps listed in the message text.
lowing resources out of service: %s on %s or %s on %s.
The resource that is taken out of service will become themirror target.

104125

ERROR

failed to start '$cmd $_[2] $user_args' on '$_[3]'Cause: The specified command failed.
Action: Check the logs for related errors and try to resolve
the reported problem.

104126

ERROR$_

104128FATAL

comm path/server not specified

104129WARN

104136

ERROR

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

Extend failed.

Cause: The hierarchy extend operation failed.
Action: Check the logs for related errors and try to resolve
the reported problem.

104143

ERROR

Mirror resume was unsuccessful ($ret

Cause: The mirror could not be established.
Action: Check the logs for related errors and try to resolve
the reported problems.

Page 79 of 79