Rss Categories


Reference Number: AA-01902 Views: 3913 0 Rating/ Voters

Introduced in the 12.0 version of LumenVox, a new configuration file allows users to configure the way that log files are generated and managed.

The following settings can be controlled via the logs.conf file, located in the config directory of the Windows LumenVox installation folder. By default, this location is C:\Program Files\Lumenvox\Engine\config\.

In Linux, edit the logs.conf file in /etc/lumenvox/.


This section contains global configuration settings for LumenVox log settings

Added in 12.0.100


Description: This value defines the maximum size after which a log file will be backed up (if enabled) and a new log file started.

Possible Values: A minimum size of 1000000 (1 MB) is imposed on this setting, attempting to select a value lower than this will result in 1 MB being used. There is no defined maximum value for this setting.

Default: 30000000 (30 MB)

Added in 12.0.100


Description: This is the number of backup files that are rotated through once a log file passes MAX_LOG_FILE_SIZE. Backup files will be named after the associated log file, with a numeric suffix and .backup, for example the first backup file for media_server_app.txt will be media_server_app.0.backup

Possible Values: 0 - 50

Default: 1

Added in 12.0.100


Description: When this option is enabled (1) log files will be created in a directory tree containing the date, allowing separation of logs based on the date they are associated with.

Possible values:

  • 0 (expanded path disabled)
  • 1 (expanded path enabled)

Default: 0

Added in 12.0.100


Description: Minimum free disk space (MB) required before logs are written out to disk.

Possible values: >=0

Note: Introduced in version 12.2.100 was the option of setting this to a value of 0 to disable this minimum disk space checking altogether

Default: 100

Moving Log Folders

We are often asked whether it is possible to move the location of LumenVox folders used to store log files and response files, etc. and whether there are some configuration settings that could be used to redirect these files to another drive with more space for example.

The easiest way to manage this is to set up symlinks where necessary, which maintains the original folder structure, however the actual locations of some of the folders may be on other drives for example.

There are several online articles including The Complete Guild to Creating Symbolic Links that describe this process in detail, for both Windows and Linux environments.

Basically, you would create symbolic links for your Logs folder (Log Files) and also the responses folder (Response Files), or other LumenVox folders you would like to relocate.

You should not need to restart the services when making these changes, however during the changes, files and folders may become unavailable for a time, so it might be better to schedule such an update using a scheduled maintenance window and restart the services afterwards, just to confirm everything is being written to where you expect.

By using this approach, the LumenVox processes are unaware of any change in the folder structure, so things continue operating as normal, including some of the housekeeping functionality that can be used to clean up and manage these files.