The Replication Server records status and error messages, including internal errors, in the Replication Server error log file. Use the admin log_name command to display the path to the current log file. The default name for the log file is repserver.log. You can change the default name by executing repserver with the -E option and specifying the new log file name.
Refer to Chapter 3 “Replication Server Commands” of the Replication Server Reference Manual, for more information about these commands.
Internal errors are those where the only action available to Replication Server is to dump the stack and exit. For diagnostic purposes, Replication Server prints a trace of its execution stack in the log and leaves a record of its state when the error occurred.
Messages continue to accumulate in the error log files until you remove them. For this reason, you may choose to truncate the log files when the Replication Server is shut down. You can also close the Replication Server log file and begin a new log file by using the admin set_log_name command.
The Replication Server log file contains messages generated during the execution of asynchronous commands, such as create subscription and create route, which continue processing after the commands complete. While you are executing asynchronous commands, pay special attention to the log files for the Replication Servers affected by the procedure.
If a log file is unavailable, important error information is written to the standard error output file, which you can display on a terminal or redirect to a file.
