Configuring Scout Server log
For the Scout Server log file eluxd.log the Scout Server creates more than one backup (Log rotation). Once a new eluxd.log is created, the previous version is saved to the file eluxd.log.1, while the old eluxd.log.1 is saved to eluxd.log.2 and so on.
The log files continue recording when the server is restarted. The creation of a new log file is triggered by the following parameters:
- log file size
- maximum number of log files
You are free to configure both thresholds by yourself.
In addition, you may modify the location of the server log file and the keep alive log file (by default in %PUBLIC%\Documents\UniCon\Scout\Server). Specify any local directory for them, but no network directory.
Modifying log rotation and location
In the file system, in %PUBLIC%\Documents\UniCon\Scout\Server, open the eluxd.ini file for editing.
To modify the rotation parameters, add the following entries:
Section Entry Default Description [ELUXD] MaxLogFileSizeMB 100 Maximum size of a log file in MB [ELUXD] MaxLogFiles 10 Maximum number of log files (eluxd.log plus backups)
To modify the log file location, add the following entry:
Section Entry Example Description [ELUXD] LogFileLocation c:\log Local directory to be used for the log files eluxd.log and keepAlive.log
Specify a local directory to which the Scout Server can write. Do not use the UNC (Uniform Naming Convention) format.
After the Scout service has restarted, the log files are written to the specified directory.
If the Scout service cannot access the directory, it cannot start and creates an entry in the Windows Event Viewer. If the Scout service is running but cannot write the log file, it creates an alert message in the Scout Console.