This configuration variable applies only to the thin client automatic update feature. If the automatic update process fails for any reason, a log file may be created on the server. This file contains a log of the update operations and details about the failure. The TC_SERVER_LOG_FILE configuration variable can be used to configure the location and name of that log file. The name can optionally include the hostname of the client machine and the process ID of the server runtime that was managing the automatic update at the time of the failure.
By default, this file is named autoupdate.%c.%p.log, where %c is replaced by the client hostname and %p is replaced by the process ID of the server runtime. The default location is the working directory specified in the alias on the server. Note that the directory must exist at the time of the failure for the log file to be created.
The location of the log file is relative to the working directory specified in the alias. For example, the following setting:
TC_SERVER_LOG_FILE updatefailed/%c.%p.log
configures the log files to be created in a directory named updatefailed relative to the working directory. The default location is the working directory specified in the alias on the server. The files are named with the hostname of the client followed by a dot and the process ID of the server runtime, ending with the .log file extension.
The client and server may be in different time zones. You can look at the file's creation date to see what time the update failed according to the clock on the server, and view the timestamps at the beginning of the lines in the log file to see what time it failed according to the clock on the client.