Troubleshooting Audit Logging
On this page
As of the time of this publication, strict mode is available and licensed only as part of the SingleStoreDB Premium edition.
You may encounter problems with the audit logging feature during initial configuration, log file rotation, or general use.
When SingleStoreDB is unable to write log entries for any reason, it will retry the operation every 10 seconds for 30 attempts.
If you specify any invalid configuration value in your memsql.
To fix a configuration problem, review your memsql.
The most common audit logging error you may encounter is a failure to write an entry in the audit log.
This error writes the following message in the affected node’s tracelog:
Failed to write audit log record., followed by a more detailed message of the cause.
If your destination directory runs out of available disk space, SingleStoreDB will be unable to write new log files.
The specified destination directory may not be accessible for many reasons.
If your destination directory’s permissions are misconfigured, SingleStoreDB will not be able to write log files.
Either specify a new destination directory that has sufficient permissions, or change the permissions on your current destination directory.
If your destination directory doesn’t exist or was removed, SingleStoreDB will not be able to write log files.
This problem may also be the root cause of more specific log file errors. Ensure that the destination directory actually exists.
If your destination directory is located on a network share and the node loses network connectivity, SingleStoreDB will not be able to write log files.
This condition usually resolves itself when network access is restored. If a node reconnects to the cluster but the destination directory is still inaccessible, you may need to restart the node.
Last modified: April 3, 2023