Use Control F to search for a specific error code in each catalog. To search for any error code, select the Search button at the top right of the screen.


Code Severity Message Cause/Action
000200 ERROR pam_start() failed
000201 ERROR pam_authenticate failed (user %s, retval %d)
000202 ERROR pam_end() failed?!?!
000203 ERROR Did not find expected group ‘lkguest’
000204 ERROR Did not find expected group ‘lkoper’
000205 ERROR Did not find expected group ‘lkadmin’
000208 ERROR pam_setcred establish credentials failed (user %s, retval %d)

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

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

000209 ERROR pam_setcred delete credentials failed (user %s, retval %d)

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

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

000902 ERROR Error removing system name from loopback address line in /etc/hosts file. You must do this manually before starting the GUI server.

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

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

000918 ERROR 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.

000931 ERROR S_LK server process died or was killed
000932 ERROR *** Too many failed attempts to start the LifeKeeper GUI server java process.
000933 ERROR *** Stopping further startup attempts.
000934 ERROR *** After correcting the problem, start the GUI server with ‘lkGUIserver start
001041 FATAL Usage error
001042 FATAL %s: both tag and id name not specified
001043 FATAL %s: resource "%s" not found on local server
001048 ERROR Resource "%s" is not ISP on server "%s" Manually bring the resource in service and retry the operation
001051 FATAL Either TEMPLATESYS or TEMPLATETAG argument missing
001052 FATAL 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.

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.

001056 ERROR Unable to get a unique tag name on server "%s" for template resource "%s"
001057 ERROR Cannot extend resource "%s" to server "%s"

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

001058 ERROR END failed resource extension of "%s" on server "%s" due to a "%s" signal – backing out changes made to server
001059 ERROR 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.

001060 ERROR Resource with either matching tag "%s" or id "%s" already exists on server "%s" for App "%s" and Type "%s"

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

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

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.

001062 FATAL create: Usage error
001063 FATAL %s: tag name not specified
001064 FATAL %s: switchback name not specified
001073 ERROR Error bringing resource "%s" in service on server "%s"
001081 WARN IP address \"$ip\" 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 and try again. If a name was provided, verify that name resolution returns a valid IP address.

002018 ERROR Error finding one of the hierarchy root(s) "%s" on server "%s". Verify that all of the resources passed in exist on the server and that server and comm paths are alive.
002019 ERROR Roots passed in which include "%s" on server "%s" don\‘t match the actual roots found for the hierarchy. In order to change the priority of a hierarchy, you must pass to the script a list of all root resources for all associated hierarchies. Verify that all root resources are in the list passed and that all of these are root resources.
002020 ERROR Error finding all roots to do root validation for resource(s) "%s" on server "%s". Verify that server and comm paths are alive, then retry the operation.
002021 ERROR Error getting equivalencies for some of the resources in hierarchy with root(s) "%s" on server "%s". Verify that all remote servers have a live comm path to the server where the hierarchy is being changed and that all equivalencies exist.
002022 ERROR There was an error changing priorities for hierarchy with root(s) "%s" and previous priorities could not be successfully restored. Verify that there is a live comm path to all servers where the hierarchies exist. When all comm paths are restored, try repairing the priorities one at a time using the command line utility hry_setpri. If the damage is too severe, the hierarchies may have to be deleted and re-created.
002023 ERROR There was an error changing priorities for hierarchy with root(s) "%s" and all previous priorities were successfully restored. Retry the operation.
002024 ERROR Resource "%s" has an equivalency on a server that does not have a live comm path with server "%s". All servers where the hierarchy exists must have a live comm path with the server where the priority is being changed. Retry the operation after all comm paths are re-established between the servers.
002025 ERROR The desired priority change on server "%s" causes a conflict with an existing priority on another server for hierarchy with root(s) "%s". Retry the operation with a different priority which doesn\‘t currently exist in the hierarchy.
002026 ERROR The requested priority change would cause the hierarchy to have reverse priorities. LifeKeeper allows resources within hierarchies to have different priority values so long as the relative order is the same for all resources within the hierarchy on all systems where the hierarchy exists. The proposed priority change would cause one of the resources within the hierarchy to have priority values in non-relative order with the other resources in the hierarchy. Try to determine a priority value which will not cause a reverse priority order and retry the operation.
002027 ERROR The selected hierarchy with root(s) "%s" does not exist on server "%s". Select a server on which the hierarchy exists and retry the operation.
002028 ERROR The selected hierarchy with root(s) "%s" only exists on server "%s". You cannot change the priority of a hierarchy that only exists on one server.
002029 ERROR The selected priority value for server "%s" does not fall within the acceptable range of 1-999. Please select a priority value within the acceptable range and retry the operation.
002030 ERROR Error getting cluster wide administrative locks for operation. Verify that all systems and comm paths are alive in cluster, then retry the operation.
004001 ERROR passed in NULL pointer to ins_othersys
004013 ERROR test_list ttag arg is NULL
004014 ERROR test_and_remove_from_list ttag arg is NULL
004016 ERROR add_to_list ttag arg is NULL
004019 ERROR remove_from_list arg is NULL
004020 ERROR add_to_list arg is NULL
004024 ERROR

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

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

004028 ERROR %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 found

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

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

004056 ERROR attempt to remote-remove resource \"%s\" that is not a shared 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 found

Cause: 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 a shared resource with machine \"%s\"

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

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

004062 ERROR attempt to transfer-restore resource \"%s\" that is not a secondary shared resource with primary on machine \"%s\"
004089 ERROR ERROR: Parallel recovery initialization failed.\n

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

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

004091 ERROR ERROR: fork failed. continuing to next resource\n

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

004093 ERROR ERROR: reserve failed. continuing to next resource\n

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

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

004095 ERROR ERROR: wait() error\n
004096 ERROR ERROR: clone %d is hung, attempting to kill it\n

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

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

004097 ERROR ERROR: Could not kill clone %d\n

Cause: 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 and determine 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. This is a system error.

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

004118 ERROR write(%s)

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

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

004119 ERROR fsync(%s)

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

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

004120 ERROR close(%s)

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

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

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

004123 ERROR fsync(%s)

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

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

004124 ERROR close(%s)

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

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

004125 ERROR wrote only %d bytes of requested %d\n

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

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

004126 ERROR open(%s)

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

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

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

004128 ERROR 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 a system error.

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

004129 ERROR read buffer overflow (MAX=%d)\n

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

Action: Check the LifeKeeper configuration and restart the LifeKeeper.

004130 ERROR close(%s)

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

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

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 and determine 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 a system error.

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

004133 ERROR 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(%s)

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

Action: Check the log for error information in detail.

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

004139 ERROR read(%s,%lu){%*.*s}
004140 ERROR read %d bytes of %lu bytes of file \"%s\"
004141 ERROR mkdirp(%s,0755)
004142 ERROR stat(%s)
004143 ERROR existing destination path \"%s\" has mode 0%o
004145 ERROR open(%s,0x%x,0%o)
004146 ERROR fchmod(%s,0%o)
004147 ERROR fchown(%s,%u,%u)
004148 ERROR lseek(%s,%u)
004149 ERROR write(%s,%u)
004150 ERROR only %u bytes written of %lu to file \"%s\"
004151 FATAL lcdMalloc failure

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

Action: A fatal error will be produced.

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

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

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

004153 ERROR must define object first with ::create() or ::fill()
004154 ERROR child() only works on local objects
004155 ERROR must define object first with ::create() or ::fill()
004156 ERROR parent() only works on local objects
004157 ERROR must specify parent tag to get child dependencies
004158 ERROR must specify child tag to get parent dependencies
004160 FATAL attempt to access empty dependency list
004161 FATAL index %d past range 0-%d
004162 ERROR must specify parent name of dependency
004163 ERROR must specify child name of dependency
004164 ERROR Priority mismatch between resources %s and %s. Dependency creation failed.

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

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

004165 ERROR The selected child and parent for the dependency have a conflicting relationship on other systems where the equivalent resources exist. Dependency creation failed.
004166 ERROR both parent and child of dependency can’t be left unspecified
004167 ERROR COMMAND OUTPUT: %s
004168 FATAL number of list elements has exceeded %d\n
004169 ERROR COMMAND OUTPUT: %s
004174 FATAL sigprocmask
004175 FATAL sigprocmask
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.

004177 ERROR %s
004178 ERROR fileno(stderr)
004179 ERROR sigset(SIGABRT)
004180 ERROR sigrelse(SIGABRT)
004182 ERROR received signal %d\n

Cause: Received signal {signum}.

004183 FATAL lcdinitsig;sig=%d
004184 FATAL lcdinitsig;default:signal=%d
004185 ERROR %s: ::receive(%d) had bad name error on incoming_mailbox %s
004186 ERROR %s: ::receive(%d) protocol error on incoming_mailbox %s

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

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

004187 ERROR %s: ::receive(%d) returned NULL message pointer and ::last_err()==r_okay on incoming_mailbox %s
004188 ERROR %s: ::receive(%d) had unknown ::last_err() status %d on incoming_mailbox %s
004189 ERROR %s: ::receive(%d) returned NULL message pointer on incoming_mailbox %s
004190 ERROR %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 with incoming mailbox {mailbox}.

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

004191 ERROR no system specified for remote execution of \"%s\"
004192 ERROR no mailbox specified for remote execution of \"%s\"
004193 ERROR retbuf can’t be NULL
004194 ERROR retp can’t be NULL
004195 ERROR Can’t find return value in return buffer. Possible buffer overflow caused by the size of the returned data.
004198 ERROR retbuf is NULL
004199 ERROR lcdsendmes: can’t set data on message
004200 ERROR lcdsendmes: can’t set data on message
004201 ERROR lcdsendmes: can’t set reply system
004202 ERROR lcdsendmes: can’t set reply mailbox
004204 ERROR attempt to send illegal message

Cause: Sending message failed due to a illegal message.

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

004207 ERROR destination mailbox \"%s\" at system \"%s\" is full. Trying Again …
004208 ERROR destination system \"%s\" is alive but the \"%s\" mailbox process is not listening.

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

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

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

004210 WARN destination system \"%s\" is temporarily dead. will try again later…
004211 ERROR can’t send to destination \"%s\" error=%d

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

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

004212 ERROR lcdsendmes: unexpected error
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 system and check the logs for related errors. Retry the same process 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 system and check the logs for related errors. Retry the same process after the system is full initialized.

004223 ERROR received message with zero length on private mailbox %s
004224 ERROR lcdsendremote: unknown message type=%d(‘%c’) received by machine \"%s\"
004225 ERROR illegal net type
004226 ERROR net type must not be ILLNET
004227 ERROR baud rate must be between B0 and B38400
004228 ERROR 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.

004229 ERROR Can’t get host name from getaddrinfo()
004230 ERROR device %s no such file or directory \n
004231 ERROR stat of device %s failed errno=\n
004232 ERROR device %s not a character special file\n
004233 ERROR device %s already in use
004234 ERROR 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.

004244 ERROR %s Will try port \"%s\" instead.
004246 ERROR no response heard from system \"%s\" on TTY port \"%s\" to reply box \"%s\" in %d seconds
004247 ERROR %s
004248 ERROR failed to allocate %dB message buffer
004250 ERROR %s Will try port \"%s\" instead.
004253 ERROR %s message failure by port %s siz=%d
004254 WARN no response heard from system \"%s\" on TTY port \"%s\" to reply box \"%s\" in %d seconds (siz=%d)
004255 ERROR %s
004256 ERROR %s
004258 WARN Communication to %s by %s FAILED

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

