Difference between revisions of "Log File Locations"
(→Setup) |
|||
| Line 6: | Line 6: | ||
=Truxton.msi= | =Truxton.msi= | ||
| − | When the setup executable spawns the <code>Truxton.msi</code>, it will tell Windows to write log messages to the user's [https://en.wikipedia.org/wiki/Environment_variable#LOCALAPPDATA local app data] <code>Low</code> folder. | + | When the setup executable spawns the <code>Truxton.msi</code>, it will tell Windows to write log messages to a file named <code>TruxtonInstall.log</code> in the user's [https://en.wikipedia.org/wiki/Environment_variable#LOCALAPPDATA local app data] <code>Low</code> folder. |
Easiest way to get there is to paste <code>%localappdata%Low</code> into the [https://en.wikipedia.org/wiki/File_Explorer File Explorer] path control. | Easiest way to get there is to paste <code>%localappdata%Low</code> into the [https://en.wikipedia.org/wiki/File_Explorer File Explorer] path control. | ||
The reason why it is written here is because the [https://en.wikipedia.org/wiki/Windows_Installer Windows Installer] will have permission to write to this folder. | The reason why it is written here is because the [https://en.wikipedia.org/wiki/Windows_Installer Windows Installer] will have permission to write to this folder. | ||
Latest revision as of 09:38, 25 July 2022
Truxton logs things in different places for different reasons.
Contents
Setup
When the user runs Truxton_Installer.exe a file will be created in the C:\ProgramData\Truxton\Setup folder.
The name of the file will begin with TruxtonSetup_ followed by a timestamp and an extension of .log
C:\ProgramData\Truxton\Setup is a folder any user can write to.
Truxton.msi
When the setup executable spawns the Truxton.msi, it will tell Windows to write log messages to a file named TruxtonInstall.log in the user's local app data Low folder.
Easiest way to get there is to paste %localappdata%Low into the File Explorer path control.
The reason why it is written here is because the Windows Installer will have permission to write to this folder.
Truxton Analyst Desktop
The analyst desktop GUI will log to local app data Probity\Truxton folder.
Easiest way to get there is to paste %localappdata%\Probity\Truxton into the File Explorer path control.
Where will be two files in this folder
Truxton Analyst.log(deprecated)TruxtonClient.log
Quick Access Chart
This is where different pieces of Truxton write log files.
| Source | Destination |
|---|---|
Truxton_Installer.exe
|
C:\ProgramData\Truxton\Setup\TruxtonSetup_*.log
|
Truxton.msi
|
%localappdata%Low\TruxtonInstall.log
|
| ETL Processes | ProgramData\Truxton\Truxton\Truxton Installation Log YYYYMMDD_HHMMSS_PIDXXXX.log
|
| Dotnet Core ETL processes | C:\Windows\System32\config\systemprofile\AppData\Local\Probity\Truxton\ETLNAME.log
|
| Analyst Desktop GUI | %localappdata%\Probity\Truxton\TruxtonClient.log
|
Other Files of Interest
Besides log files, other files can be generated when things go wrong...
Truxton Service
If you have crash dumps enabled, the Truxton service's dumps will be written to C:\Windows\System32\config\systemprofile\AppData\Local\CrashDumps\TruxtonService.exe.*.dmp
ETL Logs
Managed ETLs will default to logging to:
C:\Windows\system32\config\systemprofile\AppData\Local\Probity\Truxton
You can change this by editting the nlog.config
Change the fileName and archiveFileName attributes of the target element with the xsi:type attribute set to File.
SOLR
SOLR has its own logging at http://localhost:8983/solr/#/~logging
PostgreSQL
Postgres stores its logs in the log folder off of the database directory.
For example, if Postgres is using "D:\Truxton Data\Database" as the storage directory, the log folder will be "D:\Truxton Data\Database\log"