Summary

The maximum allowed log file size before log rotation is 2GB, but you want to allow a higher limit.

Issue

There is a maximum size limit of 2GB for audit log files in BoKS Manager when setting max allowed log file size before log rotation.

Resolution / Workaround

Install the hotfix HFBM-0036 from the HelpSystems Community Portal.

The hotfix functions as follows:

The limit is still in effect, but now if max size and threshhold size are both set to 0 (logadm -M 0 -T 0), this is interpreted as no limit,

i.e. log rotation must be performed using logadm -nf in a cron script or similar. Files larger than 4GB are now supported, but

there are still OS limitations on file size depending on file system used.

The code has also been modified so that if the log directory and backup log directory are on the same device, log rollover is performed by renaming the existing log file instead of copying it, speeding up the rollover process.

NOTE 1: You may have to set

RLIMIT_HARD_FSIZE=unlimited

RLIMIT_FSIZE=unlimited

in the ENV file to avoid process limits affecting logging.

NOTE 2: For a log file (LOG) larger than 2 GB, "bkslog -f LOG" will work, but just "bkslog" will not (bkslog -f LOG reads the file directly, while just bkslog will read via the master process, and the API used cannot handle large files).

NOTE 3: When files are larger than 4GB, viewing logs in FCC will not work.

NOTE 4: "boks_bru -p -l" to include log files in the backup will not work when the log files are very large. The old (deprecated) GUI used this when backing up the database. This is now changed NOT to include log files when backing up the database from the old GUI.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 25, 2018