Action: Check system configuration and network connection.

004261 WARN COMMUNICATIONS failover from system \"%s\" will be started.

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.

004263 ERROR can not set read pid if network type is TCP
004264 ERROR can’t remotely set read pid
004265 ERROR can’t remotely increment statistics
004266 ERROR can only set write pid if network type is TTY
004267 ERROR can’t remotely set write pid of TTY object
004268 ERROR can not set baud if network type is TCP
004269 ERROR baud rate must be between B0 and B38400
004270 ERROR can’t set network type to ILLNET
004271 ERROR object already has this nettype
004272 ERROR system \"%s\" device \"%s\" never had its net type set
004273 FATAL internal buffer too small
004274 ERROR must specify new network name
004275 ERROR must define network type when it is being created
004276 ERROR priority must be in range 1 thru 99
004279 FATAL prefix_lkroot("config/LK_START_TIME"));
004281 ERROR must specify original network name
004282 ERROR must specify original device path
004283 ERROR new system \"%s\" and device \"%s\" can’t be same as old system and device
004284 ERROR new system \"%s\" can’t be same as old system \"%s\"
004285 ERROR
004286 ERROR new system \"%s\" and device \"%s\" can’t be same as old system and device
004288 FATAL illegal timeout baud %d
004292 ERROR resource \"%s\" %s

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

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

004293 ERROR resource \"%s\" %s

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

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

004294 ERROR resource \"%s\" requires a license (for Kit %s/%s) but none is installed

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

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

004295 ERROR The current number of in-service \"%s/%s\" resources (=%d) has already reached or exceeded the maximum allowed (=%d). Resource \"%s\" can not be restored at this time. To remove this restriction contact your SIOS Technology sales representative.
004296 ERROR The total number of \"%s/%s\" resources (=%d) in the system exceeds the maximum allowed (=%d). No resources of this type will be restored until the number is reduced to the maximum allowed or less. Resource \"%s\" can not be restored at this time. To remove this restriction contact your SIOS Technology sales representative.
004297 ERROR secondary remote resource \"%s\" on machine \"%s\" is already 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 of service and do in service on local resource again.

004298 ERROR remote resource \"%s\" on machine \"%s\" is still in-service, restore of resource \"%s\" will not be attempted!\n
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.

004301 ERROR exceeded internal maximum number of resources to restore (%d)
004302 ERROR exceeded internal maximum number of resources to restore (%d)
004303 ERROR resource \"%s\" not found
004304 ERROR restore() can’t restore resource \"%s\"
004311 ERROR can’t perform \"remove\" action on resources in state \"%s\"

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

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

004313 ERROR remove of resource \"%s\" has failed

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

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

004318 ERROR %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.

004322 ERROR %s,priv_globact(%d,%s): script %s FAILED returning %d
004326 ERROR %s,priv_globact(%d,%s): cmd \"%s\" returned error \"%d\" retbuf=\"%s\"
004330 ERROR can’t run all pre global stripts together
004332 ERROR 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.

004334 ERROR action \"%s\" has failed on resource \"%s\"
004335 ERROR setpriority(PRIO_PROCESS, 0, %d)
004336 FATAL execl(%s)
004337 ERROR fork(%s)
004338 ERROR waitpid failed (%s)
004339 ERROR child killed by signal %d (%s)
004340 ERROR child stopped by signal %d (%s)
004341 ERROR child continued (%s)
004342 ERROR unknown stoppage of child (%s)
004344 ERROR first tag is NULL or zero length
004345 ERROR second tag is NULL or zero length
004346 ERROR equivalency type must not be ILLEQV
004347 ERROR priority values cannot be zero for a SHARED equivalency
004348 ERROR both resources of the equivalency are the same
004349 ERROR resource \"%s\" cannot be remote for a \"%s\" equivalency
004350 ERROR resource \"%s\" cannot be remote for a \"%s\" equivalency
004351 ERROR a \"%s\" equivalency must have one remote resource

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

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

004352 ERROR both resources of a \"%s\" equivalency must not be remote
004356 WARN Use unsupported option %s for remove. This option may be removed in future upgrades.
004357 ERROR Priority of system \"%s\" for resource \"%s\" must be the same in all equivalencies
004358 ERROR Priority conflict. Remote priority value %u for resource \"%s\" is already assigned to another system
004360 ERROR \"%s\", \"%s\" is not a shared resource
004361 ERROR \"%s\", \"%s\" is not a shared resource
004367 ERROR both resources of the equivalency are the same
004370 FATAL attempt to access empty equivalency list
004371 FATAL index %d past range 0-%d
004372 FATAL internal buffer too small
004375 FATAL sigset(SIGALARM) failed
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 within a reasonable time and the LCD cannot operate without the LCM.

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

004377 ERROR in %s, %s is not a valid value for %s\n
004378 FATAL mpcntl(MPCNTL_BIND)
004380 ERROR initlcdMalloc;ftok
004381 ERROR initlcdMalloc;shmget
004382 ERROR initlcdMalloc;shmctl
004383 ERROR initlcdMalloc;shmget
004384 ERROR initlcdMalloc;shmget
004385 ERROR initlcdMalloc;shmget,IPC_EXCL
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 documentation and ensure that the server meets the minimum requirements and that the operating system is configured properly.

004387 ERROR initlcdMalloc;shmat
004388 ERROR nsbrk: allocation overflow linno=%d incr=%d\n
004389 WARN flag initialisation: removing stale flag %s\n
004390 WARN flag initialisation: removing insane flag %s\n
004391 FATAL internal buffer too small
004392 FATAL action_has_finished() called before wait_for_action()
004393 FATAL can’t find my wait flag=%s
004394 FATAL expected wait flag \"%s\", found \"%s\"
004395 FATAL can’t remove my wait flag %s
004396 ERROR process pid=%d
004399 ERROR argument must be of form machine:flag
004401 WARN wait_for_action: deleting insane flag %s\n
004402 FATAL can’t find my wait flag=%s
004405 ERROR chk_man_interv: Unable to create flag file <%s>, using default CONFIRMSODEF value %d.
004406 ERROR chk_man_interv: Unable to write to flag file <%s>, using default CONFIRMSODEF value %d.
004407 ERROR chk_man_interv: Unable to invoke sendevent, using default CONFIRMSODEF value %d.
004410 ERROR wait_for_action flag %s is already held by process %d\n
004412 FATAL wait_for_action: curpid=%d
004413 WARN wait_for_action: admin flag %s removed because owner terminated
004415 ERROR acquisition of lock %s timed out after %d tries\n
004416 WARN Caller process %d has disappeared – removing admin flag\n
004419 ERROR must specify flag name
004420 ERROR must specify new flag name
004422 ERROR must specify flag name to remove
004425 ERROR index of \"%d\" past maximum \"%d\"
004426 ERROR object empty; use ::create() first
004427 ERROR object empty; use ::fill() first
004428 ERROR new field not specified properly
004429 ERROR index of \"%d\" past maximum \"%d\"
004430 ERROR object empty; use ::create() first
004431 ERROR object empty; use ::fill() first
004432 ERROR can’t change field because %s already in use
004433 ERROR use ::create() on local objects
004434 ERROR new name not specified properly
004435 ERROR object has already been created as %s
004436 ERROR new name not specified properly
004437 ERROR local object %s was not allocated using C++ \"new\" operator
004438 ERROR remote object %s for system \"%s\" must not be allocated using C++ \"new\" operator
004440 ERROR index %d past range 0-%d ondx=%d
004441 ERROR attempt to access empty base list ondx=%d
004442 FATAL failed to compile requires regexp, err=%d
004443 FATAL failed to compile except regexp, err=%d
004444 WARN License key (for Kit %s/%s) has EXPIRED

Cause: Your license has expired.

Action: Contact Support to obtain a new license.

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

Cause: Your license is about to expire.

Action: Contact Support to obtain a new license.

004446 ERROR %s
004447 ERROR must specify application name
004448 ERROR must specify resource type name
004449 ERROR must specify resource type name
004450 ERROR must specify application
004453 ERROR resource type \"%s\" for application \"%s\" is unknown on machine \"%s\"
004454 ERROR can’t remove entry for local system \"%s\"
004455 ERROR can’t set network type to ILLSYS
004457 FATAL internal buffer too small
004458 ERROR must specify new system name
004459 ERROR must specify system name to remove
004461 ERROR must specify system name
004462 ERROR system \"%s\" not defined on machine \"%s\".
004463 ERROR must specify system name
004464 ERROR system \"%s\" not defined on machine \"%s\".
004465 ERROR must specify system name
004466 ERROR system \"%s\" not defined on machine \"%s\".

Cause: The specified system name is not known.

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

004467 ERROR system \"%s\" unknown on machine \"%s\"

Cause: The specified system name is not recognized.

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

004468 ERROR %s
004469 ERROR must specify new application name
004470 ERROR must specify application name to remove
004472 ERROR application \"%s\" unknown on machine \"%s\"
004473 FATAL new not allowed for lcdlock
004474 FATAL delete not allowed for lcdlock
004475 FATAL ftok(%s, %d)
004476 FATAL can’t exclusively create semaphore set
004477 FATAL can’t get semid of semaphore set
004478 FATAL can’t remove semaphore set
004479 FATAL can’t create new semaphore set
004480 FATAL can’t get semid of semaphore set
004481 FATAL can’t initialize semaphore set
004483 FATAL can’t obtain LCD daemon semaphore
004485 WARN can’t get key for GUI semaphore
004486 WARN can’t get GUI semaphore
004487 FATAL tag index %d must be less than %d
004488 FATAL tag %d already in use
004489 FATAL tag index %d must be less than %d
004490 FATAL destructed lock %d without releasing it first
004491 FATAL must specify lock request using rl() or wl()
004492 ERROR can’t get semaphore semvals
004493 FATAL attempt to pop empty lock stack at[%d,%s]
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.

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

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

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.

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

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

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

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

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

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.

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

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

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.

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

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

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

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

004512 ERROR

Cause: An error occured on the remote machine.

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

004513 ERROR \"%s\" may not contain white space characters
004516 ERROR must define object first with ::create() or ::fill()
004517 ERROR must define object first with ::create() or ::fill()
004518 ERROR must define object first with ::create() or ::fill()
004519 ERROR must define object first with ::create() or ::fill()
004520 ERROR must define object first with ::create() or ::fill()
004521 ERROR must define object first with ::create() or ::fill()
004522 ERROR must define object first with ::create() or ::fill()
004523 ERROR must define object first with ::create() or ::fill()
004524 ERROR must define object first with ::create() or ::fill()
004525 ERROR must define object first with ::create() or ::fill()
004526 ERROR must define object first with ::create() or ::fill()
004527 ERROR must define object first with ::create() or ::fill()
004528 ERROR must define object first with ::create() or ::fill()
004529 ERROR id \"%s\" already is use by resource \"%s\"
004530 ERROR list pointer is NULL
004531 ERROR buffer pointer is NULL
004532 ERROR list pointer is NULL
004533 ERROR event class must not be NULL
004534 ERROR event type must not be NULL
004535 ERROR list pointer is NULL
004538 ERROR event class must not be NULL
004539 ERROR event type must not be NULL
004540 ERROR list pointer is NULL
004542 ERROR event class must not be NULL
004543 ERROR event type must not be NULL
004544 ERROR must define object first with ::create() or ::fill()
004545 ERROR only local access is allowed
004546 ERROR must define object first with ::create() or ::fill()
004547 ERROR buffer pointer is NULL
004548 ERROR must define object first with ::create() or ::fill()
004558 ERROR must define object first with ::create() or ::fill()
004560 ERROR \"%s\" may not contain ^A character
004563 ERROR can’t set resource init type to ILLINIT
004564 ERROR must define object first with ::create() or ::fill()
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.

