When you create a Director or server, you can specify the name of the trace file to be used for that server. During tracing, all calls made by the client application to the Director or server are logged in the trace file.
To start tracing server activity, on the Realtime View tab right-click a Director or server and select Start Trace. To stop writing trace activity to the trace file, right-click a Director or server and select Stop Trace.
To simplify troubleshooting, trace files are segmented into 200 megabyte files with numeric identifiers appended to each file’s extension. For example, when a trace file named trace.trc reaches 200 megabytes, it is renamed to trace.trc0001 and logging continues in trace.trc. When trace.trc again reaches 200 megabytes, the file is renamed to trace.trc0002, and so on.
To view a trace file
-
On either the Realtime View or Service Directory tab, right-click a Director or server and select View Trace File. (If a trace has not been started, the trace file may not yet exist.) The trace file viewer opens, as shown in the figure below.
Note: For servers on Linux systems, you must have the appropriate permissions to be able to view or manipulate the trace file.Figure 1. Trace File
If a trace file has been segmented, only the most recent trace data is displayed. You cannot view the data stored in segmented files (.xxx0001, .xxx0002, and so on) through the Director System Manager.
Note: Refer to Interpreting Trace Files for information on interpreting the information in trace files. -
To save a copy of the trace file, click Save Local. You can then open the saved file using the editor of your choice, which can be helpful when searching trace files for specific information.
-
To open a previously saved copy of a trace file, click Open Local.
-
To reload the trace file, click the Reload icon.
-
To close the trace file, click Close.
To change trace files, use the Properties window, as described in Viewing and Modifying Server Properties.