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 |
|---|---|---|---|
| 124004 | FATAL | resource tag name not specified | Cause: Invalid arguments were specified for the "quickCheck" operation. Action: Ensure that the correct arguments are passed. |
| 124005 | FATAL | resource id not specified | Cause: Invalid arguments were specified for the "quickCheck" operation. Action: Ensure that the correct arguments are passed. |
| 124007 | FATAL | Failed to get resource information | Cause: The filesystem resource's info field does not contain the correct information. Action: Put the correct information in the resource's info field or restore the system from a recent "lkbackup" to restore the original info field. |
| 124008 | ERROR | getId failed | Cause: The filesystem resource could not find the underlying disk device. Action: Check adjacent log messages for further details. Verify that the resource hierarchy is valid and that all required storage kits are installed. |
| 124009 | ERROR | LifeKeeper protected filesystem is in service but quickCheck detects the following error | Cause: The filesystem kit has found something wrong with the resource. Action: Check the messages immediately following this one for more details. |
| 124010 | ERROR | \"$id\" is not mounted | Cause: The filesystem resource is no longer mounted. Action: No action is required. Allow local recovery to remount the resource. |
| 124011 | ERROR | \"$id\" is mounted but with the incorrect mount options (current mount option list: $mntopts, expected mount option list: $infoopts | Cause: The filesystem resource is mounted incorrectly. Action: No action is required. Allow local recovery to remount the resource. |
| 124012 | ERROR | \"$id\" is mounted but on the wrong device (current mount device: $tmpdev, expected mount device: $dev | Cause: The filesystem resource has the wrong device mounted. Action: No action is required. Allow local recovery to remount the resource. |
| 124015 | ERROR | LifeKeeper protected filesystem \"$tag\" ($id) is $percent% full ($blocksfree free blocks). | Cause: The filesystem is getting full. Action: Remove or migrate data from the filesystem. |
| 124016 | WARN | LifeKeeper protected filesystem \"$tag\" ($id) is $percent% full ($blocksfree free blocks). | Cause: The filesystem is getting full. Action: Remove or migrate data from the filesystem. |
| 124020 | FATAL | cannot find device information for filesystem $id | Cause: The filesystem resource could not find the underlying disk device. Action: Check adjacent log messages for further details. Verify that the resource hierarchy is valid and that all required storage kits are installed. |
| 124029 | ERROR | Failed to find child resource. | Cause: The filesystem resource could not determine its underlying disk resource. Action: Ensure that the resource hierarchy is correct. |
| 124032 | FATAL | Script has hung. Exiting. | Cause: Processes had files open on a mounted filesystem that needed to be unmounted. Killing those processes has taken too long. Action: If this error continues, try to temporarily stop all software that may be using the mount point to allow it to be unmounted. If the filesystem still cannot be unmounted, contact Support. |
| 124042 | ERROR | file system $fs failed unmount; will try again | Cause: Processes had files open on a mounted filesystem that needed to be unmounted. It can take multiple attempts to clear those processes. Action: No action is required. Allow the process to continue. |
| 124046 | ERROR | file system $fsname failed unmount | Cause: A filesystem could not be unmounted. Action: If this error continues, try to temporarily stop all software that may be using the mount point to allow it to be unmounted. If the filesystem still cannot be unmounted, contact Support. |
| 124049 | ERROR | Local recovery of resource has failed (err=$err | Cause: A filesystem resource has a problem that cannot be repaired locally. Action: No action is required. Allow the resource to be failed over to another system. |
| 124051 | WARN | getId failed, try count : $cnt/$try | |
| 124052 | ERROR | \"$id\" is mounted but filesystem is shutdown state. | |
| 124054 | ERROR | Failed to change mount option from \"$old_opts\" to \"$new_opts\" for migration | |
| 124103 | ERROR | $ERRMSG Script was terminated for unknown reason | Cause: This message should not occur under normal circumstances. Action: Check adjacent log messages for further details. |
| 124104 | ERROR | $ERRMSG Required template machine name is null | Cause: Invalid arguments were specified for the canextend operation. Action: Ensure that the arguments are correct. If this error happens during normal operation, please contact Support. |
| 124105 | ERROR | $ERRMSG Required template resource tag name is null | Cause: Invalid arguments were specified for the canextend operation. Action: Ensure that the arguments are correct. If this error happens during normal operation, please contact Support. |
| 124106 | ERROR | $ERRMSG Unable to access template resource \"$TemplateTagName\ | Cause: The resource's underlying disk information cannot be determined. Action: Ensure the hierarchy is correct on the template system before extending. |
| 124107 | ERROR | $ERRMSG Resource \"$TemplateTagName\" must have one and only one device resource dependency | Cause: The resource has too many underlying devices in the hierarchy. Action: Ensure the hierarchy is correct on the template system before extending. |
| 124108 | ERROR | $ERRMSG Unable to access template resource \"$TemplateTagName\ | Cause: The resource cannot be found on the template system. Action: Ensure the hierarchy is correct on the template system before extending. |
| 124109 | ERROR | $ERRMSG Can not access canextend for scsi/$DeviceResType resources on machine \"$TargetSysName\ | Cause: The target system is missing some required components. Action: Ensure that the target system has all the correct kits installed and licensed. |
| 124110 | ERROR | $ERRMSG Either filesystem \"$TemplateLKId\" is not mounted on \"$TemplateSysName\" or filesystem is not shareable with \"$TargetSysName\ | Cause: The filesystem isn't in service on the template system or doesn't meet the requirements for extending to the target system. Action: Make sure the resource is in service on the template system and review the product documentation regarding the requirements for extending filesystems. |
| 124111 | ERROR | $ERRMSG File system type \"${FSType}\" is not supported by the kernel currently running on \"${TargetSysName}\ | Cause: The filesystem's type cannot be mounted on the target system due to lack of kernel support. Action: Ensure that the target system has all its kernel modules configured correctly before extending the resource. |
| 124112 | ERROR | must specify machine name containing primary hierarchy | Cause: Invalid arguments were specified for the creFShier operation. Action: If this error happens during normal operation, please contact Support. |
| 124113 | ERROR | must specify primary ROOT tag | Cause: Invalid arguments were specified for the creFShier operation. Action: If this error happens during normal operation, please contact Support. |
| 124114 | ERROR | must specify primary mount point | Cause: Invalid arguments were specified for the creFShier operation. Action: If this error happens during normal operation, please contact Support. |
| 124115 | ERROR | must specify primary switchback type | Cause: Invalid arguments were specified for the creFShier operation. Action: If this error happens during normal operation, please contact Support. |
| 124118 | ERROR | dep_remove failure on machine \""$PRIMACH"\" for parent \"$PRITAG\" and child \"$DEVTAG.\ | Cause: Cleanup after a dependency creation failed. Action: Check adjacent log messages for further details. |
| 124119 | ERROR | ins_remove failure on machine \""$PRIMACH"\" for \"$PRITAG.\ | Cause: Cleanup after an instance creation failed. Action: Check adjacent log messages for further details. |
| 124121 | ERROR | ins_remove failure on machine \""$PRIMACH"\ | Cause: Cleanup after a resource creation failed. Action: Check adjacent log messages for further details. |
| 124122 | ERROR | $ERRMSG Script was terminated for unknown reason | Cause: This message should not occur under normal circumstances. Action: Check adjacent log messages for further details. |
| 124123 | ERROR | $ERRMSG Required template machine name is null | Cause: Invalid arguments were specified for the depstoextend operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124124 | ERROR | $ERRMSG Required template resource tag name is null | Cause: Invalid arguments were specified for the depstoextend operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124125 | ERROR | $ERRMSG Unable to access template resource \"$TemplateTagName\ | Cause: The resource was unable to locate its underlying disk resource. Action: Ensure the hierarchy and all dependencies are correct before extending. |
| 124126 | ERROR | unextmgr failure on machine \""$PRIMACH"\ | Cause: The cleanup, after a failed resource extend operation, failed. Action: Manually clean up any remaining resources and check adjacent log messages for further details. |
| 124128 | ERROR | unextmgr failure on machine \""$PRIMACH"\" for \"$PRITAG.\ | Cause: The cleanup, after a failed resource extend operation, failed. Action: Manually clean up any remaining resources and check adjacent log messages for further details. |
| 124129 | ERROR | $ERRMSG Script was terminated for unknown reason | Cause: This message should not occur under normal circumstances. Action: Look for additional log messages for more details. |
| 124130 | ERROR | $ERRMSG Required template machine name is null | Cause: Invalid arguments were specified for the extend operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124131 | ERROR | $ERRMSG Required template resource tag name is null | Cause: Invalid arguments were specified for the extend operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124132 | ERROR | $ERRMSG Required target mount point is null | Cause: Invalid arguments were specified for the extend operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124133 | ERROR | $ERRMSG Unable to access template resource \"$TemplateTagName\ | Cause: The tag being extended doesn't exist on the template system. Action: Ensure that the hierarchy is correct on the template system before extending. |
| 124134 | ERROR | $ERRMSG Detected conflict in expected tag name \"$TargetTagName\" on target machine. | Cause: A resource already exists on the target system with the same tag as the resource being extended. Action: Recreate one of the conflicting resources with a different tag. |
| 124135 | ERROR | $ERRMSG Resource \"$TemplateTagName\" does not have required device resource dependency or unable to access this resource on template machine. | Cause: The resource or its underlying disk resource cannot be found on the template system. Action: Ensure that the hierarchy is correct on the template system before extending. |
| 124136 | ERROR | $ERRMSG Resource \"$TemplateTagName\" must have one and only one device resource dependency | Cause: The resource has multiple underlying devices in the hierarchy on the template system. Action: Ensure the hierarchy is correct before extending and that the filesystem resource only depends on a single disk resource. |
| 124137 | ERROR | $ERRMSG Can not access extend for scsi/$DeviceResType resources on machine \"$TargetSysName\ | Cause: The files required to support the given storage type aren't available on the target system. Action: Ensure that the required kits are installed on the target system and licensed. |
| 124138 | ERROR | $ERRMSG Unable to access target device resource \"$DeviceTagName\" on machine \"$TargetSysName\ | Cause: The required underlying disk resource doesn't exist on the target system. Action: Check adjacent log messages for further details and ensure that the target system is properly configured for hosting the resources being extended. |
| 124141 | ERROR | $ERRMSG Unable to find mount point \"$TemplateLKId\" mode on template machine | Cause: The details of the mount point on the template system cannot be determined. Action: Ensure that the resource is in service and accessible on the template system before extending. |
| 124142 | ERROR | $ERRMSG Unable to create or access mount point \"$TargetLKId\" on target machine | Cause: The mount point could not be created on the target system. Action: Ensure that the mount point's parent directory exists and is accessible on the target system. |
| 124143 | ERROR | $ERRMSG Two or more conflicting entries found in /etc/fstab on \"$TargetSysName\ | Cause: The device or mount point appears to be mounted more than once on the target system. Action: Ensure that the mount point is not mounted on the target system before extending. |
| 124144 | ERROR | $ERRMSG Failed to create resource instance on \"$TargetSysName\ | Cause: The resource creation on the target system failed. Action: Check adjacent log messages for further details. Make sure to check the logs on the target server. |
| 124145 | ERROR | $ERRMSG Failed to set resource instance state for \"$TargetTagName\" on \"$TargetSysName\ | Cause: The source state could not be changed to OSU on the target system. Action: Check adjacent log messages for further details. |
| 124146 | ERROR | must specify machine name containing primary hierarchy | Cause: Invalid arguments were specified for the filesyshier operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124147 | ERROR | must specify primary mount point | Cause: Invalid arguments were specified for the filesyshier operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124149 | ERROR | create file system hierarchy failure | Cause: The process of finding the resource instance failed. Action: Check adjacent log messages for further details. |
| 124150 | ERROR | create file system hierarchy failure | Cause: The system failed to read the /etc/mtab file. Action: Check adjacent log messages for further details. |
| 124152 | ERROR | create file system hierarchy failure | Cause: The underlying disk resource could not be found. Action: Check adjacent log messages for further details. |
| 124153 | ERROR | create file system hierarchy failure | Cause: Creating the filesystem resource failed. Action: Check adjacent log messages for further details. |
| 124154 | ERROR | create file system hierarchy failure | Cause: The info field for the resource could not be updated. Action: Check adjacent log messages for further details. |
| 124155 | ERROR | create file system hierarchy failure | Cause: The switchback strategy could not be set on the resource. Action: Check adjacent log messages for further details. |
| 124157 | ERROR | create file system hierarchy failure \(conflicting entries in /etc/fstab\ | Cause: The mount point could not be removed from the /etc/fstab file. Action: Check adjacent log messages for further details. |
| 124160 | ERROR | Unknown error in script filesysins, err=$err | Cause: This message should not occur under normal circumstances. Action: Check adjacent log messages for further details. |
| 124161 | ERROR | create filesys instance – existid – failure | Cause: This message should not occur under normal circumstances. Action: Check adjacent log messages for further details. |
| 124163 | ERROR | create filesys instance – ins_list – failure | Cause: Checking for an existing resource failed. Action: Check adjacent log messages for further details. |
| 124164 | ERROR | create filesys instance – newtag – failure | Cause: The system failed to generate a suggested tag for the resource. Action: If this error happens during normal operation, contact Support. |
| 124168 | ERROR | create filesys instance – ins_create – failure | Cause: The filesystem resource could not be created. Action: Check adjacent log messages for further details. |
| 124169 | ERROR | filesys instance – ins_setstate – failure | Cause: The new filesystem resource's state could not be initialized. Action: Check adjacent log messages for further details. |
| 124173 | ERROR | create filesys instance – dep_create – failure | Cause: The resource's dependency relationship with its underlying disk could not be created. Action: Check adjacent log messages for further details. |
| 124174 | ERROR | machine not specified | Cause: Invalid arguments were specified for the rmenu_mp operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124175 | ERROR | mount point not specified | Cause: Invalid arguments were specified for the rmenu_mp operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124177 | ERROR | unexpected multiple matches found | Cause: One or more systems show a filesystem or mount point used more than once. Action: Verify filesystem devices and mount points and ensure that filesystems are only mounted once. Look for additional log messages for more details. |
| 124178 | ERROR | machine name not specified | Cause: Invalid arguments were specified for the rmenump operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124180 | ERROR | must specify filesystem type | Cause: Invalid arguments were specified for the validfstype operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124181 | ERROR | mount point not specified | Cause: Invalid arguments were specified for the validmp operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124182 | ERROR | The mount point $MP is not an absolute path | Cause: A mount point was specified that isn't an absolute path (doesn't start with a '/'). Action: Specify a mount point as an absolute path starting with a '/'. |
| 124183 | ERROR | $MP is already mounted on $MACH | Cause: The requested mount point is already in use on the system. Action: Specify a mount point that isn't in use or unmount it before retrying the operation. |
| 124184 | ERROR | The mount point $MP is already protected by LifeKeeper on $MACH | Cause: The system is already protecting the specified mount point. Action: Choose a different mount point that isn't already being protected. |
| 124185 | ERROR | The mount point $MP is not a directory on $MACH | Cause: The mount point refers to a non-directory such as a regular file. Action: Choose a mount point that refers to a directory. |
| 124186 | ERROR | The mount point directory $MP is not empty on $MACH | Cause: The specified mount point refers to a directory that isn't empty. Action: Choose a mount point that is empty or remove the contents of the specified directory before retrying the operation. |
| 124187 | ERROR | server name not specified | Cause: Invalid arguments were specified for the valuepmp operation. Action: Ensure the script is called correctly. If this error happens during normal operation, please contact Support. |
| 124188 | ERROR | There are no mount points on server $MACH | Cause: There are no possible mount points for filesystem resource on the server. Action: Check adjacent log messages for further details. |
| 124194 | WARN | Please correct conflicting \"/etc/fstab\" entries on server $UNAME for: $FSDEV, $FSNAME | Cause: After deleting a filesystem resource, some entries in /etc/fstab need to me manually cleaned up. Action: Manually clean up the /etc/fstab file. |
| 124195 | ERROR | getchildinfo found no $OKAPP child for $PTAG | Cause: The system could not find a child resource in the hierarchy. Action: Check adjacent log messages for further details and ensure that the hierarchy is correct before retrying the operation. |
| 124196 | ERROR | enablequotas – quotacheck may have failed for $FS_NAME | Cause: The quota operation failed. Action: Check adjacent log messages for further details in both the lifekeeper log and in /var/log/messages. |
| 124198 | ERROR | enablequotas – quotaon failed to turn on quotas for $FS_NAME, reason | Cause: The quota operation failed. Action: Check adjacent log messages for further details in both the lifekeeper log and /var/log/messages. |
| 124200 | ERROR | The device node $dev was not found or did not appear in the udev create time limit of $delay seconds | Cause: A device node (/dev/…) was not created by udev. This may indicate an issue with the storage or the server's connection to the storage. Action: Check adjacent log messages for further details in both the lifekeeper log and in /var/log/messages. |
| 124201 | WARN | Device $device not found. Will retry wait to see if it appears. | Cause: This can happen under normal conditions while udev creates device node entries for storage. This message should not happen repeatedly. Action: Check adjacent log messages for further details in both the lifekeeper log and in /var/log/messages. |
| 124202 | ERROR | Command \"$commandwithargs\" failed. Retrying …. | Cause: The given command failed but may have failed temporarily. This failure may happen during normal operations but should not keep failing. Action: Check adjacent log messages for further details if this message continues. |
| 124204 | WARN | cannot make file system $FSNAME mount point | Cause: The mount point directory could not be created. Action: Ensure that the mount point can be created. This may be due to filesystem permissions, mount options, etc. |
| 124207 | ERROR | \"fsck\"ing file system $FSNAME failed, trying alternative superblock | Cause: This message indicates that the typical filesystem check failed. This message may be ok for ext2 filesystems or other filesystems where an alternative superblock location is used. Action: Check adjacent log messages for further details. |
| 124209 | ERROR | \"fsck\"ing file system $FSNAME with alternative superblock failed | Cause: This indicates that an ext2 filesystem (or other filesystem where an alternative superblock location is used) check failed with the alternative superblock location. Action: Check adjacent log messages for further details and instructions on how to proceed. |
| 124210 | WARN | POSSIBLE FILESYSTEM CORRUPTION ON $FSNAME ($FPNAME | Cause: A filesystem was put in service or failed over when it was out of sync with its mirror source. Action: Check adjacent log messages for further details and review the product documentation for information on how to bring the filesystem in service safely. |
| 124211 | ERROR | Reason for fsck failure ($retval): $ret | Cause: This log message is part of a series of messages and gives the actual exit code from the fsck process. Action: Check adjacent log messages for further details and instructions on how to proceed. |
| 124212 | ERROR | \"fsck\" of file system $FSNAME failed | Cause: The check of the filesystem failed. This is usually due to the filesystem having corruption. Action: Check adjacent log messages for further details. Review the product documentation for instructions on how to handle possible filesystem corruption. |
| 124213 | WARN | POSSIBLE FILESYSTEM CORRUPTION ON $FSNAME ($FPNAME | Cause: The system or user tried to bring into service a filesystem that may be corrupted. This can happen if a filesystem is switched or failed over when it was out of sync with its mirror source. Action: Check adjacent log messages for further details and review the product documentation for instructions on how to bring the resource into service safely. |
| 124214 | ERROR | Reason for fsck failure ($retval) | Cause: This message should follow a previous log message about a filesystem check failure and gives the process exit code of the fsck process. Action: Check adjacent log messages for further details. |
| 124218 | ERROR | File system $FSNAME was found to be already | Cause: This message is part of a series of messages. Action: Check adjacent log messages for further details. |
| 124219 | ERROR | mounted after initial mount attempt failed. | Cause: This message is part of a series of messages. This should not happen under normal circumstances but may not be fatal if the resource can be put in service. Action: Check adjacent log messages for further details in both the lifekeeper log and in /var/log/messages. |
| 124220 | ERROR | File system $FSNAME failed to mount. | Cause: The filesystem could not be mounted. Action: Check adjacent log messages for further details. |
| 124221 | WARN | Protected Filesystem $ID is full | Cause: The filesystem is full. Action: Remove unused data from the filesystem or migrate to a larger filesystem. |
| 124222 | WARN | Dependent Applications may be affected <> | Cause: This indicates that an operation on a resource is likely to cause operation on other resources based on the resource hierarchy. Action: Make sure it's acceptable for the indicated resources to be affected before continuing. |
| 124223 | ERROR | Put \"$t\" Out-Of-Service Failed By Signal | Cause: This message should not occur under normal circumstances. Action: Check adjacent log messages for further details. |
| 124227 | ERROR | Put \"$i\" Out-Of-Service Failed | Cause: The operation failed. Action: Check adjacent log messages for further details. |
| 124230 | ERROR | Put \"$t\" In-Service Failed By Signal | Cause: This message should not occur under normal circumstances. Action: Check adjacent log messages for further details. |
| 124231 | ERROR | Put \"$t\" In-Service Failed | Cause: The operation failed. Action: Check adjacent log messages for further details. |
| 124234 | ERROR | Put \"$t\" In-Service Failed | Cause: The operation failed. Action: Check adjacent log messages for further details. |
Post your comment on this topic.