Difference between revisions of "Debugging the Loader"
Jump to navigation
Jump to search
(Created page with "Debugging the Truxton loader sucks. Most of the time, loads get stuck. When that happens, you must find out what is clogging the pipes. =Syslog= Use the Syslog.Server too...") |
|||
| Line 7: | Line 7: | ||
=Les= | =Les= | ||
| − | |||
Execute Les with the <code>--verbose Yes</code> command line option. | Execute Les with the <code>--verbose Yes</code> command line option. | ||
This will result is a large log file in the <code>StatusMonitorDump</code> file in <code>C:\ProgramData\Truxton\Status Monitor Dumps</code> | This will result is a large log file in the <code>StatusMonitorDump</code> file in <code>C:\ProgramData\Truxton\Status Monitor Dumps</code> | ||
Revision as of 07:04, 19 May 2020
Debugging the Truxton loader sucks. Most of the time, loads get stuck. When that happens, you must find out what is clogging the pipes.
Syslog
Use the Syslog.Server tool.
Les
Execute Les with the --verbose Yes command line option.
This will result is a large log file in the StatusMonitorDump file in C:\ProgramData\Truxton\Status Monitor Dumps
Log Files
You can use these log files to help see what happened in the system during a T1 test:
TruxtonRoot\bin\TestingSyslog.txt- This contains all of the messages logged via syslog.C:\ProgramData\Truxton\Status Monitor Dumps\XXX_DebugDump.xml- This contains the current status of all ETLsC:\ProgramData\Truxton\Status Monitor Dumps\StatusMonitorLogXXX.txt- This contains a log of everything Les was thinking.
