Note: This article applies to adTempus 5 and later. For adTempus 5, see article K00000417.
Summary
adTempus produces diagnostic logs that can be used by Arcana Development support staff to diagnose problems.
Log Location
Separate log files are created for the adTempus service and the adTempus Console.
adTempus Service
Log files for the adTempus service are found in
[program files directory]\Arcana Development\adTempus\Instances\[InstanceName]\logs\
For example,
C:\Program Files\Arcana Development\adTempus\Instances\Default\logs
The current log file is named "adtempus.service.log". Previous log files are named "adtempus.service.log.1" through "adtempus.service.log.9". Each time the adTempus service is restarted, or if the log file reaches 10MB in size, a new log file is started.
adTempus Console
Log files for the adTempus Console are found in the user's TEMP directory ("%TEMP%").
The current log file is named "adtempus.console.log". Previous log files are named "adtempus.console.log.1" through "adtempus.console.log.9". Each time the adTempus Console is restarted, or if the log file reaches 10MB in size, a new log file is started.
adTempus Job Host
The Job Host process hosts execution for scripts and some other operations. Log files for the host process are found in the TEMP directory of the user whose account the job is running under. The log file is named "adtempus.jobhost.nnnn.log", where nnnn is the Windows Process ID (PID) of the instance of the host process. Old log files are periodically deleted automatically.
Log Contents
During normal operation, adTempus writes to the log files only when potential problems are detected during adTempus operations. Generally such issues are also reported to the user, through error messages or alerts in the Console. The diagnostic log files contain additional details that can be used to trace the cause of the problem.
Enabling Full Diagnostic Logging
When attempting to diagnose a problem it is sometimes necessary to have adTempus log more extensive information to the logs. Follow the instructions below to do this when instructed to do so by support personnel.
Please ZIP any log files sent to Arcana Development.
Important: When you ZIP the log files, be sure that the current log file ("adtempus.service.debug.log") is included. Some ZIP utilities will not include this file because it is in use. If this happens, make a copy of the file and add the copy to the ZIP.
To configure logging, run the "adtloggingconfig.exe" program.
- To configure logging for the Console, run this program from the folder "C:\Program Files\Arcana Development\adTempus\5.0\Console"
- To configure logging for the Service or Job Host, run this program from the program folder for the appropriate instance: "C:\Program Files\Arcana Development\adTempus\instances\InstanceName\bin" (where the InstanceName is generally "Default")
In the adtloggingconfig tool, check the Enable debug logging option for the adTempus service, Console, and/or Job Host, as appropriate.
Click OK to save the changes and close the tool. adTempus will now begin writing a second set of log files.
- For the adTempus service, the files are named "adtempus.service.debug.log", "adtempus.service.debug.log.1", etc.
- For the adTempus Console, the files are named "adtempus.console.debug.log", "adtempus.console.debug.log.1", etc.
- For the job host, the files are named "adtempus.jobhost.nnnn.debug.log.
To turn off logging when it is no longer required, uncheck the Enable debug logging option, then click OK to save changes and close the tool.
Changes take effect immediately and do not require a restart of the adTempus service or Console.