004566 ERROR must define object first with ::create() or ::fill()
004567 ERROR split brain detected while setting resource \"%s\" to \"%s\" state (SHARED equivalency to resource \"%s\" on machine \"%s\" which is in state \"%s\"). Setting local resource ISP but aborting the operation.

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

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

004568 ERROR split brain detected while setting resource \"%s\" to \"%s\" state (SHARED equivalency to resource \"%s\" on machine \"%s\" which is in state \"%s\"). Setting local resource ISP but aborting the operation.

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

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

004600 ERROR is_on_primary: tag name can’t be NULL
004603 ERROR no resource has an equivalency in resource hierarchy containing resource with tag \"%s\"
004605 ERROR findins: both tag and id can’t be NULL
004606 ERROR no resource instance has either a tag \"%s\" or an identifier \"%s\"
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.

004614 ERROR can’t set init state to ILLINIT
004615 ERROR application name argument illegal
004616 ERROR resource type name argument illegal
004617 ERROR tag argument illegal
004618 ERROR identifier argument illegal
004619 ERROR resource with tag \"%s\" already exists with identifier \"%s\"

Cause: The provided tag name already exists.

Action: Choose a different tag name.

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

Cause: The provided identifier already exists.

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

004621 ERROR The current number of \"%s/%s\" resources (=%d) has already reached or exceeded the maximum allowed (=%d). The \"%s\" resource can not be created at this time. To remove this restriction contact your SIOS Technology sales representative.
004636 FATAL attempt to access empty resource list
004637 FATAL index %d past range 0-%d
004643 ERROR Instance tag name is too long. It must be shorter than %d characters.

Cause: Tag name is too long.

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

004644 ERROR Instance id is too long. It must be shorter than %d characters.
004645 ERROR Instance info field is too long. It must be shorter than %d characters.
004646 ERROR Tag name contains illegal characters

Cause: Tag name contains an illegal character.

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

004657 ERROR undeleted instance \"%s\" depends on instance \"%s\" that is to be deleted
004667 ERROR ERROR: Could not lock child, moving on to next one\n
004668 ERROR ERROR: fork failed. continuing to next dependent\n
004671 ERROR ERROR: wait() error\n
004672 ERROR ERROR: clone %d is hung, attempting to kill it\n
004673 ERROR ERROR: Could not kill clone %d\n
004676 FATAL Lcd_shgp->roots is NULL
004681 ERROR malloc error
004689 ERROR can’t force global delete actions if remove initialization is turned off
004690 ERROR can’t specify app, typ, id or tag when top is set
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.

004692 ERROR can’t set application when tag or id is set
004693 ERROR can’t set resource type when tag or id is set
004694 ERROR must specify at least one argument
004710 FATAL number of list elements has exceeded %d\n
004711 ERROR can’t set both tag and identifier at same time
004712 ERROR can’t set application when tag or id is set
004713 ERROR can’t set resource type when tag or id is set
004720 ERROR must specify tag to get parents
004721 ERROR must specify tag to get parents
004723 ERROR attempt to change state of resource \"%s\" from OSF state to the %s state from COMMON equivalency
004724 ERROR attempt to change state of resource \"%s\" from OSF state to the %s state from COMMON equivalent resource \"%s\" on machine \"%s\"
004727 ERROR reserve_resources(%s,%s): getpgid FAIL
004728 ERROR Lcd_shgp->roots is NULL
004731 ERROR reserve type set to LCDRESRV_NONE
004732 ERROR reserve_resources(%s,%s): setsid() FAIL
004734 ERROR Process %d in process group %d tried %d times to reserve resources but failed.
004735 FATAL reserve type set to LCDRESRV_NONE
004736 FATAL reserve type set to LCDRESRV_NONE
004737 FATAL Lcd_shgp->roots is NULL
004738 FATAL clr_res(%d): getpgid FAIL
004739 ERROR Process %d in process group %d attempted to clear reservation on resource \"%s\" by process %d in group %d expecting it to be reserved by process %d.
004740 ERROR \"%s\" may not contain ctrl characters
004741 ERROR \"%s\" may not contain ctrl characters
004742 ERROR chk_man_interv: Unable to open flag file <%s>, using default CONFIRMSODEF value %d.
004743 ERROR chk_man_interv: Invalid instruction %d in flag file <%s>, using default CONFIRMSODEF value %d.
004744 ERROR chk_man_interv: CONFIRMSODEF value apparently invalid, using %d instead
004745 ERROR failed to access lkexterrlog path=%s

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

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

004746 ERROR lkexterrlog failed runret=%d cmdline=%s

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

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

004776 ERROR failed to read the temporal recovery policy log.
004779 ERROR resource \"%s\" with id \"%s\" has %s
004780 ERROR local recovery is disabled by the current settings. The recovery of resource \"%s\" will not be attempted.
004781 ERROR Local recovery is disabled by the temporal recovery settings. The recovery of resource \"%s\" will not be attempted.
004782 ERROR Resource \"%s\" was in state \"%s\" before event occurred – recovery will not be attempted

Cause: The resource is already in service. Recovery will 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 still needed.

004786 ERROR %s on failing resource \"%s\"

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

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

004787 ERROR Failover is blocked by current settings. MANUAL INTERVENTION IS REQUIRED
004788 EMERG 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.

004793 ERROR lcdsendremote transfer resource \"%s\" to \"%s\" on machine \"%s\" failed (rt=%d)

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

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

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.

004798 ERROR SHARED resource \"%s\" is being restored because machine \"%s\" has failed
004799 ERROR Restore of resource \"%s\" has failed – initiating inter-machine recovery
004805 ERROR ADDLIST_ERROR for \"%s\"
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 to recover serially. If the recovery fails, check for error messages related to the resources which failed to recover to find out what further actions to take.

004810 ERROR Attempting serial recovery due to possible parallel recovery failure
004811 WARN The sendevent resource lists are too large for the %d byte buffer. The resource length is: %d.
004812 ERROR malloc failure
004813 ERROR lock_open_trp_lock(): failed to open file: %s.
004814 ERROR increase_trs_buffer(): failed to reallocate buffer for temporal_recovery_stamp.
004815 ERROR add_entry_into_trs_buffer(): failed to malloc initial buf for temporal_recovery_stamp.
004816 ERROR add_entry_into_trs_buffer(): failed to increase buf for temporal_recovery_stamp.
004817 ERROR read_temporal_recovery_policy(): fail to read policy configurations.
004819 ERROR read_temporal_recovery_log(): failed to fopen file: %s. fopen() %s.

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

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

004820 ERROR read_temporal_recovery_log(): failed to malloc initial buf for temporal_recovery_stamp.

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

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

004821 ERROR read_temporal_recovery_log(): failed to reallocate buffer for temporal_recovery_stamp.

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

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

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

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

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

004823 ERROR rename(%s, %s) failed.

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

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

004829 FATAL err=%s line=%d Semid=%d numops=%zd 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.

004860 ERROR 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 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.

004864 ERROR 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 (exit: %d)

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.

005000 ERROR poll_handler::get events – polling
005001 WARN poll_hand::get_events() spent %ld secs\n
005002 WARN poll_handler::get_events(): revents = 0x%04x\n
005003 WARN pid %d:
005004 ERROR poll_handler
005005 WARN fd %d:
005006 ERROR setting socket process owner
005007 WARN fd %d:
005008 ERROR getting current socket flags
005009 WARN fd %d:
005010 ERROR setting socket for asynchronous notification
005011 WARN poll_hand::set_poll() spent %ld secs\n
005012 WARN fd %d:
005013 ERROR getting current socket flags
005014 WARN fd %d:
005015 ERROR unsetting socket for asynchronous notification
005016 WARN poll_hand::unset_poll() spent %ld secs\n
005017 WARN po_box::dispatch_msg(): _msg_list.size = %d, _req_list.size = %d\n
005018 WARN po_box::dispatch_msg(): sending ctl part of message, size=%zu\n
005019 WARN WARNING:po_box::dispatch_msg():_bytes_out wrapped around\n
005020 WARN po_box::dispatch_msg(): sending data part of message, size=%zu\n
005021 WARN sent message to driver\n
005022 WARN po_box request for non-existent driver: %s:%s to %s:%s (%s/%u) (%d/%d)\n
005023 WARN WARNING:po_box::put():_bytes_in wrapped around\n
005024 WARN po_box::put_msg – bad command %s\n
005025 WARN po_box::put_msg – bad command %s\n
005026 WARN ctl_po_box %s got bad string (%d) size %ld: %s\n
005027 WARN add_conn dev(%s) lipa(%s)\n
005028 WARN postoffice remove sys/dev %s/%s\n
005029 ERROR fopen of /tmp/mbox_dbg
005030 WARN tli_fdget_i[%u] – device(%s)\n
005031 WARN tli_fdget_i::d’tor spent %ld secs\n
005032 WARN tli_fdget_i::execute get_events() spent %ld secs\n
005033 WARN tli_fdget_i[%u] running, events=0x%x\n
005034 WARN tli_fdget_i[%u]::execute: accept device (%s)\n
005035 ERROR tli_fdget_i::execute accept fails
005036 WARN tli_fdget_i::execute accept() spent %ld secs\n
005037 WARN getnameinfo() failed %s\n
005038 WARN tli_fdget_i[%u]::execute device(%s) ripa(%s) lipa(%s)\n
005039 WARN tli_fdget_i::execute event 0x%hx\n
005040 ERROR tli_fdget_i::execute – getaddrinfo
005041 ERROR tli_fdget_i::execute – creating socket
005042 WARN tli_fdget_i::execute my_socket() spent %ld secs\n
005043 ERROR setsockopt setting SO_REUSEADDR
005044 WARN tli_fdget_i::execute t_bind() spent %ld secs\n
005045 ERROR 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 are properly configured. If this message continues and resources cannot be put into service, contact Support.

005046 WARN tli_fdget_i::execute bind() spent %ld secs\n
005047 ERROR tli_fdget_i::execute listen failed
005049 WARN tli_fdget_o[%u] to %s on dev %s local ip %s remote ip %s\n
005050 WARN tli_fdget_o[%u] to %s on dev %s dies\n
005051 WARN tli_fdget_o::execute get_events() spent %ld secs\n
005052 WARN tli_fdget_o[%u] running, events=0x%x\n
005053 ERROR tli_fdget_o::execute – get SO_ERROR socket option
005054 WARN tli_fdget_o[%u]::execute – established outbound connection to %s at %s\n
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 are properly configured. If this message continues and resources cannot be put into service, contact Support.

005056 ERROR COMMAND OUTPUT: %s
005057 WARN tli_fdget_o[%u] runs in alarm loop\n
005058 ERROR tli_fdget_i::execute – getaddrinfo
005059 ERROR tli_fdget_o::execute – creating socket
005060 WARN tli_fdget_o::execute my_socket() spent %ld secs\n
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 are properly configured. If this message continues and resources cannot be put into service, contact Support.

