Understanding log files in EngageOne Vault

Vault 5.4, 5.5, 5.6, 6.0,6.1, 7.0, 7.1, 7.2, 7.3 and 7.4.  All Platforms
EngageOne Vault installations will have at least one e2loaderd, e2serverd, and e2renderd log file.

Versions of Vault older than 5.4 used a different naming convention for the log files. This article is not applicable to Vault 4.0, 5.0, 5.1, 5.2, or 5.3 although conceptually the idea of the logs is the same.

Optionally, the Vault may have multiple instances of these, along with e2routerd for load balancing.  In that case, there will also be an e2routerd log

In very rare instances user might be using e2util in standalone mode to compress document runs. In that case, there will also be an  e2util log

The user running the Service Client binary (uclient) on the Windows platform will also have a uclient log

Each log file will follow the naming convention below:

ModuleName.YYYYMMDD.HHMMSS.ThousandthsOfSeconds.log  where

ModuleName = the name of the module being logged
ThousandthsOfSeconds = subdivision of time in thousandths of a second

for example:


is the log file for the e2loaderd module, which started on March 18th 2013 at 9:15AM

Log File Locations: By default, the log files for e2loaderd and e2serverd will be located in the <vault install path>/server/log directory.  e2renderd logs will be located in the e2renderd directory, in a subdirectory called log.  e2routerd will likewise store its logs in e2routerd/log

e2loaderd log: The e2loaderd log will contain all information pertaining to the loading of documents.

e2routerd / e2renderd log: The e2routerd / e2renderd log will contain information regarding document requests and responses

e2serverd log: The e2serverd log will contain information regarding server responses to requests

All logs will log error messages, along with the date and time of their occurrence.
UPDATED:  June 16, 2020