Logs in TA

You can use the Logs pane to view and print a history of Error, Audit, Warning and Diagnostic messages that were generated by TA . These messages are part of normal TA operations but diagnostic messages are logged only when troubleshooting.

If there are a lot of logging messages, it may take a long time to load them when this window is selected. If there are more than 10,000 messages in the Logs pane, a dialog with these message displays when the window displays: There are <number> log messages for the current production day. It is recommended that you enable Server Side Filtering and redefine your selection criteria. Would you like to display the Log Filter dialog now?

It is recommended that you select the Yes option and filter the log messages from the Server Side to download and display only the messages that you are interested in. If you do not use the Server Side filter with the log messages, all of the log messages are downloaded and it may take a long time to display these messages. For more information on filtering the logs, refer to the Log Filter Dialog.

With each message, TA includes a message source to help you determine where the error occurred. The possible sources are:

  • Clients

  • Masters

  • Agent Manager

  • Fault Tolerance

  • Dependency Manager

  • Job Manager

  • Action Manager

  • Queue Manager

  • Users

  • Fault Tolerance

  • Client Manager

  • Compiler

  • Database

  • Communication

Error Messages

Error messages all concern a failure or abnormal operation of some kind. Origins include agent problems, fault tolerance components, and actions that were not executed. An Error message gives you information that helps you determine where to look to resolve the error. By default, error messages appear in red text but this color can be modified in the Preferences dialog.

Audit Messages

Audit messages generally relate routine details of TA operations. Operating system errors are the exception, and are included under TA audit messages. By default, Audit messages appear in green text but this color can be modified in the Preferences dialog.

Audit messages fall into these categories:

  • Master – Records all accounts of when the Master started and stopped.

  • Purging – Records all accounts of when job occurrences and audit messages are purged from the database.

  • Production Schedule – Records all accounts of when jobs change status, and of when the production schedule is recreated.

  • User Actions – Records when TA items are added or edited, such as jobs, job groups, job events, job actions, etc. Impersonate User activities are also logged.

  • Operator Actions – Records job control performed on job occurrences in the production schedule.

  • Fault Tolerance – Records activities of the fault tolerance mechanism when installed.

Audit messages include:

  • Master status

  • Purging of old jobs from the production schedule

  • Purging of audit, error, and diagnostic messages

  • Production date turnover

  • Job occurrence status change

  • Add, edit and delete actions from different TA panes

  • Job control performed by a user or through an action

  • Normal fault tolerance activities

  • System error messages

Warning Messages

Warning messages are generated by conditions that can lead to potential problems. They are precautionary alerts to a user to investigate a condition before it becomes a problem. Warning messages always appear in the log in gray text because their color cannot be configured.

Diagnostic Messages

Diagnostic messages are used for internal debugging purposes as a tool for better analysis of product code. Diagnostics for the various system components that comprise TA are configured from the Logging tab of the System Configuration dialog. The level of diagnostic logging detail can be configured for each individual component. While the default diagnostic setting is Severe, the settings range from None to High Debug. The higher settings should only be used under the supervision of Support personnel. The amount of information collected on the higher settings can consume large volumes of disk space on your machine.

The default location for diagnostic logs on a Windows Master machine is C:\Program Files\Tidal\Scheduler\Master\logs.

The default location for diagnostic logs on a Unix Master machine is: opt/Tidal/Master/logs.

Selecting the Client Diagnostics option on the Logging tab will collect diagnostic information on the connection socket between the Master and the TA Client.

Other information about the TA Client is collected from the Poll Activity pane in the Master Status pane. Right-clicking in this pane and selecting the Client Debug option enables the TA Client diagnostic logging that gathers information into a file in the Master directory called sadiags.txt.