005062 WARN tli_fdget_o::execute bind() spent %ld secs\n
005063 ERROR LifeKeeper: can’t get service %s, protocol %s\n
005065 ERROR tli_fdget_o::execute – connect
005066 ERROR COMMAND OUTPUT: %s
005067 WARN tli_fdget_o::execute my_connect() spent %ld secs\n
005068 WARN vs_driver[%u]::execute(): Entering\n
005069 WARN vs_driver[%u]::execute(): Before loop, ready()=%d, vstate()=%d\n
005070 WARN vs_driver[%u]::execute(state=_vrhead): Invalid request, going away.\n
005071 WARN vs_driver[%u]::execute(): Receiving data of size %
005072 WARN vs_driver[%u]::execute(): Receive complete.\n
005073 WARN vs_driver[%u]::execute(): Bottom of loop, ready()=%d, vstate()=%d\n
005074 WARN vs_driver[%u]::execute(): Leaving\n
005075 WARN vs_driver[%u]::send: ready()=%d, vstate()=%d\n
005076 WARN lcm_driver[%u]::send(): lstate()=%d\n
005077 WARN lcm_handler[%u]::execute(%d,%p,%p): Entering\n
005078 WARN lcm_hand::exec() spent %ld secs\n
005079 WARN lcm_handler::run(): Got request %d for sys %s, mailbox %s\n
005080 WARN driver %u forwarding request to %u, size %zu\n
005081 WARN lcm_handler::handle_send_msg(): Message from %s:%s to %s:%s\n
005082 WARN forwarding message to %s to dev null\n
005083 WARN driver %u got a ping at %ld\n
005084 WARN handle forward driver %u driver %u gone!\n
005085 WARN _add_driver\n
005086 WARN ..find other\n
005087 WARN ..find this\n
005088 WARN .. driver’s lipa(%s) ripa(%s) sys(%s) dev (%s)\n
005089 WARN .. foundother(%p) foundthis(%p) _add_driver(%x)\n
005090 WARN system_driver::add_driver: cmd=%s\n
005091 WARN did add_driver event for %ld @%ld\n
005092 WARN .. exit _add_driver ret val(%d)\n
005093 WARN _add_driver(tli_fdget_i %p)\n
005094 WARN ..lst(%p)\n
005095 WARN exit _add_driver ret val(1)\n
005096 WARN _add_driver(tli_fdget_o %p)\n
005097 WARN ..lst(%p)\n
005098 WARN exit _add_driver ret val(1)\n
005099 WARN rm_driver %ld – sys %s, dev %s\n
005100 WARN rm_driver %u – sys %s, dev %s @%ld\n
005102 WARN rm_driver – hangup on driver 0\n
005103 WARN exit rm_driver 1\n
005104 WARN exit rm_driver 0\n
005105 WARN rm_driver %u – sys %s, dev %s @%ld\n
005107 WARN rm_driver – hangup on driver 0\n
005108 WARN system_driver::rm_driver: cmd=%s\n
005109 WARN did remove_driver event for %u @%ld\n
005110 WARN rm driver: other driver @%p (%u)\n
005111 WARN _add_odriver_event(system %s driver %s)\n
005112 WARN exit _add_odriver_event(%d)\n
005113 WARN add_odriver(%p)\n
005114 WARN exit add_odriver(%d)\n
005115 WARN _add_idriver_event(system %s driver %s)\n
005116 WARN exit _add_idriver_event(%d)\n
005117 WARN add_idriver(%p)\n
005118 WARN exit add_idriver(%d)\n
005119 WARN rm_odriver(system %s driver %s)\n
005120 WARN exit rm_odriver %d\n
005121 WARN rm_odriver_event(system %s driver %s)\n
005122 WARN exit rm_odriver_event %d\n
005123 WARN rm_idriver(system %s driver %s)\n
005124 WARN exit rm_idriver %d\n
005125 WARN rm_idriver_event(system %s driver %s)\n
005126 WARN exit rm_idriver_event %d\n
005127 WARN find_odriver\n
005128 WARN find_get_odriver\n
005129 WARN exit find_get_odriver %p\n
005130 WARN find_idriver\n
005131 WARN find driver, sys %s, idriver %ld, odriver %ld\n
005132 WARN system_driver::add_connect: adding connection to sys %s, device %s\n
005133 WARN removing connection to sys %s, device %s\n
005134 WARN finding connection to sys %s, device %s\n
005135 WARN found connection\n
005136 WARN didn’t find connection\n
005137 WARN WARNING:ser_num::ser_num():global_num about to wrap around\n
005138 WARN WARNING:ser_num::ser_num(ser_num&):global_num about to wrap around\n
005139 WARN sig_hold %u, attempt to assign invalid signal %d\n
005141 WARN invalid signal %d\n
005142 WARN sys %.8s, box %.8s\n
005143 WARN lcm_pipe::open – socket() failed, err %d, pid %d\n
005144 WARN lcm_pipe::open – connect() failed, err %d, pid %d\n
005145 ERROR opening the file

Cause: A pipe could not be opened or created.

Action: Check adjacent log messages for more details.

005146 WARN In lcm_pipe[%u]::execute(%d,%p,%p)\n
005147 WARN LCM heartbeat interval = %ld\n
005148 WARN LCM missed heartbeat limit = %u\n
005149 WARN LCM missed heartbeat limit = %u\n
005150 WARN tli_handler %u dev %s lipa(%s) ripa(%s)\n
005151 WARN new tli_handler %u on dev %s\n
005152 WARN tli_handler %ld to %s on dev %s\n
005153 WARN new tli_handler %u to %s on dev %s\n
005154 WARN creating new tli_fdget_o on %s to %s\n
005155 WARN tli_hand::d’tor shutdown() spent %ld secs\n
005156 WARN openpoll fd %d\n
005157 WARN done closing fd\n
005158 WARN tli_hand::exec t_look() spent %ld secs\n
005160 WARN tli_handler %u going away (POLLERR) at %ld lastread=%ld lastping=%ld\n
005162 WARN tli_hand::exec %u send a ping at %ld\n
005163 WARN tli_handler::run %u to %s on dev %s\n
005164 ERROR tli_handler::handle-error:sending/receiving data message

Cause: A message failed to be sent or received.

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

005165 WARN errno %d\n

Cause: A message failed to be sent or received.

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

005166 WARN poll 0x%hx\n

Cause: A message failed to be sent or received.

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

005167 WARN handler for sys %s\n

Cause: A message failed to be sent or received.

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

005168 WARN tli_hand::xmit send() spent %ld secs\n
005169 WARN tli_hand::rcv recv() spent %ld secs\n
005170 WARN sig_execute::_handler_func – sig=%d\n
005171 WARN sig_execute::_handler_func – SIGPOLL si_code=0x%x, si_band=0x%lx, si_fd=%d\n
005172 ERROR fdget::fdget – creating socket
005173 ERROR fdget::fdget – binding socket
005174 ERROR fdget::fdget – listen on socket
005175 WARN fdget::fdget() spent %ld secs\n
005176 WARN fdget dtor deleting fd %d\n
005177 WARN fdget::fdget d’tor spent %ld secs\n
005178 ERROR fdget::execute – accepting connection
005179 WARN fdget::exec() spent %ld secs\n
005180 WARN garbage_collection: unknown message\n
005181 WARN Normal Data:\n
005182 ERROR garbage_collection: get normal
005183 WARN cntl[%d]:\n
005184 WARN \n
005185 WARN %02x
005186 WARN \n
005187 WARN data[%d]:\n
005188 WARN \n
005189 WARN %02x
005190 WARN \n
005191 WARN Priority Data:\n
005192 ERROR garbage_collection: get priority
005193 WARN cntl[%d]:\n
005194 WARN \n
005195 WARN %02x
005196 WARN \n
005197 WARN data[%d]:\n
005198 WARN \n
005199 WARN %02x
005200 WARN \n
005201 WARN garbage_collection: invalid peek flag\n
005202 WARN .. new add_tli_handler _ptr (system – %s device – %s)\n
005203 WARN entering todo: current _ptr (system – %s device – %s)\n
005204 WARN deleting add_tli_handler\n
005205 WARN in %u, out %u, me %u\n
005206 WARN idriver last_alarm %ld, mine %ld\n
005207 WARN odriver %u lastread %ld, mine (%u) %ld\n
005208 WARN adding driver with event(tli_handler-%u)\n
005209 WARN i_m_running: @%ld\n
005210 WARN incoming mailbox::is_empty – send 1 failed\n
005211 WARN incoming mailbox::remove – failed\n
005212 WARN incoming_mailbox::receive(), before send\n
005213 WARN incoming_mailbox::receive(), before 1st receive\n
005214 WARN incoming_mailbox::receive(), before 2nd receive\n
005215 WARN incoming_mailbox::receive(), after 2nd receive\n
005216 WARN outgoing_mailbox::can_talk – %s\n
005217 WARN outgoing_mailbox::can_talk – %s\n
005218 WARN outgoing_mailbox::can_talk – %s\n
005219 WARN outgoing_mailbox::can_talk – %s\n
005220 WARN outgoing_mbox::send can’t send request\n
005221 WARN attempt to send null message\n
005222 WARN outgoing_mailbox::send – can’t send data\n
005223 WARN outgoing_mailbox::send – receive failed\n
005224 WARN outgoing_mailbox::send – receive garbled\n
005225 WARN 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.

005226 WARN so_driver[%u]::xmit write() writing %zu bytes: <%s>
005227 WARN so_driver::xmit write() failed, errno = %d
005228 WARN so_driver::xmit write() wrote %d bytes: <%s>
005229 WARN so_driver::xmit write() spent %ld secs
005230 WARN so_driver::rcv read() failed, errno = %d
005231 WARN so_driver::rcv read() received %d bytes: <%s>
005232 WARN so_driver::rcv getmsg() spent %ld secs
005233 WARN In so_driver[%u]::execute(%d,…)
005234 WARN In so_driver[%u]::execute(): No action taken
005235 WARN found tcp connection to iwstp\n
005236 WARN didn’t find tcp connection to iwstp\n
005237 WARN lcm_handler retry send from %s:%s to %s:%s (%d)\n
005238 WARN detected duplicate request from %s:%s to %s:%s\n
005239 WARN lcm_handler retry timer set to %d based on lcd remote timeout of %d s (%d s)
005240 WARN clean up stale dup_list entry (%d s): %s:%s to %s:%s last: %s
005241 WARN dup_list: %s %s %s %s %d %d (%d)
005243 WARN add new dup_list entry %s:%s to %s:%s %d %d (%d)
006009 ERROR fork failed: %s
006012 ERROR quickCheck script ‘%s’ (%d) failed to exit after %u seconds. Forcibly terminated. Please examine the script or adjust the LKCHECKINTERVAL parameter in %s.

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

Action: Perform the steps listed in the message text.

006014 ERROR LKCHECKINTERVAL parameter is too short. It is currently set to %d seconds. It should be at least %ld seconds. Please adjust this parameter in %s and execute ‘kill %d’ to restart the lkcheck daemon.
006028 ERROR fmt, arg );
006029 ERROR Usage:%s [-?] [-f frequency]
006030 ERROR -? print this help summary
006031 ERROR -f number test frequency in seconds
006102 ERROR 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.

