Logfile Name Caching

Beginning with v9.4.0, if you are integrating with the BeyondInsight for Unix & Linux, you can enable the caching of logfile names. The logfile names, creation/access time, and run host association are saved in SQLite databases for better console experience and functionality.

enablelogcaching

  • Version 10.3.0 and earlier: enablelogcaching setting not available.
  • Version 10.3.1 and later: enablelogcaching setting available.

When set to yes, log file name caching is enabled and the Privilege Management for Unix and Linux services refer to logcachedb and iologcachedb settings keywords for the appropriate database paths. Set to no to disable log file name caching feature. Default value is yes (if commented out or omitted from the settings file).

logcachedb

  • Version 9.3 and earlier: logcachedb setting not available.
  • Version 9.4 and later: logcachedb setting available, with the following behavior:

This setting holds the absolute path of the SQLite database file which stores information on the event log and I/O log file pathnames on the log host. If the database file does not yet exist, it is created when the first row is inserted.

If this setting does not exist in the pb.settings file, it disables the log file name caching feature.

  • Version 10.3.1 and later: logcachedb setting available, with the following behavior:

Starting in v10.3.1, this setting holds the absolute path of the SQLite database file which stores information only on Privilege Management for Unix and Linux event log file pathnames on the log host. If the database file does not yet exist, it is created when the first row is inserted.

Commenting out this setting does not disable log file name caching feature. To enable/ disable log file name caching feature, use the enablelogcaching setting.

logcachedb /var/log/pblogcache.db
logcachedb /opt/<prefix>pbul<suffix>/dbs/pblogcache.db

Log hosts

logcachedb_delay

  • Version 9.4.0 and earlier: logcachedb_delay setting not available.
  • Version 9.4.1 and later: logcachedb_delay setting available.

Maximum accumulated time in milliseconds that the log host busy handler sleeps during the retry cycles when it encounters a locked logcachedb database. If not specified, the default value is 100,000 milliseconds. The valid range is 0 - 1,200,000 milliseconds. A 0 value means no retries are attempted and a database locked error is logged immediately. Increase the value if there is a high demand on updating the log file name caching database and there are too many database locked errors reported. A higher value, however, may affect the performance of the log host.

SQLite may decide not to invoke the busy handler if it determines the possibility of a deadlock.

logcachedb_delay   200000
logcachedb_delay   10000

Log hosts

iologcachedb

  • Version 10.3.0 and earlier: iologcachedb setting not available.
  • Version 10.3.1 and later: iologcachedb setting available.

This setting holds the absolute path of the SQLite database file which stores information only on Privilege Management for Unix and Linux I/O log file pathnames on the log host. If the database file does not yet exist, it is created when the first row is inserted.

Commenting out this setting does not disable the log file name caching feature. To enable/ disable the log file name caching feature, use the enablelogcaching setting.

iologcachedb /var/log/pbiologcache.db
iologcachedb /opt/<prefix>pbul<suffix>/dbs/pbiologcache.db

Log hosts

iologcachedb_delay

  • Version 10.3.0 and earlier: iologcachedb_delay setting not available.
  • Version 10.3.1 and later: iologcachedb_delay setting available.

Maximum accumulated time in milliseconds that the log host busy handler sleeps during the retry cycles when it encounters a locked iologcachedb database. If not specified, the default value is 100,000 milliseconds. The valid range is 0 - 1,200,000 milliseconds. A 0 value means no retries are attempted and a database locked error is logged immediately. Increase the value if there is a high demand on updating the log file name caching database and there are too many database locked errors reported. A higher value, however, may affect the performance of the log host.

SQLite may decide not to invoke the busy handler if it determines the possibility of a deadlock.

iologcachedb_delay 20000
iologcachedb_delay 10000

Log hosts