Novell DATA SYNCHRONIZER, Руководство администратора

Страница: 26 / 50

26 Novell Data Synchronizer Administration Guide
n
ov
do
cx (e
n)
16
Ap
ril 20
10
Use the following command to check the most recent additions to a log file:
tail -f log_file_name .log
Three of the Synchronizer log files are automatically compressed and are rotated when they reach 4
MB in size. After 99 files have accumulated, the oldest log file is deleted when a new log file is
created. Log rotation is controlled by the following files:
/etc/logrotate.d/datasync-syncengine
/etc/logrotate.d/datasync-configengine
/etc/logrotate.d/webadmin
For more information, see the Linux
logrotate
(http://linux.about.com/od/commands/l/
blcmdl8_logrota.htm) command.
3.4.2 Sync Engine Log File
The Sync Engine log file (
engine.log
) reports on events that pass through the Sync Engine as they
transfer from connector to connector. It logs problems with the physical connection to each
connector and with communication between connectors. It also logs problems with the event XML
files.
3.4.3 Config Engine Log File
The Config Engine log file (
configengine.log
) reports on configuration setting changes made in
Synchronizer Web Admin and on any effects of those changes on the connections between the Sync
Engine and connectors. It also logs issues with starting and stopping connectors and tracks the poll
cycle for changes in LDAP groups.
3.4.4 Web Admin Log File
The Web Admin log file (
server.log
) reports problems with the Synchronizer Web Admin
interface. Typically, you would not see problems here unless you edited the XML source for one of
the Configuration pages and introduced invalid XML. If a Configuration page does not display
correctly after you edit the XML source, you can check this log file for help resolving the problem
with the XML.
3.4.5 Connector Manager Log File
The Connector Manager log file (
connectorManager.log
) reports problems with loading a
connector with the configuration provided on the connector’s Configuration page.
The Connector Manager starts one Python thread for itself and an additional Python thread for each
connector that it manages. When you list Connector Manager threads or Python threads in a terminal
window, you cannot tell which Python thread is associated with the Connector Manager and which
Python thread is associated with each connector. The Connector Manager log file lists each
component and the PID number associated with each one. This can be very useful for
troubleshooting.