Log files are system output files that can help diagnose or track warnings, issues, and problems with the applications. The following provide insight as to what a log file might include. Each log file should be analyzed and treated individually.
LocSvc.log - Reports networking/NIC issues.
DataSvcsSvc.log - Reports problems mainly related to job scheduling of Data Service policies. For example, warnings at startup, no active Vaults, a Vault is not yet registered, or no found jobs to run. When a Vault does start, Data Services Service picks up its jobs to run.
Vault.log - Contains errors, warnings, or informational messages from the VaultSvc. Normally, for every start message you should see a stop message. If there is another start message immediately following the first start message, then the VaultSvc was not properly stopped in its previous run. “CYA” messages are informational messages for Phoenix DEM. There is no loss of data, only a warning that the database had to be rebuilt/re-indexed.
Purge When 80Pct Full.log - Log entries report a summary of the Data Service Job (Purge When 80Pct Full) running. Every Data Service policy that runs produces this file with job information. If there are any errors or warnings, it also creates an “.err” version of the same file.