| Error message |
Cause |
Appropriate action |
| snaplock.log.mdata.IOerr
|
This event is generated when there is a SnapLock logging metadata I/O error. The SnapLock logging system will not function until this condition is corrected.
|
SnapLock log file I/O errors can be a result of a full volume or a corrupted log file. Check that there is enough disk space to satisfy logging requirements. If a corrupt file is suspected, archive the log with the snaplock log archive
command or change the log volume with the snaplock log volume
command. |
| snaplock.log.IO.error
|
This event is generated when there is a SnapLock log file I/O error. The SnapLock logging system will not function until this condition is corrected.
|
SnapLock log file I/O errors can be a result of a full volume or a corrupted log file. Check that there is enough disk space to satisfy logging requirements. If a corrupt file is suspected, archive the log with the snaplock log archive
command or change the log volume with the snaplock log volume command. |
| snaplock.user |
This event is generated when the SnapLock logging system fails to log the addition or deletion of a compliance user to or from the compliance group. The actual operation might have succeeded. This event only applies when there is a failure to securely log the request.
|
No corrective action is necessary. However, a secure log of the request might not exist, and you should check the SnapLock log volume for correct operation. |
