Insufficient Resources

The following alerts trigger when there are not enough resources for LDT operations.

• LDT-ALERT: Aborting rekey of file [FileName] due to insufficient disk space

  The key rotation process was stopped on a GuardPoint because there was not enough available disk space.

  Solution: Resize or free up space in the file system where the PathName resides. Key rotation automatically starts again when sufficient free space becomes available.

• LDT-ALERT: Failed to launch transformation on [GuardPoint]

  LDT failed to launch the data transformation process on the specified GuardPoint.

  Solution: The most common causes of this failure are:

  • Low amount of system resources, such as free disk space.

  • Check the system logs for insufficient free space in underlying file systems. You can free up space by removing older files or resizing your underlying file system. You may resize the file system on-line or off-line.

  For other issues, contact Customer Support.

• LDT-ALERT: QoS failed to start

  The Quality of Service subsystem failed to launch QoS services due to lack of system resources.

  Solution: A low amount of available memory is the most common cause of this failure.

  Contact Customer Support.

• LDT-ALERT: Skipped key rotation on GuardPoint [GuardPoint] due to insufficient disk space

• LDT-ALERT: MDS file [PathName] exceeded diskspace quota on gp [GuardPoint]

  There was not enough storage space in one or more file systems containing GuardPoints undergoing rekey.

  Solution: Check the file systems where your GuardPoints reside to see how much space it is using. Add more storage space as needed. After the condition is corrected and disk space is available, LDT operations resume automatically.

• LDT-ALERT: Low space on guard point [GuardPoint], increase free space or LDT will be suspended.

  Available storage space in the file system containing the GuardPoint is nearing the threshold below which LDT rekeying cannot continue. If available space does drop below that threshold, rekeying will be automatically suspended.

  Solution: Check the file system where your GuardPoint resides to see how much space is available. Make more free space available if necessary. After the condition is corrected and storage space is available, rekeying resumes automatically.