007001 ERROR %s: path in disk.reserve (%d bytes) exceeds maximum path length (%d bytes).
007002 ERROR %s: FAILFASTTIMER is not numeric, using default value (%d).
007003 ERROR %s: FAILFASTTIMER cannot be zero, using default value (%d).
007004 ERROR %s: FAILFASTTIMER is too large, using default value (%d).
007006 ERROR %s: SKIPNOTREADY is not numeric, using default value (%d).
007007 ERROR %s: SKIPNOTREADY is too large, using default value (%d).
007009 ERROR %s: SCSIHANGMAX is not numeric, using default value (%d).
007010 ERROR %s: SCSIHANGMAX cannot be zero, using default value (%d).
007011 ERROR %s: SCSIHANGMAX is too large, using default value (%d).
007013 ERROR %s: ERRORRETRY is not numeric, using default value (%d).
007014 ERROR %s: ERRORRETRY cannot be zero, using default value (%d).
007015 ERROR %s: ERRORRETRY is too large, using default value (%d).
007017 ERROR %s: MAXSENDEVENTRETRY is not numeric, using default value (%d).
007018 ERROR %s: MAXSENDEVENTRETRY cannot be zero, using default value (%d).
007019 ERROR %s: MAXSENDEVENTRETRY is too large, using default value (%d).
007021 ERROR %s: DAEMONSTACKSIZE is not numeric, using default value (%d).
007022 ERROR %s: DAEMONSTACKSIZE cannot be less than %d, using default value (%d).
007023 ERROR %s: DAEMONSTACKSIZE is too large, using default value (%d).
007025 ERROR %s: FILTERHUNGMSG is not numeric, using default value (%d).
007026 ERROR s: FILTERHUNGMSG is too large, filtering 100 of messages.
007029 ERROR %s: DAEMONKEEPDEVICEOPEN must be `TRUE’ or `FALSE’, using default value (‘%s’).
007031 ERROR %s: DAEMONHALTONCE must be `TRUE’ or `FALSE’, using default value (‘%s’).
007033 ERROR %s: SCSIHALT must be `TRUE’ or `FALSE’, using default value (‘%s’).
007035 ERROR %s: SCSIEVENT must be `TRUE’ or `FALSE’, using default value (‘%s’).
007037 ERROR %s: SCSIERROR must be `halt’ or `event’, using default value (‘%s’).
007039 ERROR %s: RESERVATIONCONFLICT must be `halt’ or `event’, using default value (‘%s’).
007040 FATAL -f option `%s’ is not numeric
007041 FATAL -f option cannot be zero
007042 FATAL -f option `%s’ is too large
007043 FATAL -n option `%s’ is not numeric
007044 FATAL -n option out of range (-20 to 19)
007053 ERROR malloc failed. Assume that it is a monitoring target device.
007058 ERROR %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 is malfunctioning or because the disk has been reserved by another server.

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

007059 ERROR %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 is malfunctioning or because the disk has been reserved by another server.

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

007060 EMERG %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 is malfunctioning or because the disk has been reserved by another server. THE SERVER WILL BE REBOOTED/HALTED.

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

007064 ERROR %s: sendevent failed for %s: ‘%s’
007066 ERROR %s: sendevent failure on device ‘%s’.
007072 ERROR %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 from the system.

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

007073 ERROR %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 from the system.

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

007075 ERROR %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 a conflict with another server. This may be because the storage is malfunctioning or because the disk has been reserved by another server.

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

007076 ERROR %s: DEVICE FAILURE on SCSI device ‘%s’, RETRY. ret=%d, errno=0x%x, retry count=%d.
007077 ERROR %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 is malfunctioning or because the disk has been reserved by another server.

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

007078 ERROR %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 is malfunctioning or because the disk has been reserved by another server.

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

007091 ERROR %s: device checking thread (id=%d) for device ‘%s’ returned an unexpected error. return %d, errno=%d, hangcount=%d
008504 ERROR LKSCSI_Open: unable to get unique ID for %s
008506 ERROR LKSCSI_Open: RESERVATIONS has invalid setting ‘%s’. Default setting used.
008507 ERROR LKSCSI_Open: valid settings: ‘ioctl’ and ‘none’.
008508 ERROR LKSCSI_Open: valid setting: ‘ioctl’.
008509 ERROR LKSCSI_Open: SUPPORT_PAGES has invalid setting ‘%s’. Default setting used.
008510 ERROR LKSCSI_Open: valid settings: ‘DONT_ASK’ and ‘CHECK_PAGES’.
008511 ERROR LKSCSI_Open: ADD_LUN_TO_DEVICE_ID has invalid setting ‘%s’. Default setting used.
008512 ERROR LKSCSI_Open: valid settings: ‘TRUE’ and ‘FALSE’.
008513 ERROR LKSCSI_Open: FULL_ID_MATCH has invalid setting ‘%s’. Default setting used.
008514 ERROR LKSCSI_Open: valid settings: ‘TRUE’ and ‘FALSE’.
008515 ERROR LKSCSI_Open: ioctlMethod set to ‘SEND_CMD’.
008516 ERROR LKSCSI_Open: ioctlMethod set to ‘SGIO_SD_NODE’.
008517 ERROR LKSCSI_Open: ioctlMethod set to ‘SGIO_SG_NODE’.
008518 ERROR LKSCSI_Open: ioctlMethod set to ‘QUERY_DRIVER’.
008519 ERROR LKSCSI_Open: ioctlMethod set to ‘QUERY_SG’.
008520 ERROR LKSCSI_Open: ioctlMethod has invalid setting ‘%s’. Default setting ‘query’ used.
008521 ERROR LKSCSI_Open: valid settings: ‘SEND_CMD’, ‘SGIO_SD’, ‘SGIO_SG’, and ‘QUERY’.
008524 ERROR LKSCSI_Open: internal error, GetIDLUN on %s failed with %d.
008534 ERROR LKSCSI_Open: unable to map %s to a generic node
008535 ERROR LKSCSI_Open: fcntl: ioctlMethod file lock failed. errno = %d.
008536 ERROR LKSCSI_Open: unlock of ioctlMethod file failed. errno = %d.
008537 ERROR LKSCSI_Open: fcntl: ioctlMethod file lock failed. errno = %d.
008538 ERROR LKSCSI_Open: unlock of ioctlMethod file failed. errno = %d.
008539 ERROR LKSCSI_Open: setIoctlMethod: open failed on %s.
010000 WARN flg_list -d $i took more than $pswait seconds to complete…
010001 ERROR flag $flag not present, switchovers may occur.
010002 WARN flag $flag not present, send message again.

Cause: This message indicates an incomplete process that 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.

010005 EMERG $PRODUCT can not be started in init runlevel $init_state
010006 WARN 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 communicating with 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 to disallow failover operations from the current server.

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

010008 WARN flag $flag not present, send message again.

Cause: A process is incomplete but will be retried.

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

010023 FATAL LifeKeeper failed to initialize properly.

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

Action: Check adjacent log messages for more details.

010024 ERROR `printf ‘Resource "%s" already exists.’ $DISK`
010025 ERROR `printf ‘Unable to get a unique tag name on server "%s" for template resource "%s"’ $MACH $DISK`

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

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

010027 ERROR Error creating resource $DISK
010030 ERROR `printf ‘Create resource dependency "%s" to "%s" failed on "%s".’ $DISKTAG $LSRFTAG $MACH`
010031 ERROR `printf ‘Failed to set resource instance state for "%s" on "%s".’ $DISKTAG $MACH`
010033 ERROR perform_action failed $DISKACTION of $DISKTAG on $MACH.
010034 FATAL Unable to start lcm.

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

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

010035 FATAL Unable to start ttymonlcm.
010036 ERROR
010038 WARN Waiting for LifeKeeper core components to initialize has exceeded 10 seconds. Continuing anyway, check logs for further details.

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

Action: Perform the steps listed in the message text.

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

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

Action: Perform the steps listed in the message text.

010040 FATAL Unable to start lcd.
010043 ERROR An equivalency for the tag $PARENT_TAG does not exist on server $SERVER
010044 ERROR An equivalency for the tag $CHILD_TAG does not exist on server $SERVER
010046 ERROR The dependency creation failed on server $SERVER:" `cat $TEMP_FILE`

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

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

010050 ERROR An equivalency for the tag $PARENT_TAG does not exist on server $SERVER"
010051 ERROR An equivalency for the tag $CHILD_TAG does not exist on server $SERVER
010053 ERROR The dependency deletion failed on server $SERVER:" `cat $TEMP_FILE`
010063 ERROR $REMSH error

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

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

010064 ERROR Possible Configuration error: More than one LifeKeeper version is installed on this host
010076 FATAL Usage: hry_setpri [-d server] -t (comma separated root tag list) -p priority [-q] hry_setpri [-d server] -t (comma separated root tag list) -l
010077 FATAL Usage: hry_setpri [-d server] -t (comma separated root tag list) -p priority [-q] hry_setpri [-d server] -t (comma separated root tag list) -l
010078 FATAL Usage: hry_setpri [-d server] -t (comma separated root tag list) -p priority [-q] hry_setpri [-d server] -t (comma separated root tag list) -l
010079 FATAL No equivalencies were found for server "%s". Verify that the server name and tag names are correct.
010080 FATAL No equivalencies were found for server "%s". Verify that the server name and tag names are correct.
010082 WARN lkswitchback($MACH): Unable to obtain automatic switchback lock — trying again in ${interval} minutes
010083 WARN COMMAND OUTPUT: $LKROOT/bin/lkswitchback
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.

010087 EMERG The uname of the system has been changed, please change it back to its original setting before starting $PRODUCT.
010088 FATAL Internal usage error in call to reorder_priorities.
010089 FATAL Internal usage error in call to reorder_priorities.
010090 ERROR create device instance failure
010091 ERROR Resource instance \"$CDEVTAG\" with id \"$DEV\" already exists on machine \"$MACH\
010092 ERROR create device instance failure
010093 ERROR create device instance failure
010095 ERROR create device instance failure
010096 ERROR create device instance failure
010101 ERROR create device instance failure `cat /tmp/V2$$`
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.

010103 ERROR lock id string not specified
010104 ERROR lock file not specified
010105 ERROR No systems registered with LifeKeeper
010106 ERROR could not get locks since machine $m is dead
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 a harmless error.

010108 ERROR 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.

010110 ERROR admin machine not specified
010111 ERROR lock file not specified
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.

010114 ERROR COMMAND OUTPUT: $LKROOT/bin/sendevent
010115 ERROR COMMAND OUTPUT: $LKROOT/bin/sendevent
010116 ERROR unable to set !lkstop flag

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

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

010121 ERROR Extended logs aborted due to a failure in opening $destination. ($syserrmsg)

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

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

010129 ERROR Error editing $DEFAULT to $varcmd
010131 ERROR $CMD: Error editing $DEFAULT to $varcmd
010132 ERROR Unable to retrieve reservation id from "%s". Error: "%s". Attempting to regenerate.

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

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

010133 ERROR No reservation ID exists in "%s". A new ID must be generated by running "%s/bin/genresid -g" on "%s".

Cause: A unique reservation id has not been defined.

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

010134 ERROR LifeKeeper does not appear to be running. Unable to determine the uniqueness of the reservation ID within the cluster.

Cause: LifeKeeper was not running when an attempt to check the uniqueness of the reservation id was made.

Action: Start LifeKeeper and rerun the uniqueness check via "/opt/LifeKeeper/bin/genresid -v".

010135 ERROR The current reservation ID of "%s" is not unique within the cluster. A new ID must be generated by running "%s/bin/genresid -g" on "%s".

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

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

010136 ERROR Unable to store reservation id in "%s". Error: "%s"

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

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

010137 ERROR Failed to generate a reservation ID that is unique within the cluster.

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

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

010138 ERROR $message);
010139 WARN $message);
010140 ERROR $COMMAND_SNMPTRAP returned $exitcode for Trap $oid:$result
010141 ERROR LK_TRAP_MGR is specified in /etc/default/LifeKeeper, but $COMMAND_SNMPTRAP command is not in PATH.
010142 ERROR $COMMAND_EMAIL returned $exitcode:$result
010143 ERROR LK_NOTIFY_ALIAS is specified in /etc/default/LifeKeeper, but $COMMAND_EMAIL command is not in PATH.
010144 ERROR can’t opendir $LICENSE_DIR: $!
010145 ERROR lktest failed
010146 ERROR lkcheck failed
010147 ERROR ins_list failed: exit code = $exit_code
010148 ERROR $msg);
010200 ERROR scsifree: uuid is NULL
010206 ERROR scsifree: invalid file format, delimiter not found.
010209 ERROR scsifree(%s): ERROR – matched multiple entries.\n
010219 ERROR scsifree(%s): LKSCSI_Open(%s) failed
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 the system is functioning properly.

010225 ERROR scsiplock(%s): open failed.
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.

010236 ERROR scsifree: invalid file format, delimiter not found.
010239 ERROR scsiplock(%s): device %s found does not match uuid %s, expected %s
010240 ERROR scsiplock(%s): uuid %s found does not match device %s, expected %s
010247 ERROR scsiplist: plist is NULL
010250 ERROR Failed to exec command ‘%s’

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

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

010400 ERROR Error: LK_TRAP_MGR is specified in /etc/default/LifeKeeper, but snmptrap command is not in PATH.
010401 EMERG local recovery failure on resource $opts{‘N’}, syncing our log and rebooting…
010402 EMERG local recovery failure on resource $opts{‘N’}, trigger VMware HA…

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

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

010403 ERROR VMware HA trigger failed
010404 ERROR snmptrap returned $err for Trap 131
010405 ERROR COMMAND OUTPUT: cat /tmp/err$$
010406 ERROR snmptrap returned $err for Trap 132
010407 ERROR COMMAND OUTPUT: cat /tmp/err$$
010408 ERROR snmptrap returned $err for Trap 130
010409 ERROR COMMAND OUTPUT: cat /tmp/err$$
010410 ERROR snmptrap returned $err for Trap 121
010411 ERROR COMMAND OUTPUT: cat /tmp/err$$
010412 ERROR snmptrap returned $err for Trap 122
010413 ERROR COMMAND OUTPUT: cat /tmp/err$$

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

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

010414 ERROR snmptrap returned $err for Trap 111
010415 ERROR COMMAND OUTPUT: cat /tmp/err$$
010416 ERROR snmptrap returned $err for Trap 112
010417 ERROR COMMAND OUTPUT: cat /tmp/err$$
010418 ERROR snmptrap returned $err for Trap 110
010419 ERROR COMMAND OUTPUT: cat /tmp/err$$
010420 EMERG local recovery failure on resource $opts{‘N’}, trigger reboot…

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

Action: No action is required.

010421 ERROR snmptrap returned $err for Trap 102
010422 ERROR COMMAND OUTPUT: cat /tmp/err$$
010423 ERROR snmptrap returned $err for Trap 101
010424 ERROR COMMAND OUTPUT: cat /tmp/err$$
010425 ERROR snmptrap returned $err for Trap 100
010426 ERROR COMMAND OUTPUT: cat /tmp/err$$
010427 ERROR snmptrap returned $err for Trap 140
010428 ERROR COMMAND OUTPUT: cat /tmp/err$$
010429 ERROR snmptrap returned $err for Trap 141
010430 ERROR COMMAND OUTPUT: cat /tmp/err$$
010431 ERROR snmptrap returned $err for Trap 120
010432 ERROR COMMAND OUTPUT: cat /tmp/err$$
010433 ERROR LK_NOTIFY_ALIAS is specified in /etc/default/LifeKeeper, but mail command is not in PATH.
010434 ERROR [$SUBJECT event] mail returned $err
010435 ERROR COMMAND OUTPUT: cat /tmp/err$$
010436 ERROR [$SUBJECT event] mail returned $err
010437 ERROR COMMAND OUTPUT: cat /tmp/err$$
010438 ERROR [$SUBJECT event] mail returned $err
010439 ERROR COMMAND OUTPUT: cat /tmp/err$$
010440 ERROR [$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.

010441 ERROR COMMAND OUTPUT: cat /tmp/err$$
010442 ERROR [$SUBJECT event] mail returned $err
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.

010444 ERROR [$SUBJECT event] mail returned $err
010445 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.

010446 ERROR [$SUBJECT event] mail returned $err
010447 ERROR COMMAND OUTPUT: cat /tmp/err$$
010448 ERROR [$SUBJECT event] mail returned $err
010449 ERROR COMMAND OUTPUT: cat /tmp/err$$
010450 ERROR [$SUBJECT event] mail returned $err
010451 ERROR COMMAND OUTPUT: cat /tmp/err$$
010452 ERROR [$SUBJECT event] mail returned $err
010453 ERROR COMMAND OUTPUT: cat /tmp/err$$
010454 ERROR [$SUBJECT event] mail returned $err
010455 ERROR COMMAND OUTPUT: cat /tmp/err$$
010456 ERROR [$SUBJECT event] mail returned $err
010457 ERROR COMMAND OUTPUT: cat /tmp/err$$
010458 ERROR [$SUBJECT event] mail returned $err
010459 ERROR COMMAND OUTPUT: cat /tmp/err$$
010460 ERROR [$SUBJECT event] mail returned $err
010461 ERROR COMMAND OUTPUT: cat /tmp/err$$
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 the operation.

010471 ERROR COMM_DOWN: Attempt to obtain local comm_down lock flag failed

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

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

010482 ERROR 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 the operation.

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.

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

010492 WARN $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 completed with 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 $FPID

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

010506 ERROR Intelligent Switchback Check Failed

Cause: Failed 5 times to perform "lcdrecover."

Action: Switch over the resource tree manually.

010600 ERROR removing hierarchy remnants
010627 WARN Equivalency Trim: does not have a full complement of equivalencies. Hierarchy will be unextended from
010629 WARN Your hierarchy exists on only one server. Your application has no protection until you extend it to at least one other server.
010712 ERROR Unextend hierarchy failed

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

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

010714 ERROR $ERRMSG Resource \"$aRes\" is currently in-service on machine \"$TARGET_MACH\".
010716 ERROR $ERRMSG Unable to access dependencies of root resource \"$aRoot\" on target machine \"$TARGET_MACH\".
010718 ERROR $ERRMSG Hierarchy \"$ROOT_LIST\" is an invalid multi-root hierarchy. Root \"$aRoot\" has no common dependencies.
010720 ERROR $ERRMSG Hierarchy on target machine has no equivalencies.
010722 ERROR $ERRMSG Unable to obtain machine access information from target machine \"$TARGET_MACH\".
010728 ERROR $ERRMSG – Required input target machine is undefined.
010730 ERROR $ERRMSG – Required input root list is undefined.
010734 ERROR $ERRMSG The unextmgr program could not be run on target machine \"$TARGET_MACH\".
010746 ERROR $ERRMSG Target machine \"$TARGET_MACH\" does not have an active LifeKeeper communication path to machine \"$aMach\" in the hierarchy." >&2

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

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

010748 ERROR $ERRMSG Unable to establish an Admin Lock Flag.
010754 ERROR $ERRMSG Unable to obtain local equivalencies information.
010756 WARN Warning – unextmgr ($TARGET_MACH, $ROOT_LIST) – Unable to remove equivalence between \"$LocTag\" on machine \"$TARGET_MACH\" and \"$RemTag\" on machine \"$RemSys\". Continuing!
010762 WARN Warning – unextmgr ($TARGET_MACH, $ROOT_LIST) – The unextend operation was not completed successfully.
010763 ERROR lock failed
011000 ERROR appremote: unknown command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011001 ERROR depremote: unknown command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011002 ERROR eqvremote: unknown command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011003 ERROR flgremote: unknown command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011004 WARN Illegal creation of resource

Cause: This will not occur under normal circumstances.

011009 ERROR insremote: unknown change field command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011010 ERROR insremote: unknown command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011011 FATAL %s

Cause: LifeKeeper could not get IPC key.

Action: Check adjacent log messages for more details.

011012 FATAL semget(%s,%c)

Cause: LifeKeeper could not get semaphore set id.

Action: Check adjacent log messages for more details.

011013 FATAL shmget(%s,%c)

Cause: System could not allocate a shared memory segment.

Action: Check adjacent log messages for more details.

011014 FATAL prefix_lkroot("out"));

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

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

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 LifeKeeper Single Server Protection but you do not have LifeKeeper Single Server Protection installed.

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

011018 ERROR lic_init_fail_msg, lc_errstring(lm_job));

Cause: License manager initialization failed.

Action: Check adjacent log messages for more details.

011020 EMERG 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.

011023 EMERG 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 and retry 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.

011029 FATAL 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.

011032 ERROR 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.

011043 ERROR COMMAND OUTPUT: %s
011044 ERROR flagcleanup:fopen(%s)

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

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

011045 ERROR flagcleanup:fopen(%s)

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

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

011046 ERROR flagcleanup:fputs(%s)

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

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

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

011048 ERROR flagcleanup:chmod(%s)

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

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

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.

011052 FATAL malloc() failed

Cause: The system could not allocate memory for LifeKeeper.

Action: Increase the process limit for the data segment.

011053 FATAL lcm_is_unavail);

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

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

011054 FATAL 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.

011055 FATAL 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 not writable.

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’)\n

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.

011059 FATAL 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.

011060 FATAL 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\"\n

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.

011062 WARN LifeKeeper shutdown in progress. Unable to perform failover recovery processing for %s\n

Cause: 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 perform failover recovery processing for %s\n

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

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

011068 ERROR ERROR on command %s

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

Action: Check adjacent messages for more details.

011070 ERROR ERROR on command %s

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

Action: Check adjacent log messages for more details.

011080 FATAL out of memory

Cause: Internal error.

Action: Increase the process limit for the data segment.

011081 FATAL 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 not removable.

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 not removable.

011084 FATAL 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 a semaphore.

Action: Try to remove the semaphore manually.

011086 ERROR shmget(%s,%c) failed

Cause: A system error has occurred while removing a shared 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 a semaphore.

Action: Try to remove the semaphore manually.

011088 ERROR shmctl(IPC_RMID) failed

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

Action: Try to remove the shared memory segment manually.

011089 FATAL Execution of lcdstatus on remote system <%s> failed\n

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

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

011090 FATAL

Cause: Internal error.

Action: Perform the steps listed in the message text.

011091 WARN

Cause: This will not occur under normal circumstances.

011092 FATAL

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

011093 FATAL

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

011094 FATAL

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

011095 FATAL

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

011096 FATAL

Cause: There is a problem with your license.

Action: Perform the steps listed in the message text.

011097 FATAL

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

011098 FATAL

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

011099 FATAL

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

011100 FATAL

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

011101 FATAL

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

011102 FATAL

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

011103 FATAL

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

011104 FATAL

Cause: There is a problem with your license.

Action: Contact Support to obtain a new license.

011105 FATAL

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.

011113 ERROR netremote: unknown subcommand type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011114 ERROR netremote: unknown command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011117 ERROR sysremote: system \"%s\" not found on \"%s\"

Cause: An invalid system name was provided.

Action: Recheck the system name and rerun the command.

011118 ERROR sysremote: unknown subcommand type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011119 ERROR sysremote: unknown command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

011120 ERROR typremote: unknown command type %d(‘%c’)\n

Cause: Internal error.

Action: Try restarting the product.

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 of adjacent error messages.

011131 EMERG 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.

011142 WARN 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.

011150 ERROR 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 &localebuf3);

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

011152 EMERG Localized license failure

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

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

011154 EMERG Single Node flag check failed.

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

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

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 LifeKeeper Single Server Protection but you do not have LifeKeeper Single Server Protection installed.

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

011164 EMERG 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.

011165 ERROR LifeKeeper initialize timed out in tag \"%s\"
015000 ERROR COMMAND OUTPUT: /opt/LifeKeeper/sbin/steeleye-lighttpd

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

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

103001 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 db2nodes.cfg does not contain any server names.

Action: Ensure the db2nodes.cfg is valid.

103002 ERROR LifeKeeper was unable to get the version for the requested instance "%s"

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

Action: Check your DB2 configuration.

103003 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 to find any nodes for the DB2 instance.

Action: Check your DB2 configuration.

103004 ERROR Unable to get the information for resource "%s"

Cause: Failed to get resource information.

Action: Check your LifeKeeper configuration.

103005 ERROR 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.

103007 ERROR Unable to get the instance home directory information for resource "%s"

Cause: Failed to get the instance home directory path.

Action: Check your LifeKeeper configuration.

103008 ERROR 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.

103009 ERROR 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.

103012 ERROR LifeKeeper was unable to start the database server for instance "%s"

Cause: The requested startup of the DB2 instance failed.

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

103013 ERROR LifeKeeper was unable to start the database server for instance "%s"

Cause: The requested startup of the DB2 instance failed.

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

103015 ERROR An entry for the home directory "%s" of instance "%s" does not exist in "/etc/fstab"

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

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

103016 ERROR LifeKeeper was unable to mount the home directory for the DB2 instance "%s"

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

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

103017 ERROR Unable to get the instance nodes information for resource "%s"

Cause: Failed to get the instance nodes.

Action: Check your LifeKeeper configuration.

103018 ERROR LifeKeeper was unable to start database partition server "%s" for instance "%s"

Cause: The requested startup of the DB2 instance failed.

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

103020 ERROR LifeKeeper was unable to stop the database server for instance "%s"

Cause: The requested shutdown of the DB2 instance failed.

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

103021 ERROR LifeKeeper was unable to stop the database server for instance "%s"

Cause: The requested shutdown of the DB2 instance failed.

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

103023 ERROR Unable to get the instance nodes information for resource "%s"

Cause: Failed to get the instance nodes.

Action: Check your LifeKeeper configuration.

103024 ERROR LifeKeeper was unable to stop database partition server "%s" for instance "%s"

Cause: The requested shutdown of the DB2 instance failed.

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

103026 ERROR Unable to get the instance nodes information for resource "%s"

Cause: Failed to get the instance nodes.

Action: Check your LifeKeeper configuration.

103027 FATAL The argument for the DB2 instance is empty

Cause: Invalid parameters were specified for the create operation.

Action: Verify the parameters and retry the operation.

103028 FATAL Unable to determine the DB2 instance home directory

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

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

103029 FATAL Unable to determine the DB2 instance type

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

Action: Check your DB2 configuration.

103030 FATAL 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 to find any nodes for the DB2 instance.

Action: Check your DB2 configuration.

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

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

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

103032 ERROR LifeKeeper was unable to get the DB tablespace containers for instance "%s" or the log path for one of its databases

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

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

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 a shared filesystem and retry the operation.

103034 ERROR A DB2 Hierarchy already exists for instance "%s"

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

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

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

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

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

103036 ERROR Unable to create the hierarchy for raw device "%s"

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

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

103037 ERROR 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.

103038 ERROR LifeKeeper was unable to create a dependency between the DB2 hierarchy "%s" and the Raw hierarchy "%s"

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

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

103039 ERROR LifeKeeper could not disable the automatic startup feature of 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 startup of the instance at system boot.

103040 ERROR DB2 version "%s" is not installed on server "%s"

Cause: LifeKeeper could not find DB2 installed location.

Action: Check your DB2 configuration.

103041 ERROR 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 the specified server. If the user does not exist, it should be created with the same uid and gid on all servers in the cluster.

103042 ERROR The instance owner "%s" uids are different on target server "%s" and template server "%s"

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

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

103043 ERROR The instance owner "%s" gids are different on target server "%s" and template server "%s"

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

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

103044 ERROR 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 instance owner {user} must match on all servers in the cluster. The location mismatch should be corrected manually on all servers before retrying the "canextend" operation.

103045 ERROR LifeKeeper was unable to get the DB2 "SVCENAME" parameter for the DB2 instance

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

Action: Check your DB2 configuration.

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

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

Action: Check your DB2 configuration.

103047 ERROR LifeKeeper was unable to get the contents of the "/etc/services" file on the server "%s"

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

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

103048 ERROR LifeKeeper was unable to get the contents of the "/etc/services" file on the server "%s"

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

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

103049 ERROR 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 are mismatched.

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

103050 ERROR 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 the operation.

103051 ERROR Error getting resource information for resource "%s" on server "%s"

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

Action: Check your LifeKeeper configuration.

103052 ERROR LifeKeeper was unable to add instance "%s" and/or its variables to the DB2 registry

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

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

103053 ERROR Usage: %s instance
103054 ERROR Unable to determine the DB2 instance type

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

Action: Check your DB2 configuration.

103055 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 to find any nodes for the DB2 instance.

Action: Check your DB2 configuration.

103056 ERROR Usage: %s instance
103058 ERROR Usage: %s instance
103059 ERROR Usage: %s instance
103060 ERROR Unable to determine the DB2 instance home directory

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

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

103061 ERROR Unable to determine the DB2 instance type

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

Action: Check your DB2 configuration.

103062 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 to find the node for the DB2 instance.

Action: Check your DB2 configuration.

103063 ERROR Unable to determine the DB2 install path

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

Action: Check your DB2 configuration.

103064 ERROR Usage: nodes -t tag -a add_nodenum | nodes -t tag -d delete_nodenum | nodes -t tag -p
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.

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

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

Action: Verify the parameters and retry the operation.

103069 ERROR 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 by resource "%s". Deleting all nodes is not allowed.

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

Action: Verify the parameters and retry the operation.

103071 ERROR LifeKeeper is unable to get the equivalent instance for resource "%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.

103074 ERROR Usage: %s instance
103075 ERROR Usage: %s instance
103076 ERROR Unable to determine the DB2 instance type

Cause: The DB2 Application Recovery Kit was unable to determine 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 to determine the DB2 instance home directory.

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

103078 ERROR The database server is not running for instance "%s"

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

Action: The DB2 instance must be started.

103079 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 to find any nodes for the DB2 instance.

Action: Check your DB2 configuration.

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

Cause: All database partition servers should be running.

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

103081 ERROR DB2 local recovery detected another recovery process in progress for "%s" and will exit.
103082 ERROR Failed to create flag "%s"

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

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

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 to determine the DB2 instance home directory.

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

104002 FATAL $msg);

Cause: This message indicates an internal software error.

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

104003 FATAL $self->Val(‘Tag’) . " is not an SDR resource");

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

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

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 $argv1: 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.

104026 ERROR cannot create $md

Cause: The mirror device could not be created.

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

104027 ERROR $_);

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

104035 ERROR Too many failures. Aborting resync of $md

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

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

104036 ERROR Failed to start nbd-server on $target (error $port)

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

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

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 and that TCP ports in the range 10000-10512 are opened and unused. 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 the source server.

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

104039 ERROR 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 the unkillable 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.

104051 FATAL Unable to open file "%s"

Cause: Failed to open /etc/mtab.

Action: Check that /etc/mtab exists and check the system log for errors.

104052 FATAL 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->{‘tag’}. Error: $ret

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

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

104057 ERROR Failed to undo temporary access for $self->{‘tag’} on $self->{‘sys’}. Error: $ret. Please verify that $fsid is not mounted on server $self->{‘sys’}.

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

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

104062 FATAL 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 ID of 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 ID of the target disk has not changed.

104067 FATAL 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 or synchronous writes must be specified.

104068 FATAL Failed to extend dependent resource %s to system %s. Error %s

Cause: The hierarchy extend operation failed.

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

104069 FATAL Failed to grow array ($ret)

Cause: During an extend the ‘template’ server where the mirror was in-service was unable to grow the array to add the new target.

Action: Check for errors in the LifeKeeper log and system log.

104070 FATAL 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.

104071 ERROR 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.

104073 EMERG WARNING: A temporary communication failure has occurred between systems %s and %s. In order to avoid data corruption, data resynchronization will not occur. MANUAL INTERVENTION IS REQUIRED. In order to initiate 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.

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

Action: Perform the steps listed in the message text.

104074 FATAL Cannot get the hardware ID of device "%s"

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

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

104075 FATAL Cannot create a new disaster recovery resource instance.

Cause: In a multi-site configuration the disaster recovery resource instance could not be created.

Action: Check for errors in the LifeKeeper log and system log.

104076 FATAL Failed to create dependency between %s and %s

Cause: In a multi-site create, creation of the dependency between the netraid resource and the disrec resource failed.

Action: Check for errors in the LifeKeeper log.

104081 FATAL 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.

104082 FATAL %s

Cause: 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.

104084 FATAL Failed to create dependency between %s and %s

Cause: In a multi-site create, creation of the dependency between the file system and netraid resource failed.

Action: Check for errors in the LifeKeeper log.

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 a precaution to prevent accidental data corruption. The mirror cannot be restored on this server until the file is removed.

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

104087 ERROR The mirror "%s" (resource: "%s") is not in sync between systems "%s" (source) and "%s" (target) (status: %s). You will not be able to failover the resource to the target system listed above. You will have to bring the resource in-service on another system first and a resync will occur to ensure data reliability

Cause: When the mirror was being taken out of service it was not in-sync. Since there is data on the source that is not on the target(s), DataKeeper will prevent the mirror from coming in-service on any node other than the last node (previous source) that had the mirror in-service.

Action: Bring the mirror in-service on the previous source and let the mirror synchronize.

104088 ERROR Unextending resource "%s" while the mirror "%s" is out of sync. The data on the target partition may be corrupted

Cause: The data_corrupt flag file on the target indicates the data on the target is not synchronized with the source.

Action: Verify the data on the target is valid before using it.

104089 ERROR Deleting resource "%s" while target "%s" is out of sync. The data on the target partition may be corrupted

Cause: The data_corrupt flag file on the target indicates the data on the target is not synchronized with the source.

Action: Verify the data on the target is valid before using it.

104091 ERROR Another nbd-client process is running for nbd%s (pid %s). This process will be terminated.

Cause: When adding a target to a mirror the nbd-client process was already running. The unexpected process will be terminated and a new process started.

Action: None

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.

104094 ERROR Unable to start the resynchronization to system "%s" for mirror "%s" (resource: "%s"). Please check /proc/mdstat, the system logs, and LifeKeeper logs for error messages

Cause: DataKeeper was unable to establish connection to the target listed.

Action: Check /proc/mdstat, the system logs, and LifeKeeper logs for error messages.

104097 ERROR Unable to stop/remove the mirror "%s" (resource: "%s") on system "%s". You can use the "mdadm —stop" command to manually stop the mirror

Cause: The mirror failed to stop.

Action: Check the system logs and LifeKeeper logs for error messages. Use fuser(1) to find processes that may be using the device and check that no file system is mounted on the mirror. To manually stop the mirror run “mdadm —stop /dev/md<#> where <#> is the mirror in the error message.”

104099 ERROR Unable to unextend the mirror for resource "%s" from system "%s"

Cause: The hierarchy unextend operation failed.

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

104101 ERROR Failed to set the resynchronization speed limit in %s.

Cause: DataKeeper was unable to update the speed limit in the /proc filesystem.

Action: Check that the /proc entry listed in the message exists and check the system log for errors.

104102 ERROR Failed to set the resynchronization speed limit in %s.

Cause: DataKeeper was unable to update the speed limit in the /proc filesystem.

Action: Check that the /proc entry listed in the message exists and check the system log for errors.

104105 ERROR Internal error in DR scripts has sent the wrong flag into SetBitmap. This is a non-fatal internal error. Please report immediately to support@us.sios.com enclosing copies of the LifeKeeper log.

Cause: The only flags allowed to SetBitmap are ‘dirty’ and ‘clean’. These are internal settings that should always be correct.

Action: Report this error to SIOS support.

104106 ERROR remote ‘bitmap -m’ command failed on $target->{‘sys’}: $ranges

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

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

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 the disk has not changed.

104110 ERROR Unable to create the mirror "%s" on system "%s"

Cause: The mirror was unable to be built during the resource creation process.

Action: Check system logs and LifeKeeper logs.

104111 FATAL Insufficient input parameters for "%s" creation

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

104112 FATAL Insufficient input parameters for "%s" creation

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

104113 FATAL Insufficient input parameters for "%s" creation

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

104114 FATAL Insufficient input parameters for "%s" creation

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

104115 FATAL Insufficient input parameters for "%s" creation

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

104116 FATAL The requested filesystem type "%s" is not supported by LifeKeeper LifeKeeper supported filesystem types are listed under "\$LKROOT/lkadm/subsys/gen/filesys/supported_fs"

Cause: The file system type selected is not supported by this version of LifeKeeper.

Action: Select a file system from the list of supported file systems.

104117 FATAL Insufficient input parameters for "%s" creation

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

104118 FATAL 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 the filesystem.

104119 FATAL Invalid data replication resource type requested ("%s")

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

104124 EMERG WARNING: A temporary communication failure has occurred between systems %s and %s. In order to avoid data corruption, data resynchronization will not occur. MANUAL INTERVENTION IS REQUIRED. In order to initiate data resynchronization, you should take one of the following resources out of service: %s on %s or %s on %s. The resource that is taken out of service will become the mirror target.

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

Action: Perform the steps listed in the message text.

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 $_);

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

104127 FATAL Cannot mount "%s" on "%s"

Cause: After successfully creating a new mirror, the file system could not be mounted on the new mirror device.

Action: Check the status of the mirror, that the mount point exists with no other file system mounted, system logs and LifeKeeper logs.

104128 FATAL comm path/server not specified

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

Action: Report this error to SIOS support.

104129 WARN

Cause: The replication connection for the mirror is down.

Action: Check the network.

104130 ERROR Mirror resize failed on %s (%s). You must successfully complete this operation before using the mirror. Please try again.

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

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

104136 ERROR 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.

104144 ERROR Unable to stop the mirror access for $self->{‘md’} on system $self->{‘sys’}. Error: $ret. Use the \"mdadm —stop $self->{‘md’}\" command to manually stop the mirror.

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

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

104145 WARN Unable to dirty full bitmap. Setting fullsync flag.

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

Action: None

104156 WARN Resynchronization of "%s" is in PENDING state. Current sync_action is: "%s"

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

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

104157 WARN /etc/sysconfig/raid-check update failed. Please %s \"md%d\" to SKIP_DEVS.

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

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

104158 EMERG WARNING: The local disk partition $self->{‘part’} for data replication device\n$self->{‘md’} has failed. MANUAL INTERVENTION IS REQUIRED.

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

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

104163 WARN The "%s_data_corrupt" flag is set in "%s/subsys/scsi/resources/netraid/" on system "%s". The mirror is being forced online.

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

Action: None

104164 ERROR The "%s_data_corrupt" flag for related mirror resource "%s" is set in "%s/subsys/scsi/resources/netraid/" on system "%s". To avoid data corruption, LifeKeeper will not restore this mirror or any related mirrors in the hierarchy.

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

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

104165 ERROR The "%s_data_corrupt" flag for related mirror resource "%s" is set in "%s/subsys/scsi/resources/netraid/" on system "%s". The mirror resource "%s" is being forced online.

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

Action: None

104170 ERROR Failed to create \"source\" flag file on shared source %s to track mirror source. This may result in a full resync.

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

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

104171 ERROR Failed to create \"source\" flag file on %s to track mirror source. Target %s will not be added to mirror.

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

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

104172 ERROR The \"source\" flag file on %s does not contain a valid target (%s). Full resync to remaining targets is required.

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

Action: Report this problem to SIOS support.

104173 ERROR Failed to create \"source\" flag file on %s to track mirror source.

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

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

104174 ERROR Failed to create \"previous_source\" flag file to track time waiting on source. Will not be able to timeout.

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

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

104175 ERROR Failed to create "data_corrupt" flag file on target "%s".

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

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

104176 ERROR The \"source\" flag file on %s to track mirror source does not exist. Full resync is required.

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

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

104177 ERROR Failed to determine amount of time waiting on %s.

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

Action: none

104178 ERROR Failed to update "source" flag file on target "%s", previous source must be merged first.

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

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

104180 ERROR Internal Error: \"previous_source\" has the local system name (%s).

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

Action: Report this error to SIOS support.

104181 ERROR Internal Error: There are no targets waiting on %s to be merged.

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

Action: Report this error to SIOS support.

104182 ERROR Failed to create \"source\" flag file on %s to track mirror source. This may result in a full resync.

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

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

104186 ERROR Failed to create \"last_owner\" flag file on %s to track mirror source. This may allow in-service of mirror on old data.

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

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

104187 WARN $REM_MACH has ${REM_TAG}_last_owner file, create flag ${FLAGTAG}_data_corrupt.

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

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

104188 WARN $REM_MACH is not alive, create flag ${FLAGTAG}_data_corrupt.

Cause: The system listed is not alive.

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

104200 EMERG Continue to wait for %s to merge bitmap and do partial resyncs to all targets, no timeout set.

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

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

104201 EMERG To stop waiting for the previous source (forcing a full resync to remaining waiting targets) run: \"%s/bin/mirror_action %s fullresync %s %s\" on %s.

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

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

104202 EMERG Continue to wait for %s to merge bitmap and do partial resyncs to all targets. Continue to wait %d more seconds.

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

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

104203 EMERG To stop waiting for the previous source (forcing a full resync to remaining waiting targets) run: \"%s/bin/mirror_action %s fullresync %s %s\" on %s.

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

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

104207 ERROR Failed to create "data_corrupt" flag file on "%s".

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

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

104208 ERROR Failed to create "data_corrupt" flag file on target "%s".

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

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

104209 ERROR Failed to create "data_corrupt" flag file on "%s".

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

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

104210 ERROR Failed to create "data_corrupt" flag file on target "%s".

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

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

104211 ERROR Failed to create "data_corrupt" flag file on target "%s".

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

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

104212 ERROR The \"source\" flag file on %s to track mirror source does not exist. Full resync to remaining targets is required.

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

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

104214 ERROR Failed to create \"source\" flag file on %s to track mirror source.

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

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

104216 ERROR Failed to create "data_corrupt" flag file on target "%s".

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

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

104217 ERROR Failed to create \"source\" flag file on shared source %s to track mirror source. This may result in a full resync.

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

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

104218 ERROR Failed to create "data_corrupt" flag file on target "%s".

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

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

104221 ERROR Failed to create \"last_owner\" flag file on %s to track mirror source. This may allow in-service of mirror on old data.

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

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

104222 ERROR Failed to create "last_owner" flag file to track mirror source". This may allow in-service of mirror on old data.

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

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

104223 ERROR Failed to create "last_owner" flag file to track mirror source". This may allow in-service of mirror on old data.

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

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

104224 ERROR Failed to create \"previous_source\" flag file.

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

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

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

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.

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

122010 ERROR The listener user does not exist on the server %s.

Cause: "Stat" command could not get user id.

Action: Retry the operation.

122011 ERROR 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 the operation.

122012 ERROR 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.

122023 ERROR The %s command failed (%d)

Cause: 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 or equal to the time needed to start the listener.

122041 ERROR 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" on server "%s"

Cause: Failed to get resource information.

Action: Check your LifeKeeper configuration.

122046 ERROR Usage error

Cause: Invalid parameters were specified for the restore operation.

Action: Verify the parameters and retry the operation.

122049 ERROR The script $cmd has hung on remove of \"$opt_t\". Forcibly terminating.

Cause: The listener remove script reached its timeout 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" on server "%s"

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

Action: Check your LifeKeeper configuration.

122055 ERROR 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" on server "%s"

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

Action: Check your LifeKeeper configuration.

122064 WARN The %s level is set to %s a %s will not occur.

Cause: The minimal Listener protection level is Start and Monitor.

Action: Start the listener manually.

122066 ERROR 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 or equal to the time needed to check the listener.

122067 ERROR Usage error

Cause: Invalid parameters were specified for the quickCheck 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.

122072 ERROR %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.

122074 WARN The local recovery attempt has failed but %s level is set to %s preventing a failover to another node in the cluster. With %s recovery set all local recovery failures will exit successfully to prevent resource failovers.

Cause: The optional listener recovery level is set to local recovery only.

Action: Switch over the resource tree manually.

122078 ERROR 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.

122082 ERROR Error getting resource information for resource "%s" on server "%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 the canextend operation.

Action: Verify the parameters and retry the operation.

122086 ERROR The values specified for the target and the template servers are the same. Please specify the correct values for the target and template servers.

Cause: The values specified for the target and the template servers are the same.

Action: Perform the steps listed in the message text.

122087 ERROR Error getting resource information for resource "%s" on server "%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" on server "%s"

Cause: Failed to get listener user name from resource information.

Action: Ensure the resource info field is valid then retry the operation.

122089 ERROR 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 and retry the operation.

122090 ERROR 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.

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

Cause: Group ID should be same on both servers.

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" on server "%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" on server "%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 the operation.

122103 ERROR Usage: %s %s

Cause: Invalid parameters were specified for the create operation.

Action: Verify the parameters and retry the operation.

122124 ERROR 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</